Document History

 1.     About This Guide

This document describes User transactions in the 3Keys CRPT connector MDLP in the SAP ATTP system.

2.     Solution overview

SAP ATTP delivers a solution to generate the reporting messages for the Russian MDLP system. The 3Keys CRPT connector MDLP automates the communication and message transfer to the Russian MDLP system, visualizes the message processing status with a monitoring transaction, downloads and processes the incoming MDLP messages in SAP ATTP. 

3.     MDLP cockpit transaction /K3T/RU_MONITOR

The MDLP cockpit transaction /K3T/RU_MONITOR is used for the monitoring of Russia reporting (it shows all messages going from SAP ATTP to MDLP through the ‘3Keys CRPT connector MDLP’ and also messages coming back to SAP ATTP through the connector).

After executing transaction /K3T/RU_MONITOR, the screen will be displayed with following selection parameters:

• Processing status: Message processing status of the incoming and outgoing MDLP messages

• MDLP Document Type: MDLP document type

• MDLP Document GUID: This GUID has been assigned by MDLP to the message, user can enter document GUID (a unique number assigned to message) to search the message

• Subject ID: Subject ID in the MDLP XML message

• Object Code (EPC): SGTINs or SSCC can be entered.

• Message ID: AIF GUID assigned to the message

• Document Number (XML): Document number in the MDLP XML message

• Approver: Message approver

• MDLP Configuration ID: Configuration ID assigned to the message

• GS1 Global Trade Item Number: GTIN

• Lot Number: Lot/Batch number

• Document Number (Bus.trans.): Linked business transaction document number to the message

• Document Year (Bus.trans.): Linked business transaction document year to the message

• Counterparty: Counterparty business partner

• Date From: Message creation interval from

• Date To: Message creation interval to

• Operation Date From: MDLP XML operation date from

• Operation Date To: MDLP XML operation date to

• Inbound messages: Select inbound messages

• Outbound messages: Select outbound messages

• Maximum Hits: Maximum amount messages to be selected

After executing the transaction, a new screen (MDLP reporting cockpit) will be displayed, and the message information will be shown based on the search criteria.

The screen has two parts. On the top of the screen the message header is shown, on the lower part the messages related to the header are displayed after a double click on the header row.

The message header has the following fields (some of the fields are hidden and can be displayed by changing the ALV Grid layout):

• Direction: Inbound or Outbound message as icon

• Status: Message processing status as icon

• MDLP Document Type

• Created on: Message header creation time converted into user time zone

• Operation Date (User Timezone): MDLP XML operation date converted into user time zone

• Changed on: Message header last changing time converted into user time zone

• Quantity SGTIN: Amount of SGTIN objects in all messages related to the header

• Quantity SSCC: Amount of SSCC objects in all messages related to the header

• Global Trade Item Number: GTIN or word Multiple in case multiple GTINs included in the message

• Lot Number: Lot/Batch number or word Multiple in case multiple Lots included in the message

• Trade Item Description: GTIN description

• Processing status: Message processing status

• Subject ID: MDLP XML Subject ID

• MDLP Configuration ID

• Approver: Message approver

• Approver Group: Message approver group

• Doc.N.(BT): Document number business transaction

• Doc.Yr.(BT): Document year business transaction

• Counterparty ID: Counterparty Subject ID

• Business Partner Number: Counterparty business partner number

• Business Partner Name: Counterparty business partner name

• Message Date (Sorted By): Message creation date as sorting parameter for sending check

• Changed by: Message changed user

• Created by: Message creation user

• Event Internal Identifier: Event GUID

• Message ID: Message header GUID

• Reporting Event Internal Identifier: Reporting event GUID

The header row needs to be selected to execute one of the following buttons on top of the screen (some of the buttons can be hidden, this is depending on the user authorization role and on parameters):

• Refresh: Refresh shown entries based on selection screen values

• ALV Grid standard buttons to filter, to sort, to search displayed data, changing layout, printing

• Cancel: The message header with all related messages will be canceled

• Approval: The message header will be approved for sending. The sequence check will be executed, and Popup warning window can appear for confirmation of skipping the sequence check.

• Change Operation Data: A Popup window to change the message operation date/time to current date/time or to a manually entered new operation date/time appears.

