Kontakt

Ansicht
Dokumentation

MDG_TR_DEST - Assign RFC Destinations for Transport Methods

MDG_TR_DEST - Assign RFC Destinations for Transport Methods

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you maintain the RFC destinations that are used to execute transport methods (before-export and after-import). You can use these RFC destinations for the following purposes:

  • Transport postprocessing
Technically, postprocessing of transports takes place in client 000 of the target system, but logically, postprocessing occurs in the import client. To be able to run these methods in the import client, you need an RFC connection for the respective target client in the target system of the transports.
  • Local client copy (transaction SCCL)
An analysis phase (also called analysis exits of client copy) is started using the RFC destination in the source clients of a local client copy. The client copy is started in the target client and the analysis is executed through the RFC destination in the source client. This analysis phase is used to copy settings that require a special activity MDG_TR_EXEC_AI (postprocess client copy) in the target client.
  • Copy by Transport Request (transaction SCC1)
If the request was not released, the export preprocessing is started through an RFC connection in the source client of the transport request before the data is copied to the target client.

For a given client, you can use the same destinations for all purposes mentioned.

Transport objects whose methods refer to the following function modules must have a valid RFC destination:

  • MDG_TR_AFTER_IMP_METHOD
  • MDG_TR_BEFORE_EXP_METHOD

If the SAP Business Suite Foundation (SAP_BS_FND) component was installed and you want to execute a client copy, you need an RFC connection to the source client of the copy.

Standard SAP deliver does not include the settings.

The system searches for suitable destinations in the following steps:

  1. Entries in the current maintenance view (table MDG_TR_DEST)
If no RFC connections were defined in this step, the system searches for a suitable RFC connection in two other steps:
  1. An RFC destination with the naming convention MDGTR@<system>CLNT <client>
(Example: system XYZ client 100 -> MDGTR@XYZCLNT100)
  1. RFC destinations with the name of the logical system of the target client

Recommendation

If you define the RFC destinations in this step, you gain a better overview.

Create a valid RFC destination for the following clients:

  • All clients in which you want Customizing requests to be imported
  • All source clients of a client copy that is to take place locally in the system

Create the RFC destinations with the following data:

  • RFC destination: Logical system name of target system in uppercase letters
  • Connection type: 3 (R/3 connection)
  • Tab page Logon/Security, group box Logon:
  • Enter User and Password. For security reasons, the user should be a communication user with sufficient authorizations for the application.

  • Enter the Client explicitly.






General Data in Customer Master   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4327 Date: 20240523 Time: 192700     sap01-206 ( 54 ms )