Hierarchy
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
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_PDPORT |
| Short Description | ABI Processing District/ Port Code |
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 | Proc.Port |
| Medium | 15 | Process.Port |
| Long | 20 | Proces District/Port |
| Heading | 30 | Processing District/ Port Code |
Documentation
Definition
ABI Processing District/ Port Code.
A code representing the processing district/ port. Valid district/port codes can be queried through the Extract Reference File chapter of this document. This code also designates where (CBPs district/port location) the statement is printed and processed.
This code must be the same in Record Identifiers B and Y.
The processing district/port is the location where the entry summary package will be input into ACS. For example, if the entry (release) were made in Wilkes Barre, Pennsylvania, the entry summary would be input at Philadelphia. The Philadelphia district/port code would be shown as the processing district/port. If the processing district/port is Philadelphia, other ports within that district (e.g., Scranton, Harrisburg, and Pittsburgh) can be included in the transmission.
A separate block of records is required for input from different processing district. Subports assigned to the same district may be transmitted within the same block of data. Example: District/port in the block control record is 3801. The Block contains entry data for ports 3801, 3802, 3803, etc.
For purposes of Daily Statement processing, the processing district/port code entered in entry summary input (Application Identifier EI) and the block control header record (Record Identifier B) alerts ACS that all entry summaries within the block, regardless of the District/Port of Entry codes shown in Record Identifier 10, should be included in the Daily Statement for the district/port code shown in the "B" record.
For example, if a block of EI input contains both Detroit (district/port code 3801) and Port Huron (district/port code 3802), and 3801 is entered in the Processing District/Port Code in the block header, both the Detroit and Port Huron entry summaries will be included in the Daily Statement for Detroit.
If a separate statement for Port Huron is desired, the Port Huron entry summaries must be in a block by themselves with 3802 specified in the block control header record as the processing district/port.
Note: This is a clarification of the use of control records and represents no change to existing entry summary filing practices.
Use
ABI Application Control - Record Identifier B, Y.
Dependencies
Example
History
| Last changed by/on | SAP | 20141106 |
| SAP Release Created in | 720 |