• Maintain Missing Data: A Popup window to enter missing data in the message appears. Prerequisite is that the message processing stopped in status 05-missing data or 45-Error missing data.

• Sequence Check: Displays the log of the sequence check for a selected message.

• Change Log: Displays the log of actions and field changes for the selected message.

• Navigate, Menu of functions for the selected message, this includes:

  • Display events: Navigation to the event in the ATTP Cockpit

  • Display business transactions:  Navigation to the business transactions in the ATTP Cockpit

  • Display reporting events: Navigation to the reporting event in the ATTP Cockpit

The click on GTIN or Lot Number will show a Popup with calculated quantities.

The message item has the following fields (some of the fields are hidden and can be displayed by changing ALV Grid layout):

• Direction: Inbound or Outbound message as icon

• Status: Message processing status as icon

• MDLP Document Type

• Processing status: Message processing status

• Created on: Message creation time converted into user time zone

• Operation result: MDLP operation status

• MDLP document GUID: MDLP request GUID

• MDLP message GUID: MDLP message GUID

• MDLP operation ID: MDLP operation GUID

• API MDLP status: Processing status in MDLP API

• Changed on: Message last changing time converted into user time zone

• Event Internal Identifier: Event GUID

• Message ID: Message header GUID

• AIF Message ID (Outbound): AIF message GUID

• Changed by: Message changed user

• Created by: Message creation user

The item row needs to be selected to execute one of the following buttons on the lower part of the screen (some of the buttons can be hidden, depending on the user authorization role, or message processing status or type):

• ALV Grid standard buttons to filter, to sort, to search displayed data, changing layout, printing

• Refresh: Refresh messages related to the selected header

• 250-recal: Send message 250

• 251-refusal_sender: Send message 251

• 252-refusal_receiver: Send message 252

• MDLP Message: Menu of functions for the selected message includes:

  • Display Message XML: Request message XML online from MDLP and display to the user

  • Download Message XML: Request message XML online from MDLP and store as file

  • Display Response XML: Request response XML online from MDLP and display to the user

  • Download Response XML: Request response XML online from MDLP and store as file

  • Reset processing status: Remove processing status to request processing status again from MDLP

  • Repeat message sending: Send message again to MDLP

• MDLP AIF, menu of functions for the selected message including:

  • Display Message XML: Display AIF message

  • Download Message XML: Download AIF message

  • Message AIF: Show AIF transaction

  • Display processing log: Display application log

3.1     MDLP message processing status

The MDLP message processing status defines the allowed actions for the message in the 3Keys CRPT Connector MDLP:

• 01-waiting_accept: Outbound message created and waiting of approval or is currently in processing by queue.

• 02-received: Inbound message received

• 05-missing_data: Message processing stopped and waiting for the user to maintain the missing message data to generate the reporting

• 10-queued: Message is currently in processing by the queue or the sequence check failed. You need to wait until queue is processed or that the predecessor message will be processed successfully that the sequence check will be successful. The user can manually approve the message and skip the sequence check.

• 20-sent: Message sent to MDLP system and waiting for the processing status update.

• 30-confirmed: Message successfully confirmed (end status).

• 35-partial: Message is partially confirmed by MDLP.

• 40-error: Message processed with error. Message can be resent again.

• 45-error_missing_data: ATTP reporting error, message data can be corrected by user with function “Maintain missing data” and resent again.

• 50-recalled: Message recalled in MDLP with message 250, 251, 252 (end status)

• 99-cancelled: Message is canceled by user (end status)

4.     Logistic monitor transaction /K3T/RU_MDLP_LM

The Logistic monitor transaction /K3T/RU_MDLP_LM is used to track the goods movements confirmation by a counterparty.

After executing transaction /K3T/RU_MDLP_LM, the screen will be displayed with following selection parameters:

• MDLP Configuration ID: Configuration ID assigned to the MDLP message

• Business Partner Number: Receiver business partner

• Document Number: Business transaction Document Number

• Document Year: Business transaction Document Year

• Document Number (XML): Document Number in MDLP XML

• Status Document: Document progress status

• Status Object: Object confirmation status

• EPC code: SSCC or SGTIN includes in the MDLP message

