Regarding Idoc issue

[Former Member]

Hi Folks,

I have triggered the Idoc from R/3 to XI.

For the statue 30: I can see the text as:

Receiver exists , No filters , No conversion , No version change

Please let me know the meaning of this.

can we use any code page conversion parameter in ALE to convert the data.

Issue is like:

In the Idoc I am getting the data correctly. But when the Idoc sent to XI with the help of batch run it went with some invalid character set. (I have checked inbound message payload in XI)

I have re-triggered the same Idoc manually using the logon language as chenese and now it went to XI with the correct Chinese character set.

Please guide me why it is transferred to Xi with Invalid data for the first time ?

Thanks,

SPMD.

[former_member208856]

For status 30, Idoc is in Yellow flag.

goto BD87 --> give Idoc number which is in Yellow mode --> Process.

Now status will be green for Status 03.

If status is 03, goto we02 --> double click on Idoc --> Control Data.

Now check Sender Port & Receiver Port.

Maintain Ports as you can see in that control data.

[Former Member]

Hi Folks,

Please answer my thread ...

Thanks,

Shabbbir.

[Former Member]

Hi,

Check whether 'Unicode' option is enabled in RFC destination(pointing to PI in R3) or not?

Regds,

[Former Member]

Hi Suresh,

Thanks for the answer, but can you please explain where we can maintain this unicode settins in RFC destination.

Thanks,

SPMD.

[Former Member]

Hi Shabbir,

This is encoding problem, as Suresh said you could try with Unicode option in RFC destination.

Go to SM59 and in your ABAP type RFC destination go to Tab MDMP & Unicode and there select Unicode as the communication type with Target System.

The other option could be to use XSLT mapping and change the encoding of your IDOC xml to d relevant chinese encoding and then call the mapping function.

Regards,

Rahul Grover

[Former Member]

Hi Rahul,

I am using sap R/3 system with release : 4.6C.

The RFC destination is of type: 3.

I can't see any MDMP tab in that...Could u please guide me the navigation steps how can we check ...

Thanks,

Shabbirpasha.MD

[Former Member]

Thanks, the issue is solved. The batch job is triggered again adding code page.

Issue is resolved.

SPMD

[Former Member]

Yes, we can use code conversion paramter in ALE to convert the data.

I did not sure about what exactly the issue. Could u please elaborate the issue.

For the statue 30: I can see the text as:

Receiver exists , No filters , No conversion , No version change

This is when the IDOC might be scheduled or stuck at the port.

[Former Member]

Hi ,

I will explain you oit clearly.We are sending idoc to XI.

we have 2 cases here:

1st case:

-

-

---

Idoc triggered for the first time and in data segements we can see the data as:

name : ³£ÖÝÊа²½­°Ù»õÓÐÏÞ¹«Ë¾ --this is in data segment.

In XI (Inbound payload) we see the same data: (Inbounb payload )

My doubt is when the same idoc triggered for the first time the data conversion is not done and when the same Idoc is triggered manually the data conversion happend and we se the correct data in chinese format.

Appreciate your help.

Thanks,

SPMD