Idoc not reaching XI

[Former Member]

Hi Experts,

We have a Idocto File(FTP) scenario.

We have configured the following to receive the Idoc from SAP to XI.

In SAP,

Sm59 u2013 RFC destination is available u2013 Connection is Successful during connection test

We20 u2013 Partner Profile is created with partner type, partner Number and Message Type

We21 u2013 Port is available for the above mentioned RFC destination.

In XI,

Sm59 u2013 RFC destination is available u2013 Connection is Successful during Connection Test

Idx1 u2013 Port is maintained with the corresponding RFC destination.

When we trigger an Idoc from SAP through We19 transaction, the idocs are not reaching XI.(i.e. we could not see any idocs in TCODE:Idx5). In We02 of SAP we could see the idocs with Status 03.

Kindly suggest what exactly would be the problem.

Best Regards

Suganya.

[former_member208856 · Accepted solution]

In XI System

IDX2 - Import Idoc Matadata.

In ECC & XI System

check SM58 SMQ1 & SMQ2. Is there any error ?

If there is any error, rectify that error & send idoc again.

[Former Member · Accepted solution]

I have checked sm58, smq1, smq2 in XI box. There are no errors...

[nikhil_bose · Accepted solution]

see which pipeline has errors in SXMB_MONI

[Former Member · Accepted solution]

The recipient details are provided correctly while triggering the idoc in we19

In sm58 of SAP system there is an error which states that "No service for system , < SAP client number> in Integration Directory"

Can anyone please suggest how we can proceed further on this?

[Former Member · Accepted solution]

>

> see which pipeline has errors in SXMB_MONI

Can we really see it in MONI even though the IDOC has not reached into XI/PI?

[Former Member · Accepted solution]

we wont be able to see any message in sxmb_moni since the idoc has not reached XI/PI

[nikhil_bose · Accepted solution]

Hi Sarvesh,

Thanks for pointing out.

Saranya,

Could you please delete the loaded Metadata in IDX2 for the particular IDoc and try triggering the IDoc from R/3 ? Check in R/3 sm58 the status of IDoc transfer. Refreshing IDX2 will show if meta data is getting filled up.

regards,

Nikhil

Edited by: Nikhil Bose on Aug 30, 2010 3:05 PM

[former_member183908 · Accepted solution]

Hi Suganya,

-->check the Business System of type Web as ABAP,check whether the LS name is assigned it or not.

--> I guess the problem might be because of that.

Thanks

[Former Member · Accepted solution]

> In sm58 of SAP system there is an error which states that "No service for system , < SAP client number> in Integration Directory"

Check the Business System in SLD and make sure the Logical system which you given there while creating it is exactly same as in the R3 system.

[Former Member · Accepted solution]

Hi Suganya,

In addition to what our Pi friends suggested earlier...

check ... menu options u2018Serviceu2013>Adapter Specific Identifiersu2019 for your Business system.Logical system name must appear under IDoc options. If not, you can specify it or click sync with SLD option. Then save and activate your changes.

Cheers,

Ram.

[Former Member · Accepted solution]

Hi Team,

We are doing a FIle to File scenario. For a field in sender source file we have some special characters like 'ö','ß' when this is passed through PI mappping the output data is something different though we do a direct mapping between source and target field.

Our requirement is to send the data as it is in the source file.

Kindly suggest

Thanks

Suganya.

[former_member342243 · Accepted solution]

How to Import Idoc metadata to idx2 .

plz help.

[former_member183908]

Hi Suganya,

---> Recheck the control record details which you provide in WE19 t-code.

-->Chck whether the details are pointing to PI or not.

Thanks

[Former Member]

The very basic thing which you have to make sure is, the recipient information mentioned in control header of IDOC is correct or not before you trigger it from WE19.

Note: Status 03 can also come if you configured some other existing port in the control record which may point to some other system.

[Former Member]

Hi,

There could be following reason:-

1. Check your IDX1 and Idx2 configuration.

2. File recevier Configuration like Directory location.

3. It may struct in queue.

Regards,

Anshul

[Former Member]

Hi

Can you check from sm58 (transactional RFC) whether you idoc stuck or got error.

Regards

Fernand.