Document History

1.    Overview

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

2.    Description

Improvements for transaction /K3TMT/SN_INFO:

• Error “Please specify Object Selection criteria” appears on press Multiple selection button at selection screen if both fields Object code (EPC) and Object code (EPC) -multiple are empty. Empty control logic for object code is corrected.

Implementation error

Improvements for transaction /K3TMT/REP_MONITOR:

• New selection screen fields added: Global Location Number, GLN Extension

• New fields added into report header ALV grid: Location name

• New function “Change ISMT GUID” added into report item ALV grid toolbar to change report ISMT GUID after data correction process at ISMT system. To use this function report header and item must be in error status and document from ISMT system for old ISMT GUID and new ISMT GUID must be identical.

• Allow sum for column SGTIN qty at report header ALV grid

• Cancel button change status of confirmed report item due to ABAP code error. Logic corrected to ignore confirmed part.

New feature

Improvements for transaction /K3TMT/RCP_MONITOR:

• Translation to language RU for selection screen fields skipped – translations added

• Function “Display document summary” and “Download document summary” return different JSON file – error in ABAP code

• If Configuration ID field is not specified on selection screen no data is displayed

Implementation error.

DISAGGREGATION_DOCUMENT report is not created for empty SGTIN object. Report creation logic was corrected to allow:

• Use SGTIN object at DISAGGREGATION_DOCUMENT report

• Empty object allowed for DISAGGREGATION_DOCUMENT report. New parameter NTF_ALLOW_EMPTY_AGGR = X added to allow aggregation with empty parent object.

• Change rule customizing via transaction /K3TMT/CUST – change mapper class for report DISAGGREGATION_DOCUMENT to new class /K3TMT/CL_UNPACK_ML_MAPPER

New feature.

Support SGTIN object with existing hierarchy output as KITU with children at LP_INTRODUCE_GOODS report. Report LP_INTRODUCE_GOODS structure corrected to support child objects for KITU.

The following customizing needs to be done:

• Add new parameter ITM_AGGR_CHECK_TYPE = 1 via transaction /K3TMT/PARAM. (This parameter defines how system analyzed SGTIN object is parent object for other SGTINs: 1 – GTIN attribute ZRU_AGGR_SGTIN expected; 2 – Check current SGTIN has child object at object hierarchy)

• Add new attribute ZRU_AGGR_SGTIN into view /STTP/V_PROPNAME via transaction SM30

• Fill GTIN attribute ZRU_AGGR_SGTIN = X for GTINs need to be displayed as KITU

• Change rule customizing via transaction /K3TMT/CUST – change mapper class for report LP_INTRODUCE_GOODS to new class /K3TMT/CL_INT_G_ML_MAPPER

New feature.

Rule selection from /K3TMT/CONF transaction works incorrectly for event containing objects with different industries due to ABAP code error.

Implementation error.

Sequence check logic corrected to delete objects from sequence check table after report confirmation from ISMT system.

Implementation error.

Necessary structures and customizing for ISMT report FTS_INTRODUCE_DOCUMENT support added. Mapper class example /K3TMT/CL_FTS_INT_MAPPER added but own class implementation required to fill notification fields correctly. Activate BC set /K3TMT/CUST_ISMT_300_2022_01_03 using transaction SCPR20.

New feature.

Documents with ISMT status “IN_PROGRESS” received from ISMT system with program /K3TMT/UD_IN not updated after first download. New logic added to check and update status until document final status. Documents with creation time from week ago to now processed with this status check logic. This overlap value could be redefined with custom value using transaction /K3TMT/PARAM (parameter name UD_IN_PROCESS_OVERLAP, parameter value – overlap value in seconds).

New feature.

True API version 4 support added but will not be implemented automatically – manual activities are required.

Both connector part corrections required connector cloud part and connector ABAP part.

In order to setup correct service paths for communication with ISMT system using True API for all industries revision 600 you should update customizing via SM30.

Steps:

1. Start transaction SM30.

1. Enter view name /STTP/V_RSRVPATH , press Maintain.

1. Make the following changes for entries with all industries, RU System NTF , System Rev 600, REST operations CREATE_DOCUMENT, ZZGET_CISES_AGG_LIST, ZZGET_CISES_INFO, ZZGET_CIS_INFO, ZZGET_DOCUMENTS, ZZGET_DOCUMENT_INFO, ZZGET_RECEIPT_INFO, ZZGET_RECEIPT_LIST, ZZGET_UTD_INFO

(for more convenience you could press Selection->By contents and enter all needed restrictions:

Industry = FS

RU Reporting System = NTF

AND RU System Revision = 600 )

CREATE_DOCUMENT        /api/v3/true-api/lk/documents/create?pg=lp

ZZGET_CISES_AGG_LIST    /api/v3/true-api/cises/aggregated/list

ZZGET_CISES_INFO /api/v3/true-api/cises/info

ZZGET_CIS_INFO    /api/v3/true-api/cises/list

ZZGET_DOCUMENTS        /api/v3/true-api/doc/listV2

ZZGET_DOCUMENT_INFO           /api/v3/true-api/documents/{document_id}/info

ZZGET_RECEIPT_INFO      /api/v3/true-api/receipt/{receiptId}/info

ZZGET_RECEIPT_LIST        /api/v4/true-api/receipt/list

ZZGET_UTD_INFO  /api/v3/true-api/documents/edo/tpr/ud

Industry = other value (for example TR)

RU Reporting System = NTF

AND RU System Revision = 600 )

CREATE_DOCUMENT        /api/v3/true-api/lk/documents/create?pg=tires

Repeat for other industry by setting create?pg=  own value for each industry

Open

New feature

3.    Solution

Import related to the transport request.

3.1    Correction instruction ATTP 3.0

3.2    Correction instruction ATTP 3.1

4.    Recommendation

Activate BC set /K3TMT/CUST_ISMT_300_2022_01_03 using transaction SCPR20.

Perform manual activities from True API version 4 support part of description section.

Test corrections from description section

5. Source code objects