• Operation Date From: Operation date in MDLP XML

• Operation Date To: Operation date in MDLP XML

• Display mode:

  • Customer Summary: Display summary cumulated for all documents per customer

  • Delivery Summary: Display summary cumulated for all objects per delivery document

  • Delivery Details: Display list of objects sent to the customer

Delivery Details view shows the SSCC / SGTIN list with following fields:

• Status: EPC Status icon

• Delivery Number: Document number from Business transaction assigned to event

• Business Partner Name: Partner name delivery has been sent to

• EPC Status: EPC Status code

• Status (text): EPC Status text

• Document Number: Document number from XML

• MDLP Doc Type: MDLP document type

• Operation Date (User): Operation date converted into user timezone

• Changed on: Date time entry has been changed

• EPC code: SSCC / SGTIN code

• GTIN: GTIN from message

• Trade item description: GTIN description

• Lot Number: Lot number from the message

• Quantity SGTIN: Message quantity SGTIN

• Changed by: message was changed by user

• Changed by message ID: message was changed by MDLP Monitor message header GUID

• Message ID: MDLP Monitor message header GUID

• Logistic batch/lot: Reserved field to display additional field of SGTIN

• Business Partner Internal ID: Business partner GUID

The row shall be selected to execute one of the following buttons:

• Reset filter:

• Summary Customer: Display customer summary view

• Summary Delivery: Display deliver summary view

• Monitor: Navigate to the MDLP monitor

Delivery Summary view

• Status: EPC Status icon

• Delivery Number: Document number from Business transaction assigned to event

• Business Partner Name: Partner name delivery has been sent to

• EPC Status: EPC Status code

• Status (text): EPC Status text

• Document Number: Document number from XML

• MDLP Doc Type: MDLP document type

• Operation Date (User): Operation date converted into user timezone

• Changed on: Date time entry has been changed

• Shipped: number of SSCCs which have been shipped

• Opened: number of SSCCs without an answer received from the partner

• Accepted: number of SSCCs accepted by the partner

• Total rejected: number of SSCCs rejected by the the partner

• Refusal sender: 251-Refusal_sender was triggered by the sender

• Refusal receiver: 252-Refusal_receiver is done by receiver and the sender receives 606-refusal_receiver_notification

• Message ID: MDLP Monitor message header GUID

• Business Partner Internal ID: Business partner GUID

The row shall be selected to execute one of the following buttons:

• Reset filter:

• Summary Customer: Display customer summary view

• Details Delivery: Display deliver details for selected summary line

• Monitor: Navigate to the MDLP monitor

Customer Summary view

• Business Partner Name: Partner name delivery has been sent to

• Shipped: number of SSCCs which have been shipped

• Opened: number of SSCCs without an answer received from the partner

• Accepted: number of SSCCs accepted by the partner

• Total rejected: number of SSCCs rejected by the partner

• Refusal sender: 251-Refusal_sender was triggered by the sender

• Refusal receiver: 252-Refusal_receiver is done by receiver and the sender receives 606-refusal_receiver_notification

• Selection interval: Selection screen interval

• Business Partner Internal ID: Business partner GUID

The row shall be selected to execute one of the following buttons:

• Reset filter

• Summary Delivery: Display deliver summary view

• Details Delivery: Display deliver details for selected summary line

• Monitor: Navigate to the MDLP monitor 

4.1    Logistic monitor status

The Logistic monitor status provides information about quantity confirmation by the counterparty:

• 00–initial

• 10-sent to MDLP: Message sent to MDLP

• 20-rejected by MDLP: Message processed with error

• 30-in progress: Message successfully processed by MDLP, waiting for counterparty confirmation

• 40-accepted receiver: All SSCCs / SGTINs confirmed by counterparty

• 45-partial accepted receiver: Some of the SSCCs / SGTINs are confirmed by counterparty, waiting for the next confirmation messages

• 50-canceled: Message canceled

• 51-rejected sender: Message canceled by sender

• 52-rejected_receiver: Message cancelation received from counterparty 

5.     MLDP serial number information transaction /K3T/RU_MDLP_SN_INFO

The Serial Number information transaction /K3T/RU_MDLP_SN_INFO is used to request information about objects from MDLP.

