SAP ABAP Data Element ADDIS_BAPI (Status of request for additionals IDoc via BAPI)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ LO-ADM (Application Component) Additionals Management
⤷ WTAD (Package) IS-R: Additionals
⤷ LO-ADM (Application Component) Additionals Management
⤷ WTAD (Package) IS-R: Additionals
Basic Data
Data Element | ADDIS_BAPI |
Short Description | Status of request for additionals IDoc via BAPI |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ADDIS_1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | BAPI |
Medium | 15 | BAPI request |
Long | 24 | BAPI request carried out |
Heading | 15 | BAPI request |
Documentation
Definition
Request status of an additionals IDoc as a result of a BAPI call.
Use
Possible values are:
- Empty
An additionals IDoc is not to be generated by a BAPI call.
- 1
The BAPI was not called. No additionals IDoc has therefore been created.
- 2
The BAPI was called and an additionals IDoc was generated.
Notes
The fact that an additionals IDoc is successfully generated by a BAPI call does not necessarily mean that is was successfully received by the recipient.
The actual generation of the IDoc is asynchronous. Any error messages from the ALE layer are recorded in a log.
History
Last changed by/on | SAP | 19980728 |
SAP Release Created in |