Kazakhstan CEDM message field value mapping
Document History
Version | Changes | Effective Date |
1.0 | First approved version | 01-May-2024 |
2.0 | Updated with RN 2024_03 | 01-Aug-2024 |
3.0 | Updated with RN_2024_04 | 01-Nov-2024 |
- 1 About This Guide
- 2 Act of acceptance Single Distributor (Акт приема/передачи Единого дистрибьютора)
- 3 Act of acceptance (Акт приема/передачи)
- 4 Introduce from EAEU (Уведомление о ввозе из стран ЕАЭС)
- 4.1 Sender BIN (БИН отправителя)
- 4.2 Sender Name (Наименование отправителя)
- 4.3 Receiver BIN (БИН получателя)
- 4.4 Country (Страна отправления)
- 4.5 Document number (Сведения об уведомлении, выписанном на бумажном носителе - Номер уведомления )
- 4.6 Document date (Сведения об уведомлении, выписанном на бумажном носителе - Дата уведомления)
- 5 Import from 3rd countries (Уведомление о ввозе из третьих стран)
- 5.1 Receiver BIN (БИН получателя)
- 5.2 Export Country (Страна экспорта)
- 5.3 Document type (Сведения о документе таможенного оформления - Тип документа)
- 5.4 Document number (Сведения о документе таможенного оформления - Регистрационный номер документа)
- 5.5 Document date (Сведения о документе таможенного оформления - Дата регистрации документа)
- 5.6 Decision code (Сведения о решении таможенного органа - Код принятого решения)
- 5.7 Decision date (Сведения о решении таможенного органа - Дата решения)
- 5.8 Customs code (Сведения о решении таможенного органа - Код таможенного органа)
- 5.9 Document type (Сведения о документе, подтверждающем соответствие товаров - Тип документа)
- 5.10 Document number (Сведения о документе, подтверждающем соответствие товаров - Номер документа)
- 5.11 Document date (Сведения о документе, подтверждающем соответствие товаров - Дата документа)
- 5.12 Document number (Сведения об уведомлении, выписанном на бумажном носителе - Номер уведомления)
- 5.13 Document date (Сведения об уведомлении, выписанном на бумажном носителе - Дата уведомления о ввозе)
- 6 Withdrawal Notification (Уведомление о выводе из оборота)
- 7 Return into circulation Notification (Уведомление о повторном вводе в оборот)
- 8 Codes transfer from non-resident (Отчет о передаче КИ от нерезидента РК)
- 9 New aggregation out of production (Новая агрегация вне производства)
About This Guide
This document describes EDO message field value mapping in 3Keys Kazakhstan EDO in SAP ATTP system
The 3Keys Kazakhstan EDO Add-On facilitates the generation of message content by leveraging data from various sources. Specifically, it considers EPCIS event extensions, source and destination parties, business partner attributes, business transaction details, and GTIN attributes. However, it’s important to note that if any mandatory fields lack values, the message will not be generated. In such cases, the system displays the relevant item in the transaction /K3TKZ/EDO_MONITOR and waiting the user manual input values for the missing fields. Additionally, customers have the flexibility to modify the message field values by implementing a Badi.
Act of acceptance Single Distributor (Акт приема/передачи Единого дистрибьютора)
API document type 0001.
ATTP rule type Z3KKZ_EDO_0001 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Sender BIN (БИН отправителя)
JSON field “senderBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Receiver BIN (БИН получателя)
JSON field “receiverBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CONS_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field RECEIVERBIN |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Номер первичного документа)
JSON field “paperNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Дата первичного документа)
JSON field “paperDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Owner BIN
JSON field “ownerBin”.
Sequence | Value determination |
1 | Value for the parameter SINGLE_DISTR_BIN maintained in the transaction /K3TKZ/EDO_PARAM - Reporting parameters |
Act of acceptance (Акт приема/передачи)
API document type 0010.
ATTP rule type Z3KKZ_EDO_0010 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Sender BIN (БИН отправителя)
JSON field “senderBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Receiver BIN (БИН получателя)
JSON field “receiverBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CONS_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field RECEIVERBIN |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Номер первичного документа)
JSON field “paperNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Дата первичного документа)
JSON field “paperDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Introduce from EAEU (Уведомление о ввозе из стран ЕАЭС)
API document type 0002.
ATTP rule type Z3KKZ_EDO_0002 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Sender BIN (БИН отправителя)
JSON field “supplierID”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Sender Name (Наименование отправителя)
JSON field “supplierName”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_NAME |
2 | Business partner name determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner name determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Receiver BIN (БИН получателя)
JSON field “receiverBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CONS_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field RECEIVERBIN |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Country (Страна отправления)
JSON field “countryCodeEAEU“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CTR_CODE. Value from list [AM,BY,KG,RU]. Reference |
2 | Business partner address country determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner address country determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Сведения об уведомлении, выписанном на бумажном носителе - Номер уведомления )
JSON field “docNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Сведения об уведомлении, выписанном на бумажном носителе - Дата уведомления)
JSON field “docDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Import from 3rd countries (Уведомление о ввозе из третьих стран)
API document type 0003.
ATTP rule type Z3KKZ_EDO_0003 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Receiver BIN (БИН получателя)
JSON field “receiverBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CONS_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field RECEIVERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Export Country (Страна экспорта)
JSON field “countryCode“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CTR_CODE. Country code length 2 characters. Reference |
2 | Business partner address country determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document type (Сведения о документе таможенного оформления - Тип документа)
JSON field “docTypeCustom“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_DECL_DOCUMENT. Value from list [DECLARATION,STATEMENT]. Reference |
2 | Value for the parameter DOC_TYPE_CUSTOM maintained in the transaction /K3TKZ/EDO_PARAM - Reporting parameters |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Сведения о документе таможенного оформления - Регистрационный номер документа)
JSON field “regNumDoc“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_DECL_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Сведения о документе таможенного оформления - Дата регистрации документа)
JSON field “regDateDoc“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_DECL_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Decision code (Сведения о решении таможенного органа - Код принятого решения)
JSON field “decisionCode“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_DECISION_CODE. Value in numeric format length 2 characters. Reference |
2 | Value for the parameter DECISION_CODE maintained in the transaction /K3TKZ/EDO_PARAM - Reporting parameters |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Decision date (Сведения о решении таможенного органа - Дата решения)
JSON field “decisionDate“ and “decisionTime”.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_DECISION_DATE. Value in ISO format YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DDTHH:MM:SS.mmmZ |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Customs code (Сведения о решении таможенного органа - Код таможенного органа)
JSON field “customsCode“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CUSTOMS_CODE. Value in numeric format length 5 characters. Example “50624” - Т/П `КОСТАНАЙ-ЦЕНТР ТАМОЖЕННОГО ОФОРМЛЕНИЯ`. Reference |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document type (Сведения о документе, подтверждающем соответствие товаров - Тип документа)
JSON field “documentType“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CERT_DOC_TYPE |
2 | Value for the parameter DOC_TYPE_0003 maintained in the transaction /K3TKZ/EDO_PARAM - Reporting parameters |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Сведения о документе, подтверждающем соответствие товаров - Номер документа)
JSON field “documentNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CERT_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Сведения о документе, подтверждающем соответствие товаров - Дата документа)
JSON field “docDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CERT_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Сведения об уведомлении, выписанном на бумажном носителе - Номер уведомления)
JSON field “paperNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Сведения об уведомлении, выписанном на бумажном носителе - Дата уведомления о ввозе)
JSON field “paperDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Withdrawal Notification (Уведомление о выводе из оборота)
API document type 0004.
ATTP rule type Z3KKZ_EDO_0004 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Sender BIN (БИН отправителя)
JSON field “senderBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Reason (Причина вывода из оборота)
JSON field “ReasonWithdrawal“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_REASON. Reason code numeric value length 2 characters. Reference |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document name (Наименование документа основания)
JSON field “docName“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NAME |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Номер документа основания)
JSON field “docNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Дата документа основания)
JSON field “docDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Return into circulation Notification (Уведомление о повторном вводе в оборот)
API document type 0005.
ATTP rule type Z3KKZ_EDO_0005 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Sender BIN (БИН отправителя)
JSON field “senderBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Reason (Причина ввода в оборот)
JSON field “ReasonIntroduce“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_REASON. Reason code numeric value length 1 characters. Reference |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document name (Наименование документа основания)
JSON field “docName“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NAME |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Номер документа основания)
JSON field “docNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Дата документа основания)
JSON field “docDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Codes transfer from non-resident (Отчет о передаче КИ от нерезидента РК)
API document type 0011.
ATTP rule type Z3KKZ_EDO_0011 assigned in the transaction /K3TKZ/EDO_CONF - Reporting configuration.
Sender BIN (БИН отправителя)
JSON field “senderBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
5 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Receiver BIN (БИН получателя)
JSON field “receiverBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CONS_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field RECEIVERBIN |
3 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
4 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Shipment country (Страна отгрузки)
JSON field “countryCode“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_CTR_CODE. Country code length 2 characters. Reference |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Shipment date (Дата отгрузки)
JSON field “shipment_date“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SHIP_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document number (Номер бумажного уведомления о ввозе)
JSON field “paperNum“
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_NUM |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
Document date (Дата бумажного уведомления о ввозе)
JSON field “paperDate“.
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PRM_DOC_DATE. Value in format YYYYMMDD |
2 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
3 | Maintain field value manually using function “Maintain missing data” in the transaction /K3TKZ/EDO_MONITOR |
New aggregation out of production (Новая агрегация вне производства)
API document type 6000.
ATTP rule type Z3KKZ_EDO_CHANGE_HRY assigned in the transaction /STTP/CUST_RULES - Maintenance View for Rules.
Sender BIN (БИН отправителя)
JSON field “senderBin”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_SUPPL_ID |
2 | Business partner registration type ZKZ_PARTIC determined based on field mapping in transaction /K3TKZ/EDO_ATTR_MAP for the reporting message field SENDERBIN |
3 | Business partner registration type ZKZ_PARTIC determined based on event read point / business location assigned business partner |
4 | Badi implementation /K3TKZ/EDO_CHG_AFTER_MAP |
Package Type (Тип упаковки)
JSON field “packageType”
Sequence | Value determination |
1 | EPCIS message event extension ZR_KZ_PACKAGE_TYPE |
2 | If aggregation has child object SSCC use constant value “LEVEL3” |
3 | If aggregation has child object SGTIN use constant value “LEVEL2” |