Administrator Guide Russia MDLP Connector
- Pavel Kanskov
- Denis Zolotarev
Document History
Version | Changes | Effective Date |
1.0 | First approved version 3Keys Russia MDLP Add-On release 3.0 | 01-Jul-2021 |
2.0 | Release RN_2023_03 | 01-Aug-2023 |
3.0 | Release RN_2024_01 | 01-Feb-2024 |
4.0 | Release RN_2024_04 | 01-Nov-2024 |
5.0 | Release RN_2025_01 | 01-Feb-2025 |
- 1 About This Guide
- 2 Installation
- 3 Maintenance and release strategy
- 4 Upgrade
- 5 Security Information
- 5.1 Other Required Documents for Security
- 5.2 Authorization Concept
- 5.2.1 Authorization objects for MDLP
- 5.2.1.1 Authorization objects for MDLP monitor action and document type /K3T/RU001
- 5.2.1.2 Authorization objects for MDLP configuration ID /K3T/RU003
- 5.2.1.3 Authorization objects for OMS token /K3T/RU004
- 5.2.1.4 Authorization objects for Russia MDLP Analytics action /K3T/RU005
- 5.2.1.5 Report / Transaction Authorizations
- 5.2.2 Further authorizations
- 5.2.1 Authorization objects for MDLP
- 6 Uninstalling
About This Guide
This guide is the central starting point for the implementation of the 3Keys Russia MDLP Add-On. It explains how to install, uninstall and implement the 3Keys Russia MDLP Add-On and provides security and operations information. Use the Administrator guide to get an overview of 3Keys Russia MDLP Add-On, its software units, and its scenarios from a technical perspective.
Installation
This section provides information about how to prepare for installation and what to do before and after the installation of 3Keys Russia MDLP Add-On.
ATTP 3.0 (STTP300)
Software Component Matrix
Software Unit | Installation Package |
SAP Advanced Track and Trace for Pharmaceuticals 3.0 (STTP300) | SAPK-300AGINSTTP |
3Keys Russia MDLP Add-On 3.0 | SAPK-300COINK3T |
Overall Implementation Sequence
The following table describes the overall installation sequence for the 3Keys Russia MDLP Add-On. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes
Step | Action | Remarks |
1 | Installation of SAP Advanced Track and Trace for Pharmaceuticals 3.0 | See SAP Note 2203586 |
2 | Installation of 3Keys Russia MDLP Add-On 3.0 | Upload installation file to the server and import component using transaction SAINT in client 000 |
3 | Installation all available releases and notes for 3Keys Russia MDLP Add-On 3.0 starting from Release RN_2023_01 https://3keys.atlassian.net/wiki/spaces/crptconnector/pages/1137442820/MDLP+releases | Installation Notes only required if the release is not completed in between two releases |
4 | Activate BC sets offered for 3Keys Russia MDLP Add-On in target client:
| In case you encounter issues with activation of a BC set please try to activate the BC set multiple times. In most cases the issue will be solved with this. |
ATTP 3.1 (STTP300 with support package 01)
Software Component Matrix
Software Unit | Installation Package |
SAP Advanced Track and Trace for Pharmaceuticals 3.0 (STTP300) with support package 01 | SAPK-300AGINSTTP SAPK-30001INSTTP |
3Keys Russia MDLP Add-On 3.1 | SAPK-301COINK3T |
Overall Implementation Sequence
The following table describes the overall installation sequence for the 3Keys Russia MDLP Add-On. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes
Step | Action | Remarks |
1 | Installation of SAP Advanced Track and Trace for Pharmaceuticals 3.0 with support package 01 | See SAP Note 2203586 |
2 | Installation of 3Keys Russia MDLP Add-On 3.1 | Upload installation file to the server and import component using transaction SAINT in client 000 |
3 | Installation all available releases and notes for 3Keys Russia MDLP Add-On 3.1 starting from Release RN_2023_01 https://3keys.atlassian.net/wiki/spaces/crptconnector/pages/1137442820/MDLP+releases | Installation Notes only required if the release is not completed in between two releases |
4 | Activate BC sets offered for 3Keys Russia MDLP Add-On in target client:
| In case you encounter issues with activation of a BC set please try to activate the BC set multiple times. In most cases the issue will be solved with this. |
ATTP 3.2 (STTP300 with support package 02)
Software Component Matrix
Software Unit | Installation Package |
SAP Advanced Track and Trace for Pharmaceuticals 3.0 (STTP300) with support package 02 | SAPK-300AGINSTTP SAPK-30001INSTTP SAPK-30002INSTTP |
3Keys Russia MDLP Add-On 3.2 | SAPK-302COINK3T |
Overall Implementation Sequence
The following table describes the overall installation sequence for the 3Keys Russia MDLP Add-On. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes
Step | Action | Remarks |
1 | Installation of SAP Advanced Track and Trace for Pharmaceuticals 3.0 with support package 02 | See SAP Note 2203586 |
2 | Installation of 3Keys Russia MDLP Add-On 3.2 | Upload installation file to the server and import component using transaction SAINT in client 000 |
3 | Installation all available releases and notes for 3Keys Russia MDLP Add-On 3.2 starting from Release RN_2023_01 https://3keys.atlassian.net/wiki/spaces/crptconnector/pages/1137442820/MDLP+releases | Installation Notes only required if the release is not completed in between two releases |
4 | Activate BC sets offered for 3Keys Russia MDLP Add-On in target client:
| In case you encounter issues with activation of a BC set please try to activate the BC set multiple times. In most cases the issue will be solved with this. |
ATTP 3.3 (STTP300 with support package 03)
Software Component Matrix
Software Unit | Installation Package |
SAP Advanced Track and Trace for Pharmaceuticals 3.0 (STTP300) with support package 03 | SAPK-300AGINSTTP SAPK-30001INSTTP SAPK-30002INSTTP SAPK-30003INSTTP |
3Keys Russia MDLP Add-On 3.3 | SAPK-303COINK3TK |
Overall Implementation Sequence
The following table describes the overall installation sequence for the 3Keys Russia MDLP Add-On. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes
Step | Action | Remarks |
1 | Installation of SAP Advanced Track and Trace for Pharmaceuticals 3.0 with support package 03 | See SAP Note 2203586 |
2 | Installation of 3Keys Russia MDLP Add-On 3.3 | Upload installation file to the server and import component using transaction SAINT in client 000 |
3 | Installation all available releases and notes for 3Keys Russia MDLP Add-On 3.3 starting from Release RN_2024_01 https://3keys.atlassian.net/wiki/spaces/crptconnector/pages/1137442820/MDLP+releases | Installation Notes only required if the release is not completed in between two releases |
4 | Activate BC sets offered for 3Keys Russia MDLP Add-On in target client:
| In case you encounter issues with activation of a BC set please try to activate the BC set multiple times. In most cases the issue will be solved with this. |
ATTP 3.4 (STTP300 with support package 04)
Software Component Matrix
Software Unit | Installation Package |
SAP Advanced Track and Trace for Pharmaceuticals 3.0 (STTP300) with support package 04 | SAPK-300AGINSTTP SAPK-30001INSTTP SAPK-30002INSTTP SAPK-30003INSTTP SAPK-30004INSTTP |
3Keys Russia MDLP Add-On 3.4 | SAPK-304COINK3T |
Overall Implementation Sequence
The following table describes the overall installation sequence for the 3Keys Russia MDLP Add-On. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes
Step | Action | Remarks |
1 | Installation of SAP Advanced Track and Trace for Pharmaceuticals 3.0 with support package 04 | See SAP Note 2203586 |
2 | Installation of 3Keys Russia MDLP Add-On 3.4 | Upload installation file with available Support Packages to the server and import component with available Support Packages using transaction SAINT in client 000 |
3 | Installation all available support packages and notes for 3Keys Russia MDLP Add-On 3.4 starting from Release RN_2024_04 https://3keys.atlassian.net/wiki/spaces/crptconnector/pages/1137442820/MDLP+releases | Only note available after last Support Package shall be considered for the installation |
4 | Activate BC sets offered for 3Keys Russia MDLP Add-On in target client:
| In case you encounter issues with activation of a BC set please try to activate the BC set multiple times. In most cases the issue will be solved with this. |
ATTP 4.1 (STTP400 with support package 01)
Software Component Matrix
Software Unit | Installation Package |
SAP Advanced Track and Trace for Pharmaceuticals on SAP S/4HANA 4.0 (STTP400) with support package 01 | SAPK-400AGINSTTP SAPK-40001INSTTP |
3Keys Russia MDLP Add-On 4.1 | SAPK-401COINK3T |
Overall Implementation Sequence
The following table describes the overall installation sequence for the 3Keys Russia MDLP Add-On. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes
Step | Action | Remarks |
1 | SAP Advanced Track and Trace for Pharmaceuticals on SAP S/4HANA 4.0 (STTP400) with support package 01 | See SAP Note 2203586 |
2 | Installation of 3Keys Russia MDLP Add-On 4.1 | Upload installation file with available Support Packages to the server and import component with available Support Packages using transaction SAINT in client 000 |
3 | Installation all available notes for 3Keys Russia MDLP Add-On 4.1 starting after last available Support Package https://3keys.atlassian.net/wiki/spaces/crptconnector/pages/1137442820/MDLP+releases | Only note available after last Support Package shall be considered for the installation |
4 | Activate BC sets offered for 3Keys Russia MDLP Add-On in target client:
| In case you encounter issues with activation of a BC set please try to activate the BC set multiple times. In most cases the issue will be solved with this. |
Maintenance and release strategy
The 3Keys Russia MDLP Add-On follows the release strategy of SAP ATTP. The updates of the 3Keys Russia MDLP Add-On are provided as a zip file that includes a workbench transport and a PDF file, similar to SAP Notes. A cumulated workbench transport for ATTP 3.0-3.3 or as support package (to be installed with transaction SPAM) for ATTP 3.4 and higher is provided four times per year (on February 1st, May 1st, August 1st, and November 1st) and includes all changes for the last three months (Release for Russia MDLP Add-On).
Upgrade
This section provides information about how to prepare for upgrade and what to do before and after the upgrade of 3Keys Russia MDLP Add-On.
The 3Keys Russia MDLP Add-On must be upgraded with each new ATTP release. Each software component version of the 3Keys Russia MDLP Add-On includes all changes required to be compatible with a particular ATTP version and service pack. The 3Keys Russia MDLP Add-On installation package has an overwrite flag active and will overwrite all 3Keys Russia MDLP Add-On objects that currently exist in the ATTP system. The BC-Set contains all required customizing settings and will overwrite customizing that currently exist in the ATTP system.
Security Information
This section deals with security topics relevant for the 3Keys Russia MDLP Add-On.
The solution is available for
SAP NetWeaver 750 and the SAP Advanced Track and Trace for Pharmaceuticals 3.0
SAP S/4HANA Foundation 2023 and SAP Advanced Track and Trace for Pharmaceuticals on SAP S/4HANA 4.0
Therefore, the corresponding security settings also apply to 3Keys Russia MDLP Add-On.
Other Required Documents for Security
Resource | Where to Find It |
SAP NetWeaver Security Guide | Go to the SAP Help Portal at http://help.sap.com/nw and select the appropriate release. The security guide is in the section Security on the product page. |
SAP Advanced Track and Trace for Pharmaceuticals Security Guide | Go to the SAP Help Portal at https://help.sap.com/viewer/product/SAP_ADVANCED_TRACK_AND_TRACE_FOR_PHARMACEUTICALS/3.0 The security guide is in the section Security in the Administrator’s guide |
Authorization Concept
This section describes the authorizations available in the 3Keys Russia MDLP Add-On.
The 3Keys Russia MDLP Add-On allows you to make specific authorization settings for all business entities of the solution. The following sections provide information about the authorization concept and the authorization objects used.
In general, authorization checks are executed when searching, displaying, or updating data within the repository system.
Authorization objects for MDLP
Authorization objects for MDLP monitor action and document type /K3T/RU001
This authorization object is used to control all MDLP transaction relevant data based on field action
Authorization Field | Authorization Object Settings |
/K3T/RU001 Russia MDLP monitor action | Assign * if role should be able to perform all actions Or assign specific actions 00 Display 01 Display request XML 02 Download request XML 03 Display response XML 04 Download response XML 05 Display AIF messages 06 Download AIF messages 07 Check data 08 Approval 09 Cancel 10 Reset status 11 Show log 12 Send 250-recall message 13 Change approver 14 Reset processing status 15 Repeat message sending 16 Send 251-refusal_sender message 17 Send 252-refusal_receiver message 18 Change Operation date 19 Maintain Missing Data 20 Sequence Check 21 Change Incoming message status 22 Navigate to Cockpit object 23 Update MDLP status 24 Process saved 211 XML 25 Remove 26 Change log 27 Logistic Monitor 28 Recalculate header Qty 29 Confirm message 30 Software Version 31 Update Token |
/K3T/RU002 Russia MDLP document type | Assign * if role should be able to display all MDLP document types Or assign specific MDLP document types, for example: 381 381-move_owner 415 415-move_order 431 431-move_place |
Authorization objects for MDLP configuration ID /K3T/RU003
This authorization object is used to control access to MDLP reporting data via transaction /K3T/RU_MONITOR or /K3T/RU_MDLP_LM based on MDLP configuration value
Authorization Field | Authorization Object Settings |
/K3T/RU003 MDLP Configuration ID | Assign * if role should be able to perform all configuration Or assign specific MDLP Configuration ID |
Authorization objects for OMS token /K3T/RU004
This authorization object is used to control access to dynamic OMS token data via transaction /K3T/RU_OMS_TOKEN
Authorization Field | Authorization Object Settings |
/K3T/RU004 OMS Token action | 01 Display OMS Token |
Authorization objects for Russia MDLP Analytics action /K3T/RU005
This authorization object is used to control access to MDLP Analytic reporting data
Authorization Field | Authorization Object Settings |
/K3T/RU005 Russia MDLP Analytics action | 01 Schedule task 02 Process task 03 Change status 04 Display request 05 Download result 06 Add ZIP response 07 Display MDLP queue 08 Execute task 09 Delete MDLP task 10 Download ZIP from MDLP |
Report / Transaction Authorizations
Authorization checks are run for all transactions or reports with configuration character as follows:
Report | Authorization Object | Authorization Field | Authorization Object Settings |
/K3T/REP_RU_MDLP_210 | /K3T/RU001 | /K3T/RU001 | 23 Update MDLP status |
/K3T/RU_MDLP_IN | /K3T/RU001 | /K3T/RU001 | 24 Process saved 211 XML |
/K3T/RU_MDLP_LM | /K3T/RU001 | /K3T/RU001 | 27 Logistic Monitor |
| /K3T/RU001 | /K3T/RU002 | Selected document types |
| /K3T/RU003 | /K3T/RU003 | Selected configuration ID |
/K3T/RU_MDLP_ MONITOR | /K3T/RU001 | /K3T/RU001 | 01 Display request XML 02 Download request XML 03 Display response XML 04 Download response XML 05 Display AIF messages 06 Download AIF messages 08 Approval 09 Cancel 10 Reset status 11 Show log 12 Send 250-recall message 13 Change approver 14 Reset processing status 15 Repeat message sending 16 Send 251-refusal_sender message 17 Send 252-refusal_receiver message 18 Change Operation date 19 Maintain Missing Data 20 Sequence Check 21 Change Incoming message status 22 Navigate to Cockpit object 26 Change log 28 Recalculate header Qty 29 Confirm message 30 Software Version 31 Update Token |
| /K3T/RU001 | /K3T/RU002 | Selected document types |
| /K3T/RU003 | /K3T/RU003 | Selected configuration |
/K3T/RU_211_XML_ BUFFER | /K3T/RU001 | /K3T/RU001 | 24 Process saved 211 XML |
/K3T/RU_MDLP_ CLEANUP | /K3T/RU001 | /K3T/RU001 | 25 Remove |
/K3T/RU_OMS_TOKEN | /K3T/RU004 | /K3T/RU004 | 01 Display OMS Token |
/K3T/RU_MAR_MONITOR | /K3T/RU005 | /K3T/RU005 | 03 Change status 04 Display request 05 Download result 06 Add ZIP response 07 Display MDLP queue 09 Delete MDLP task 10 Download ZIP from MDLP |
/K3T/RU_MAR_SCD_MD | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_SCD_PR | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_SCD_RM | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_SCD_SH | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_TASK_EXEC | /K3T/RU005 | /K3T/RU005 | 08 Execute task |
/K3T/RU_MAR_TASK_PROC | /K3T/RU005 | /K3T/RU005 | 02 Process task |
/K3T/RU_MAR_REP_PROC | /K3T/RU005 | /K3T/RU005 | 02 Process task |
/K3T/RU_MAR_SCD_GEN_MD | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_SCD_GEN_PR | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_SCD_GEN_RM | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
/K3T/RU_MAR_SCD_GEN_ON_MV | /K3T/RU005 | /K3T/RU005 | 01 Schedule task |
Further authorizations
Authorizations for Maintenance Views
In addition to the authorization object, an authorization group has been assigned to each maintenance view / underlying views of view clusters according to the delivery class:
Delivery class = E / C: Authorization Group = ATTC
Delivery class = A: Authorization Group = ATTO
Delivery class = S: No Authorization Group.
Uninstalling
You can use the SAP Add-On Installation Tool to uninstall add-ons. However, the uninstallation is possible only if the following prerequisites are met for individual add-on components:
You have imported the latest SAINT update (at least SPAM Version 75).
Procedure:
Call the SAP Add-On Installation Tool with the transaction code SAINT in client 000.
Choose the "Uninstallable Components" tab and select the add-on component version K3T from the list
To start the uninstallation process, choose "Start".
A confirmation prompt alerts you to possible dangers of the uninstallation and refers to this add-on-specific SAP Note with important information. Be sure to read this SAP Note and follow its instructions.
Define the start options.
Once you have read this SAP Note and followed its instructions, choose "Continue" to start the uninstallation with the chosen start options. To cancel the uninstallation, choose "Cancel".
After you start the uninstall process, the Add-On Installation Tool runs a predefined sequence of phases. Should an error occur in any of these phases, the uninstall process is stopped and the error is described to the extent possible. Once you have corrected the problem, you can choose "Continue" to continue the uninstallation.
At first, the Add-On Installation Tool performs preparation steps and check steps. If errors cannot be corrected in these phases, you can choose "Back" to stop and reset the uninstallation. In later phases, if changes and deletions have already been made in the system, a reset is no longer possible, and the system displays a relevant error message. In this case, the errors must be rectified, and the uninstallation must be completed.
Following the successful uninstallation of the add-on, you can choose "Logs" to display the implementation logs.
To complete the uninstallation, choose "Exit".