Kontakt

Ansicht
Dokumentation

KPE_VC_PPESTATUS_PLM - Define Status

KPE_VC_PPESTATUS_PLM - Define Status

ABAP Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

In this section, you define which iPPE objects are subject to status management. In status management, you define certain states that an object must reach before the next business processes can begin. You can shape the status management for each object individually.

You define a status in the following way:

  1. In the SAP Reference IMG, choose Cross-Application Components -> Integrated Product and Process Engineering -> General Settings -> Define Settings for Status Management.
The screen Change View "Status IDs": Overview appears.
  1. Select New Entries.
  2. Enter a key and a description for the status and save your entries.
  3. Select the status and choose Status Values.
The screen Change View "Status Values": Overview appears.
  1. Select New Entries.
  2. Enter the keys, meanings, and if required, icons and descriptions for the values that your status can have.
  3. Choose Status Preconditions if you wish to define preconditions.
  4. Select New Entries.
  5. Enter a key and a description for each precondition and state whether it must be fulfilled or not.
  6. Select Status Object Types.
  7. State the iPPE objects to which this status is to apply.
  8. Select Status Predecessors if your status builds on other statuses that must be fulfilled first.
  9. Enter the preceding status and state whether it has to be fulfilled.
  10. Save your entries.

If you create a status for an assembly item or component variant that is assigned above the superior node of a product class, the system always creates the same number of status graphs as the number of classes that exist in the associated product class hierarchy.

For example, node C1 has the class CL1 (of class type 300). Class C1 is assigned two subclasses, CL11 and CL12, in the class hierarchy. For variant V1 of the node C1, the system then assigns three status graphs for the classes CL1, CL12, and CL13.

Status 0001 (released for construction) for component variants:

Status 0001 can have the following values: 001 for initial and 002 for successful. This shows that a component variant is either released or not released for construction.

The precondition 001 (DMU data available) must be fulfilled before the status 0001 can be set to 002 (successful). You can specify whether this precondition must be fulfilled (cannot be overridden) or may be fulfilled (can be overriden with warning). In the latter case, the status can achieve the value 'successful' even if the precondition has not been fulfilled.

Status 0001 is valid for component variants (S_CSMPST), and is automatically used for all component variants created in the system.

If the component variants have to reach various different statuses and be released, you can state whether the status has preceding statuses that must be fulfilled.






BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3464 Date: 20240523 Time: 202818     sap01-206 ( 57 ms )