SAP ABAP IMG Activity SIMG_CFMENUOM00OM17 (Define Activities for Status Change)
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_CFMENUOM00OM17 Define Activities for Status Change  
Transaction Code S_ALR_87005450   IMG Activity: SIMG_CFMENUOM00OM17 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOM00OM17   Define Activities for Status Change 
Customizing Activity SIMG_CFMENUOM00OM17   Define Activities for Status Change 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOM00OM17    

In this work step, you define activities per status change for a status sequence.

This means that the following activities are defined for every status change:

  • Is the goods receipt to be carried out with the status change automatically?

    If yes, you must select the field, goods receipt for the status change.

  • Is the kanban to be printed with this status change?

    If yes, you must select the field, Kanban print for this status change.

  • Is the system to branch into a user-defined function procedure with this status change?

    If yes, select the field User exit.

    With the "user exit" the system provides a function module that contains all the relevant data for Kanban. It makes sense to use a "user exit", for example if, in Kanban, the goods withdrawal is always backflushed. If you do not want this, you can use the "user exit" to trigger a GI to cost center when the container is set to empty.

    It is also possible, to use the "user exit" to issue a message if an error occurs when changing the status.

    For each status change, the system accesses the "user exist" as the last function so that all the necessary data is available.

Use the enhancement MPKB0001 to activate the function module.

Warning

If you only want to carry out one particular function when setting the container to empty, you must take all status changes into account, that lead to status "empty".

Example

Requirements

Standard settings

Recommendation

If you use the standard Kanban procedures, you do not require any activities described above.

Activities

If necessary, define the activities described above.

Further notes

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
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_CFMENUOM00OM17 0 HLA0006762 KANBAN Control 
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
TPKAK S - Table (with text table) SM30 0000000000 Define Actions for Status Switching 
History
Last changed by/on SAP  19981222 
SAP Release Created in