SAP ABAP Data Element MCL_PROTO (Indicator: Write log for RWF / picking waves?)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ VL (Package) WS-SHP: General Processing for Shipping
Basic Data
Data Element MCL_PROTO
Short Description Indicator: Write log for RWF / picking waves?  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type XFELD    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Log? 
Medium 15 Write log? 
Long 20 Write log? 
Heading 3 Log 
Documentation

Definition

This indicator specifies whether or not a log for updating the workload data for the rough workload forecast or the picking waves should be created additionally in parallel when operative documents (for example, a purchase order) are being written.

This log serves to detect incorrect settings in Customizing. The log contains messages that lead to an incorrect update of workload data or even cause the workload data not to be updated at all.

You can display and analyze the log subsequently using the Customizing function Display log.

Example

You have created a purchase order with the following item:

Material 4711 FLORA Margarine 250 gramms, Qty 5, Unit of measure: Carton

To determine the workload, a unit-of-measure load category is derived from the unit of measure to determine the workload.
If no UoM load category was assigned to the unit of measure, the load table cannot be read and therefore no workload can be determined. In this case, a respective message is entered into the log.

Note

  1. This log is ideally suited for preparing productive operation. If the function for the rough workload forecast or the picking waves are productive, the log update should no longer be active. The log should then only be used for analyzing update errors.
  2. The log update has a negative effect on the performance of the system. Also, the logs need space in the database. Therefore, the switch should only be set to active as described under 1).
  3. From time to time, you should delete logs that are no longer required in order to make space available in the database. For this purpose, use the function Delete log.

History
Last changed by/on SAP  19970910 
SAP Release Created in