After executing transaction /K3T/RU_MDLP_SN_INFO, the screen will be displayed with following selection parameters:

• Subject ID:

• MDLP Configuration ID: Configuration ID to send and receive MDLP message

• 210-query_kiz_info: Radio button to receive SGTIN or SSCC hierarchy information by sending a 210 message and receiving a 211 message

• 220-query_hierarchy_info: Radio button to receive SSCC hierarchy information by sending a 220 message and receiving a 221 message

Selection block 210-query_kiz_info

• SGTIN (09)GTIN(21)SN: SGTIN can be entered

• SSCC (00)SSCC get parent: SSCC can be entered to receive parent information

• SSCC (00)SSCC get hierarchy: SSCC can be entered to receive hierarchy information

Selection block 220-query_hierarchy_info

• SSCC (00)SSCC get hierarchy info: SSCC can be entered to receive hierarchy information

• Update MDLP status: execute an MDLP status update based on the received information

After executing the transaction, an XML file will be displayed in case the MDLP request was answered successfully.

If the Checkbox Update MDLP status is activated the SGTIN status is updated in the DB table /K3T/RU_MDLP_STA with the current MDLP status.

6.     Reporting Notification transaction /K3T/RU_CREATE_NTF

Regulatory Reporting Russia: Create Notification transaction /K3T/RU_CREATE_NTF is used to create notifications using the selection screen parameters.

After executing transaction /K3T/RU_CREATE_NTF, the screen will be displayed with the following selection parameters:

Block Object Selection:

·       Manual enter Radio button: Specify object codes using selection screen field

o   Object Code (EPC): Object codes to be included into message

·       Business transaction objects Radio button: use objects assigned to business transaction to include into message

o   Document number: document number for business transaction search

o   Document year: document year for business transaction search

·       Upload from file Radio button

o   File name: file upload path with search help

o   File Template button: download file template example

Block Reporting Notification:

·       702 radio button: generate message 702

·       703 radio button: generate message 703

·       601 radio button: generate message 601

·       603 radio button: generate message 603

·       613 radio button: generate message 613

Block Notification 702:

·       Subject ID: MDLP Participant GUID

·       IDNo of Taxpayer Individual: Tax number

·       Registration Reason Code

·       Document Number: Confirming document details: document number

·       Document Date: Confirming document details: document date

·       Sale Contract Type: Contract type upon sale

·       Source of Financing: Financing source types

·       Contract Number: Contract (agreement) register number in the Unified Procurement Information System

Block Notification 703:

·       Subject ID (GUID): MDLP Participant GUID

·       Customs Receiver ID (GUID): Product location identifier in the customs-controlled area

·       Document Number: Confirming document details: document number

·       Document Date: Confirming document details: document date

·       Sale Contract Type: Contract type upon sale

Block Notification 601:

·       MDLP Configuration ID: Configuration ID to send and receive MDLP message

·       Subject ID: MDLP Participant GUID

·       Receiver ID: MDLP Participant GUID

·       Document Number / Source document details: document number

·       Document Date / Source document details: document date

·       Turnover Operation Type: Type of operation of shipment from warehouse

·       Source of Financing: Financing source

·       Sale Contract Type: Contract type

·       Contract Number: Contract (agreement) register number in the Unified Procurement Information System

Block Notification 603:

·       MDLP Configuration ID: Configuration ID to send and receive MDLP message

·       Subject ID: MDLP Participant GUID

·       Document Number: Confirming source document details - number

·       Document Date: Confirming source document details - date

·       Owner ID in IS “Labeling”

Block Notification 613:

·       MDLP Configuration ID: Configuration ID to send and receive MDLP message

·       Subject ID (GUID): MDLP Participant GUID

·       Seller ID: MDLP Participant GUID

·       Receiver ID: MDLP Participant GUID

·       Customs Receiver ID (GUID): Product location identifier in the customs-controlled area

·       Sale Contract Type: Contract type

·       Document Number: Source document details: document number

·       Document Date: Source document details: document date

After executing the transaction, the program creates the notification and sends it to MDLP.

If the EPC object is not available in SAP ATTP the notification will be created without reporting event. 

