Job GRAC_SPM_LOG_SYNC_UPDATE fails with unicode error

[Hari1]

Hello team,

We have scheduled the above job GRAC_SPM_LOG_SYNC_UPDATE to run every hour to synchronized logs from ECC system.

Now the job is suddenly failing and job log is showing the below error

Error in RFC; 'Data objects in Unicode programs cannot be compare'

we maintained communication type as unicode in RFC (SM59) in GRC to ECC and in ECC TO GRC, but still the job is cancelling with the above error.

one more point, we are getting this error only in GRC production pointing to ECC production and is succesfully executing for the BI connector

Please let me if you anyone has experienced similar error.

Thanks in advance

Hari

[alessandr0]

Dear Hari,

the error comes because the program checks for unicode (you can see in SE38 -> attributes of the program).

As I've never seen such error I need some more information. Do you face a dump in ST22?

Regards,

Alessandro

[Hari1]

Dear Alessandro,

Thanks for your reply.

There are no dumps in ST22 and there is no error information in SLG1 also.

As mentioned previously, this job is not cancelling in GRC quality and Dev systems.

I alredy checked the program attributes and unicode check is active.

Out of the below  two jobs which one is required to schedule when we activate Firefighter log review workflow.

FireFighter Log Synch

FireFighter Workflow Synch

Will there be any issue to schedule the job FireFighter Log Synch instead of FireFighter Workflow Synch job if Firefighter log review workflow is activated?

Thanks
Hari

[alessandr0]

Dear Hari,

the issue is very strange and I don't have a solution at the moment.

The two jobs do consider parameter 4007. If 4007 is set to NO then the application only collects the logs with job GRAC_SPM_LOG_SYNC_UPDATE. The workflow and notification is sent with job GRAC_SPM_WORKFLOW_SYNC. If it's set to NO both jobs need to be run.

I would recommend to set parameter 4007 to YES, so that the workflow is automatically sent with the GRAC_SPM_LOG_SYNC_UPDATE program. The second program is not needed.

Hope this helps for understanding.

Regards,

Alessandro

[Hari1]

Dear Alessandro,

We have configuration exactly what you have mentioned.

We logged a  call to SAP and see what is the solution. I will also let you know.

Thanks

Hari

[alessandr0]

okay - keep us posted.

Thanks and regards,

Alessandro

[Former Member]

Hello HariKrishna,

Can you please let me know if any solution is proposed, I am also getting the same error..

Thank you !

Akshat

[Hari1]

Hello Jaiswal,

SAP informed that they are still investigating the issue. I will update the solution as soon as we get it.

Could you check and compare the versions of the GRC plug-ins in both the backend and the GRC system?

In our case, the back end systems have higher version of GRC plug-ins compared to plug-ins version in GRC systems.

Back end: GRCPINW V1100_700 & GRCPIERP V1100_700

GRC :GRCPINW V1000_700 & GRCPIERP V1000_700

SAP suggested either to downgrade the plug-in version in the back end system or upgrade GRC 10.0 to GRC10.1. We have debated with SAP on this, because the same job is executing without any issues in Quality and DEV systems.  Still they are investigating the issue.

Thanks

Hari