SAP ABAP Data Element OKSTA (Status: communication successful)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-MD-PCT (Application Component) Product Catalog
⤷ WBBC (Package) IS-R: Replenishment list
⤷ CRM-MD-PCT (Application Component) Product Catalog
⤷ WBBC (Package) IS-R: Replenishment list
Basic Data
Data Element | OKSTA |
Short Description | Status: communication successful |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EDI_STATUS | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table | TEDS1 |
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 | OK status |
Medium | 15 | Status comm. OK |
Long | 20 | Status Communic. OK |
Heading | 2 | OK |
Documentation
Definition
IDoc status indicating that communication was successful. This status should be set to the last value that can be sent as a status message to the ERP system as successful communication by the subsequent converter or the receiving POS system.
This value should not be set to '18' (EDI subsystem initiated ok) if restart is to be used in the POS data - outbound. The system can then no longer determine which of the IDocs that have already been transferred to a subsequent converter have already been processed.
History
Last changed by/on | SAP | 20010607 |
SAP Release Created in |