ISMT Release 2022_02
Document History
Version | Changes | Effective Date |
1.0 | First approved version 3Keys ISMT Add-On release 2022_02 | 01-May-2022 |
1. Overview
This document describes changes in the 3Keys ISMT connector ABAP part.
2. Notes
Note | Description | Category |
Runtime error HTTP_NO_MEMORY occurs on multiple serial number info requests from ISMT system via True API. ABAP code corrected to close connection explicitly after each REST client call. Implementation error. Corrections for transaction /K3TMT/UD_MONITOR:
Implementation error. After approve message function via transaction /K3TMT/REP_MONITOR lock is not released if user press Cancel after sequence check warning. Implementation error. User interface improvements of default processing logic for selection screen fields containing date/time when “Date from” or “Date to” value is empty.
This correction includes transactions /K3TMT/REP_MONITOR (fields “Date From/To”, “Operation Date From/To”, “Received Date From/To”), /K3TMT/UD_MONITOR (fields “Document Date From/To”, “Invoice Date From/To”, “Received Date From/To”), /K3TMT/RCP_MONITOR (fields “Document Date From/To”, “Received Date From/To”). Implementation error. | Implementation error | |
Some universal documents skipped on first inbound universal document download with program /K3TMT/UD_IN because of the limit parameter on True API request. Default limit value is 1000. This default value now could be redefined with custom value using transaction /K3TMT/PARAM (parameter name UD_IN_LIST_LIMIT, parameter value – integer value. Maximum allowed value is 10000 according to True API documentation). New maintenance view /K3TMT/V_FLTR_IN created to change universal document overlap value without transport request. Maintenance view can be started via transaction SM30. | New feature, Implementation error | |
Runtime error DBSQL_DBSL_LENGTH_ERROR occurs on background program /K3TMT/RESPONSE execution. Report was sent to ISMT system successfully and received error status on ISMT system side. Runtime error occurs when report response is trying to be processed via background program /K3TMT/RESPONSE. The reason is the error text field could not be stored at database table as it exceeded maximum length limit 1300 characters. The following correction is implemented: if error text field exceeded 1300 characters error text will be stored as “First 1297 error text characters”+ “…”. Implementation error. ISMT status is not updated for report SGTINs after receiving correct response (status CHECKED_OK) from ISMT system. Implementation error. Runtime error DBSQL_DBSL_LENGTH_ERROR occurs on report sending with Approval button via transaction /K3TMT/REP_MONITOR. Report was trying to be sent to ISMT system but received error from ISMT system. Runtime error occurs on response processing. The reason is the error text field could not be stored at database table as it exceeded maximum length limit 1300 characters. The following correction is implemented: if error text field exceeded 1300 characters error text will be stored as “First 1297 error text characters”+ “…”. | New feature, Implementation error |
3. Transport request ATTP 3.0
The transport request D14K900241 includes the release notes RN_2022_02 for ATTP 3.0 with following list of implemented notes.
Note: The transport request D14K900226 (RN_2022_01) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2022_02_1 | D14K900229 | D14K900226 | 21-Feb-2022 |
2022_02_2 | D14K900231 | D14K900226 | 14-Mar-2022 |
2022_02_3 | D14K900239 | D14K900226 | 20-Apr-2022 |
4. Transport request ATTP 3.1
The transport request D13K900037 includes the release notes RN_2022_02 for ATTP 3.1 with following list of implemented notes.
Note: The transport request D13K900030 (RN_2022_01) is a prerequisite for the import
Note | Transport | Prerequisites | Release date |
2022_02_1 | D13K900032 | D13K900030 | 21-Feb-2022 |
2022_02_2 | D13K900033 | D13K900030 | 14-Mar-2022 |
2022_02_3 | D13K900036 | D13K900030 | 20-Apr-2022 |