Hierarchy
⤷ SLL-LEG (Application Component) Global Trade Services
⤷ /SAPSLL/LEGAL_CUS_LOCALIZATION (Package) Global Trade Services: Objects w/o Third Lang. Translation
Basic Data
Data Element | /SAPSLL/ABI_RDPORT |
Short Description | ABI Receiver District/Port |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR4 | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | Rec Port |
Medium | 16 | Rec Distric Port |
Long | 20 | Rec. District/Port |
Heading | 22 | Receiver District/Port |
Documentation
Definition
ABI Receiver District/Port.
A code representing the district/port of the data processing site where the data is returned. If positions 40 43 of this record are space filled, this code also represents the sender district/port.
Both the filer and the district/port codes in the transaction control header (A) and trailer (Z) records must be the same, and they identify the data processing site of the participant (which may be a service bureau).
The relationship between the district/port and filer codes in the transaction control records (A and Z) and the district/port and filer codes in the block control records (B and Y) must be established with CBP prior to transmission of the data. ACS security verifies this information for each transmission. Therefore, a service bureau or multi port broker/importer who wishes to transmit data for a new office location must contact a CBP Client Representative prior to transmission for that location. Likewise, the CBP Client Representative must be notified if an already active participant changes from a service bureau to an independent operation, or the reverse, or changes from one service bureau to another.
Use
ABI Application Control - Record Identifier A., Z.
Dependencies
Example
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 720 |