cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC-XI-File

Former Member
0 Kudos

One more question !

OK..I am trying to send IDOC from SAP to XI to File.

My error in SAP:

"No service for system SAPAC3, client 005 in Integration Directory"

My System details:

SAP R/3 46C

XI30 - SP9.

I copied an IDOC using WE19 and changed the Recipient port and partner to point to XI and I got the above error.

Before I explain all my config settings, two qstns:

1> what shld the business system role be for the bus system pointing to SPR3 box ? (Application system or Integration server)

2> Don't we need to build ALE model from SAP-XI in R/3 system ? Txn BD64.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

STALANKI
Active Contributor
0 Kudos

/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

This will actually deal with your port and partner problems.Read them and use it.

Former Member
0 Kudos

Thanks Sravya.

BTW kudos for writing excellent weblogs. I found weblogs for mapping (I and II) very helpful.

Points awarded.

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

This is because it is in PE and it will go out as soon as it will get the free process.

Thanks,

Prateek

Former Member
0 Kudos

Thanks Prateek.

It is still not working. If I seen the inbound queue in SMQ2, status is SYSFAIL and if I dbl click that it has 5 entries (bcos I tried sending it 5 times) and status text for each line is 'Transaction recorded'.

also when I use SXMB_MONI and click on the message id, I do NOT see any XML on the two windows.

Any ideas what is happening ?

sam_raju
Contributor
0 Kudos

Hi Bhaven,

Make sure that you have the AI_RUNTIME_JCOSERVER and AI_DIRECTORY_JCOSERVER RFC destinations in SM59 of XI are correctly defined.

Also, make sure the UNICODE radiobutton is checked for the following RFC Destinations in SM59.

AI_RUNTIME_JCOSERVER

AI_DIRECTORY_JCOSERVER

LCRSAPRFC

SAPSLDAPI

Hope this helps.

Rgds,

Sam Raju

sam_raju
Contributor
0 Kudos

Hi Bhaven,

Create the IDoc receiver communication channel in your Integration Directory for the R/3 Business System with RFC Destination(same as in SM59 of XI), PORT(same as in IDX1) and SAP Release. Try executing your message from SM58 by clicking on F6.

This should work.

Rgds,

Sam Raju

Former Member
0 Kudos

I did that and SM58 gives error as:

"Function module does not exist or EXCEPTION raised"

I am sending IDOC from SAP to XI..why do I need to create Recvr comm channel for SAP system ?

-Thanks though

Bhaven

bhavesh_kantilal
Active Contributor
0 Kudos

Hi Bhaven,

I have mailed u the IDOC tutors, hope they prove to be useful.

Meanwhile, do take a look at this blog too

Regards,

Bhavesh

Former Member
0 Kudos

Thanks Bhavesh.

What blog are you referring to ? Can u plz send me that link again ?

Also what email acct did you send me the tutors ? I just checked my emails and I don't have not received any emails from you.

-Thanks

Bhaven

sam_raju
Contributor
0 Kudos

Hi Bhaven,

>>>>>><i> I am sending IDOC from SAP to XI..why do I need to create Recvr comm channel for SAP system ?</i>

This is a workaround and it works fine with this change. Execute the message in SM58 after you create the Idoc receiver CC in ID.

Another workaround is to deactivate the syntax check in Transaction SXMB_ADMIN in the menu option 'Configure Integration Engine' for the category IDoc (set the current value to '0').

Also Check the following

1) In SM59 of XI,HTTP INTEGRATION_DIRECTORY_HMI has tested succesfully with response status 500.

2) In Tr. code SXi_Cache select XI Runtime cache-->start delta cache refresh.

3) Execute the message again from SM58 of R/3 system to see if it works.

Rgds,

Sam Raju

bhavesh_kantilal
Active Contributor
0 Kudos

Hi Bhaven,

I guess when you work late into the night, your mind gets clogged

here is the blog, I was referring to,

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

Regards,

Bhavesh

Former Member
0 Kudos

Thanks Bhavesh

Points awarded .

Former Member
0 Kudos

Sam,

I am finally able to get IDOC into XI. SM59 for INTEGRATION_DIRECTORY_HMI was not working and now it if fixed.

But I am not able to see the file in XI box (usr/sap/trans dir. In sxmb_moni status of the message is 'Scheduled for outbound processing' and NOT 'Message processed'.

What could be the reason ?

Insufficient priviliges to write/create file on unix ? I have asked BASIS abt that?

-Thanks

Bhaven

MichalKrawczyk
Active Contributor
0 Kudos

hi,

did you maintain TCODE - IDX1?

sap port - SAP<SID>

>>>>2> Don't we need to build ALE model from SAP-XI in R/3 system ? Txn BD64

no need for that

Regards,

michal

Former Member
0 Kudos

Thanks Michal.

Yes I did idx1 for SAP<SID>, idx2 also.

Also adapter specific settings for bus system also populated correctly.

Also read ur post for "unable to conver sender service to an ALe log system" and made sure log system is assigned to my business system.

If you need I can send all my settings separately in a word document to ur email id.

Let me know and thanks a million.

BTW, I see the idoc status as 03 in we05 but SM58 shows the error as posted in my original post, indicating that IDOC is still "hanging" in SAP.

Bhaven.

MichalKrawczyk
Active Contributor
0 Kudos

hi,

but this error indicates that the IDX1 is wrong

can you check it once more?

did you try to do F6 in SM58?

Regards,

michal

Former Member
0 Kudos

My idx1 screen:

*****

Port SAPAC3

Client 005

Description Port to SAP AC3 System

RFC Destination AC3

Partner No.

Partn.Type

****

My Idoc control record screen:

****

Recipient:

Port XI3_005 XI3 System

Partn.type LS Logical system

Function

Partner number XI3_005 XI3/005 System

Sender:

Port SAPAC3

Partn.type LS Logical system

Partn.function

Partner number AC3005 AC3 R/3 to R/3 Base Logical Syste

***

F6 in SM58 still gives error "No func module exists".

-Thanks

Bhaven