SAP ABAP IMG Activity SIMG_CMMENUOLMBNAKO (Maintain Conditions)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ MB0C (Package) Customizing R/3 inventory management
IMG Activity
ID SIMG_CMMENUOLMBNAKO Maintain Conditions  
Transaction Code S_ALR_87000145   IMG Activity: SIMG_CMMENUOLMBNAKO 
Created on 19981222    
Customizing Attributes SIMG_CMMENUOLMBNAKO   Maintain Conditions 
Customizing Activity SIMG_CMMENUOLMBNAKO   Maintain Conditions 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CMMENUOLMBNAKO    

You use the condition records to assign an output type to a goods movement (for example, goods receipt for purchase order), that is, you define the conditions to be met for a certain output type.

The values to be entered for an output type depend on the access sequence defined for the output type.

Example

You define condition records for output type WA01, which is assigned to access sequence 0003 (table 072). You have to enter the following values accordingly:

  • transaction type (for example, WA for goods issue)
  • version (for example, 1 for individual slip)
  • print indicator (for example, 1 for material document printout)

For each goods movement, the system checks whether the conditions thus created are met for the output type. If so, an output of this type is created.

It is also possible to maintain the following data in the conditions:

  • time (for example, immediately upon updating)
    The time may differ from that of the output type.
  • language
    If you maintain a language in the condition, the goods receipt/issue slips will be printed in this language.
    If you do not maintain a language in the condition, the goods receipt/issue slips will be printed in the logon language. If this is not known to the system at the time of updating, they will be printed in the language defined for the plant.
  • fixed print parameters (for example, printer)
    This is not generally useful since printer determination is more flexible via plant/storage location or user.
  • fixed mail partner
    This is not generally useful since the mail partners are automatically determined by the system (for example, by the person entering the purchase order or by the MRP controller).
  • parameters for sending a mail message
    You can, for example, define whether a message is to be sent as an express mail.
  • parameters for processing a mail message
    Here, you can define a transaction that is called up automatically when the recipient processes the mail message.

    These are the possible transactions:

    • MB03 (display material document)    for GR mails
    • ME23 (display purchase order)     for GR mails
    • CO06 (backorder processing)     for missing parts messages

      When calling up these transactions, you can also transfer parameters, for example, material document number, material number, purchase order number. (See the sections Missing part message (MLFH) and Notifications of goods receipts (MLGR, MLMD, MLUD below.)

Default setting

The condition records are not maintained in the SAP Standard configuration because condition records are like master data. The condition records cannot be transported.

Recommendation

SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.

Activities

Select Material document -> Condition -> Display to check whether the condition records have been maintained for a given output type.

If this is not the case, create the following conditions:

  • goods receipt/issue slips

    OutTy    Trans.    Version    Print indicator
    WA01     WA     1     1
    WA01     WA     1     6
    WA01     WE     1     6
    WA02     WA     2     1
    WA02     WA     2     6
    WA02     WE     2     6
    WA03     WA     3     1
    WA03     WA     3     6
    WA03     WE     3     6
    WE01     WE     1     1
    WE01     WE     1     2
    WE02     WE     2     1
    WE02     WE     2     2
    WE03     WE     3     1
    WE03     WE     3     2
    WF01     WF     1     1
    WF01     WF     1     2
    WF02     WF     2     1
    WF02     WF     2     2
  • goods receipt/issue slips for materials provided to subcontractors

    OutTy    Trans.    Version    Print ind.    Debits/credits indicator
    WLB1     WA     1     3         H (= credit)
    WLB2     WA     2     3         H
    WLB3     WA     3     3         H
  • label printout
    You maintain the conditions for this output type with the same data as for goods receipt/issue slips plus the label type and label form.
  • missing parts message (MLFH)

    Create a condition with missing parts indicator = X.

    Choose Goto -> Means of Communication and then Goto -> Execution Parameter. You reach the dialog box Change Execution Parameter. Here you maintain the following data for mail processing:

    • transaction code: CO06 (backorder processing)
    • parameter CAUFVD-MATNR     Id MAT
    • parameter CAUFVD-WERKS     Id WRK
    • parameter CAUFVD-PRREG     Id PRR
  • goods receipt notifications MLGR, MLMD, and MLUD

    In each case, create a condition with GR message indicator = X.

    Only maintain a condition for output type MLUD if you want to receive a mail for underdeliveries. It is useful to work with either MLGR (mail for every goods receipt) or MLUD (mail only for underdelivery).

    Choose Goto -> Means of Communication and then Goto -> Execution Parameter. You reach the dialog box Change Execution Parameter. Here you maintain the following data for mail processing:

    • transaction code: MB03 (display material document)
    • parameter RM07M-MBLNR     Id MBN
    • parameter RM07M-MJAHR     Id MJA

      Alternatively, you can call up transaction ME23 (display purchase order):

    • transaction code: ME23 (display purchase order)
    • parameter RM06E-BSTNR     Id BES
  • kanban (WEK1)
    Create a condition with kanban indicator = 1.

Notes on transport

The condition records are like master data and therefore cannot be transported.

Business Attributes
ASAP Roadmap ID 259   Establish Forms and Messages 
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 SIMG_CMMENUOLMBNAKO 0 HLA0006045 O HLA0006047 O HLA0006048  
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
IMGDUMMY D - Dummy object MN21 1 Create Condition: Inventory Mgmt 
IMGDUMMY D - Dummy object MN22 2 Change Condition: Inventory Mgmt 
IMGDUMMY D - Dummy object MN23 3 Display Condition: Inventory Mgmt 
History
Last changed by/on SAP  19981222 
SAP Release Created in