SAP ABAP Data Element CCRCE_FLG_INIT (Initial Run)
Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   EHS-SAF (Application Component) Product Safety
     CBRC (Package) EHS: Substance-Related Regulation Checks
Basic Data
Data Element CCRCE_FLG_INIT
Short Description Initial Run  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type ESDBOOLE    
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 Initial 
Medium 20 Initial Run 
Long 30 Initial Run 
Heading 30 Initial Run 
Documentation

Definition

Causes the report to be started as an initial run.

Use

  • If you set this indicator when you start the report RREGCH_VT or in a variant for background processing of this report, the system uses the start date and end date entered for data selection.

    All logistics documents that are new or have been changed between the start date and end date are read and tracked in the initial run. The start and end date do not correspond with the date on which the document was posted. If the dates were to correspond to the actual posting or validity date the documents could be booked twice or not booked at all.

    To track all documents for a time period, you must extend the time period into the past and future so that all postings relevant for the time period are taken into consideration.
    The validity date used for substance volume tracking is the posting date for confirmed quantities. For planned quantities the date depends on the scenario, for example, the delivery date. For example, if a purchase order item is changed within the specified period, it is written to the monitoring tables with the delivery date and thereby assigned to the period and year of the delivery date for tracking purposes. The start and end dates of successful runs of substance volume tracking are saved in table CCRCT_RUN per regulation and scenario. If the entered date values overlap with the date values of runs that have already taken place, substance volume tracking does not run. Multiple tracking of confirmed substance quantities for the same period would lead to inconsistent data.

    If the end date is the same as the current date, the current time minus 30 minutes is used as the end time point. This is to avoid problems that could be caused by material documents created during the run overlapping.
    The 30-minute time difference can be changed using environment parameter SVT_TRACKING_DIFF_TIME. The value defines the time allowed between determining the change time-point for the material document and the database commit for the material document. The material is not tracked, if the difference between these two time-points is greater than the specified time difference.

  • If you set this indicator when you start the report RREGCH_FILL or in a variant for background processing of this report, the system uses the material and material category entered for data selection. Asterisks (*) are supported as placeholders.

Dependencies

Example

History
Last changed by/on SAP  20100310 
SAP Release Created in 46C