Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-LOC (Application Component) Localization⤷
ID-DMEE (Package) International Development: Data Medium Exchange Engine
Basic Data
| Data Element | DMEE_ID_VALUE |
| Short Description | DMEE: Value of Identifier |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | 10 | ID Value |
| Medium | 15 | ID Value |
| Long | 23 | Identifier Value |
| Heading | 30 | Identifier Value |
Documentation
Definition
Refers to the character string in an incoming file that the DME Engine uses to uniquely identify a data record.
Use
Each data record in an incoming DME file must contain a character string that uniquely identifies the record. The DME Engine uses this character string (identifier) to recognize the data record and assign it to the corresponding segment in the format tree.
You need to define an assignment rule for each segment of the format tree, in order to link the segment (via the identifier and segment reference ID) to a data record in the incoming file.
Dependencies
Example
The data record "005BUPA001ANDERSONCONSULTING123450000468739" is identified as a record for a business partner by means of the character string "BUPA" in position 4 through 7. For this data record, a segment is defined in the format tree with the reference ID "PARTNER", and the following assignment rule is defined:
Rule No. Identifier ID Offset Ref. ID of Tgt Segmt
Assigned by system BUPA 3 PARTNER
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 470 |
