Versions Compared

Version Old Version 1 New Version Current
Changes made by

Denis Zolotarev

Denis Zolotarev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Version

Changes

Effective Date

1.0

First approved version

3Keys MDLP Add-On release 2023_0102

01-FebMay-2023

1. Overview

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

2.   Notes

Note

Description

Category

2023_0102_1New BC

Set Function module /K3T/CUST_MDLP_3_2 Short Text: 3Keys MDLP Add-On 3.2 created

Software Component K3T 3Keys CRPT Connector Add-On Release changed to 302

New feature

2023_01_2

New function “Confirm message” added into transaction /K3T/RU_MONITOR - Russia reporting monitor to finish message processing manually without response from MDLP system. New menu item is created for menu “Special functions“.

Processing logic:

  • Check authority for object /K3T/RU001 field /K3T/RU001 value “29”.

  • Check message status is 20-Sent (item level)

  • Display warning PopUp to the user

  • Add new entry to the Change Log with action “User message confirmation”

  • Finish message processing by positive MDLP response emulation

New feature

2023_01_3

Function “Recalculate Header Quantity“ RU_AIF_IN_RETURN_SCN2 provided with Note 2023_01_4 works incorrectly due to ABAP code error. In some scenarios transaction /AIF/ERR contains the following log text:

  • “Failed validation: MDLP/ATTP hierarchies for object &1 have differences“

  • Several log messages to save error text “Error UNCAUGHT_EXCEPTION (1F09B73915F6B645E10000000A11447B) when calling /K3T/RU_AIF_IN_GEN
    Line 1 in /K3T/CL_RR_RU_UTILS===========CM00K (/K3T/CL_RR_RU_UTILS===========CP)
    An exception with the type CX_SY_CONVERSION_OVERFL OW was raised, but was not handled locally or decl
    ared in a RAISING clause.
    An exception of type 'CX_SY_CONVERSION_OVERFLOW' o ccurred, that was not caught anywhere in the call
    hierarchy. It was not handled locally or declared using a RAISING clause.
    Line 69 in /K3T/CL_RR_RU_UTILS===========CM00K (/K3T/CL_RR_RU_UTILS===========CP)
    Overflow converting from '256'
    The attempt to convert '256' returned a value whic h lies outwith the valid value range. This resulte
    d in an overflow.
    Error when calling /K3T/RU_AIF_IN_GEN”

Error

2023_02_2

Function “Navigate to Reporting event” works incorrectly at transaction /K3T/RU_MONITOR implemented with MDLP Note 2022_03_4 works incorrectly for message 915 in case message contains more than one item.After correction SSCC quantity displays total number of unique SSCC from all 915 message parts.“Russia MDLP Monitor”. Problem occurs at ATTP version 3.1 and 3.2

Error

2023_0102_4New function module 3

Function “Reset processing status” works incorrectly at transaction /K3T/RU_AIF_IN_RETURN_SCN2 created to process inbound message 601 with turnover type “2”-return (In case turnover type is different from “2” function module /K3T/RU_AIF_IN_SCN is called). The following object processing is supported:

  • SGTIN

  • SSCC as originally shipped

  • SSCC unpacked from originally shipped SSCC

  • SSCC with less SGTINs as originally shipped

Unknown SSCC in ATTP will not be accepted and raise error.

For each SSCC current hierarchy from MDLP system is requested and compared with actual hierarchy at SAP ATTP system. In case SGTIN or SSCC exists at SAP ATTP and absent in MDLP hierarchy unpacking event is added to EPCIS message

New featureMONITOR “Russia MDLP Monitor” for message containing more than 2 items in status 20-Processing. As a result message has header status 20-Processing (instead of status 10-Scheduled) and dispatcher program ignores message.

Logic for multiple request message 211 from MDLP system works incorrectly due to ABAP code error. Additional validation control for correct XML added. In case incorrect XML is received repeat message request is executed.

Error

3.    Transport request ATTP 3.0

The transport request A1DK900434 A1DK900498 includes the release notes RN_2023_01 02 for ATTP 3.0 with following list of implemented notes.

Note: The transport request A1DK900392A1DK900434 (RN_20222023_0401) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2023_0102_21

A1DK900397A1DK900436

A1DK900392A1DK900434

1514-NovFeb-20222023

2023_0102_32

A1DK900401

A1DK900392

23-Nov-2022

N/A

2023_0102_43

A1DK900430A1DK900486

A1DK900392A1DK900434

2604-JanApr-2023

4.    Transport request ATTP 3.1

The transport request A2DK900463 A2DK900519 includes the release notes RN_2023_01 02 for ATTP 3.1 with following list of implemented notes.

Note: The transport request A2DK900359A2DK900463 (RN_20222023_0401) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2023_0102_21

A2DK900367A2DK900471

A2DK900359A2DK900463

1514-NovFeb-20222023

2023_0102_32

A2DK900384A2DK900479

A2DK900359A2DK900463

2321-NovFeb-20222023

2023_0102_43

A2DK900459A2DK900501

A2DK900359A2DK900463

2604-JanApr-2023

5.    Transport request ATTP 3.2

The transport request A3DK900095 A3DK900132 includes the release notes RN_2023_01 02 for ATTP 3.2 with following list of implemented notes.

Note: The transport request A2DK900359A3DK900095 (RN_20222023_0401) is a prerequisite for the import

Note      

Transport

Prerequisites

Release date

2023_0102_1

A3DK900035

MDLP Release 2022_04

15-Nov-2022A3DK900099

A3DK900095

14-Feb-2023

2023_0102_2

A3DK900031

MDLP Release 2022_04

15-Nov-2022A3DK900107

A3DK900095

21-Feb-2023

2023_0102_3

A3DK900044

A2DK900031 or SAPK-302COINK3T

23-Nov-2022

2023_01_4

A3DK900093

A2DK900031 or SAPK-302COINK3T

26-Jan-A3DK900118

A3DK900095

04-Apr-2023

View file
nameATTP30_Release_2023_0102_3Keys_MDLP_Connector.zip
View file
nameATTP31_Release_2023_0102_3Keys_MDLP_Connector.zip
View file
nameATTP32_Release_2023_0102_3Keys_MDLP_Connector.zip

...