Inbound IDOC - RCVPOR is blank

[Former Member]

Hello everyone,

I have created a scenario for X12 850 to ORDERS05 IDoc.  The EDI_DC40 elements have been hardcoded in the Message Mapping but when I post the IDoc into SAP, the RCVPOR is always blank.

I've looked at all the threads posted on this but I still have not been able to populate this field.

The Partner profile displayed in the Control Record are as follows:

Recipient information

Port: blank

Partner Number: ILDCLNT130

Partn. Type: LS

Function: blank

Sender information

Port: is populated

Partner number: is populated

Partn. Type: KU

Partner Role: CR

I have also tried various configuration changes in the receiver IDoc_AAE adapter (7.4).  I have selected/unselected the "Apply Control Records from Payload", "Apply Sender from Payload" and "Apply Receiver from Payload" but the RCVPOR is always blank.

I really would appreciate all the help on getting this resolved.

Thanks,

Dave

[Former Member · Accepted solution]

Thanks Dimitri and Eng Swee for responding!

I found the issue.  I incorrectly specified the SNDPFC as SP instead as AG.  Once corrected, the IDoc posted into SAP with the correct RCVPOR field.

Cheers,

Dave 

[Dimitri]

Hi David,

This is how I created my message mapping...

The following fields in the EDI_DC40 segment can be filled with constants.

• SNDPOR – sender port
• SDNPRN – sender partner number
• RCVPOR – receiver port
• RCVPRN – receiver partner number

Afterwards, they will be overwritten

• By the header mapping settings for the sender part
• By the receiver IDOC adapter for the receiver part

In my ICO object, I indicated my SAP receiving Business System in the header mapping part.

That should to it. Please try it and revert back

Kind regards,

Dimitri

[Former Member]

Hi Dimitri,

Thanks for replying!

As you stated, I did hardcode the RCVPOR field (and others) but not sure I understand how to define the SAP receiving Business System in the header mapping part.  Are you saying I need to specify my BS in the Header Mapping - Receiver Communication Component?  If so, how should I set the "Advanced Options" in the IDoc_AAE adapter for the payload?

Not sure if this is an issue, but my BS is configured as <sid>_<client> but the RCVPOR should be SAP<sid>.

Thanks!

[Former Member]

Dimitri,

When I view the IDoc Control Records with the PI IDoc Adapter Monitor, I do see that RCVPOR is populated with SAPILD.  So not sure why it is then blank when posted into SAP.

Thanks

[engswee]

Hi David

If the RCVPOR is populated on the PI side and you can see it in PI's monitor, I suspect the issue might be the configuration on the receiving SAP system.

Can you check if the IDoc in the receiving system is in status 56? If it is, then it might be because there is no matching partner profile configured in WE20. Do refer to my reply on the thread below:-

Recipient port and Message function are missing

I'd suggest you check the partner profile on the receiving system, make sure the config matches:

- sender information (sender partner no, sender partner type, sender partner role)

- and message details (message type, message variant, message function)

Rgds

Eng Swee