Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ CIIC (Package) CIM integration: Customizing
IMG Activity
ID | PPPI_PO_212 | Define Order Type-Dependent Parameters |
Transaction Code | S_ALR_87008811 | IMG Activity: PPPI_PO_212 |
Created on | 19990126 | |
Customizing Attributes | PPPI_PO_212 | Define order type-dependent parameters |
Customizing Activity | PPPI_PO_212 | Define order type-dependent parameters |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PPPI_PO_212 |
In this step, you define the parameters that are valid for each order type and plant. The parameters are split up as follows:
- Master data
Here, you define the data that influences master data selection or order master data maintenance. The screen contains the following indicators:
- MstRecSel defines whether the process order must be used with a master recipe or can be used without a master recipe.
- The recipe selection ID defines the priorities according to which the recipe is selected.
- Application defines how the BOM alternatives are selected.
- Cost accounting
Here, you define the parameters relevant for cost accounting, such as costing variants for planned and actual costs and a results analysis key.
- General data
Here, you define the following parameters:
- Substitute MRP controller/substitute production scheduler. These are proposed when you create process orders if an MRP controller or production scheduler are not specified in the material master, or if there is no reference to material.
- CopyPlannedOrdSchedg - defines that scheduling of the planned order is trabsferred unchanged to the process order.
- PDC active - enables data exchange with a PDC system
- Workflow for PO chg. - defines that a Workflow is generated when quantities or dates are changed in the order and affect existing purchase orders. In addition, a default rule for the split is displayed on this screen.
- Status change
Here, you define whether you want change documents to be written if a status change occurs. You also define the level at which the change documents are written:
A status change document documents the following:
- which status has been changed
- who changed the status
- whether the status has been activated or deactivated
- the transaction in which the status change has been carried out
In the process order, you can define the status at the following levels:
- order header level
- operation level
- material component level
Status change documents can thus be defined independently of each other, at each of these four levels.
Note
If you have defined these parameters such that status change documents are written for a particular order level, the SAP System only writes a status change document for a status change from this point in time if the order (or operation/component) has been created since the status change documents have been activated.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PPPI_PO_212 | 0 | HLA0006252 | Process Order |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_T399X_40 | V - View | COR4 | PPPI_PO | Parameters dependent on order type |
History
Last changed by/on | SAP | 19990126 |
SAP Release Created in |