7.     OMS token transaction /K3T/RU_OMS_TOKEN

The Russia OMS token transaction /K3T/RU_OMS_TOKEN is created to monitor and request OMS token periodically with the MDLP connector for systems specified in customizing table /K3T/RU_OMS_C. The OMS token will be stored in the ATTP safe storage.

After executing transaction /K3T/RU_OMS_TOKEN, the screen will be displayed with following selection parameters:

• System name: system name for dynamic token periodic processing

• OMS token lifetime in minutes: update interval based on modified time field

Block Action

• Check OMS token: Check and process OMS token

• Display OMS token: Display current OMS token value

After executing the transaction, depending on selection screen values:

• The program checks the OMS token lifetime, it requests a new token with the MDLP connector if the lifetime is exceeded and updates the token in the ATTP safe storage.

• The program display current OMS token value. 

8.     MDLP inbound message processing transaction /K3T/RU_MDLP_IN

The MDLP inbound message processing transaction /K3T/RU_MDLP_IN is used to process inbound MDLP messages uploaded from MDLP to SAP ATTP using the 3Keys Connector Java part.

After executing transaction /K3T/RU_MDLP_IN, the screen will be displayed with following selection parameters:

• MDLP Document Type: MDLP message type (for example 601)

• MDLP Configuration ID: Configuration ID assigned to the MDLP message

• MDLP message GUID: MDLP document GUID assigned to the message by MDLP

• Update status (checkbox): Update inbound message status (for example from error to received)

• Processing status: new status value to be assigned via update status option.

After executing the transaction, depending on selection screen values:

• The program updates the status of the inbound message

• The program downloads XMLs for each inbound/outbound message with status received and transfers this message to SAP AIF for further processing. The following steps executed:

• create /K3T/RU_MONITOR entry

• run specific logic given in the customizing for inbound message processing

• create reporting events for inbound/outbound message

• create initial SGTIN MDLP status for outbound messages

• check sequence queue and trigger processing if the queue is not empty

9.     Transaction /K3T/RU_MDLP_CHG_RUN

The timestamp of the last successful inbound message download from MDLP stored in the SAP ATTP. This timestamp can be adjusted with transaction /K3T/RU_MDLP_CHG_RUN.

After executing transaction /K3T/RU_MDLP_CHG_RUN, the screen will be displayed with following selection parameters:

• MDLP Configuration ID: Configuration ID assigned to MDLP message

• Set new time manually (radio button)

• Date: new date for inbound/outbound message check

• Time: new time for inbound/outbound message check

• Calculate new time (radio button): Calculate new date time based on current date time minus specified days

• Subtract days from today: Number of days to calculate new date for inbound/outbound message check

• Display actual values (radio button): Display current values of dates for inbound/outbound message check

Block Russia MDLP message check

Time: new time for inbound

• Inbound (6xx): Change date for inbound message check (for example 601 message)

• Outbound (103xx): Change date for outbound message check (for example 10311 message)

• Test run (no update):

After executing the transaction, date for inbound/outbound message check is updated and execution log is displayed.

If Checkbox Test run is activated no update is performed. 

10.     MDLP connector validation report transaction /K3T/RU_MDLP_CON_VAL

MDLP connector validation transaction /K3T/RU_MDLP_CON_VAL is used to test the MDLP connector with fixed test scenario.

After executing transaction /K3T/RU_MDLP_CON_VAL, the screen will be displayed with following selection parameters:

• MDLP Connector Java part vers: Java part version currently testing

• MDLP Connector environment: Environment currently testing, example Yandex cloud

Block Message 331

• MDLP Configuration ID: Configuration ID to send and receive MDLP message

• Subject ID (GUID): MDLP Participant GUID

• Seller ID (GUID): MDLP Participant GUID

• Receiver ID (GUID): MDLP Participant GUID

• Customs Receiver ID (GUID): Product location identifier in the customs-controlled area

• SGTIN: EPC SGTIN

• SSCC:  EPC SSCC

Block Message 613

• MDLP Configuration ID: Configuration ID to send and receive MDLP message

Block Message 252

• Subject ID (GUID): MDLP Participant GUID

• Shipper ID (GUID): MDLP Participant GUID

Block Output:

