PI: File to IDOC port is empty in R/3 system

[ronnypol]

Hi,

We send an IDOC from PI. We can see the IDOC in R/3 (WE20) but the "port" is missing under "recipient infromation", there is no character in there. The other fields are all set. Where we have to set our port? In the communication channel is nothing to set.

Thanks

Ronny

Edited by: Ronny Pol on Feb 12, 2010 4:22 PM

[former_member208856]

For IDoc Port & Partner Profile on PI & ECC system.

You have to create Port at PI :

In IDX1,

Import Matadata in IDX2.

at ECC

Create Port in WE21

& Create Partner Profile at WE20.

Make entry in WE20 for Inbound Message for IDoc.

In message mapping Disable the control records.

Check these setting.

[abhijitbolakhe]

Hi

The following configurations must be followed for succefull posting of data in File2idoc interface.

1) A logical system name should be assigned to the third party Business system in SLD.

2) In R3, create a logical system (BD54)....its name should be same as used in Third party Business system.

3) Now create a partner profile in R3 (we20) type LS....partner profile name should be same as logical system name.

4) add the inbound parameters in the partner profile

Now, when data is posted in SAP...receipent information will contain the port details and data will be sucessfully uploaded in sap

Regards

Abhijit

[Former Member]

Hi Ronny,

Can you see the RCVPOR in your payload?? if yes then select all the three check boxes in adapter refers to payload.

Basically there are two ways to send Receiver and Sender details to R/3, one is from payload and the other is from configuration....if you check the "Apply Control record from payload" along with this you should check "Take Sender from payload" and "Take Reciever from payload"......if you uncheck Apply control record from payload then it will take these details from SLD. Make sure that these are given there.

Regds,

Pinangshuk.

[Former Member]

Am considering you are populating control record data(RCVPOR,RCVPRN,RCVPRT,RCVPFC) in PI before sending it to ECC. If yes, in the receiver IDOC channel check the option Apply control record values from payload

All of it will then be reflected in WE20.

Regards

Soumen...

[ronnypol]

Hi Soumen

No, we are not populating control record data in PI. We deactivated these fields...

Regards

Ronny

[Former Member]

No, we are not populating control record data in PI. We deactivated these fields...

Then I guess its unable to pick all the information(regarding sender/receiver port) from standard configuration.

Check the configuration once again that you have done(Abhijit's post above states the steps).

or

If you have time try the approach to populate EDIDC40 node in mapping and checking the option(Apply control record data from payload) in receiver IDOC channel.

Regards

Soumen...