SAP ABAP Data Element LVS_DIRTA (Automatic TO Creation Immediately After TR Generation)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       LVS (Package) Application development Warehouse Management (WM)
Basic Data
Data Element LVS_DIRTA
Short Description Automatic TO Creation Immediately After TR Generation  
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 Immed.TO 
Medium 15 Immed.TO 
Long 20 Auto. TO Creation 
Heading  
Documentation

Definition

Indicator determining that automatic transfer order generation is active.

Automatic transfer order generation can be initiated both during the creation of the IM document as well as during material staging for production orders (PP interface).

After the IM document has been created, a transfer order for a transfer requirement or for a posting change notice is created, provided the following requirements are met:

  • Automatic transfer order generation is active (depending upon the movement type for all items of the IM document for which a transfer requirement or a posting change notice is to be created.
  • Within the entire document, the postings are executed in one warehouse number only.
  • If the current document is to created for each function module, for example, from the usage decision of QM, the automatic transfer order generation function must not be switched off. This can be the case if on the basis of the constellation in the inspection lot automatic TO generation is not appropriate (see also the documentation on the interface WM <-> QM).

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