cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to find Idoc in XI

Former Member
0 Kudos

Hi,

Idoc -> XI -> File

I am trying to send an Idoc (ZANSO_MT) from R/3 side to XI.

Status of the message is green in we05 in R/3 but I am unable to find it in XI. I have checked in idx5, we05.

All the RFC connections are working fine with authorization test.

Althought, I was successfully able to import Idoc metadata in IR but I have an error in idx2 "Basic Type ZANSO_MT is unknown". This IDoc is released in R/3 side and I am successfully able to generate and send it.

Pls let me know where to check.

Regards,

Anirudh.

Accepted Solutions (0)

Answers (6)

Answers (6)

turmoll
Active Contributor
0 Kudos

Looks like it is in error status in SM58 on R/3 side.

Jakub

Former Member
0 Kudos

Thank you all for your responses.

@Jayasimha

RFC destinations are working fine as mentioned in my first post.

I have done connection test and also authorization test.

I can see the IDoc successfully sent in we05 in R/3.

I have also changed the port name in idx1 in XI same as in R/3 but still no success.

@Vijayanth

Check smq1,2. Both are empty. I can import Idoc metadata for ORDERS03 or WP_PLU03 from R/3 but not ZANSO_MT.

I created this custom Idoc in R/3 and I am able to import it in IR.

@Nallam

I have released Idoc in R/3 with transaction we30, we31 and we82. I am successfully able to import this Idoc in IR.

@Seshagiri

I have created this basic type in R/3 and able to import it in IR.

The problem is that in idx2 when I try to import it, it doesn't work but other Idocs like orders etc are getting imported successfully.

@NagaDurga

Tried it but no success.

@Jakub

I can see some errors for this Idoc in sm58 in R/3 but many ZANSO_MT Idocs are successfully processed and their status is green in we05.

Regards,

Anirudh.

Former Member
0 Kudos

hi

please check the logical sys name in the partner profile(we20).it must be same as xi LS name.

you should maintain the LS name for both the xi as well as source system in tcode bd54.

regards,

navneet

turmoll
Active Contributor
0 Kudos

> @Jakub

> I can see some errors for this Idoc in sm58 in R/3 but many ZANSO_MT Idocs are successfully processed and their status is green in we05.

What is the error? Green in we05 does not mean - "delivered to target system". It is still in ERP.

Regards,

Jakub

Former Member
0 Kudos

Navneet,

I have changed the name of R/3 logical name in sm59 in R/3.

Do I have to do it in XI too?

I am testing it again... and will let you know.

Also, one more point that I want to mention.

When I send the Idoc via a report, it gets stuck with status 30.

I then go to we19 and reprocess it. It then get successfully processed.

Regards,

Anirudh.

Former Member
0 Kudos

hi

please check these links

http://download.oracle.com/docs/cd/E05554_01/books/ConnSAP/ConnSAPTroubleshooting5.html

all r saying that there is problem in partner profile.

status 30 mins idoc are ready to dispatch,and execute bd87.

you can try RBDMOIND also.

thats why u r getting success with we19..

Former Member
0 Kudos

hi,

Try keeping the port in XI ( IDX1) same as the sender port in ECC(we21)

Thanks,

Durga

Former Member
0 Kudos

Hi,

You have to provide the correct Basic Type for the idoc in IDX2(in XI)

This type of the Basic Type is not present in R/3( ZANSO_MT)

Check it once

Regards

Seshagiri

former_member192295
Active Contributor
0 Kudos

HI,

It is due to authorization problem, we can import idoc structure but can't receive data from R3, that why it is throwing error, check with basis team for authorization meanwhile once again check all necessary steps weather all segments and idoc versions are released or not.

Meanwhile check all mandatory segments are populated or not why because some time based on values segments will be populate automatically some times it will be hide due to no value.

It will solve easily.

former_member183906
Active Contributor
0 Kudos

Hii

Check in outbound Queues(SMQ1 and SMQ2). if the messages are struck there, if so then unlock the message and activate it. Check SM58.

If still not resolved, in IDX2, check if its old metadata. Renew it.

Rgds

Former Member
0 Kudos

1)Create the RFC destination in XI for ECC System of type 3 ( if it created the check the RFC destination is working or not)

2) Create th port in IDX1( Xi server). The port name should be same as the sender port of ECC server and place teh RFC which is created in step 1.

Above are the steps to be done in XI other wise IDOC wont come into XI.