Document History

1. Overview

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

2. Description

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

• Header status is not changed.

• After successful processing message still blocks sequence queue.

After correction header status will be changed to:

• Processing if message has only one part

• If message has more than 1 part:

o   Scheduled if all other parts has status scheduled.

o   Recalled if status was reset for 250/251/252 message.

o   Processing for all other cases.

After successful processing message will not block sequence queue.

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

• Header status is different from message status (header status scheduled and message status error).

• When trying to “Reset processing status”, the following message is displayed:

Message locked by other process. Started by user USER1 at 04.06.2021 12:53:18 (MonId XYZ)

Message no. /K3T/REP_RU098

USER1 is the User ID who is executing the Reset (not background job user).

Implementation error.

After correction additional change log line appears for action “Send document” to inform user about connection issue (field name “OPERATION_RESULT” field value “MDLP connection issue”). Header and message status are not changed. Lock is deleted correctly, and it is possible to perform function “Repeat message sending” or “Reset processing status”.

Open

3. Solution

Import related to the transport request.

3.1 Correction instruction FP04

3.2 Correction instruction FP05

3.3 Correction instruction ATTP 3.0

4. Recommendation

Test functionality “Repeat message sending” and “Reset processing status”

5. Source code objects