Hierarchy
BBPCRM (Software Component) BBPCRM⤷
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_REFEREN |
| Short Description | Reference Module |
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 | 8 | Ref. |
| Medium | 16 | Reference Module |
| Long | 16 | Reference Module |
| Heading | 8 | Ref. |
Documentation
Definition
The external data module guarantees referenced integration of external data. This is most relevant when calling a document in the change mode. The reference-integrated data are updated when a changing call is executed.
The referenced integration of external data via a reference module is only guaranteed if the option Reference is activated external data integration before generating the dialog application detail screen for the element list with the appropriate documentation element.
With the function modules named with the Default module, a reference module also regularly requires a Get- and/or GetRef module and a Flush module. A Save- (and/or SaveRef-)module is then only required, if the external data module is also a Change module or if the references are not saved in the document master file or in the generated document table. If this is the case, then it will be necessary to set up a Reference table via the Data Dictionary.
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in |