• Approver 1 name: Approver name

• Approver 1 role: Approver role

• Approver 2 name: Approver name

• Approver 2 role: Approver role

• Approver 3 name: Approver name

• Approver 3 role: Approver role

• Export log to PDF file checkbox: export execution log to PDF file

After executing the transaction, program checks the connection to the MDLP connector Java part. The serial number information will be requested from MDLP using 210/211 messages for the given SGTIN or SSCC. A 331 message is generated and send to MDLP. The incoming message 613 will be received and processed. The message 252 will be sent to cancel the 331 message.

The results can be printed or stored as PDF file a proof for a successful connectivity and message processing test. 

11.     Change or delete downloaded hierarchy message for SCN transaction /K3T/RU_211_MSG

The download MDLP message 211 XML from buffer transaction /K3T/RU_211_MSG is used to process XML received on inbound MDLP message hierarchy request.

After executing transaction /K3T/RU_211_MSG, the screen will be displayed with following selection parameters:

• MDLP message GUID: MDLP document GUID hierarchy information was requested for

• Object code (EPC): EPC code hierarchy information was requested for

• Delete checkbox: Delete stored XML

After executing the transaction, depending on selection screen values:

• Program download XML for message and object from selection screen and store as XML file using file save dialog window.

• Program deletes stored XML from the database. 

12.     Transaction /K3T/RU_MAR_MONITOR - Russia MDLP Analytics: Task monitor

The transaction /K3T/RU_MAR_MONITOR is used for the monitoring of processing the Russia analytics reports tasks.

After executing transaction /K3T/RU_MAR_MONITOR, the screen will be displayed with following selection parameters:

• MDLP Configuration ID: Configuration ID assigned to the request

• MDLP Analytics Report type: 01-SSCC Hierarchy, 02-Remaining Medicines, 03-Medicine Disposal, 04-Pricing Report, 05-General Report on Movement, 06-General Report on Disposal, 07-General Pricing Report, 08-General Report on Remaining

• Processing status: 00-New (request created), 01-Created (request ready for sending to MDLP), 10-Sent to MDLP (request sent to MDLP), 20-Ready (results downloaded from MDLP), 30-Completed (processed with report /K3T/RU_MAR_TASK_EXEC), 40-Error (error in processing), 50-Canceled (canceled by user), 60-No data in MDLP (request for filter criteria has no data in MDLP)

• Error code: Processing error code

• MR Request Internal Identifier: Internal request GUID

• MR Task Internal Identifier: Internal task GUID

• Request created From / Request created To: Time of request creation

After executing the transaction, a new screen (Russia MDLP Analytics: Task monitor) will be displayed, and the task information will be shown based on the search criteria as ALG Grid with following fields (some of the fields are hidden and can be displayed by changing the ALV Grid layout):

• Status and Status Icon

• Report type and Report type description

• Configuration ID

• Created time: Time of task creation

• Retrieval completed: Time of downloading results from MDLP

• Task filter: first 100 characters of the request filter

• Error code: Processing error code

• Error text: Processing error text

• Period type: Month or Week

• Period From: First day of Period specified on task schedule

• Period To: Last day of Period specified on task schedule

Following buttons on top of the screen shown (some of the buttons can be hidden, this is depending on the user authorization role):

• Refresh: Refresh shown entries based on selection screen values

• Change status: Update task processing status manually

• Display request: Display request sent to MDLP

• Download result: Download stored result zip file

• Add ZIP: Upload zip file as result, troubleshooting or test purposes

• MDLP Queue: Request from MDLP and display open tasks

• Delete MDLP task: Delete task at MDLP with ID from Popup window

• MDLP ZIP: Download general report data from MDLP with ID from Popup window

13.     Transaction /K3T/RU_MAR_SCD_MD - Task scheduler Medicine disposal

The transaction /K3T/RU_MAR_SCD_MD or report /K3T/RU_MAR_SCD_MD can be executed by user or as background job to request Medicine disposal report from MDLP.

After executing transaction /K3T/RU_MAR_SCD_MD, the screen will be displayed with following selection parameters:

• Start date / End date: Request filter parameters

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• Lot number: Restriction for the Lot numbers

