Show TOC

Maintain Conditions

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.

In addition, you can store 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.
  

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)

• 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).

• kanban (WEK1)
  Create a condition with kanban indicator = 1.

Notes on transport

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