Hierarchy

⤷

⤷

Basic Data
Data Element | CNV_20306_AUFTR |
Short Description | Order management active |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CNV_20306_RKAC2 | |
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 | Orders |
Medium | 15 | Orders |
Long | 20 | Order management |
Heading | 2 | OR |
Documentation
Definition
Indicator that, together with the CO interface, controls the specific defaults for internal order management.
Use
The following values are valid:
" " - Inactive
Internal order management is inactive. Order validation does not take place. Orders cannot be used as account assignment objects for internal CO postings. For postings in FI, you can assign orders only after deactivating the corresponding warning message. The R/3 System then treats these as real postings but does not update them. Any cost center then posted accepts them as statistical postings only.
1 - Active
Internal order management is active on a limited basis. Orders are validated against the order master. They can be used as account assignment objects. In the corresponding posting transactions, the CO files are updated.
2 - Active for validations
Internal order management is inactive. Orders are validated against the order master. They can be used as account assignment objects, but are not updated in the corresponding posting transactions. Later implementation of internal order management makes follow-up posting of cost-accounting-relevant business transactions onto orders in the corresponding CO files possible.
3 - Active for existence validation
Controls as indicator 2, except that the orders are checked only for proof of existence, and not whether they are allowable for the relevant posting transaction.
History
Last changed by/on | SAP | 20141030 |
SAP Release Created in | 46C |