Skip to end of banner
Go to start of banner

Kazakhstan OMS Release 2024_02

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Document History

Version

Changes

Effective Date

1.0

First approved version

3Keys Kazakhstan OMS Add-On release 2024_02

01-May-2024

1. Overview

This document describes changes in the 3Keys Kazakhstan OMS connector ABAP part.

2.   Notes

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

3.    Transport request ATTP 3.0

The transport request A4DK900XXX includes the release notes RN_2024_02 for ATTP 3.0 with following list of implemented notes.

Note: The transport request A1DK900548 (RN_2023_03) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2024_02_1

A1DK900637

A1DK900548

02-Feb-2024

4.    Transport request ATTP 3.1

The transport request A2DK900XXX includes the release notes RN_2024_02 for ATTP 3.1 with following list of implemented notes.

Note: The transport request A2DK900605 (RN_2023_03) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2024_02_1

A2DK900705

A2DK900605

02-Feb-2024

5.    Transport request ATTP 3.2

The transport request A3DK900XXX includes the release notes RN_2024_02 for ATTP 3.2 with following list of implemented notes.

Note: The transport request A3DK900182 (RN_2023_03) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2024_02_1

A3DK900295

A3DK900182

02-Feb-2024

6.    Transport request ATTP 3.3

The transport request A4DK900XXX includes the release notes RN_2024_02 for ATTP 3.3 with following list of implemented notes.

Note: The transport request A3DK900111 (RN_2024_01) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2024_02_1

A4DK900126

A4DK900111

02-Feb-2024

  • No labels