Hierarchy
TDAGBCA (Software Component) TechniData Basic Components⤷
EHS (Application Component) Environment, Health and Safety⤷
/TDAG/RCS (Package) REACH Compliance - General
IMG Activity
| ID | /TDAG/RCS_INPUT_CHK | Specify Rules for Consistency Check |
| Transaction Code | /TDAG/13000049 | (empty) |
| Created on | 20110801 | |
| Customizing Attributes | /TDAG/RCS_INPUT_CHK | Specify Rules for Consistency Check |
| Customizing Activity | /TDAG/RCS_INPUT_CHK | Specify Rules for Consistency Check |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /TDAG/RCS_INPUT_CHK |
Use
In this Customizing activity, you define the rules that are used to check the consistency of your use data. You use the consistency check to make sure that use records are correct and complete based on your company requirements. This check is performed automatically when the system reads use collection data or use and exposure data.
You build rules by specifying whether the sector of end use, process category, product category, and article category are forbidden, mandatory, or optional for each combination of main user group and environmental release category.
The environmental release category must be monovalent. If you want to check the environmental release category in a multivalent constellation, you must provide a rule for each monovalent combination of the main user group and environmental release category.
Requirements
Standard settings
The standard system is delivered with consistency check rules that ensure that use data is compliant according to chapter R12 of the European Chemicals Agency (ECHA) use descriptor system as an example.
A default input check algorithm is delivered with method CK_INPUT in the default implementation of the Input Use Checks Business Add-In (BAdI). This BAdI uses the consistency check rules to check the compliance of use records.
Activities
Adapt the standard settings and the BAdI implementation, if necessary.
Example
Use record:
MUG ERC SU PROC PC AC
SU3 ERC2 SU1 - - -
Check rules:
MUG ERC SU PROC PC AC
SU3 ERC2 Forbidden Mandatory Forbidden Forbidden
SU3 ERC2 Mandatory Forbidden Forbidden Forbidden
SU3 ERC2 Forbidden Forbidden Mandatory Mandatory
Use record is consistent because it fulfils the check rule in line 2. The other check rules are ignored.
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 | /TDAG/RCS_INPUT_CHK | 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 |
| /TDAG/RCSV_INPCK | V - View | SM30 |
History
| Last changed by/on | HAUH | 20110801 |
| SAP Release Created in | 110_600 |
