Reorganize Mappings

This transaction is used to :

• Create SWH table based on an existing SWM table, if a corresponding SWH table does not already exist. This is done to handle the mappings as a standard Static data transaction with version display, 4-eye principle etc.
• Reorganizes “alternative mappings” of a message to become the “normal” mappings, before any new alternative mappings for a future release can be imported into the installation. Failing to do so will mean that the currently valid mappings are lost. This must be avoided and to ensure a smooth handling, the existing transaction “REOSWH” (now renamed to “Reorganize Mappings”) is enhanced to support the reorganization task.

Reorganize “alternative mappings”:

This transaction archives old mappings and will move alternative mappings to be “normal” ones. Thus, allowing new alternative mappings to be imported without overwriting mappings that are still required. The series of steps that the transaction does automatically while execution are as follows:

• Checks for any available alternative mappings in the environment where the transaction is executed. If available, then all the mappings (alternative & non-alternative) are exported to a zip file in the data partition (e.g. T:\xxx\data\swm).
• For each message with an alternative mapping, checks if a non-alternative mapping exists,
  • If a non-alternative mapping for the message (e.g., MT 760) exists then, it deletes the old mapping without the flag set and then deletes the “Alternative mapping” flag from the alternative mapping, so that this one becomes the current existing mapping which will be executed.
  • If a non-alternative mapping for the message does not exists then (meaning this message was introduced with “Standards Release 2021”, e.g. MT 765 ), it deletes the “Alternative mapping” flag from the alternative mapping, so that this one becomes the current existing mapping which will be executed.
• Once all mappings are updated, the current mappings (without any alternative mapping) are exported again to “T:\xxx\data\swm” folder.
• It is important that when the REOSWH transaction is being executed, tables “SWH” and “SWM” are not locked, meaning no one else updates any mappings. In case of any errors during this process, the process is stopped, and all changes are rolled back.

Once the transaction is executed, it is important to check for logs, and cross verify in DBxSWH that no alternative mapping exists. After the above process is successfully completed, the new mappings for the upcoming release can be imported into the system.

Reorg