• Exclude expired Batch: check Expiry Data on the Lot and exclude from the request

• Determine Config ID radio button: Get Configuration ID based on Subject ID from the business partner based on GTIN parameter BR_OWNER_GLN

• Use MDLP Fix Config ID radio button:  Use fix Configuration ID for the requests to MDLP

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Get Lot numbers from selection screen or all batches for the GTIN excluding expired if parameter set on the selection screen.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters with split by 90 days if Start/End date interval excide 90 days.

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 3 shall be implemented to overwrite standard selection logic.

14.     Transaction /K3T/RU_MAR_SCD_RM - Task scheduler Remaining medicines

The transaction /K3T/RU_MAR_SCD_RM or report /K3T/RU_MAR_SCD_RM can be executed by user or as background job to request Remaining medicines report from MDLP.

After executing transaction /K3T/RU_MAR_SCD_RM, the screen will be displayed with following selection parameters:

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• Lot number: Restriction for the Lot numbers

• Exclude expired Batch: check Expiry Data on the Lot and exclude from the request

• Determine Config ID radio button: Get Configuration ID based on Subject ID from the business partner based on GTIN parameter BR_OWNER_GLN

• Use MDLP Fix Config ID radio button:  Use fix Configuration ID for the requests to MDLP

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Get Lot numbers from selection screen or all batches for the GTIN excluding expired if parameter set on the selection screen.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 2 shall be implemented to overwrite standard selection logic.

15.     Transaction /K3T/RU_MAR_SCD_SH - Task scheduler SSCC / SGTIN data

The transaction /K3T/RU_MAR_SCD_SH or report /K3T/RU_MAR_SCD_SH can be executed by user or as background job to request SSCC / SGTIN report from MDLP.

After executing transaction /K3T/RU_MAR_SCD_SH, the screen will be displayed with following selection parameters:

• Serialized Trade item: SGTIN list

• Serialized Container: SSCC list

• MDLP Configuration ID

The report will create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 1 shall be implemented to overwrite standard selection logic.

16.     Transaction /K3T/RU_MAR_SCD_PR - Task scheduler Pricing Report

The transaction /K3T/RU_MAR_SCD_PR or report /K3T/RU_MAR_SCD_PR can be executed by user or as background job to request Pricing information from MDLP.

After executing transaction /K3T/RU_MAR_SCD_PR, the screen will be displayed with following selection parameters:

• Week

• Month

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• MDLP Configuration ID

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Input to both values (week and month) is not allowed.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 4 shall be implemented to overwrite standard selection logic.

17.     Program /K3T/RU_MAR_SCD_GEN_PR - Russia MDLP Analytics: Task scheduler General Pricing Report

The report /K3T/RU_MAR_SCD_GEN_PR can be executed by user or as background job to request General Report Pricing information from MDLP.

After executing program /K3T/RU_MAR_SCD_GEN_PR, the screen will be displayed with following selection parameters:

• Week

• Month

• All GTINs radio button: Send request without GTINs to get report with all available GTINs

• Select GTINs radio button: Select GTIN from system

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• Lot number: Restriction for the Lot numbers

• Determine Lot: Read all available Lots from system

• Exclude expired Batch: check Expiry Data on the Lot and exclude from the request

• MDLP Analytics Source type: Restriction for Finance Source type

• Aggregation type: Aggregate result data by GTIN or GTIN + Lot. In case of GTIN aggregation Batch data is not filled at result data

• Determine Config ID radio button: Get Configuration ID based on Subject ID from the business partner based on GTIN parameter BR_OWNER_GLN

• Use MDLP Fix Config ID radio button:  Use fix Configuration ID for the requests to MDLP

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Get Lot numbers from selection screen or all batches for the GTIN excluding expired if parameter set on the selection screen. Input to both values (week and month) is not allowed.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 7 shall be implemented to overwrite standard selection logic.

18.     Program /K3T/RU_MAR_SCD_GEN_MD - Russia MDLP Analytics: Task scheduler General Report on Disposal

The report /K3T/RU_MAR_SCD_GEN_MD can be executed by user or as background job to request General Report Medicine disposal information from MDLP.

After executing program /K3T/RU_MAR_SCD_GEN_MD, the screen will be displayed with following selection parameters:

