cancel
Showing results for 
Search instead for 
Did you mean: 

Error in SAP HCM Integration with SuccessFactors Recruiting module

Former Member
0 Kudos

Hello,

I am integrating my R3 With SuccessFactors Recruiting in the module when I'm running the program RH_SFI_SYNCH_METADATA always giving me this mistake

Error retrieving data for SFSF recruiting ad hoc reports

Technical error: Receiving list of SFObjects from SFSF failed

All I can see in the trace is the following

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

Caused by: com.sap.mw.jco.JCO$J2EEAbapException: (126) EP_ERROR: Exception during profile read

at com.sap.rprof.remoteProfile.ejb.GetProfileParameterBean.processFunction(GetProfileParameterBean.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)

at com.sun.proxy.$Proxy3338.processFunction(Unknown Source)

... 10 more

Thank you very much, experts

Ruben Moral.

Accepted Solutions (1)

Accepted Solutions (1)

Muniyappan
Active Contributor
0 Kudos

can you check message status in PI? are you able to see request and response?

is the message delivered to SF successfully?

in SF

you can go to Admin tools-->SFAPI audit logs to see the sf logs.

Former Member
0 Kudos

I see this logs

Muniyappan
Active Contributor
0 Kudos

Looks like issue with soap axis. check this.

Former Member
0 Kudos

It`s worked !!!!

Now you are giving me other errors,

<?xml version="1.0" encoding="UTF-8" ?>

- <ns1:SFWebServiceFaultException xmlns:ns1="http://sap.com/xi/SFIHCM01">

- <standard>

<faultText>Invalid SFAPI session!</faultText>

</standard>

- <addition>

<errorCode>INVALID_SESSION</errorCode>

<errorMessage>Invalid SFAPI session!</errorMessage>

</addition>

</ns1:SFWebServiceFaultException>

Muniyappan
Active Contributor
0 Kudos

Hi Ruben,

this looks different issue. please create new thread.

Former Member
0 Kudos

ok

former_member184948
Active Participant
0 Kudos

Can you tell us what you did to fix that error?

Former Member
0 Kudos

Hi,

this was resolved with 1776204 sap note.



Former Member
0 Kudos

Hi,

this was resolved with 1776204 sap note.



Answers (4)

Answers (4)

sunil_singh13
Active Contributor
0 Kudos

Ruben,

Your Log shows  "Exception during profile read" Looks like connectivity is not setup correctly. Please Perfrom some connectivity test using other Scenario and see if it goes well.

Thanks,

Sunil Singh

former_member229310
Active Participant
0 Kudos

Hello Rubén,

As you said you are correct, the problem is arising during the generation of message within HCM.

Do you see any other scenarios working or  is this first scenario you are implementing ?  Kindly verify initial settings at HCM to make the Integration set up. Do you have any SSO in this scenario configured to make connection with SF.

Let us know more on the flow so someone can provide inputs.

Cheers!!!

Former Member
0 Kudos

I see this log

former_member184948
Active Participant
0 Kudos

Hi,

Check the payload of the message in PI both going out and specially coming in from SF. That payload many times contain exact error.

Former Member
0 Kudos

But the interface fails to connect with SuccessFactors, since the problem is between SAP HCM and PI

former_member186851
Active Contributor
0 Kudos

Hello Ruben,

All the certificates required to connect SFSF are installed in PI?

Former Member
0 Kudos

All required certificates have been installed.

Former Member
0 Kudos

I see this log

Former Member
0 Kudos

Can you check the logs on Successfactors side ? This will give you the exact error if it is an application error.

Former Member
0 Kudos

Hello,

I do not know where the logs are. Can I have them indicate how ?.

Thank you!