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_ROFCOD |
Short Description | ABI Receiver Office Code |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR2 | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | R Off Cod |
Medium | 15 | Rec Office Code |
Long | 20 | Receiver Office Code |
Heading | 20 | Receiver Office Code |
Documentation
Definition
ABI Receiver Office Code.
A code agreed upon by the user and the CBP representing a specific user's office for output only.
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 block control header (B) and trailer (Y) records must contain the district/port and entry filer codes associated with the data contained within the block.
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 |