Because of the SWIFT-Release 2021, there is a need for new data-fields of the business-sector of Guarantees. It is necessary to enter one contract changing transaction (i.e. adding a reference - GITADD) to initialize these new data-fields. Instead of changing every single guarantee you can execute the transaction SPTS20. This transaction generates a automatic processing GITADD to every guarantee that fits to the following criteria:

• Guarantee isn't closed
• Guarantee isn't marked as converted (new data-fields are already initialized)
• There is no GITADD in the queue of incoming, break or correction
• There isn't a GITADD that waits for automatic processing

An entry like “ Already created a SPT entry for contract <REFERENCE>” indicates a problem that fits to last two bullet-points.

In the case of a problem with this automatic task, you can enter a GITADD manually, if SWIFT-2021-Release is active.

To ensure that the data for the initialization is correct, the above-mentioned action must be done after activation of SWIFT-Release-2021.

If you don't initialize the new data-fields, they can't be used for statistic purpose. We don't expect negative effects in the daily processing.

With SWIFT 2021 many new fields have been installed.

The following table shows, how they where filled for contracts, created before SR2021 activation.

To make clear, if all fields which are mandatory for handling after SR2021 activation are filled, a new flag was inserted:

REC\S20STAFLG
Content empty means - no, contract created before SR2021
Content Y means - yes, contract created after SR2021 activation, so all checkrules are done.
Content M means - yes, all fields mandatory for handling a contract after being opened are filled. Fields only mandatory for opening itself might stay empty.

SWT20-Migration