PI to ECC IDoc transfer issue

[Former Member]

Hi All,

We have an MDM to IDoc scenario. MDM is sending data which is converted to IDOC.

In the receiver IDOC channel we have the below setup.

We are getting the below error.

MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Recipient Partner Number is not available.

Even for setups where we have used the Apply Control Records from Payloads and provided values we are getting the same issue.

The same interface works perfectly in Production and other environments,

What can be the possible issue?

Thanks,

Shaibayan

[manoj_khavatkopp · Accepted solution]

• When you are not using Apply control record from payload, i hope you are using Header mapping in the ICO  cross check Logical system is maintained in the Adapter Specific Attributes of the business system maintained or not , if not make sure you maintain it in SLD and you may re-import the business system again.

• cross check in we20 whether the partner exist and it has the inbound parameter setup done for whatever IDOC you are pushing.

Br,

Manoj

[Former Member · Accepted solution]

• When you are not using Apply control record from payload, i hope you are using Header mapping in the ICO cross check Logical system is maintained in the Adapter Specific Attributes of the business system maintained or not , if not make sure you maintain it in SLD and you may re-import the business system again.

- We are not using Header Mapping. The thing is the interfaces stopped working suddenly and only for these types of IDocs where we are not sending RCVPRN.

• cross check in we20 whether the partner exist and it has the inbound parameter setup done for whatever IDOC you are pushing.

- No authorization for this.

[Former Member · Accepted solution]

Below is the config from SLD for the concerned BS for which we are facing this issue.

Also in the mapping RCVPOR is mapped to a constant SAPDEV.

SAPDEV for the concerned test system is SAPUAT.

You can consider the above as the screenshot of the business system for SAPUAT system.

[PriyankaAnagani · Accepted solution]

Are you using Idoc or Idoc_AAE adapter?

If its IDoc_AAE, can you try with "Override IDoc Control Headers" option in the IDoc receiver channel.

Refer this
http://scn.sap.com/docs/DOC-59083

Also make sure

• Cache is updated correctly.
• Restart IDoc receiver channel after enabling this.

---Priyanka

[Former Member · Accepted solution]

We are using IDOC_AAE. We are not using Override IDoc Control Headers. Even without this the IDocs are flowing in other environments.

[manoj_khavatkopp · Accepted solution]

Chk in we20.

[Former Member]

Somehow the Adapter Specific Identifier was getting removed. We fixed it and its working.

[Former Member]

Hi Shaibayan, Please check the SAP Note 1653715 on this and also cross validate the NWA->Application Resources -> javaIdocAdapter (Resource Adapter) between your working / Not working environments. There might be some config related idoc might have been missed .

- Muru

[Former Member]

Hi Muru,

I checked the mentioned SAP Note and DefaultSenderPort is set with proper value for both Prod  as SAP<PROD> and Non-Prod as SAP<NONPROD>. Also other Connection Factory details are the same.

The issue seems to be finding the Receiver ECC details.

Thanks,

Shaibayan