Document History
Version | Changes | Effective Date |
1.0 | First approved version 3Keys Uzbekistan OMS Add-On release 2023_ |
04 | 01- |
Nov-2023 |
1. Overview
This document describes changes in the 3Keys Uzbekistan OMS connector ABAP part.
2. Notes
Note | Description | Category |
New ATTP rules implemented for pharma industry: BR_CRYPTO_COMM for Utilization report and BR_CRYPTO_DECOMM for Drop-out report.
In case some of EPCIS messages are sent in parallel the OMS ID is locked and aggregation report is failed with error 6-Mapping error.
To avoid this error after correction system will not lock OMS on aggregation report sending. For all other OMS operations new Custgen parameter Z3KUZ_OMS_LOCK_TRIES added to change locking attempt number. (The default locking number is 20 with 2 seconds delay).
In case aggregation event for SSCC-SSCC has been sent before aggregation SGTIN-SSCC (for example if aggregation report SGTIN-SSCC is failed with error 6-Mapping error) aggregation report JSON could be send again with changed JSON content. There are available options to send report to OMS again:
use OMS Web interface and fill optional field with value
use GTIN attribute “RR_RU_PRODLINE_ID” or new Custgen parameter “Z3KUZ_OMS_PRDLINE_ID” UZ OMS: Production line ID to fill optional field “productionLineId” with value
Implementation error.
In case SAP Note 3104883 is not installed Release 2023_03 installation failed with error with DDIC activation error for structure /K3TUZ/S_RR_UZ_UTIL_DET_10. To avoid this error new data element used for Production Date field. Implementation error. | Error | |
In some scenarios Uzbekistan OMS aggregation reports based on EPCIS object event includes objects with GTINs belongs to different OMS cabinets. Additional logic added to split Uzbekistan OMS aggregation into different reporting events based on OMS ID value. OMS Id value is determined based on GTIN value using the following logic:
Participant ID field is determined based on GTIN value using the following logic:
New feature. | New feature | |
Utilization report production date field determination logic corrected:
ABAP code corrected for Drop out report. | Error |
3. Transport request ATTP 3.0
The transport request A1DK900546 A1DK900592 includes the release notes RN_2023_03 04 for ATTP 3.0 with following list of implemented notes.
Note: The transport request A1DK900500A1DK900546 (RN_2023_0203) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2023_ |
04_1 |
A1DK900532
A1DK900500
A1DK900558 | A1DK900546 | 07-Aug-2023 | |
2023_04_2 | A1DK900560 | A1DK900546 | 18-Sep-2023 |
2023_04_3 | A1DK900586 | A1DK900546 | 17-Oct-2023 |
4. Transport request ATTP 3.1
The transport request A2DK900601 A2DK900647 includes the release notes RN_2023_03 04 for ATTP 3.1 with following list of implemented notes.
Note: The transport request A2DK900525A2DK900601 (RN_2023_0203) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2023_ |
04_1 |
A2DK900589
A2DK900525
A2DK900619 | A2DK900601 | 07-Aug-2023 | |
2023_04_2 | A2DK900625 | A2DK900601 | 18-Sep-2023 |
2023_04_3 | A2DK900634 | A2DK900601 | 17-Oct-2023 |
5. Transport request ATTP 3.2
The transport request A3DK900184 A3DK900215 includes the release notes RN_2023_03 04 for ATTP 3.2 with following list of implemented notes.
Note: The transport request A3DK900136A3DK900184 (RN_2023_0203) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2023_ |
04_1 |
A3DK900166
A3DK900136
A3DK900192 | A3DK900184 | 07-Aug-2023 | |
2023_04_2 | A3DK900200 | A3DK900184 | 18-Sep-2023 |
2023_04_3 | A3DK900204 | A3DK900184 | 17-Oct-2023 |
View file | ||
---|---|---|
|
View file | ||
---|---|---|
|
View file | ||
---|---|---|
|
...