Version

Changes

Effective Date

1.0

First approved version

3Keys MDLP Add-On release 2022_03

01-Aug-2022

Note

Description

Category

2022_03_1

Functionality MDLP Analytic reporting works incorrectly after MDLP release April 2022. The following corrections have been implemented:

Selection screen field “Max wait time after creation (sec)” type changed to allow input more than 999 seconds

Delay for task creation operation changed from 1 seconds to 30 seconds (New parameters /K3T/MDLP_API_TSK_HRY_DELAY, /K3T/MDLP_API_TSK_MDP_DELAY, /K3T/MDLP_API_TSK_REM_DELAY with value 30 shall be maintained in the transaction /K3T/RU_PARAM)

Error code TASK_LIMIT_EXCEEDED changed to USER_TASK_LIMIT_EXCEEDED and MEMBER_TASK_LIMIT_EXCEEDED

Status “No data” logic corrected to set status not only on task creation but on task control status. If created task returns status “FAILED” plus error text “No data are found for the parameters specified.” Or “Выгрузка не создана. По указанным параметрам не найдено данных.”. To add new error text value for status “No data” new parameters: /K3T/MDLP_API_TSK_NO_DATA_TXT1, /K3T/MDLP_API_TSK_NO_DATA_TXT2, /K3T/MDLP_API_TSK_NO_DATA_TXT3, /K3T/MDLP_API_TSK_NO_DATA_TXT4 shall be maintained in the transaction /K3T/RU_PARAM. Result error text will be combined as text1+text2+text3+text4.

New selection screen field “Queue processing method” added. Available values:

1 - “FIFO” (default value) means task will be processed in order task have been created.

2 - “Create if slot is available” means program will create new task after each successful task result processing when free slot is available at MDLP side (to minimize wait time between task creation)

New field “Branch ID” is requested from MDLP for report types “Remaining medicines” and “Medicine disposal”

New selection screen field “Retry after max wait times” added into new selection screen block “Task response wait options” with the following processing logic:

Each task created at MDLP system existing without final status (COMPLETED or ERROR) is checked for processing time (task creation time at MDLP + “Max wait time after creation (sec)” is less than time now). In case task processing time is more than “Max wait time after creation (sec)” seconds task processing is stopped by program and task is deleted from MDLP with error “Maximum response time reached. Setting error status”. For each task now new internal max wait time counter implemented to create new task at MDLP instead of stop task processing if counter value is less than “Retry after max wait times”.

Corrections for report types “Remaining medicines” and “Medicine disposal”:

New selection screen fields “Determine lot” and “Maximum Task Lots” added into transactions /K3T/RU_MAR_SCD_MD and /K3T/RU_MAR_SCD_RM. In case one of the following fields “Lot number” criteria or “Determine lot” check box or “Exclude expired Batch” checkbox is selected program selects all lot numbers for each GTIN from SAP system with additional check at least serialized item exists for lot. Selected lots are splitted into groups for each GTIN with maximum lot numbers equal to “Maximum Task Lots” parameter. New MDLP API task creates for each group.

Selection screen validation control implemented for transaction /K3T/RU_MAR_SCD_MD Task scheduler Medicine disposal.

Selection screen validation control implemented for transaction /K3T/RU_MAR_SCD_RM Task scheduler Remaining medicines.

New report type “Pricing Report” added to request price information from MDLP system using the common approach for MDLP analytic reporting

New feature

2022_03_2

New inbound MDLP document types support added according to MDLP schemes 1.37-1.38.

The following MDLP document types corrected:

• 601-move_order_notification

• 602-receive_order_notification

• 623-change_property_notification

• 627-posting_notification

The following MDLP document types created:

• 629-move_place_notification

• 630-move_state_dispatch_notification

• 631-successor_acceptance_notification

• 632-expired_writeoff_notification

• 633-attention_notification

• 634-move_place_all_notification

New BC sets /K3T/CUST_MDLP_300_2022_03_02 (3Keys MDLP Add-On Note 2022_03_02) and /K3T/CUST_MDLP_3_1_2022_03_02 (3Keys MDLP Add-On 3.0 Note 2022_03_01) include all customizing for new created document types.