• Week

• Month

• All GTINs radio button: Send request without GTINs to get report with all available GTINs

• Select GTINs radio button: Select GTIN from system

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• Lot number: Restriction for the Lot numbers

• Determine Lot: Read all available Lots from system

• Exclude expired Batch: check Expiry Data on the Lot and exclude from the request

• MDLP Analytics Source type: Restriction for Finance Source type

• Determine Config ID radio button: Get Configuration ID based on Subject ID from the business partner based on GTIN parameter BR_OWNER_GLN

• Use MDLP Fix Config ID radio button:  Use fix Configuration ID for the requests to MDLP

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Get Lot numbers from selection screen or all batches for the GTIN excluding expired if parameter set on the selection screen. Input to both values (week and month) is not allowed.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 6 shall be implemented to overwrite standard selection logic.

19.     Program /K3T/RU_MAR_SCD_GEN_RM - Russia MDLP Analytics: Task scheduler General Report on Remaining Items

The report /K3T/RU_MAR_SCD_GEN_RM can be executed by user or as background job to request General Report Remaining Items information from MDLP.

After executing program /K3T/RU_MAR_SCD_GEN_RM, the screen will be displayed with following selection parameters:

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• Lot number: Restriction for the Lot numbers

• Determine Lot: Read all available Lots from system

• Exclude expired Batch: check Expiry Data on the Lot and exclude from the request

• MDLP Analytics Source type: Restriction for Finance Source type

• Determine Config ID radio button: Get Configuration ID based on Subject ID from the business partner based on GTIN parameter BR_OWNER_GLN

• Use MDLP Fix Config ID radio button:  Use fix Configuration ID for the requests to MDLP

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Get Lot numbers from selection screen or all batches for the GTIN excluding expired if parameter set on the selection screen.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 8 shall be implemented to overwrite standard selection logic.

20.     Program /K3T/RU_MAR_SCD_GEN_ON_MV - Russia MDLP Analytics: Task scheduler General Report on Movement

The report /K3T/RU_MAR_SCD_GEN_ON_MV can be executed by user or as background job to request General Report On Movement information from MDLP.

After executing program /K3T/RU_MAR_SCD_GEN_ON_MV, the screen will be displayed with following selection parameters:

• Week

• Month

• All GTINs radio button: Send request without GTINs to get report with all available GTINs

• Select GTINs radio button: Select GTIN from system

• GS1 Global Trade Item Number: Optional GTIN list

• Country code: GTIN Country code

• Lot number: Restriction for the Lot numbers

• Determine Lot: Read all available Lots from system

• Exclude expired Batch: check Expiry Data on the Lot and exclude from the request

• MDLP Analytics Source type: Restriction for Finance Source type

• Determine Config ID radio button: Get Configuration ID based on Subject ID from the business partner based on GTIN parameter BR_OWNER_GLN

• Use MDLP Fix Config ID radio button:  Use fix Configuration ID for the requests to MDLP

The report will select all active GTIN, restricted to the list from the selection screen or based on selected country code. Get Lot numbers from selection screen or all batches for the GTIN excluding expired if parameter set on the selection screen. Input to both values (week and month) is not allowed.

Create request (table /K3T/RU_R_REQ) and tasks (table /K3T/RU_R_TSK) based on the selection parameters

The Badi /K3T/BADI_RU_MAR_SCD with filter REP_TYPE = 5 shall be implemented to overwrite standard selection logic.

21.     Obsolete transactions

Following the obsolete transactions:

• /K3T/RU_MDLP_GET_DOC - Russia MLDP document download

• /K3T/RU_CONNECTOR - MDLP connector

22.     Customizing transactions

Following the transaction list for customizing and configuration describes in the configuration guide:

/K3T/RU_CONF - Russia reporting configuration

/K3T/RU_CRULE - Russia reporting rule parameter

/K3T/RU_OMS_C - Russia OMS configuration

/K3T/RU_PARAM - Russia parameters

/K3T/RU_RULE_PRM - Russia non-standard rule

/K3T/RU_MAR_CONF - Russia MDLP Analytics: Configuration

/K3T/RU_SSF_C - Russia MDLP Certificate assignment