SAP ABAP IMG Activity CBRC_SELECT_CRITERIA (Specify Selection Criteria for Volume Tracking)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBRC (Package) EHS: Substance-Related Regulation Checks
IMG Activity
ID CBRC_SELECT_CRITERIA Specify Selection Criteria for Volume Tracking  
Transaction Code S_SH1_20000008   IMG Activity: CBRC_SELECT_CRITERIA 
Created on 20051006    
Customizing Attributes CBRC_SELECT_CRITERIA   Specify Selection Criteria for Volume Tracking 
Customizing Activity CBRC_SELECT_CRITERIA   Specify Selection Criteria for Volume Tracking 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CBRC_SELECT_CRITERIA    

Use

In substance volume tracking, the system reads logistics data from the following tables, depending on the scenario:

Scenario    Scenario Category    Tables    Date for Planned Quantities

PUR    PURCHASE_REQUISITION    EBAN    EBAN-LFDAT: Delivery date of item

PUR    PURCHASE    EKKO, EKPO, EKET, MKPF, MSEG    EKET-EINDT: Delivery date of item

SO    SALES    VBAK, VBAP, VBEP, VBPA, VBUP    VBEP-EDATU: Schedule Line Date

SO    DELIVERY    LIKP, LIPS, VBPA, VBUP, MKPF, MSEG    LIKP-WADAT: Planned date of goods movement

IMP    PURCHASE_REQUISITION    EBAN    EBAN-LFDAT: Delivery date of item

IMP    PURCHASE    EKKO, EKPO, EKET, MKPF, MSEG    EKET-EINDT: Delivery date of item

EXP    SALES    VBAK, VBAP, VBEP, VBPA, VBUP    VBEP-EDATU: Schedule Line Date

EXP    DELIVERY    LIKP, LIPS, VBPA, VBUP, MKPF, MSEG    LIKP-WADAT: Planned date of goods movement

PRO    PRODUCTION    AUFK, AFKO, AFPO, RESB, MKPF, MSEG    AFKO-GSTRS: Scheduled start

PRO    REPET_MANUFACTURING    PLAF, RESB, MKPF, MSEG    PLAF- PSTTR: Basic start date

CON    PRODUCTION    AUFK, AFKO, AFPO, RESB, MKPF, MSEG    AFKO-GSTRS: Scheduled start

CON    REPET_MANUFACTURING    PLAF, RESB, MKPF, MSEG    PLAF- PSTTR: Basic start date

The date for planned quantities determines the monitoring period and the year to which the quantity is assigned.

For processing of confirmed quantities, the posting date in the material document (MKPF-BUDAT) is decisive for all scenarios.

Note:

For repetitive manufacturing, you cannot use Customizing to define the selection criteria for tables RESB, MKPF, and MSEG. Instead, use the function modules CBRC_PROREP_CO_DATA_READ and CBRC_PROREP_PL_DATA_READ as copy templates for customer-specific modules.

In this Customizing activity, you specify selection criteria for the data from these tables. You can thus restrict the logistics data that is monitored and specify, for example, which documents are tracked in substance volume tracking.

If you want to restrict substance volume tracking and monitoring in the online checks to specific transactions, you can use the table SYST with the field TCODE.

Note that you can considerably reduce the runtime of the program for substance volume tracking (report RREGCH_VT) by restricting your selection so that it is more selective. In particular, you can improve the runtime by filtering database tables with a large amount of transaction data (for example, tables RESB and MSEG).

During substance volume tracking of confirmed quantities, the system considers generally all material documents (table MSEG) that have a reference to logistics documents relevant for the respective scenario category. The link between the material document and the logistics document is dependent on the respective scenario category:

  • For the scenario category PRODUCTION, a reference to a production order or a process order is necessary. The link occurs between the field AUFNR (order) of the table MSEG (Document Segment: Material) and the field AUFNR (order) of the table AFKO (Header Data in PP Orders) or, for repetitive manufacturing orders, of the table AUFK (Order Master Data).
  • For the scenario category PURCHASE, a reference to a purchase order is necessary. The link occurs between the field EBELN (purchase order) and EBELP (item) of the table MSEG (Document Segment: Material) and the fields EBELN (purchase order) amd EBELP (item) of the table EKPO (Purchasing Document Item).
  • For the scenario category DELIVERY, a reference to a outbound delivery is necessary. The link occurs between the field XBLNR (reference) of the table MKPF (Header: Material Document) and the field VBELN (delivery) of the table LIKP (SD Document: Delivery Header Data).
  • There is no link to the material documents for the scenario categories PURCHASE_REQUISITION and SALES. So only planned quantities can be tracked in these scenario categories.

In order for the system to correctly determine the quantities for each scenario, you must normally define the selection criteria in a way that the system reads only the material documents and logistics documents that are relevant for the respective regulatory list. When defining the selection criteria, be especially aware that material documents possibly reference different logistics documents. For example, if a goods receipt is booked to a stock transport order, it can occur that a material document of the goods receipt also refers to the associated outbound delivery. In this case, it is possible that an insufficient definition of the selection criteria can cause the material document to be taken into account in both the scenario for sold quantities and the scenario for purchased quantities. To prevent this, you can define, for example, for each scenario a selection criterion for the transaction type (field VGART) of the material document (table MKPF).

Also, be aware during the definition of the selection criteria that an intersection of the selected data for each logistics document is generated during substance volume tracking. For example:
You want to track imported purchased quantities. You have defined only selection criteria for the table EKPO (Purchasing Document Item). If you defined the selection criteria so that no position of a purchase order is determined to be relevant, then also the intersection of the data records for the purchase order is empty. As a result, no planned or confirmed quantities are determined for the purchase order.

For more information, see SAP Note 1020462.

You use table MARA to define selection criteria for the materials to be monitored. In addition, you can classify materials as relevant to substance volume tracking in the classification view of the material master. This classification is read if you enter the standard function module CBRC_MM_REL_MATNR_FILTER under Specify Scenarios in the Material Determination field.

The options described above for selectively restricting the materials for substance volume tracking affect the transfer of data from the property tree (report RREGCH_FILL). In addition, in the standard system the data transfer program reads selection settings for table ESTRH (specification headers) from the property tree, to filter out specifications that are not relevant for material assignment. In addition, you can define the selection criteria in the table RCG_ESTRH to specifically filter out monitored substances. The fields in the table RCG_ESTRH are also available in the table ESTRH.

Use these filter options to limit the volume of data that is transferred from the property tree to the tables for substance volume tracking.

It is better to specify material-related selection criteria independently of scenario. You need to specify scenario-specific criteria if the function modules for substance determination per material and component explosion are defined per scenario in the Customizing activity Specify Scenarios.

Example

In the following example, the system evaluates only materials of the material types raw material, semifinished product, and finished product for the regulation REACH and the scenario IMP:

Reg.    Scen.    Table     Field    Sel. Option    Lower Limit

REACH    IMP    MARA    MTART    equal to    ROH

REACH    IMP    MARA    MTART    equal to    HALB

REACH    IMP    MARA    MTART    equal to    FERT

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG CBRC_SELECT_CRITERIA 0 HLA0100681 Product Safety 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
CCRCV_FILTER V - View SM30  
History
Last changed by/on SAP  20051117 
SAP Release Created in 46C