New selection screen fields “Gov Contract Number” and “Gov Contract Date” added into transaction /K3T/RU_CREATE_NTF Create Reporting Notification for RU block Notification 601

New feature

2022_03_3

Transaction /AIF/ERR contains error messages for rule execution (Namespace /STTEO Interface RULES_GEN Version 1) with log messages about runtime error inside AIF processing function module.

Log message part example:

Error UNCAUGHT_EXCEPTION (1F09B73915F6B64SE10000000A11447B) when calling /STTP/AIF_PROCESS_...

Line 1 in /K3T/CL_RR_RU_UTILS===========CM01H (/K3T/CL_RR_RU_UTILS===========CP)

An exception with the type CX_SY_ITAB_LINE_NOT_FOUND was raised, but was not handled locally or declared in a RAISING clause

The error reason is the ABAP code to determine fields “Subject ID”/”Config ID” for transaction /K3T/RU_MONITOR entry created with error status. MDLP document type 911 was not expected, and additional logic added to process MDLP document types 911, 912, 913, 914, 915.

Error

2022_03_4

In some scenarios transaction /K3T/RU_MONITOR contains message 342 with incorrect field values quantity SGTIN, quantity SSCC in case message contains more than one item.

New menu item “Special Functions” added into transaction /K3T/RU_MONITOR menu with new child item “Recalc. Header Qty”.

Processing logic:

• Execute authority check for object /K3T/RU001 field /K3T/RU001 value 28

• Get all MDLP items for selected document header

• Calculate SGTIN quantity and SSCC quantity extracted from AIF reporting event

• Update document header fields SGTIN quantity, SSCC quantity, modified user, modified time

• Create change document log with action “Recalculate header Qty”

Error

2022_03_5

In some scenarios response from MDLP system for notification with several parts at item level contains MDLP API status “NO_DOCUMENT_IN_MDLP” and operation result “Rejected” for message part. In this case message change status to “40-Error” at transaction /K3T/RU_MONITOR and automatic message sending is blocked due to error message. At the same time Response XML contains correct XML with operation result “Confirmed”. To correct message status function “Reset processing status” is used and response is received again with correct status but further messages do not send automatically

Error

Note

Transport

Prerequisites

Release date

2022_03_1

AT1K900965

AT1K900937

22-Jul-2022

2022_03_2

AT1K900945

AT1K900937

11-Jul-2022

2022_03_3

AT1K900947

AT1K900937

21-Jun-2022

2022_03_4

AT1K900963

AT1K900937

19-Jul-2022

2022_03_5

AT1K900967

AT1K900937

27-Jul-2022

Note      

Transport

Prerequisites

Release date

2022_03_1

D1AK900450

D1AK900428

22-Jul-2022

2022_03_2

D1AK900444

D1AK900428

11-Jul-2022

2022_03_3

D1AK900434

D1AK900428

21-Jun-2022

2022_03_4

D1AK900448

D1AK900428

19-Jul-2022

2022_03_5

D1AK900452

D1AK900428

27-Jul-2022

Note      

Transport

Prerequisites

Release date

2022_03_1

A1DK900330

A1DK900272

22-Jul-2022

2022_03_2

A1DK900324

A1DK900272

11-Jul-2022

2022_03_3

A1DK900313

A1DK900272

21-Jun-2022

2022_03_4

A1DK900329

A1DK900272

19-Jul-2022

2022_03_5

A1DK900333

A1DK900272

27-Jul-2022

Note      

Transport

Prerequisites

Release date

2022_03_1

A2DK900293

A2DK900213

22-Jul-2022

2022_03_2

A2DK900285

A2DK900213

11-Jul-2022

2022_03_3

A2DK900273

A2DK900213

21-Jun-2022

2022_03_4

A2DK900289

A2DK900213

19-Jul-2022

2022_03_5

A2DK900297

A2DK900213

27-Jul-2022