Hierarchy
⤷ SRM-EBP (Application Component) Enterprise Buyer
⤷ BBP_APPLICATION (Package) Structure Package EBP
⤷ ME (Package) Application development R/3 Purchasing
Basic Data
Data Element | APOMS |
Short Description | APO as Planning System |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | APOMS | |
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 | EP |
Medium | 15 | Ext. Planning |
Long | 20 | External Planning |
Heading | 2 | EP |
Documentation
Definition
Determines whether delivery schedule lines created against a scheduling agreement item are planned in the standard system or in the Advanced Planner and Optimizer (APO).
Use
If you select this indicator, you cannot create any schedule lines manually in the standard system. Instead, the schedule lines are created in the APO system either manually or through the planning run.
Dependencies
You use the combination of document type and the Ext. Planning indicator to define whether the release documentation is to be displayed in the standard system or in the APO system:
- If planning, release generation, and release documentation are to occur in APO (Ext. Planning 1), use the document type LP.
- If planning, release generation and release documentation are to occur in the standard system (Ext. Planning _), use the document type LPA.
This indicator is transmitted to the APO system when the scheduling agreement is transferred from the standard system via the Core Interface (CIF).
In the case of scheduling agreements with planning and release generation in APO, you see this setting in the SA Processing Control field on the Scheduling Agreement tab page in the external procurement relationship.
The operative delivery schedules generated in the APO system are 'stored' in the standard system as delivery schedule lines.
Example
History
Last changed by/on | SAP | 20000131 |
SAP Release Created in | 46C |