SAP ABAP Data Element COMPE (Complete Version in Case of Externally Generated Requisition)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
MM-PUR (Application Component) Purchasing
⤷
MEDCM (Package) Purchasing: Change Management
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR (Application Component) Purchasing⤷
MEDCM (Package) Purchasing: Change Management
Basic Data
| Data Element | COMPE |
| Short Description | Complete Version in Case of Externally Generated Requisition |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Extern. OK |
| Medium | 15 | External OK |
| Long | 20 | External version OK |
| Heading | 1 | E |
Documentation
Definition
Determines whether externally generated versions of purchase requisitions (created via BAPIs, for example) are to be completed automatically.
Use
If you have selected the indicator and the requisition is created or changed externally, all versions of the requisition will automatically be marked as Completed by the system.
If you have not selected the indicator, the versions must be marked as Completed manually.
Dependencies
Not until the current version has been completed:
- Can a requisition be converted into a PO, for example
- Does the release procedure start (if applicable)
Example
History
| Last changed by/on | SAP | 20011120 |
| SAP Release Created in | 470 |
