Document History

1.    Overview

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

2.    Description

The aggregation message (911, 912, 913, 914, 915) objects not deleted from the table /K3T/RU_MSG_OBJ after successful confirmation from MDLP. The number of entries is growing in the table /K3T/RU_MSG_OBJ and causing performance issues during the sequence check.

The deletion of entries in the table /K3T/RU_MSG_OBJ for aggregation message (911, 912, 913, 914, 915) is implemented instead of updating the field DELFLAG = X.

The parts of the same 915 message will be deleted together after all parts successfully confirmed from MDLP.

The updating logic with setting DELFLAG = X for non-aggregation message is not changed because messages can be canceled with 250, 251, 252 and object MDLP status must be set to the old value.

Program /K3T/RU_MDLP_CLEANUP selection screen new field “With Delete flag only” added into block “Temporally stored data”. This option allows to delete message objects based on expiry period without delete flag check.

The new logic with deletion can be deactivated with parameter /K3T/DEL_CONF_MSG_OBJ_INACTIVE = X in the transaction /K3T/RU_PARAM.

New feature.

Note version 2.0 contains in additional corrections below.

Program /K3T/RU_MDLP_CLEANUP causing performance issues during the temporary object deletion.

Additional indexes implemented into database tables /K3T/RU_LM_ITM, /K3T/RU_MON_H, /K3T/RU_MSG_OBJ, /K3T/RU_R_TSK.

Program /K3T/RU_MDLP_CLEANUP selection screen new field “Delete Package size” added into block “Selection Criteria”. This option allows to split data before performing DELETE database operation into fixed packages to reduce database workload.

Implementation error.

Program /K3T/RU_MDLP_CLEANUP selection screen new block “MDLP analytic tasks” added into block “Selection Criteria”. This option allows to cleanup MDLP analytic reporting data. The following parameters available for selection:

• “Delete data older as days” – restrict task selection period with today – days. Task selection logic is based on task requested date.

• “Clear ZIP” – clear ZIP field at the MDLP analytic task data (table /K3T/RU_R_TSK)

• “Delete analytic tasks/requests” – delete MDLP analytic task data (table /K3T/RU_R_TSK) together with request data (/K3T/RU_R_REQ)

• “Including result table” – delete MDLP analytic result tables (/K3T/RU_R_MD, /K3T/RU_R_RM) on delete analytic tasks step

New feature.

Sequence check log via transaction /K3T/RU_MONITOR contains a lot of successful entries and warning “Memory low. Leave the transaction before taking a break” appears on display log. Maximum log entries have been restricted with default value 50 (for each report item). This value could be redefined using parameter /K3T/RU_MAX_LOG_INFO_ROWS in the transaction /K3T/RU_PARAM. If parameter is not specified default value 50 used.

Implementation error.

In case reporting rule was triggered using “Retrigger rule” button via /STTP/COCKPIT transaction and reporting event has not been created due to some reason reporting event from previous rule execution for this event used to set status of monitor entry.

Implementation error.

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

3.4    Correction instruction ATTP 3.1

4.    Recommendation

Execute report /K3T/RU_MDLP_CLEANUP regularly with variant for deletion temporally stored data to reduce the table space and improve performance for the sequence check.

Open

5.    Source code objects