Inbound Idoc processing issues - Partner Profiles - error status 56

[#1]

Hello All,

I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.

The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.

The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?

SOAP Header in IDocOutbound tag

<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>

<SAP:RCVPRN>[String Value]</SAP:RCVPRN>

<SAP:RCVPRT>LS</SAP:RCVPRT>

I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?

When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.

Any help is very much appreciated! 😄

[Former Member]

Hello All,

Thank you for the responses. I followed the basic ALE configuration check lists above before and everything seemed to be fine. My answer came with some trial and error and other outside help. There were a few issues i want to address for the inbound xml from XI to the ERP:

1: Receiver Partner Number

-- When i checked the SLD Logical System Name for the business system it was correct. When i checked the Logical System Name of the business system in the integration builder (by opening the business system object, clicking 'service' from the object menu and clicking 'adapter-specific identifier'), i noticed the Logical System Name was a differnt value which ended up being the unknown string that i was trying to find before. Clearing the SLD cache did not resolve this link and the value needed to be updated in the Integration Builder manually. This is done by first selecting to change the Business System Object and clicking the copy from SLD icon after going to the above-mentioned adapter-specific identifier. This resolved the IDOC receiver partner number being an unknown string value.

2. Sender Partner Number

-- Originally i did not believe this to be an issue with the ALE config, but apparently i did not cosider that the matching between the Logical System Names in the SLD, Integration Builder Objects, and the Logical System Name in the recieving remote system would be CAP sensitive. Although the value of the Logical System Name is correct, some of the characters of the Logical System Names in the SLD and Integration Builder were lower-case. The same Logical System Name in the remote ERP system were all upper-case. I fixed this in the SLD and cleared the SLD cashe on the Integration Builder and it worked. Now i get a status 51, but i just need to fill the proper fields for proper idoc inbound processing since the partner profiles are now being found with the (now) correct header data.

[former_member859847]

Hi,

Could you please check the TRFC logs in SM58.

some times, our confiuration is good but there is a possibility of trfc rerros.

then u have to release and refresh.

regards

mahesh.