Introduction

In Solution Documentation you can assign End User Roles. In 7.0 and 7.1 this can be done on Tab End User Roles in transactioni SOLAR01, SOLAR02 and SOLMAN_DIRECTORY, in 7.2 in transaction SOLDOC. When you transport a project/solution to another system the references to these end user roles point to nothing, so you will want to transport the objects. By default the End User Role subtypes are Job, Organizational Unit and User. The subtypes can be extended via IMG activity Assignment of End User Roles (SM30-view V_SAROLECUST). Some customers also added PFCG roles via customizing. These roles can be created in Organizational Management (Area Menu PP76, transaction PPSC – Create). All Objects created with this transaction like e.g. Job (type C) and Org-Unit (type O) can be transported. Users (type US) and PFCG roles (type AG) can’t be transported this way.

Fill the transport

Call transaction RE_RHMOVE30. Enter current plan version 01 and object type. Unset Test flag and create customizing transport request:

Now select all entries to be transported and execute by pushing button Transport/Delete.

Check number range status

This kind of objects uses number ranges. So a transport can lead to overwrites. Before you import your transport in the target system, note the highest object number in your transport. Then check the number range counter in the target system. Go to transaction SPRO and IMG activity:

SAP Customizing Implementation Guide
    SAP NetWeaver
        Application Server
            Business Management
                SAP Business Workflow
                    Basic Settings
                        Number Range Maintenance
                            Maintain number ranges

Number range must be higher in comparison to transported highest value to avoid values being overwritten with creation of new entries in target system. Therefore go to Number range maintenance of Subgroup 01$$ and check the current status. This group is responsible for creating numbers for plan variant 01 and any objects. Check also if there is a special group for your object type. If you transport jobs (type C) chekc if there is a subgroup 01C. This would be used for jobs in plan variant 01 only. Probably it is not there as in our screenshot.

Import

If this is o.k. you can safely import your transport.

Adapt number range counter

After the import you need to adapt the number range counter to a value higher then the ones imported. This avoids that duplicate numbers are used when new objects are created.

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply