SAP ABAP IMG Activity PPPI_MD_223 (Define BOM Status)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ CIIC (Package) CIM integration: Customizing
⤷ 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_MD_223 | Define BOM Status |
Transaction Code | S_ALR_87005996 | IMG Activity: PPPI_MD_223 |
Created on | 19981222 | |
Customizing Attributes | PPPI_MD_223 | Define BOM status |
Customizing Activity | PPPI_MD_223 | Define BOM status |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PPPI_MD_223 |
Via the BOM status, you define which other application areas can use a bill of material with this status.
- In the different areas in a company (such as costing), the BOM is exploded according to the application. When you define an application for a certain area in the company, you select the status indicators in the Mininum requirements of BOM status dataset that the BOM status must have before the BOM is read for the BOM explosion.
- In MRP, the following indicators are checked directly from the definition of the BOM status:
- Explosion in MRP
- Released for orders
MRP only reads BOMs whose BOM status has at least one of these indicators.
- Exception messages are relevant to MRP only. You can allocate an exception message to a BOM status which must be checked by the MRP controller.
If a BOM whose status has an exception message allocated to it is exploded in MRP, the exception message tells the MRP controller that he may have to correct the planning result manually. In this way, you can exclude materials requiring manual correction from the total planning result.
You define exception messages in the IMG for material requirements planning.
Requirements
Before you can allocate an exception message to a BOM status, you must complete step Define and group together exception messages.
Note
Do not delete a status if bills of material with this status exist.
Actions
Define BOM statuses according to your requirements.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory 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 | PPPI_MD_223 | 0 | HLA0006271 | Master Recipe |
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_T415S | V - View | OS23 | PPPI_MD | Define BOM status |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |