IDM 7.2 SP6 integration with GRC 10 not working at all.

[AshishAnand]

Dear Experts,

For one of our customer, We are tring to integrate GRC 10 with IDM 7.2 SP 6.

We are having some problem with "  <ReqInitSystem>................5</ReqInitSystem>" tag.

Could you please share some information on the uasge and working of the <ReqInitSystem> tag?

Thanks and Regards

Ashish

[AshishAnand]

In the web service GRAC_USER_ACCES_WS we are referring to the highlighted tag.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soapenv:Body>

<GracIdmUsrAccsReqServices xmlns="urn:sap-com:document:sap:soap:functions:mc-style">

<CustomFieldsVal xmlns=""/>

<Language xmlns=""/>

         <Parameter xmlns=""/>

<RequestHeaderData xmlns="">

<Reqtype>?</Reqtype>

<Priority>?</Priority>

<ReqDueDate/>

<ReqInitSystem>?</ReqInitSystem>

<Requestorid>?</Requestorid>

<Email>?</Email>

<RequestReason>?</RequestReason>

<Funcarea>?</Funcarea>

<Bproc>?</Bproc>

</RequestHeaderData>

<RequestedLineItem xmlns="">

<item>

<ItemName>?</ItemName>

<Connector>?</Connector>

<ProvItemType>?</ProvItemType>

<ProvType/>

<AssignmentType/>

...

[Murali_Shanmu]

Ashish,

You have not clearly explained what error message you are facing with and at what step.

Once you have imported the GRC Provisioning Framework into IDM, you will see a new repository being created called GRC10. There is a constant inside this repository called "GRC_REQUESTOR_INITSYSTEM". SAP mentioned to set a meaningful value to this parameter. In my case, I set it to the Logical system name of my ERP system, which is the same value set in AC_APPLICATION_ID of the ERP Repository constant.

Cheers,

Murali

[Former Member]

We got the solution for same, XML tag "<ReqInitSystem>?</ReqInitSystem>"
got included in hand over between SAP IdM 7.2 and GRC AC 10 recently.

Same value should be maintained in both IdM and Access Control.

Work to be ensured:

While creating connector in Access Control add the connector to scenario AUTH-PROV(can be dependent upon client set up).

Regards,

Nishant