Hierarchy
⤷ CA-GTF-CSC (Application Component) Country-Specific Objects
⤷ ID-DMEEA (Package) INTDEV: ABA services of Data Medium Exchange Engine
Basic Data
Data Element | DMEE_SEGM_REF_ID_ABA |
Short Description | DMEE: Reference ID of the Target Segment |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DMEE_REF_NAME_ABA | |
Data Type | CHAR | Character String |
Length | 12 | |
Decimal Places | 0 | |
Output Length | 12 | |
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 | Ref ID |
Medium | 20 | Ref. ID of Tgt Segmt |
Long | 30 | Reference ID of Target Segment |
Heading | 20 | Ref. ID of Tgt Segmt |
Documentation
Definition
Definition
Refers to the reference ID of the target segment in the DME Engine format tree.
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, called an identifier in the DME Engine, to recognize the data record and assign it to the corresponding segment in the format tree. The DME Engine makes this assignment using the reference ID that was defined for the particular segment.
You need to specify a reference ID for each segment of the format tree that is to be used in an assignment rule to link the segment to a data record in the incoming file.
Dependencies
Example
The data record "005BUPA001SMITHCONSULTING123450000468739" 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 | 20040312 |
SAP Release Created in | 640 |