cancel
Showing results for 
Search instead for 
Did you mean: 

IDoc_AAE Receiver Adapter Error

jose_augastine3
Active Participant
0 Kudos

Hi

I am getting the below error

"Adding control record to payload failed due to Error during transform: java.lang.NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable chars"

It is happening for all scenarios in quality environment

It is working fine in development environment

All interfaces are using External Definition instead of Idoc since I need multiple idocs from single file.

I referred Note 1862655 (but not clear)

Do I have to maintain my receiver interface name as <MSGTYP>.<IDOCTYP>.<CIMTYP> and whether it has to be created under urn:sap-com:document:sap:idoc:messages ???

Then how it is working in development ?

what should be CIMTYP ?

Exampel : INVOIC.INVOIC01.???

Also I am using "Override IDoc Control Headers" in Advanced tab and passing SNDPOR, SNDPRT, SNDPRN

Any help is highly appreciated.

Jose

Accepted Solutions (1)

Accepted Solutions (1)

RaghuVamseedhar
Active Contributor
0 Kudos

screenshots

jose_augastine3
Active Participant
0 Kudos

Thanks a lot Raghu ...

Still I am confused, it worked perfectly fine in Development, but after transport to Quality I was getting this error

Will modify and will update you soon

jose_augastine3
Active Participant
0 Kudos

Raghu ... You made my day ... Thanks a lot 

Answers (1)

Answers (1)

RaghuVamseedhar
Active Contributor
0 Kudos

Jose,

I faced same issue last week. It is not recommended to use external definitions in PO for IDoc. I am sharing screenshots on how I was able to fix this issue.

jose_augastine3
Active Participant
0 Kudos

Hi Raghu

System is not allowing me to create Service Interface with <MSGTYP>.<IDOCTYP>.<CIMTYP>

"." (dot) is not allowed

How did you manage it ?

Thanks

Jose

RaghuVamseedhar
Active Contributor
0 Kudos

Jose,

Please do not use IDoc External Definition in message mapping, operational mapping and in ICO. This issue should be fixed.