Skip to Content

In lot of projects, there is a huge number of partner profiles to be configured. These have to be then manually keyed in every environment. Following blog explains how partner profiles can be transport using SAP Transports. This will save several days of effort depending on the scope.

The steps will assume that an ECC system has a Development client(600) and a test client(610).

Key and very important per-requisite is to avoid have SID in the RFC destination used on the partner profile. Create something like SAPPI_IDOC for example, rather than PID_IDOC and PIQ_IDOC.

Principles

  1. Maintain all Work Centers & Partner Profiles in client 600 (Do not maintain Work Centers & Partner Profiles in any other systems/clients)
  2. Create separate transports for Partner Profiles & Work Centers
  3. Optionally, create separate transports for Partner Profiles for different logical systems (so they can be transported at different times if required).
  4. Test transports by importing them to client 610 using SCC1 and verify if everything is imported correctly. Work Center transports should be imported before Partner Profile transports. Best practice to keep Logical systems in separate transport as well and import them before partner profiles.
  5. Release transports.

Transporting Work Centers

  1. Create a new Customizing Transport
  2. Run program RHMOVE30 & enter the following parameters:
    1. Plan Version = ‘01’
    2. Object Type = ‘A’
    3. Object ID = List of Work Centers to Transport
    4. Reporting Period = ‘Today’
    5. Evaluation Path =  ‘B007’
    6. Status Vector = 1
    7. Task = Task of transport created (this must be the task, not the main transport ID)
    8. Transport Objects = checked
    9. All other fields should be blank/un-checked
  3. Execute program, select all entries displayed and select “Transport/Delete” button. (This step can take some time if there are multiple work centers selected)
  4. Review the contents of the transport created. The entry for “PDWS” should be blank. The entry for “PDST” should have keys populated. If entries for HRP1217 have been added to the transport, then edit the transport and delete them. (It it is important these are deleted otherwise the transport will fail).
  5. Check the transport by importing it to client 610 using Tcode SCC1.

Blog_2013-10-25_14-16-19.png

Words of warning: This program transports the relationships between the work centers you specify & the tasks linked to it, but also the reverse relationship from the task to the work center. (Both relationships are required). It also transports any other relationships from the task, so the relationship from the task to all other work center is transported. If the other Work Center do not exist in the target system then the transport will fail (though only to build the links to the missing work center – all other links will be activated).

The systems are all aligned now, so this shouldn’t be an issue, so long as no “dummy” work centers are created in client 600 (and work centers aren’t manipulated in the other systems). If you experience issues, check that there are no work centers in client 610 that should not be transported. (If there are then set the validity period in the past so they are not picked up by the transport program).

 
 

Transporting IDoc Partner Profiles

  1. Create a new Workbench Transport & go to edit mode.
  2. To transport the Partner Profile Header:
    1. Add an entry for R3TR TABU EDPP1 to the transport
    2. Update the Table key for the entry, setting client = 600, Partner No = “Partner Profile #
  3. To transport the Inbound Parameters:
    1. Add an entry for R3TR TABU EDP21 to the transport
    2. If you want to transport all the Inbound parameters, update the Table key for the entry, setting client = 600, Partner No = “Partner Profile #” and Partn. Type = ‘*’
    3. If you want to transport a specific entry then complete the key as above, but populate additional fields to specify the entry you want. (Add multiple table keys if you want to transport multiple entries
  4. To transport the Outbound Parameters:
    1. Add an entry for R3TR TABU EDP13 to the transport
    2. Update the Table keys as per the guidance for the Inbound Parameters
  5. To transport the Message Control entries for Outbound Parameters:
    1. Add an entry for R3TR TABU EDP12 to the transport
    2. Update the Table keys as per the guidance for the Inbound Parameters
  6. Save the transport (you will get warnings about the tables, but you can ignore these).
  7. Check the entries are correct by importing it to client 610.

Recommendation: To minimize the risk of missing some config, transport all the entries for a Partner in a single transport. However, if only a single entry is required (after all entries have been transported) it may make sense just to transport that entry to reduce regression impact.

* Special thanks to David Bennett for researching this approach.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply