...

1.    Overview

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

2. Description

New transaction /K3TKZ/MPT_API_SAAS implemented to configure MPT Connector SAAS part.

Predefined RFC connection to connector with empty Path prefix is required. For example, if you have RFC connection “MPT“ for sending notifications with Path prefix, please create new connection “MPT_API“ with the same credentials without Path prefix.

Available actions:

• Display certificate information: receive certificate information from connector

• Upload Certificate: upload file and send certificate file to connector (P12 file is expected)

• Upload Configuration: upload file and send configuration file to connector (YAML file is expected)

For each action authority check is performed with authorisation object /K3TKZ/001 field /K3TKZ/DAC values 53-Display Certificate, 54-Upload Certificate, 55-Upload Configuration.

New transaction /K3TKZ/MPT_API_TEST implemented to test MPT API.

Predefined RFC connection to connector with empty Path prefix is required.

Available actions:

• Health Check: test connector status

• Display certificate information: receive certificate information from connector

• API Call: execute API call to MPT system

For each action authority check is performed with authorisation object /K3TKZ/001 field /K3TKZ/DAC values 53-Display Certificate, 56-Call API, 57-Health Check.

New transaction /K3TKZ/MPT_API_LOG implemented to display MPT API Audit Log.

Authority check is performed on transaction run with authorisation object /K3TKZ/001 field /K3TKZ/DAC value 58-Display MPT API Log.

Transaction has selection screen to search specific entries at MPT API Audit Log database table. To restrict log selection log attributes can be specified.

Result data display with ALV grid. Due to technical reasons value of fields REQUEST, RESPONSE, PATH is shortened on display to get detail information double click is supported. To get full list export file option is available.Runtime error occurs on sending notification to MPT in case IMPORT notification contains field DecisionDateTime with Datetime value in future.

Response contains code 400 with the following JSON: {“code”:400,”description”:”ru.crpt.trueapi.exception.document…<JSON part deleted>”}

This JSON can not be saved to DB field error_text due to its length. Additional logic is implemented to trim error_text value before save to database. If value length is more than 1300 characters first 1297 characters + “…” will be saved.

Implementation error

Function “Navigate to reporting event” works incorrectly at transaction /K3TKZ/DOC_MONITOR. Transaction /STTP/COCKPIT is opened without related reporting event opening due to ABAP code error.

Implementation error

Import 3rd country message created incorrectly. The attribute itemNumber value of node <product> contains incorrect value different from declaration item number.

New event attribute ZR_KZ_DECL_POS created to use as attribute itemNumber value. New attribute is mandatory and empty value is not allowed. In case event has no ZR_KZ_DECL_POS property message will stop with status 05-Missing Data. Popup screen for “Missing data“ enhanced to include new field “Reg.Doc Item Number”.

Single value for all product lines is expected.

New feature

Missed event attributes ZR_KZ_DECL_POS, ZR_KZ_IMPORTER_ID, ZR_KZ_IMPORTER_NAME, ZR_KZ_OPER_TYPE, ZR_KZ_PARTIC_ID, ZR_KZ_PARTIC_NAME added into transformation /K3TKZ/EPCIS_SAPEXT.

Implementation error

Notification field mapping corrected for all notification types to process Participant ID and Participant Name (exact field name depends on notification type) fields with the following logic:

• step 1: if event has event attributes participant ID and participant Name (for example Importer ID and Importer name for Import from 3rd countries) use this values and skip other participant ID determination steps

• step 2: if event has attribute mapping (transaction /K3TKZ/ATTR_MAP) find participant ID and participant Name from attribute mapping function. New registration type ZKZ_PAR_NM created to maintain Participant name at Business Partner level. If customising is found /K3TKZ/ATTR_MAP skip other participant ID determination steps

• step 3: find Business partner from Read Point GLN (or Biz location GLN in case Read point GLN is empty), use registration number from Business Partner

New feature

3. Solution

Import related to the transport request.

3.1    Correction instruction ATTP 3.0

3.2    Correction instruction ATTP 3.1

3.3    Correction instruction ATTP 3.2

4. Recommendation

Test corrections from description section Add event attribute ZR_KZ_DECL_POS to EPCIS message to trigger Import 3rd country message correctly

5. Source code objects 

...