Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-MRP-BD (Application Component) Master Data⤷
MD0C (Package) Customizing R/3 Material Requirements Planning
IMG Activity
| ID | SIMG_CFMENUOPP1OMIU | Define Action Keys |
| Transaction Code | S_ALR_87006221 | IMG Activity: SIMG_CFMENUOPP1OMIU |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOPP1OMIU | Define Action Keys |
| Customizing Activity | SIMG_CFMENUOPP1OMIU | Define Action Keys |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOPP1OMIU |
In this IMG activity, you define the action key.
In the SAP standard system, the following actions have been implemented:
Action key Action
BOME Explode BOM
BEMA Explode BOM, check material availability
NEMA Check material availability without BOM explosion
MAAV Check mat.availability, explode BOM if necessary
RSMA Reset availability check
SCHE Schedule planned order
CPOD Change planned order
PRNT Print component list
ZZXX Customer-defined action
With the action CPOD, you can change the following data of the planned order:
- Order quantity, scrap quantity
If the order quantity in the transfer structure is not blank, then the order and scrap quantities from the transfer structure are copied to the planned order. The quantities must be specified in the base unit of measure.
- Order start date, order finish date, opening date
If these dates are not blank in the transfer structure, MDCD they are copied from the transfer structure in the planned order. The validity of the dates (for example, they correspond to the factory calendar) is checked during the online transaction.
- Production version
If the production versions are not blank in the transfer structure, they are copied from the transfer structure in the planned order. The validity of the production versions is checked during the online transaction.
- Sequence number
If the sequence number is not blank in the transfer structure MDCD, it is copied from the transfer structure in the planned order.
The sequence number is given in the production order or the planned order at header level and is valid for all the operations of the order. The sequence number is used to sort orders to be displayed in the planning table (capacity planning) and for organizing the dispatching sequence using the sort key.
Customer-defined actions
For customer-defined actions, the action code is flagged with date and time in the planned order and, if necessary, changed planned order data is transferred. A separate key must be defined for customer actions from the customer name range.
Example
Requirements
Standard settings
Recommendation
Activities
Check the action key and define customer-defined actions, if necessary.
Further notes
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOPP1OMIU | 0 | HLA0006456 | Procurement Proposal |
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_T46AS | V - View | SM30 | 1 | Action Code - Planned Order Control |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
