SAP ABAP IMG Activity SIMG_CFMENUOM00OM20 (Define Strategies for Adopting Calculation Proposals)
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_CFMENUOM00OM20 Define Strategies for Adopting Calculation Proposals  
Transaction Code S_ALR_87005461   IMG Activity: SIMG_CFMENUOM00OM20 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOM00OM20   Define Strategies for Copying Calculation Proposals 
Customizing Activity SIMG_CFMENUOM00OM20   Define Strategies for Adopting Calculation Proposals 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOM00OM20    

In this step, you define strategies for the adoption of proposals from the automatic kanban calculation.

Adding Kanbans

If the system has added new kanbans as a result of the automatic kanban calculation, you must make the following settings:

  • Unlocking Sequence

    If the control cycle involved has locked kanbans, these are unlocked first. In the event that not all locked kanbans are unlocked, it is necessary to specify which kanbans are to be unlocked first:

    • Kanbans with a low status (each status has a number: FULL = 5, EMPTY = 2, WAITING = 1 etc.)
      • With this setting, the remaining kanbans acquire the satus WAITING more quickly. As a result, kanbans that are no longer needed are withdrawn from circulation more quickly.
    • Kanbans with a low item number
      • With this setting, preference is given to keeping kanbans with a high item number locked. These are then deleted first. This setting contributes towards maintaining a cohesive number range.
  • Number Assignment for New Kanbans

    When new kanbans are added to the control cycle, you must decide whether:

    • The item numbers are to be assigned consecutively as of existing number levels, or
    • Any gaps that have arisen due to the deletion of kanbans, for example, are to be closed first

Removing Kanbans

If kanbans are removed as a result of the automatic kanban calculation, you must make the following settings:

  • Sequence for Locking Kanbans

    If the affected control cycle has kanbans with the initial status WAITING, these can be deleted first (check the Delete Kanbans mit Initial Status First box to do this). Kanbans with other statuses are locked. You must specify which kanbans are to be locked first:

    • Kanbans with high status (each status has a number: FULL = 5, EMPTY = 2, WAITING = 1 etc.)

      If kanbans with a high status are locked first, kanbans that are not needed are withdrawn from circulation as quickly as possible.

    • Kanbans with high item number

      If kanbans with a high item number are locked first, this contributes towards maintaining a cohesive number range.

  • Lock Kanbans with Initial Status First

    With this setting, you specify whether kanbans with the status WAITING are to be deleted first, before other kanbans are locked.

    If you first delete the kanbans with the status WAITING, you achieve a quicker implementation of the change proposals through the kanban calculation.

    If you decide against the deletion of the kanbans with the status WAITING, the kanban number range remains gap-free.

  • Delete Locked Kanbans

    As a rule, kanbans are not deleted from a control cycle immediately. Instead they are first locked, then run through the remaining status sequence up to the next setting to empty, and are then set to the initial status WAITING by the system. After this, they can be deleted.

    With this setting, you decide whether locked kanbans are to be deleted as well when the proposals are next adopted, without running through the remaining status sequence.

Example

Requirements

Standard settings

Recommendation

Activities

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_CFMENUOM00OM20 0 HLA0006761 Control Cycle - KANBAN 
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_TPKBU V - View SM30 Strategies for the Adoption of Calculation Proposals 
History
Last changed by/on SAP  20090901 
SAP Release Created in