cancel
Showing results for 
Search instead for 
Did you mean: 

File Adapter issue

Former Member
0 Kudos

Hi All,

I am trying to create a scenario for IDOC(incoming) and Flat file(receiver).

While doing the configuration for the "Receiver communication channel" with the "File adapter" I find that the "Adapter Engine" is not coming up in the drop down.

Can you please let me know if some thing needs to be set up in the SLD(Business Landscape) for this to come up? If no, can you please help me in find out what could be other reasons for this.

Regards,

Rupesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

HI Rupesh,

>>I find that the "Adapter Engine" is not coming up in the drop down.

is it for File adapter only or for all adapters?

I re-imported xi3.0_basis*.tpz file once again, then it got sorted out. If possible, try like this.

Regards,

Ravi.

Answers (8)

Answers (8)

Former Member
0 Kudos

Hi Latika,

I have created one BS(BS1) for the file receiving part with technical system(TS1) which is of third party.

Now,is it required the there should be another business system(BS2) for the XI server.Since the scenario is "IDOC from ECC5 to Flat file through XI"

If yes let me know what shoudl be the parameters.

Regards,

Rupesh.

Former Member
0 Kudos

Hi rupesh,

from ur reply it seems i am misunderstood ) i am talkin about a BS in SLD that represents ur XI server.

we give this BS in " Related integration server" in SLD for our third party or other BS (in ur case BS1) i.e u mst have given a BS in " Related integration server" in SLD for ur BS1.

so what i meant was check this BS.

check:

1. Have u assigned the role "Integration Server" to ur BS (which represents XI)?

2. Is the pipeline URL correct? http://<xiserver>:<port>/sap/xi/engine?type=entry

3. Is the technical system (for this BS) pointing correctly to ur XI server?

If there is no such entry in SLD then create it.

regards,

latika.

Former Member
0 Kudos

Hi Rajeev,

Thanks for the reply.

But still its not coming up in the "Adapter Engine" drop down.

Regards,

Rupesh

prateek
Active Contributor
0 Kudos

Erro may b due to inconsistent SLDs

Apply SAP Note 764176

<i>[Reward helpful answers. This would encourage others to answer]</i>

Regards,

Prateek

Former Member
0 Kudos

Hi All,

Any update on the following problem.

Regards,

Rupesh.

Former Member
0 Kudos

Hi rupesh,

you did not provide any details about TS and BS for ur XI server. please check those on the lines i mentioned earlier.

Regards,

latika.

Former Member
0 Kudos

Hi Rajeev/Latika,

Thanks for your replies.

The following are my SLD set details:

1.There is one SWCV(S1) and Product(P1) created for the scenario.

2.These have been assigned to the third party Technical system(TS1),i.e., for File transfer.

3.These have also been assigned to a business system(BS1).

4.BS1 is also linked to TS1.

5.BS1 has got the XI system assigned to it as integration server.

These are the settings.Is there some thing missing which needs to be set up other than this???

Regards,

Rupesh R Nair

Former Member
0 Kudos

Hi Rupesh,

in your SLD, TS1 is third party tech system...create BS1 for TS1......use this BS1 in ID in this scenario and create your recever file adapter in this BS1 system.....

Create a business system BS2 which will be having your XI tech system TS2 and then assingn BS2 to integration server........

then in your file adapter, you will get your adapter engine......

Thanks,

Rajeev Gupta

Former Member
0 Kudos

Hi All,

Thanks for the help.

Is there any guide where the setting of SLD id mentioned.

This would be helpful for my current issue as the instance where I am stuck, I feel is because of SLD set up.

Regards,

Rupesh.

Former Member
0 Kudos

Rupesh,

For a File to IDOC scenario, you would need one business service (for File sender) and one Business sytem (for R/3). The business system should be based on a Tech system of type R/3. Apart from these, you should have a RFC destination (Type H) maintained in R/3 pointing to XI.

If you need to use ABAP proxies in this system, maintain your config as per this weblog

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Regards,

Jai Shankar

Former Member
0 Kudos

Hi Rupesh,

Plz check ur SLD configurations once again.

Have u assigned the role "Integration Server" to ur Busi Sys?

Is the pipeline URL correct? http://<xiserver>:<port>/sap/xi/engine?type=entry

Is the technical system pointing correctly to ur XI server?

Have u created two Tech sys? Web AS ABAP and Web AS Java?

Check on these lines or provide these details.

for configuration of TS and BS u can refer:

http://help.sap.com/saphelp_nw04/helpdata/en/35/758ece54588548960c63a7e93e8122/frameset.htm

regards,

latika.

Message was edited by:

Latika Sethi

Former Member
0 Kudos

Hi Rupesh,

in SLD, in technical system, make your R/3 system and XI system as WebAsJAVA systems and also make your XI system as integration engine......

Thanks,

Rajeev Gupta

Former Member
0 Kudos

Hi all,

Can any one provide me with a step by step process for creating an IDOC -Flat file scenario.

Regards,

Rupesh R Nair.

Former Member
0 Kudos

Hi Rupesh,

This will help you

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

Regards,

Ram

Former Member
0 Kudos

Hi Rupesh,

Pls check this as well

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

My Home > Exchange Infrastructure > ...Main > Step-by-Step Guides > File To IDOC

Regards,

Ram

Former Member
0 Kudos

Hi Latika/Ravi,

Thanks for your input

I had assigned the required system as the integration server.

It was not coming up after that also.

Is there any other reasons for this??

Regards,

Rupesh.

Former Member
0 Kudos

Hi Rupesh,

If u r using local adapter engine then that shud com in drop down else Integration Server shud come.

For this u have to maintain an entry in SLD--Technical System and Business System.

mention the system as integration server and not application system

[reward if helpful]

regards,

latika.