Note

Description

Category

2024_02_1

In some scenarios Kazakhstan OMS aggregation reports based on EPCIS object event includes objects with GTINs belongs to different OMS cabinets. Additional logic added to split Kazakhstan OMS aggregation into different reporting events based on OMS ID value.

OMS Id value is determined based on GTIN value using the following logic:

1. Read industry from GTIN

2. Read Business partner based on GTIN attribute BR_OWNER_GLN

3. Read OMS system for business partner with system type OMS and system group SAP_KZ_20

Participant ID field is determined based on GTIN value using the following logic:

1. Read Business partner based on GTIN attribute BR_OWNER_GLN

2. Read Business partner Registration number for Registration type "ZKZ_PARTIC"

New feature.

In some scenarios Kazakhstan OMS aggregation reports based on EPCIS object event includes objects with multiple GTINs belongs to the same OMS cabinet. Sequence check displays error in AIF “Crypto code is not yet confirmed for GTIN 1234 Serial 56789” and stops reporting event sending to OMS system. At the same time Crypto code in the system has correct confirmation status “Confirmed”. The reason is ABAP code error.

Aggregation report fields determined based on GTIN are filled with values from the first GTIN

Implementation error.

New feature, error

2024_02_2

To prevent adding the ZDEV transport layer to customer STMS transport routes, the 3Keys Kazakhstan OMS Connector ABAP packages transport layer was changed from ZDEV to SAP

New feature