SAP ABAP Data Element /SAPSLL/ICON_STICM (Technical Incompleteness of Document)
Hierarchy
☛
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation
⤷ SLL-LEG (Application Component) Global Trade Services
⤷ /SAPSLL/CORE_LEGAL (Package) Legal Services: Core Functions
⤷ SLL-LEG (Application Component) Global Trade Services
⤷ /SAPSLL/CORE_LEGAL (Package) Legal Services: Core Functions
Basic Data
Data Element | /SAPSLL/ICON_STICM |
Short Description | Technical Incompleteness of Document |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SYCHAR132 | |
Data Type | CHAR | Character String |
Length | 132 | |
Decimal Places | 0 | |
Output Length | 132 | |
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 | Tech.Incom |
Medium | 15 | Tech. Incompl. |
Long | 25 | Technically Incomplete |
Heading | 30 | Technically Incomplete |
Documentation
Definition
The status of the technical incompleteness check provides information to the user as to whether the data is complete from the process perspective. A document that is technically incomplete can still be used to supply data for advance declarations or customs declarations from the "Declaration prior to goods receipt" worklist.
A document is considered technically complete when the following fields are filled in:
- Sea/air waybill number
- Flight or journey number
- Number of packages
- Place of loading
- Place of unloading
- Loading date
- Planned arrival date
- Carrier
- Consignor
- Seller
Use
Dependencies
Example
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 900 |