Content Comparison

Note

Description

Category

2021_03_1

New option implemented to display information about installed MDLP Connector software version via transaction /K3T/RU_MONITOR. New button “Software Version” added into header ALV toolbar

Software component K3T assigned for packages /K3T/REP_RU, /K3T/REP_RU_SRV as part of SAP certification preparation

New feature

2021_03_2

Function “Reset processing status” at transaction /K3T/RU_MONITOR works incorrectly:

• Header status is not changed.

• After successful processing message still blocks sequence queue.

Function “Repeat message sending” at transaction /K3T/RU_MONITOR works incorrectly in case connection problem to MDLP occurs on message sending.

Error

2021_03_3

Function “Sequence check” works incorrectly for message 915 in case other message with early operation date exists with the same top-level SSCC, the part of SGTIN-SSCC is send before another message with early operation date.

Single run protection in program /K3T/RU_MDLP_IN works incorrectly

Error

2021_03_4

Runtime error on program /K3T/RU_OMS_TOKEN when program run first time if more than one OMS system is configured for dynamic token.

In some cases, BR_CRYPTO_COMM reporting event failed with token related error.

New option added into program /K3T/RU_OMS_TOKEN to execute ping specified system. Ping result is available at SLG1 application log

New feature

2021_03_5

New option added to program /K3T/RU_MDLP_CLEANUP to delete logistic monitor data

New feature

2021_03_6

Operation date is calculated incorrectly for message 313 created based on rule type Z3K_313: current date time used instead of event date time

Error

2021_03_7

New mode “API request” added into transaction /K3T/RU_MDLP_SN_INFO with support multiple EPC code input for mass MDLP status update

New feature