GENERALITIES
| WP1 |
Specification | A Specification is an object that exists in the EHS module. Each of these objects serve a purpose and is defined by a certain codification. It can be
|
Property tree | The STANDARD SAP “Property tree” refers to the series of classes where information is maintained for the specifications. It contains hundreds of classes that are not always relevant for the specification. That is why we created several customized Property trees, that are views or variants of the Standard one, and which only show the information relevant for the type of specification, and sometimes the zone. Some specifications have dedicated Property trees: for example Pure Substances and Transport Classification. Products have 1 Property tree per zone: EU, AP, LA, NA. However the common classes can be found in all property trees: for example when you maintain the pH value in section 9, it will be applicable for all the zones, you don’t need to maintain it 4 times The organization of the property tree mirrors the SDS. Information that is not directly displayed on the SDS is located in the section “0” of the property tree. |
Layout | If phrases are maintained as multiple values within 1 instance, they appear one under the other, without a line break If phrases are maintained as multiple instances they appear one under the other, with a line break, so it allows the SDS writer to highlight some content and improve visibility There are some exceptions. For example Recommended filter type (Section 8>Respiratory protection) and Glove material (Section 8>Hand protection) are single values fields in the standard SAP so you can only maintain 1 value per instance |
Rating | The most common rating is PUBLIC: it is displayed on the SDS and read by the rules. It is the only rating read by the rules. The CUSTOMER rating can be used to display information on the SDS that must be ignored by the rules. For example the GHS rule needs a state of matter and can only read one type of state of matter. But if the product is handled at a temperature close to its melting point, you may want to indicate 2 instances: 1 PUBLIC instance “solid” to be read by the rule and 1 CUSTOMER instance “liquid > 35C” to be displayed additionally on the SDS. This proves to be very useful in the sections 11 and 12 when you want to populate the content of the SDS without preventing the rule from using data from ingredients for mixtures (see section 11/12 for more explanation) INTERNAL rating: for information only, not displayed, not read by the rule. For example, the GHS rules populate the ATE with an INTERNAL rating in section 11 DANGEROUS rating: has priority 1 for the Dangerous Goods Information. It is also displayed on the SDS. OFFICIAL rating: it is a default rating provided by SAP in certain classes. |
MANAGEMENT OF INGREDIENTS’ IDENTIFIERS – WP1
- The name of the ingredient displayed on the SDS is coming from a priority listing, in the language of the generation, or in the “empty language” if it does not exist in the language of generation
- The 1st priority is in fact the Z_GENx identifiers, when the corresponding component type is chosen (see next paragraph)
- There must always be at least 1 identifier Z_INTERNAL with no language assigned
Priority listing for all templates but US, Canada, Asia | Priority listing for US and Canada | |||||||||||||||||||||||||||||||||||||||
|
|
Priority listing for Asia | |||||||||||||||
|
COMPOSITIONS TABLE
WP1 | Purpose of this level of composition, in WP1 |
Exact Composition Based on Products | Indicate products as ingredients (raw materials, intermediates) |
Standard Composition + Legal Composition if necessary | The standard composition is NOT mapped to the SDS. It is the basis for all calculations. It is only composed of PURE_SUB. When an ingredient must be described differently according to the country due to regulation or registration constraints, a Legal Composition is maintained for the corresponding zone. The Legal composition then replaces the standard one for any calculation made for this country or zone. |
Hazardous Ingredients + Non Hazardous Ingredients for NA | These are the compositions mapped to the SDS. They are populated by rules or maintained manually. |
SVT Compositions (for certain countries) | They are filled when needed for the Substance Volume Tracking Functionality |
MANAGEMENT OF CONFIDENTIALITY – WP1
- Choosing an alternative name and hiding the CAS number are 2 separate and independent functionalities
- The work is done in the class “Generic Composition for Confidentiality”
- Advantage: done only once but will apply throughout the document every time the selected ingredient appears, in CH3, 8, 11, 12, 15
- A validity area must be chosen manually by the SDS writer, it can be 1 or several countries or WORLD. The SDS writer is responsible for ensuring that the local regulations allow hiding the identity of a chemical
- A PURE_SUB can have up to 5 of these alternative names, maintained by EHS Admin via the Z_GEN1, 2, 3, 4, 5 identifiers
Tip: copy and paste the ingredients from the standard composition!
1) Choose an alternative name without hiding the CAS number
- Choose the relevant Z_GEN from the match code as component type
2) Choose an alternative name and hide the CAS number
- Choose the relevant Z_GEN from the match code as component type
- Choose the exception value ZE
3) Hide the CAS number only without choosing an alternative name
- Choose the component type Z_HIDECAS from the match code
- Choose the exception value ZE
MANAGEMENT OF FAMILIES – WP1
- Use of inheritance functionality
- 1 specification = 1 grade = 1 material group (PF1) = 1 commercial product (WP1)
- Inheritance is always defined by 3 parameters:
- Inheritance data model is often multi level
- Inheritance links cannot be copied from 1 specification to another
- An inheritance link is created at the header level
- Of the Source specification (in the bottom half of the Relationships screen)
- Or Target specification (in the top half of the Relationships screen)
- Inheritance should not be broken: the “copy template” functionality should be used to do a one shot copy when maintaining a dynamic inheritance is not appropriate, or a new master or inheritance template should be created
- The same inheritance templates are used to create inheritance links (permanent, dynamic relationship between 2 spec s) or copy template (one shot copy). Many templates already exist. Make sure you check the existing ones before creating a new one!
- Any user can create its own template, they must be created in the Public TEMPLATE folder
- You can see which classes are passed in one given template by clicking on its name from the list
This page has no comments.