SAP ABAP Data Element CN10_OFFSET (Time Interval (In Days) for Determining Requirements Date)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   PS-MAT (Application Component) Material
     CN_MAT (Package) Material for the project
Basic Data
Data Element CN10_OFFSET
Short Description Time Interval (In Days) for Determining Requirements Date  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type INT3    
Data Type NUMC   Character string with only digits 
Length 3    
Decimal Places 0    
Output Length 3    
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 TmInterval 
Medium 15 Offset to finsh 
Long 20 Time Interval (Days) 
Heading LSp 
Documentation

Definition

Use

You can create bill of material items as components for network activities and assign them by using the bill of material transfer (CN33). The requirement date of a new component is a result of the earliest or latest start or finish date of the activity when taking the activity-related time interval into account.

If an item is assigned to an activity whose relevant date lies in the past, requirements are created, if necessary, which are not taken into account in the planning horizon of requirements planning. To set the requirements date of new components to a realistic date, specify the time interval in days. In addition, if you set the indicator for determining the requirements date in the settings for bill of material transfer, the system calculates a realistic requirements date by adding the time interval you specified to the current date. For any new assignments, the system checks whether the requirements date for the activity is smaller than the calculated realistic date. If the check is positive, the system sets the requirements date of the component to the realistic requirements date, and flags it as a manually maintained date. The date is thereby not influenced by network scheduling.

Dependencies

Example

History
Last changed by/on SAP  20020506 
SAP Release Created in 470