Document History

1.    Overview

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

2. Description

Transaction and dictionary object text system name renamed from EDO to “CEDM” / “ЦЭДМ”.

Additional Kazakhstan CEDM message types added to the 3Keys Kazakhstan CEDM connector

• Return into circulation (Возврат в оборот)

New feature.

CEDM report “Codes transfer from non-resident” (type 0011) changed according to CEDM API changes from May 2024:

• new optional fields “paperNum”, “paperDate” added. Field value is determined from event attributes ZR_KZ_PRM_DOC_NUM, ZR_KZ_PRM_DOC_DATE

• field “shipment_date” determination logic changed to use new event attribute ZR_KZ_SHIP_DATE

• sending process changed: signature step added on sending (technical change automatically executed with 3Keys CEDM connector)

New feature.

CEDM report “Import from EAEU” (doc type 0002) changed:

• in case participant tax code is determined via transaction /K3TKZ/EDO_ATTR_MAP - “Reporting attributes mapping” then the business partner name and country read from address data to fill the Name (field “supplierName“) and Country (field “countryCodeEAEU”).

• configuration determination changed to find configuration for tax code from field “receiverBin” instead of “supplierID”)

New feature.

CEDM report “Import from 3rd countries” (doc type 0003) changed:

• in case there is no event attribute for country and participant tax code for field “SENDERBIN“ is specified via transaction /K3TKZ/EDO_ATTR_MAP - “Reporting attributes mapping” then the business partner country read from address data to fill the the ExportCountry (field “countryCode”).

• field Custom document type logic changed to read value from 3Keys parameter “DOC_TYPE_CUSTOM” (transaction /K3TKZ/EDO_PARAM) if there is no event attribute

• field Decision code logic changed to read value from 3Keys parameter “DECISION_CODE” (transaction /K3TKZ/EDO_PARAM) if there is no event attribute

New feature.

Runtime error on report sending related to response error counter. New logic added to program /K3TKZ/EDO_DISPATCHER for server error processing during program run. New select-options “Server error response codes” and parameter “Stop after failed attempts” with additional response code control added.

Implementation error.

Transaction /K3TKZ/EDO_API_SAAS updated with new approach for upload participant data and certificate. Selection screen variant save for participant upload action is restricted.

New feature.

Support for CEDM API version 2 added. Manual activities are required (see Solution section).

New feature.

Changes for CEDM status values “Эмитирован КМ” - “EMITTED”, “Нанесен КМ” - “APPLIED”, “Списан” - “WRITTEN_OFF”, ”Возвращён в оборот” - “INTRODUCED_RETURNED”.

New feature.

3. Solution

Import related transport request

Activate BC Set depending on your ATTP version:

• /K3TKZ/CUST_EDO_3_0_2024_03_03 (SAP ATTP 3.0 version)

• /K3TKZ/CUST_EDO_3_1_2024_03_03 (SAP ATTP 3.1 version)

• /K3TKZ/CUST_EDO_3_2_2024_03_03 (SAP ATTP 3.2 version)

• /K3TKZ/CUST_EDO_3_3_2024_03_03 (SAP ATTP 3.3 version)

Maintain REST path using transaction SM30 view /STTP/V_RSRVPATH.

Upload configuration and participant via transaction /K3TKZ/EDO_API_SAAS.

3.1    Correction instruction ATTP 3.0

3.2    Correction instruction ATTP 3.1

3.3    Correction instruction ATTP 3.2

3.4    Correction instruction ATTP 3.3

4. Recommendation

Regression test for all messages.

5. Source code objects