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_TRACK_SCENARIOS | Specify Scenarios |
| Transaction Code | S_SH1_20000006 | IMG Activity: CBRC_TRACK_SCENARIOS |
| Created on | 20051006 | |
| Customizing Attributes | CBRC_TRACK_SCENARIOS | Specify Scenarios for Volume Tracking Dependent on Regulations |
| Customizing Activity | CBRC_TRACK_SCENARIOS | Specify Scenarios for Volume Tracking Dependent on Regulations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CBRC_TRACK_SCENARIOS |
Use
In this Customizing activity, you specify how the system determines data for the individual scenarios and regulations and how it executes further process steps.
Requirements
Standard settings
Activities
"Assign Scenarios to Scenario Categories" Activity
In Customizing for Substance Volume Tracking, you can specify scenarios or scenario categories for your settings in many places. The settings then apply only for the specified scenario or scenario category. This allows you to make different settings for different scenarios or scenario categories, and thus specify that, for example, purchased quantities are determined from different data than produced or sold quantities.
"Specify Data Determination per Regulation and Scenario" Activity
If you use the CBRC_LIB_TRACK_SUBST_GET function for component explosion, you can use the User Exit field to specify a user exit. For example, you can specify a user exit that stops the explosion of the composition at a specific item.
The value in the Exit Parameter field is passed as a parameter value to the user exit function, where it can be evaluated. You must first create the user exit in the Customizing activity Manage User Exits and specify a function module. The user exit must have user exit type SUB_EX_GCT. Use reference function module C1F2_EXIT_GET_COMP_TREE as a copy template for customer-specific checking functions.
If you use the CBRC_TSC_LIB_TRACK_SUBST_GET function for component explosion, the two fields User Exit and Exit Parameter are ignored.
If you want to filter out of certain specifications from substance volume tracking, the following fields must be filled with values: Value Assignment Type for Filtering Out Specifications, Characteristic for Filtering Out Specifications, and Characteristic for Regulatory List for Filtering Specifications. The default values are:
- Value Assignment Type for Filtering Out Specifications: SAP_EHS_1023_012
- Characteristic for Filtering Out Specifications: SAP_EHS_1023_012_INFO
- Characteristic for Regulatory List for Filtering Specifications: SAP_EHS_1023_012_BASE
Use these values if you want to use the value assignment types or characteristics for filtering out specifications in the standard system. If you want to use other values, specify these.
The filter is limited to substances to be tracked (lowest expanded level of the composition) and to a corresponding regulatory list.
Note that for filtering out specifications, the same phrase key must be assigned to the environment parameter Filtering Out Specifications (SVT_PHR_SPEEXCL_REG) in the Customizing activity Specify Environment Parameters as is used in assigning values in the characteristic for filtering out specifications. The corresponding value assignment instance must match the rating and validity area that are specified for the Value Assignment Type 1.
The value in the Value Assignment Type 1 or Value Assignment Type 2 field defines the value assignment type of the composition from which the components to be monitored are determined. If you use bill of materials (BOM) transfer into EH&S, check whether you need to enter the same value assignment type or a different value assignment type than for the BOM transfer.
The rating and the validity period determine which value assignment instances are transferred from the EH&S data to the logistics system. The value assignment instances to be transferred are selected according to the following rules:
- The rating must match.
- The validity period of the value assignment instance must include the validity period in Customizing. In other words, all countries in the validity period in Customizing must also be in the set of countries in the validity period of the value assignment instance.
- The value assignment instance must be active.
This Customizing activity also controls whether the compositions are filled according to scenario or independently of scenario in the logistics tables of volume tracking. If a function module is entered separately for substance determination for the material and for the component explosion in an entry without a specified scenario, the components are filled independently of scenario. Otherwise, they are filled according to scenario. In the standard system, various scenarios and function modules are available.
In the Data Transfer: Polymer/Monomer selection field, you can specify for each scenario and regulation which components of a specification labeled as a polymer are to be transferred to the EHS: Composition (EH&S Data) (CCRCT_EHS_COMP) table using the Substance Volume Tracking: Data Transfer from Property Tree program.
If you configure different data transfer settings for polymers and monomers for each scenario, you also have to specify the data transfer from the property tree for each scenario. To do this, you enter the function modules for each scenario in the selection fields Function for Determining the Substances for the Material and Function for Exploding the Components. If the function modules for a scenario are not maintained, this scenario-independent entry is transferred to the table.
If you specify a value for a scenario in the Data Transfer: Polymer/Monomer selection field, you also have to configure further settings for the corresponding regulatory list in the Customizing activity Specify Polymer Labeling and Monomer Composition for Each Regulation.
Note
You can make customer-specific adjustments to the date fields by using function module CBRC_LIB_KEY_BUILD. Use this function module as a copy template.
The scenarios PUR and IMP and the scenario SO and EXP cannot be used at the same time for the same regulation and the same materials, because otherwise the same quantities will be processed multiple times.
You can exchange the function module listed here for a customer-specific module. Use the relevant function module as a copy template.
Note the following when defining scenarios:
- You can delete scenarios that are not required.
- You must not define new scenarios.
- You must not change the assignments of scenarios and scenario categories delivered with the system.
- If you specify your own function modules, their interfaces must match those of the standard function modules.
Example
The rating in Customizing matches the rating in the value assignment instance, and the value assignment instance is active.
- The validity period in Customizing is REG_EU, the validity period in the value assignment instance is REG_WORLD. The value assignment instance is transferred.
- The validity period in Customizing is REG_EU, the validity period in the value assignment instance is DE. The value assignment instance is not transferred.
- The validity period in Customizing is US, the validity period in the value assignment instance is US. The value assignment instance is transferred.
The rating and the validity period are only read from the entry in Customizing that has no entry in the Scenario field. In other words, these values are scenario-independent and can only be defined per regulation.
For the other fields, if Customizing is read for a specific regulation and a specific scenario, the entry where both the regulation and the scenario match overrides the entry for the regulation without a scenario. However, the blank fields in the scenario-specific entry are filled with the corresponding values in the scenario-independent entry. This means that you only need to enter field values that are the same for all scenarios once, in the scenario-independent entry.
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_TRACK_SCENARIOS | 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_SCENTYPE | V - View | SM30 | Assign Scenarios to Scenario Categories | |||
| CCRCVC_DET | C - View cluster | SM34 | Specify Data Determination per Regulation and Scenario |
History
| Last changed by/on | SAP | 20100728 |
| SAP Release Created in | 46C |
