WmSAP Adapter error - Error during client call in service

, ,
1

Scenario - We developed a new interface and are sending inbound IDOCs to SAP.
issue - We are getting the transaction rolled back.

We have checked the pub.sap.transport.ALE:OutboundProcess service and it is not throwing any error and is successful. The SAP transaction list shows the structure confirming to SAP metadata repository but getting the below error:-

WmSAP Adapter: Error during client call in service “java.lang.NullPointerException - null”: “{1}”

Below is entire audit log for the transaction:-

Audit Log
SyncALETransport - Create 0A242416363D562F8A601463
Persisted message body to packages/WmSAP/txStore/04165F64/A2636806/243D2A13.xml
WmSAP Adapter: Error during client call in service “java.lang.NullPointerException - null”: “{1}”
SyncALETransport - Rollback 0A242416363D562F8A601463

Please let us know if anyone has faced this issue earlier We are looking into this but wanted to check if this is a known error. Not much came up after a google search :slight_smile:

Thanks,
Kushal

2

What steps did you follow in sending IDocs from webMethods to SAP

pub.sap.client:confirmTID must be always called after pub.sap.transport.ALE:OutboundProcess “for transactional invocation to complete transactions on SAP.” Did you follow the same ?

Thanks,

3

Hi,

We just use ALE:outboundProcess. I think we use confirmTID when explicitly we have invoked CreateTID.

My understanding was that outboundProcess will take care of the confirmation part implicitly.

Please correct me if wrong.

Thanks,
Kushal

4

we have invoked CreateTID.
"My understanding was that outboundProcess will take care of the confirmation part implicitly. "

Yes that’s correct.

What is your current fix level on the SAP Adapter7.1?

HTH,
RMG

5

Hi RMG,

thanks, fix level is SAP_7.1_Fix8

Are we missing any updated fix here.?

also, is there any possible way to check the rfc logs in SAP system to find more about this issue ?

Thanks,
Kushal

6

Hi Kushal,

latest Fix is SAP_7.1_Fix14.

Which Version of the JCo-Libs are you using?
This information can be found in the About-Page of the SAP-Adapter.

Latest Version I know of is JCo 3.0.13 which requires SAP_7.1_Fix14 to work correctly.

Did you check the persisted XML (packages/WmSAP/txStore/04165F64/A2636806/243D2A13.xml)?

Is the Metadata of the IDoc listed in the DDIC-Cache?
If so, clear the cache and try again.

Are there any Entries in the Error-Log related to the NullPointerException?

Regards,
Holger

7

Kushal – Also,iff you missed to provide the authentication access shared to the user which is sending IDOC to the SAP System, this error will be expected sometimes. Please also cross check this point.

Thanks,

8

Kushal – Also,iff you missed to provide the authentication access shared to the user which is sending IDOC to the SAP System, this error will be expected sometimes. Please also cross check this point.

Thanks,

9

Kushal – Also,iff you missed to provide the authentication access shared to the user which is sending IDOC to the SAP System, this error will be expected sometimes. Please also cross check this point.

Thanks,

10

Kushal – Also,iff you missed to provide the authentication access shared to the user which is sending IDOC to the SAP System, this error will be expected sometimes. Please also cross check this point.

Thanks,

11

Thanks a lot for the patch update news.

We were having a corrupt mapping which caused the null pointer issue. We replaced the mapping service with new mapping and it worked for us.

Thanks again for all your support and expertise.

Regards,
Kushal

12

Thanks a lot for the patch update news.

We were having a corrupt mapping which caused the null pointer issue. We replaced the mapping service with new mapping and it worked for us.

Thanks again for all your support and expertise.

Regards,
Kushal

13

Thanks a lot for the patch update news.

We were having a corrupt mapping which caused the null pointer issue. We replaced the mapping service with new mapping and it worked for us.

Thanks again for all your support and expertise.

Regards,
Kushal

14

Thanks a lot for the patch update news.

We were having a corrupt mapping which caused the null pointer issue. We replaced the mapping service with new mapping and it worked for us.

Thanks again for all your support and expertise.

Regards,
Kushal

15

Glad to hear issue got resolved :smiley: Thanks for updating the forum.

Thanks,