Kazakhstan CEDM Release 2025_01
Document History
Version | Changes | Effective Date |
1.0 | First approved version 3Keys Kazakhstan CEDM Add-On release 2025_01 | 01-Feb-2025 |
1. Overview
This document describes changes in the 3Keys Kazakhstan CEDM connector ABAP part.
2. Notes
Note | Description | Category |
Transaction /K3TKZ/EDO_MONITOR changed:
Program /K3TKZ/EDO_OMS_REP configuration ID determination corrected for case single tax code is not unique and used for multiple Business partners. New actions implemented into transaction /K3TKZ/EDO_API_SAAS to configure SAAS Log mode. Existing authorization object to display certificate used. Available actions:
For each action authority check is performed with authorisation object /K3TKZ/001 field /K3TKZ/DAC value 53-Display Certificate. | New feature, error | |
Function Sequence check is extended with new sequence check rule to check SSCC pallets from message online at CEDM system. It is expected SSCC pallets from message exist at CEDM and contains child elements SSCC type (child elements started with prefix “00“). New sequence step check is not active by default and could be activated via transaction /K3TKZ/EDO_PARAM. New parameters for sequence check step activation per CEDM message type.
The system will skip sequence check step “Check SSCC pallets online” if parameter for online sequence check per CEDM message type is not maintained. New maintenance view /K3TKZ/V_EDOPAR created to change 3Keys parameter value without transport request. Maintenance view can be started via transaction SM30. Document sending process improved to send document by steps. The next sending step is only started after all documents relevant for previous sending step have been processed. New parameters for delay added to selection screen program /K3TKZ/EDO_DISPATCHER to wait specific time between sending steps:
Response processing improvement for error document status. Error for document from CEDM system is received via new API method “marks-error/{docID}” and saved item field “Error text”. To use new API method It is required to activate BC Set /K3TKZ/CUST_EDO_3_X_2025_01_02 and maintain rest service manually (see Solution section). Support of local packaging in Kazakhstan added. To send crypto code request for local production maintain GTIN parameter “ZKZ_OMS_RTM” with value “PRODUCTION” or business partner company registration type “ZKZ_OMSRMT” value “PRODUCTION”. Please refer to Kazakhstan OMS Configuration guide for details. Maintain “EDO Status send from” and “EDO Status change to” in the transaction /K3TKZ/EDO_CUST and save as customizing transport and import in test and production ATTP system. This will allow to send “Act of acceptance” and “Act of acceptance Single Distributor” with status “APPLIED” (“Нанесен КМ”) as first message to CEDM system and change status to “INTRODUCED” (“Введен в оборот“) after successful notification processing. | New feature |
3. Transport request for ATTP 3.0
The transport request A1DK900799 includes the release notes RN_2025_01 for ATTP 3.0 with following list of implemented notes.
Note: The transport request A1DK900779 (RN_2024_04) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2025_01_1 | A1DK900787 | A1DK900779 | 17-Dec-2024 |
2025_01_2 | A1DK900791 | A1DK900787 | 15-Jan-2025 |
4. Transport request for ATTP 3.1
The transport request A2DK900926 includes the release notes RN_2025_01 for ATTP 3.1 with following list of implemented notes.
Note: The transport request A2DK900889 (RN_2024_04) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2025_01_1 | A2DK900912 | A2DK900889 | 17-Dec-2024 |
2025_01_2 | A2DK900918 | A2DK900912 | 15-Jan-2025 |
5. Transport request for ATTP 3.2
The transport request A3DK900474 includes the release notes RN_2025_01 for ATTP 3.2 with following list of implemented notes.
Note: The transport request A3DK900446 (RN_2024_04) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2025_01_1 | A3DK900456 | A3DK900446 | 17-Dec-2024 |
2025_01_2 | A3DK900466 | A3DK900456 | 15-Jan-2025 |
6. Transport request for ATTP 3.3
The transport request A4DK900553 includes the release notes RN_2025_01 for ATTP 3.3 with following list of implemented notes.
Note: The transport request A4DK900499 (RN_2024_04) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2025_01_1 | A4DK900527 | A4DK900499 | 17-Dec-2024 |
2025_01_2 | A4DK900541 | A4DK900527 | 15-Jan-2025 |
7. Support package for ATTP 3.4
The support package SAPK-30451INK3TKZ3 includes the release notes RN_2025_01 for ATTP 3.4 with following list of implemented notes. Import support package with transaction SPAM.
Note: The support package SAPK-30444INK3TKZ3 is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2025_01_1 | A5DK900083 | support package SAPK-30444INK3TKZ3 | 17-Dec-2024 |
2025_01_2 | A5DK900089 | A5DK900083 | 15-Jan-2025 |
8. Support package for ATTP 4.1
The support package SAPK-40151INK3TKZ3 includes the release notes RN_2025_01 for ATTP 4.1 with following list of implemented notes. Import support package with transaction SPAM.
Note: The build SAPK-401COINK3TKZ3 is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2025_01_1 | H18K900048 | software build SAPK-401COINK3TKZ3 | 17-Dec-2024 |
2025_01_2 | H18K900054 | H18K900048 | 15-Jan-2025 |