IDOC- XI- FILE

[Former Member]

Hi to all,

I am working with IDOC to FILE scenario in XI, IDOC is successfully created with status 03 in R/3 system (using EDI i.e sending PO to Vendor).

I designed and configured both IR and ID objects Successfully .

Problem Is when i am sending IDOC in R/3 it is not reaching XI,

a) there is no data at the specified location in Receiver communication channel ie

b) there are no messages in IDX5, SSMB_MONI.

BUT when I send some TEST data (idoc data converted to xml data) using

RUNTIME WORKBENCH-- COMPONENT MONITORING,

Success message is seen in SXMB_MONI.

PLZ provide me with a solution.

With regards

UDAY.

[Former Member · Accepted solution]

Hello Udday,

Let us know what kind of error do you see in SM58 when you send the idoc to XI. SM58 tells us why the idoc is not reaching XI .

Thanks,

Nivedita

[Former Member · Accepted solution]

hi to all

thank u for u responses ,in sm58 it said abt the <b>tcode IDX1</b> and the description

said <b>PORT sapxxx, client yyy RFC destination contains error</b>

in the XI system my port in IDX1 was <b>sap_xxx</b> with rfc connecting to R/3 sytem

later i changed name of the port to <b>sapxxx </b>

after that when i sent IDOC from R/3 system XI sytem was able to recieve the msg successfully and i could see message in IDX5 and SXMB_moni.

<b>the lesson learnt is name of the PORT in the XI system play a vital role </b>

thank u to one and all for helping me out.

Especially NIVEDITA's input was helpful..

Thank u

UDDAY.

[Former Member]

hi to all

thank u for ur responses,i have checked with sm59 its working fine with remote logon.and maintained partner profiles in we20 in the r/3 side but<b> in sm58 i had some logs which i deleted successfully </b>,then i got metadata in idx2 in the xi system ,

after that i again sent idoc thru we19 and removed logs in sm58 but<b> still there are no messages in idx5 or even sxmb_moni,</b>

plz help me in solving this pbm,reward points will be awarded fully if sucessfully

regards

udday

[Former Member]

Hello Vuday....

Make sure of the following steps to test the scenario.

Testing:

Log in to Adaptor Monitor and check for the file adaptor. The status of the adaptor should be green and working.

Check the ftp connection, it should connect to destination folder without any error.

Log in to sender system, go to transaction WE19 (test tool to generate IDoc), generate Idoc of the required message type.

Log in to Xi system and execute transaction SXMB_MONI and check for the XML messages. Use your source and destination system to filter messages, it should have chequered flag.

Check the destination directory, it should have file with the name specified along with the time stamp. Check the file, it should have data for all segments.

Reward Points if it is useful....

Thanks,

Satya Kumar.....

[Former Member]

Hi ,

You may have to load the meta data using IDX2 after creating the port using transaction IDX1. Trying doing this and let me know ?

Thanks,

Nivedita

[Former Member]

Hi Udday,

The problems can be the following:

- The parnert isn't defined in the WE20 transaction or the Idoc isn't configured as outbound in the WE20.

- You can send a Idoc copy to XI with the transaction WE19 (If the send is succesfull a message indicating the new idoc number will be show in the screen otherwise the system will show a error).

- Review the parameters of the control record of the Idoc.

Regards,

Jose

[ravi_raman2]

I would look at what manuel suggested............then rerun the idoc test tool...we19 ..check status of outbound idoc in r/3 then run to xi and check there if not found check inbound queue to see where its stuck..

Regards

Ravi Raman

[Former Member]

Hi Udday,

Check the transaction <b>SM58</b> in your sender system and see if the Idoc is struck there.

Make sure you have a port created in XI to receive the IDoc(IDX1)

Regards,

Divija.

[Former Member]

check BD87 on R/3 side

Thanx

Aamir

[Former Member]

hi

on R/3 side status of the IDOC is 03. still do i need to execute BD87.

regards

uday

[Former Member]

well you might have send IDOC via WE19 from R/3 right?

its possible that IDOC can get stuck and for that you need to look into BD87

Thanx

Aamir

[former_member181962]

Hi,

Did you check if you have defined your partner profiles(we20), Ports(we21) and rfc destination for XI from R/3(SM59) correctly?

If not check them.

Regards,

Ravi Kanth Talagana