Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NMED (Package) R/3MED: Medical documentation GSD
Basic Data
Data Element | N2_ISAEND |
Short Description | Changing Inclusion of External Data |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 7 | Change |
Medium | 7 | Change |
Long | 20 | Changing Inclusion |
Heading | 20 | Changing Inclusion |
Documentation
Definition
External data are integrated into the current document category in a changing status.
External data can be integrated in a changing or unchanging status. A changing integration is only possible when using a Change module.
With an Unchanging integration, the value of the external data is copied at every predefinition at the time the document is created or when the command Predefine document is executed, or even when transferred by the user into the respective documentation elements. After predefinition or transferring, there is no further relation between document contents and the source data. The document contents can be modified how the user desires, and can freely be made different from the source data.
With a Changing integration, the value of the external data can be immediately transferred just like the unchanging integration is transferred. If the transferred data is changed or new data are entered for the relevant documentation elements, the new or modified data will be written back into their same tables as the external data. To insure such a changing integration of external data, a Referencing integration of external data is usually necessary, because storing the reference is also necessary for locating the data to be changed.
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in |