SystemID RealmID association in CIG

Concept:

Standard CIG supports integration of one Realm to only one Backend ERP with the system landscape handling TEST & PROD environments. To address specific customer requirements where they need to change their existing CIG Test connection to a different backend ERP system, the following workaround may be adopted

Workaround resolution:

Consider, Ariba has a realm 342-T and it is connected to ERP SystemID QATCLNT001. This is done during Project creation.

SystemID – RealmID Association can also be viewed in MyConfiguration->CrossRefs->RealmId

On completion of QA activities for the integration, a different system(such as Production)may be intended for integration. In such case, a new project with necessary details must be created. RealmID association in this project must be with the new SystemID.

At this point, two associations will be displayed for the same realm.

Although only one is required, there are two at this moment. To overcome the technical ambiguity, please follow the below steps:

1. Navigate and Goto previous project.
2. From the previous project, remove the connection in step2 and add a dummy one.
3. Under MyConfiguration->CrossRefs->RealmID, delete the previous association.
4. You are now good to use the new systemID for existing realm.

In Short:

CIG offers a way to configure different instances such as Test (QA activities) and Production(Live version), etc. One such approach is maintaining multiple backend systems connected to single realm. Ambiguities observed can be resolved by following this approach when two or more connections in respective projects are active for same realm.

Please share your valuable feedback in the comments section. Also, help share the content to make other consultants resolve such blockers.