Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U (Application Component) SAP Utilities⤷
EE80 (Package) IS-U: Customizing
IMG Activity
| ID | _ISUBDDL_000001 | Define Notes for Device Locations |
| Transaction Code | S_KK4_74000693 | IMG Activity: _ISUBDDL_000001 |
| Created on | 19990816 | |
| Customizing Attributes | _ISUBDDL_000001 | Define Notes for Device Locations |
| Customizing Activity | _ISUBDDL_000001 | Define Notes for Device Locations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _ISUBDDL_000001 |
In this section you maintain notes for the device location (object IFLOT).
You define notes for an entity if you wish to store information for that entity in addition to the information contained in the standard fields. After you have defined a note, a note block is proposed in the corresponding maintenance and display transactions. In this note block you can store information in SAPscript.
Fixed text objects for the entities are provided. These text objects have a fixed key, which must not be changed. In addition, a text ID for each text object is provided. You have the option of changing or deleting this text ID or of creating additional text IDs.
Example
The predefined text object EVER (entity for the contract) already has the text ID ISU general notes for the contract, which is provided by SAP. You now have the option of creating a second text ID with special agreements, e.g. ZISU special agreements. Once you have defined this setting, two note blocks will be proposed in the maintenance and display transactions.
Requirements
You must have maintained the following data:
- Define languages for the notes. Specify the languages in which notes can be created by choosing Cross-Application Components -> General Application Functions -> Notes -> Define Languages for Notes.
Standard settings
There is one table entry for each entity for which a note can be defined. To define additional note blocks you must create additional text IDs.
Recommendation
We recommend that you use the standard specifications and that, for clarity, you propose a maximum of one note block on the master data screen.
Activities
- Check whether the list of notes provided meets your requirements.
- If you wish to define additional note blocks, position the cursor on the appropriate text object and choose Text IDs.
- Choose Create.
- Define the additional note block that you require for entering additional information (e.g. Text ID = ZISU, Meaning = special agreements).
Further notes
Once a text ID is deleted, any notes already entered will no longer be displayed.
Example
Requirements
Standard settings
Recommendation
Activities
Maintain notes for the device location with the text object IFLOT.
Further notes
This text object is the same as the text object for the connection objects.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _ISUBDDL_000001 | 0 | I110004813 | Device location |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| SE75 | T - Individual transaction object | SE75 | EGPL | Define Notes for Device Locations |
History
| Last changed by/on | SAP | 20021022 |
| SAP Release Created in |
