This release note describes the conversion of application and Customizing tables for dangerous goods master data as regards the change from Release 4.0B to 4.5A.
The Dangerous goods regulation field has been included in the key for maintaining data in the whole dangerous goods system. For this reason, the existing key fields "mode of transport category" and "validity area" are no longer required in the Customizing data for application data or "mode of transport category".
The conversion was made as dangerous goods data can be maintained more exactly and easily using dangerous goods regulations instead of mode of transport categories and validity areas. Entries such as mode of transport category 'inland waterway' and validity area 'world' are included directly when you create data records with dangerous goods regulations.
Changes have thus been made to structures, Customizing and application tables. For this reason you must convert the contents of these tables if you used dangerous goods management in a productive system for 4.0A/B or if you want to prepare for your productive system using existing master data and Customizing table entries.
The relationships between the old keys and new keys have been stored in a central Customizing table Dangerous goods regulation (THM063). For integrity purposes, a 1:1 relationship is required between this objects. Two or more "subregulations" must be maintained for regulations that refer to more than one mode of transport type, such as IATA or CFR. This is because their contents are different as regards the individual modes of transport.
As you will probably have to intervene in the conversion process, we made sure that no XPRAs are included. The contents of the Customizing tables are not converted within the tables. Instead, new entities are created and are filled using the old data. You do not have to fill the entities as soon as you change to Release 4.5A; this can also be done at a later date. The conversion must be carried out for productive systems.
Data conversion is necessary for the new structures for the dangerous goods master and Customizing tables. A key change for the dangerous goods master (DGTMD) and the Customizing tables is supported. The entities are created in accordance with the dangerous goods regulation (and other possible attributes) and no longer in accordance with the mode of transport type and/or the validity area.
Virtually all Customizing tables for the dangerous goods master are affected by the conversion. Instead of renaming the old Customizing tables, new tables have been created and the old tables will not be used actively in future. An automatic XPRA is therefore not required. Instead, reports are made available for both the areas mentioned above, thereby providing a consistent database.
It is essential that dangerous goods regulations are allocated to mode of transport categories and validity areas. Before conversion, an appropriate table must be constructed using existing data. The table can also be maintained manually at a later stage. There are eight steps in the process:
Step 1: Convert the old table for dangerous goods data (TDG63).
Step 2: Check the dangerous goods regulations table and maintain data if required.
Step 3: Check to see whether you can convert the dangerous goods material master data (DGTMD) at a later stage.
Step 4: Convert table for dangerous goods material master data (DGTMD).
Step 5: Convert regulation-dependent Customizing tables.
Step 6: Check and maintain regulation-dependent Customizing tables.
Step 7: Check and maintain dangerous goods master (DGTMD).
Step 8: Automatic check for referential integrity.
The steps must be carried out in the order given. However, after each step, you can restart the process in one of the previous steps. For example, you may be required to branch once more to dangerous goods regulation maintenance (THM063) (2) after checking the conversion of the dangerous goods material master (DGTMD) (3). You may also have to check and maintain Customizing (6) or master data (7) after you have checked the referential integrity (8).
You may not need to carry out this step if little or no data has been
maintained in the "Derivations of Regulations" table (TDG63), for
example. The following example shows how the data is converted. In the last data record, you can see which overlaps can occur.
Source: TDG63 Target: THM063
| MTransCat | V.Area | DGReg. | DGReg. | MTransCat | V.Area | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| 01 | EU | ADR | ADR | 01 | EU | |||||
| 01 | DE | GGVS |
Data conflicts if there is an n:1 relationship between mode of transport category - validity area combinations and dangerous goods regulations, and not a 1:1 relationship. This can be seen in the example of the CFR regulation. In this case you must maintain the data. This is also necessary if not all of the combinations of mode of transport category and validity area that were used previously have been maintained in table TDG63.
The data in the dangerous goods regulation table (THM063) is used for converting the dangerous goods material master and the remaining Customizing tables that are dependent on the mode of transport category at a later stage. You must make sure that a secondary key is clearly defined for the mode of transport category/validity area combination. A 1:1 relationship is thus created between this combination and a dangerous goods regulation. In the following example, the new entries are shown in a different colour. The entries with dangerous goods regulation CFR were deleted and two new entries adopted.
THM063 Dangerous goods regulation
| DGReg. | Cat | V.Area |
|---|---|---|
| ADR | 01 | EU |
| GGVS | 01 | DE |
| RID | 02 | EU |
| GGVE | 02 | DE |
| CFR_1 |
Call the IMG activity
Define dangerous goods regulations .
Errors may occur during the conversion of DGTMD and therefore you should check the THM063 table and edit it as required (step 2).
In this step, you can use a check routine to find out whether a conversion will run successfully. If so, the data can be actually converted in step 4.
If not, you must adapt the table THM063 (step 2) or dangerous goods master (DGTMD).
In carrying out the conversion, the system overwrites the old contents
of the fields in the DG Regulation column with the entries in table
THM063. In the following example, the changed field contents are represented differently:
DGTMD (before)
| Material | MTransCat | V.Area | DGReg. | |||
|---|---|---|---|---|---|---|
| 4711 | 01 | EU | ADR | |||
| 4711 | 01 | EU | ||||
| 4712 | 01 | DE |
DGTMD (after)
| Material | DGReg. | MTransCat | V.Area | |||
|---|---|---|---|---|---|---|
| 4711 | ADR | 01 | EU | |||
| 4711 | ADR | 01 | EU |
It may be that a conversion in the table DGTMD is not possible due to the contents of table THM063. This is the case if a combination of mode of transport category and validity area from the DGTMD does not exist in the THM063 table. If this is the case, you must maintain the entries in the THM063 table. As the system uses this data for converting the Customizing tables (step 5) you must adhere strictly to the existing sequence of data.
Finally, the following Customizing tables must be converted:
* Transport Categories (TDG03/04),
* Dangerous Goods Classes (TDG09/10),
* Dangerous Goods Letters (TDG11/12),
* Danger Labels (TDG17/18)
* Hazard Identification Numbers (TDG31/32)
All the above-mentioned tables are converted using the dangerous goods
master data. The following table contents of the DGTMD are adopted for
transport categories and hazard identification numbers in the examples as described below:
DGTMD
| Material | DGReg. | MTransCat | V.Area | TransCat1 | TransCat2 | HazIDNo. | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| 4711 | ADR | 01 | EU | 2 | 22 | |||||
| 4711 | ADR | 01 |
The following example shows conversion using transport classifications
(TDG03/04). The example applies to this view only. Only the tables are converted.
| TDG03/04 | THM003/004 |
|---|
| MTransCat | TransCat | Description | DGReg. | TransCat | Description | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| 01 | 1 | tank | ADR | 1 | tank | |||||
| 01 | 2 | packaged |
The conversion report can be called again at any time as the old data still exists in the system as before. You should delete the entries in the target tables before restarting the system. This function is available as an option (indicator) in the reports.
In the following example, the last entry in the TDG03/04 tables is not converted as it is not used anywhere in DGTMD. You are informed of this in the log. The system was also unable to convert transport category 4 to mode of transport category 01, or to convert 2 to 02. This is because they did not exist in the original table. The reason for this was inconsistency in the original data that was, for example, caused by deleting Customizing entries. Errors like these also appear in the log.
The hazard identification number table cannot access mode of transport
categories as key fields. The following example shows the process using the ADR and GGVS regulations:
| TDG31/32 | THM031/032 |
|---|
| HazIDNo | Description | DGReg. | HazIDNo. | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
20| | inert gas | | | ADR | | 22 | | refrigerated gas | 22 |
| |