Transport
Training Materials
>> Refer to the DG user advanced training manual. (broken link)
Dangerous Goods regulations are maintained on DG Specification in CG02 called DG_CL_SUB . The system is capable of maintaining the regulations for a variety of regulations (ADG, ADN, ADR, ANTT, CN_DG, DOT, IATA_C, IATA_P, IMDG, KR_DG, NOM, NZ_DG, RID, TDG, ZA_DG). Nearly all the applicable DG data is maintained on the DG_CL_SUB (exceptions will be noted later).
The DG_CL_SUB passes the DG data to one or more products (PRODCOM) through the inheritance functionality. Inheritance allows the product to always have the exact data that is maintained in the DG_CL_SUB. If the DG_CL_SUB is updated, all related products will instantaneously be updated.
>> Refer to the Data model page.
The information printed on all SDS documents comes from this data. Similarly, the Transport Sheet and other transport labels that are available in Sinequa come from this data.
DG Specifications are populated with a combination of regulatory data from the CLEO database as well as manually assigned data. The CLEO data is directly loaded and maintained on "UN-listed substance" specifications, called LS_UN_SUB. There is a LS_UN_SUB for each UN number classification. It maintains the data for UN number, proper shipping name, possible packing groups for that UN number, and danger labels (classes and sub-classes, but not marine pollutant or anything else) per each regulation. Within each DG_CL_SUB, an S_UN_SUB and Risk Potential (packing group) is assigned for each regulation. It is usually the same LS_UN_SUB for each regulation, but it can sometimes be different. Examples of this include when DOT is NA1993 and other regulations are non-regulated, when TDG is UN1170 while other regulations are UN1987 for when ethanol content is below 24%, and when dealing with RQ products that only apply to DOT.
For labels used at the material level in plants and other material specific shipping documents such as the BOL, each material assigned to a PRODCOM must be updated using the filling transaction in SAP (DGE5). Each time DG data is updated, the DG filling transaction must be ran. The filling can be run by specifying material code, specifying a PRODCOM (affects all assigned materials to PRODCOM), or by specifying a DG_CL_SUB, (affects all materials that are assigned to all PRODCOM's inheriting from the DG_CL_SUB,). It it possible to have this DGE5 transaction ran automatically on a regular basis (e.g. daily, weekly) to ensure the data on the materials is always in sync with the data in CG02 as it was done in legacy Solvay (to be updated), however, in WP1, this transaction must be ran manually. The DGE5 transaction updates the data on each material at the DG Master, and this material-level data can be seen using transaction DGP3.
DG data model
Focus on Dangerous Goods integration in PF1
The DG classification is always maintained in the module SAP EHS in the WP1 ERP . From there, it is copied over to the module SAP EHS of the PF1 ERP via an automatic program.
In the SAP EHS module, data are maintained in a "commercial product" (or "PROD_COM"), which aggregates several materials that are the same product under different packaging. The idea in EHS is to work on an aggregated object to avoid maintaining the same information for all the package sizes.
To allow this, material codes must be assigned to EHS commercial products. This is done for PF1 based on material group :
- a new material group triggers the creation of a new (and empty) commercial product in EHS. Then this commercial product may be completed or instead the material group re assigned manually to another existing (and already completed) commercial product
- a new material code attached to an existing material group is automatically assigned to the EHS commercial product to which the material group is assigned
A last step is to populate the DG master in PF1 . This is also done via automatic program.
| More questions? Contact EH&S and Substance Team . |
|---|
This page has no comments.