Transporting of connecting specific settings

[Former Member]

Hi all

We are having problems transporting connector specific settings from the GRC Dev system to the GRC QA system.

We have a landscape where our GRC Dev system connects to ERP Dev, GRC QA connects to ERP QA and GRC Prod connects to ERP Prod.

In DEV, we only had a connector group which contains a connector to the ERP Dev system.

When the settings are transported from GRC Dev to QA, the settings in QA still point to the ERP Dev system.

How can connectors be set up so that transported settings that contain connectors will instead point to ERP QA system?  Should all connectors for the ERP QA and ERP Prod system be configured in Dev?  Or do connector specific settings have to be maintained directly in GRC QA and Prod clients.

The specific settings that we are having trouble with include:

1. Rule set

Transported the rule set but the actions in functions point to the ERP Dev system once transported to QA

I suppose we can download from Dev and upload to QA get around this

2. Access control > Maintain Mapping for Actions and Connector Groups

3. Access control > Maintain Connectors

4. Integration Framework > Maintain Connector Groups

There may be other ones as well...

Any help is much appreciated

Don

[Former Member]

Hi Don,

You may copy the Rules by using program GRAC_COPY_RULES in SE38. Here you can copy the rules of one system to other.

Regards,

Yukti

[Former Member]

This is a very good query , mainly the Rule set related , others can be a one time configuration activity , but the ruleset changes can be more frequent .

• Transported the rule set but the actions in functions point to the ERP Dev system once transported to QA

Any best practices on how to manage this , we also plan to utilize the transport mechanism to manage ruleset changes.

Thanks

-Ranjiv

[neerajmanocha]

Hi Don & Ranjiv,

For transporting rules from one system to another for specific system/connector, you can use program GRAC_COPY_RULES to copy your dev rules to prd rules. You can use this copy program in DEV itself after creating a connector for your PRD system (it is irrespective, whether PRD connector is getting tested or working or not).

As per best practices, Connectors should be created sepeartely in all the landscapes. This is a one time job and can be done in Production server itself once at the time of configuring.

One of the SAP note 135028 also has suggested to maintain couple of settings directly in production wherever required.

So either approach .... 1. Creating PRD connectors in DEV and then transporting it to PRD.... OR ....2. Creating connectors in PRD system directly..... .both can be adopted.

Thanks & Regards

Neeraj

[simon_persin4]

Neeraj,

Configuring connectors directly in production is NOT best practice nor should it ever be considered as such. However, thanks for the tip on the GRAC_COPY_RULES program.

Have a look on www.grcexpertonline.com where you'll find a position paper that I wrote on this particular issue.

My solution is to follow proper ABAP change management standards and have in mind what your production system should look like before you actually configure development. This way you'll have your to-be connection configuration sorted and in proper transport requests which you can progress through the landscape.

You can update the SM59 master data configuration to adjust to "proper" target systems as you move through the landscape or amend in pre-prod directly if you have to but please don't recommend direct changes in production on your COMPLIANCE tool.

Simon