sending IDoc from ERP to PI

[Former Member]

Hi all,

I am trying to sent IDoc's from the ERP (SAP ECC) side to PI. But the IDocs are not arriving at the PI side. In ECC tc:we05 they seem to be successfully sent.

The Partner Type in we20 is "LI". I added the IDoc to the Outbound parameters and set the PORT to the Port we use for PI. But unfortunately it is not working.

Any idea why?

[former_member183908 · Accepted solution]

Hi Chris,

--> As suggested check the SM58 t-code.

-->Also check the RFC destination is pointing to your PI system or not.The details in the RFC destination of type 3 should be details of PI.

Thanks

[Former Member · Accepted solution]

Yes, there is no problem in sm59. I tested it. it works

[former_member183908 · Accepted solution]

Hi chris,

--> Did you check SM58 t-code?

-->In the partner profiles check whether the radio button tirgger idoc is selected or collect idocs is selected.

-->Also check the port which you provided in partner profiles is correct.

Thanks

[Former Member · Accepted solution]

Hi,

I tried other IDocs and they are working fine. But in the ORDERS case it is not working. The only difference is that the IDoc is not LS. It is used in Partner Type LI.

But also when I open we19 and type the other LS definition in the control record I get the same problem. I don't know why?

[Former Member · Accepted solution]

In sm58 there is the following error.

EDISDEF: Port ... segment defn ZTPI08000 in IDoc type ORDERS05 CIM ty

Any ideas on this?

[Former Member · Accepted solution]

Hi,

Delete and reimport your ORDER idoc in your PI system (transaction IDX2)

Regards,

Carme.

[udo_martens · Accepted solution]

Hi Chris,

just deleting the meta data i IDX2 is enough. PI will renew them automaticly.

Regards,

Udo

[vkaushik82 · Accepted solution]

delete metedata as mentioned above but reimporting will not be required because 1st time when you will send the IDOC it will automatically create a metedata in this case.

[Former Member · Accepted solution]

Thanks you. Problem solved.

[Former Member]

Hi Chris,

Check SM58(tRFC queue) in ECC for the error log. the IDoc must be stucked there only.

Regards,

Pinangshuk.

[former_member208856]

When sending IDoc from ECC System to PI.

some settings needed on ECC System & PI System

On ECC System

Create Port in WE21 type LS (Logical System) use RFC Destination TYPE ABAP in that port.

Create Partner Profile using PORT in WE20.

Add the Idoc as Outbound in that Partner Profile.

Now on PI System

PI System does not have structure / matadata of IDoc.

Create Port in IDX1.

Import IDoc Matadata in IDX2 use Port created in IDX1.

Create complete scenario & send IDoc from ECC, it will reach at PI System, if successful at ECC.

[vkaushik82]

check Tcode sm58 if any errors are there