RFC Destinations, database copy

[Former Member]

Hi Forum,

when you are to make a database copy how can you backup the rfc - destinations (sm59) of the target system ?

Same question as for partner conventions (we20).

Kind regards

samplitude

[sunny_pahuja2]

Hi,

> when you are to make a database copy how can you backup the rfc - destinations (sm59) of the target system ?

R3TR TABU RFCDES

R3TR TABU RFCDOC

R3TR TABU RFCDESSECU

R3TR TABU RFCATTRIB

R3TR TABU RFCCHECK

R3TR TABU RFCGO

R3TR TABU RFCTA

Copy all above tables in a transport and later on import in the target system again to get the same RFC configuration.

> Same question as for partner conventions (we20).

R3TR TABU EDIPHONE

R3TR TABU EDMA

R3TR TABU EDMAT

R3TR TABU EDMMS

R3TR TABU EDP12

R3TR TABU EDP13

R3TR TABU EDP21

R3TR TABU_EDPAR

R3TR TABU_EDPI1

R3TR TABU_EDPO1

R3TR TABU_EDPO3

R3TR TABU_EDPP1

R3TR TABU_EDPPV

R3TR TABU_EDPVW

R3TR TABU_EDIPOD

R3TR TABU_EDIPOA

R3TR TABU_EDIPORT

Copy all above tables for partner profile in transport request. Please remember partner profiles are client dependent. If system has multiple clients then same steps in need to be follow in all clients.

Thanks

Sunny

Edited by: Sunny Pahuja on Jan 9, 2010 8:55 PM

[Former Member]

Hello,

The above list is far from complete, creating a distinctive list of tables for RFC and ALE is not that easy.

That's why I don't like the approach of exporting tables before a system refresh.

Tables for trusted RFC are missing, tables for ALE distribution models are missing, ALE conversion rules, even the table for logical system names is missing, etc ... you did not ask for it, that's true, because maybe you forgot.

I always recommend to do the ALE setup (logical system names, partner profiles, distribution models, filtering, conversion rules, ...) for all systems (DEV, QA, ...) on a system that you never refresh, in other words in the PRD system.

Advantage, when you copy PRD to QA, you have all the ALE setup included.

There is no risk of sending data to the wrong system, because during post refresh phase you will run a BDLS in QA in order to rename the logical system name.

During post refresh in QA I always delete all productive RFC destinations and recreate the ones to the other QA systems manually, for 7 QA systems with trusted RFC this takes me max 15 minutes.

Also note that a lot of ALE setup like distribution models, filtering, conversion rules, ... can be transported in order to allign your system landscape.

Wim