on 10-17-2013 10:29 PM
Hi Akshay,
Make sure you have maintained Logical Port ( Logical port can be same as Target Connector (as defined in SM59)) under "Maintain Connectors and Connection Types".
Its a Mandatory Configuration step to retrieve data from Plug-In System.
Best Regards,
Rama
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Akshay,
As I mentioned earlier, Ensure to check the "Logical Port" ( same as Target Connector that is defined in SM59)
Note: For GRC System "Logical Port"(same as Target Connector) means the RFC Destination that is defined in SM59 in GRC Box and it doesn't point towards BD54 entry.
The error "CCITS" you are getting is related to Logical Port entry only. So try to check your RFC entries in GRC Box and correct them.
Best Regards,
Rama
Hi Rama,
The entries are exactly as you mentioned in the above screen shot as well.
The logical port entry is same as the Entry in Target Connector which in turn is same as the RFC Connection.
Ramakrishna Dadi wrote:
Note: For GRC System "Logical Port"(same as Target Connector) means the RFC Destination that is defined in SM59 in GRC Box and it doesn't point towards BD54 entry.
Yes, I have done exactly the same as above. Logical System entry in BD54 & SCC4 is different and I am not referring to it.
Entry in BD54/SCC4 for this System Client => LOGSYS500
RFC Destination from GRC to this System Client => PR8CLNT500
GRC Connector (Target Connector) in SPRO => PR8CLNT500
Logical Port in Maintain Connectors and Connection Types => PR8CLNT500
Source Connector => <Blank>
Also the screen-shot again.
Hope you mean this only.
Regards,
Akshay
Hi Akshay
Entry in BD54/SCC4 for this System Client => LOGSYS500
Can you please test changing LOGSYS500 to PR8CLNT500 in BD54
If not (not sure if this works) try:
Logical Port in Maintain Connectors and Connection Types => PR8CLNT500
change this value for the Logical Port to be LOGSYS500 (i.e map the connector back to the logical port
Regards
Colleen
Hi Colleen,
Tried both the scenarios you have mentioned above.
In case 1, "Can you please test changing LOGSYS500 to PR8CLNT500 in BD54" getting the same error => Correctly define the Logical Connection in CCITS
In case 2, "change this value for the Logical Port to be LOGSYS500 (i.e map the connector back to the logical port" getting the error => RFC LOGSYS500 doesnt exists.
So if i have an RFC Connection as LOGSYS500 rather than current one PR8CLNT500, it will become case 1 where everything is same name as BD54 entry.
To this point I feel this as a bug because this being the highest SP13 and this error is in entirely new Scenario i.e. "EAM Master Data Synch", perhaps SAP can only now provide the solution.
However, much appreciate your help.
Regards,
Akshay
Hello,
Connectors are nothing but RFC,s you create .
GRC AC 10.0, Integration Scenarios, PROV, SUPMG, AUTH, ROLEMG, Access Control, Correctly define the logical connection in CCITS
Due to some interdependencies related to certain scenarios in GRC AC10.0 it is required to maintain a Scenario to Connector link for all 4 scenarios available for Access Controls in version 10:
- AUTH (Authorization Management)
- PROV (Provisioning)
- ROLEMG (Role Management)
- SUPMG (Super user Priviledge Management)
This link can be established under transaction SPRO => Governance, Risk & Compliance => Common Component Settings => Maintain Connection Settings.
Connector Settings
you can maintain the connector settings for the systems that are connected to the access control application
If you want to make specific connector as productive and enable PSS for it, you can maintain those settings in connector settings.
Regards,
Prasant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Can you please elaborate a bit about Defining Logical Connection in CCITS?
I am working on Configuring De-Centralized EAM (Firefighting), GRC AC 10 SP13
While running the synchronization job EAM Master Data Synch, I am getting the error as below:
I have maintained the Integration Scenarios correctly for all PROV, SUPMG, AUTH, ROLEMG for this connector.
Can you please point, what could be the issue.
I have also checked the RFC for any white spaces!
Regards,
Akshay
Hi Colleen,
Yes logical system is defined in SALE/BD54.
Earlier when we had only one back-end system we kept the naming convention that way only i.e. Logical System=RFC Connection=GRC Connector.
But now as we are doing the final implementation, we have multiple systems where logical system happens to be same. For ex- PRD-500 (Prod System, Logical System-LOGSYS500) and RRD-500 (Pre-Prod System, a copy of PRD System here also Logical System-LOGSYS500) so to avoid this situation we have created connectors as <SID>CLNT<CLIENT> to maintain the uniqueness of the connectors.
Is this really not allowed? I mean if RFC Connection/Connector is not same as Logical System then things may not work? Because till now Access Risk Analysis is working absolutely fine.
If that's really the case do we have to change our logical systems to maintain the uniqueness?
Moreover, initially I also concluded that naming inconsistency of Logical System/RFC Connection/GRC Connector could be the issue, so I had tested the same scenario for one of the another connectors for which RFC Connection & Logical System (At Back-end) are exactly same as the Connector, I was getting the same error there also.
I am not sure what could be the exact cause?
For all the searches on this I have came across the check is to ensure that the Integration Scenarios should be maintained correctly for all four scenarios, which they are already.
Let me know what you think?
Regards,
Akshay
or ex- PRD-500 (Prod System, Logical System-LOGSYS500) and RRD-500 (Pre-Prod System, a copy of PRD System here also Logical System-LOGSYS500) so to avoid this situation we have created connectors as <SID>CLNT<CLIENT> to maintain the uniqueness of the connectors.
I recommend you use the convention <SID>CLNT<CLIENT> and save yourself the grief and make it easier to validate and troubleshoot your connector configuration.
Try setting PRDCLNT500 in BD54 and SM59. In your integration framework as Ramakrishna mentioned below "Maintain Connectors and Connection Types". See if that fixes your issue
Regards
Colleen
Yes, I am keeping that naming convention only i.e. <SID>CLNT<CLIENT>.
Setting the RFC Connection & GRC Connector same as Logical System in BD54, doesnt helps
In that case too, the same error is coming.
All other entries are as specified in Maintain Connector and Connection Types
Awaiting SAP's intervention now.
Regards,
Akshay
I resolved that error "Error in Connector; Reason Correctly define the Logical Connection in CCITS"
The error was not due to the configuration fallout, rather it was an authorization issue.
The Housekeeping user with with which the EAM Master Data Sync job used to run was not having required authorizations.
Following authorization made it work Auth. Object - GRFN_CONN with ACTVT - 16
Once authorized job ran successfully and no error spool created.
I validated the sync by opening some tables in Plug-in system post that
Thanks for your help too!
Regards,
Akshay
hi please it wud be a great help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.