Error when Loading Metadata for IDOC Adapter

[Former Member]

Everybody,

I know this should be pretty straight forward and that there are a few posts about it. But following the Demo 3.0 guide and the posts I can't seem to load the data into the IDOC Adapter. I did every step in the guide and when I try to execute IDX2 for the source port I previously created I get the error "No RFC Destination is maintained for the port".

Following the guide I have my XI host

ID:ABC

Instance:01

Client:700

Executed IDX1 and got port SAPABC_107 with RFC Dest-ABC_107, which I defined previously with transaction sm59 and the test came back ok.

When I try to execute IDX2 I get the error message...

What am I missing ?????

Thanks!

Diego

[Former Member]

Hi,

Is there anything set up in transaction IDX1 for this as well ?

Hope this helps.

Colin.

[Former Member]

Everything was setup before (by following the XI 3.0 Demo guide) here are the steps I did:

1. Setup an RFC R/3 Destination on my client 107 (American Airlines) to client 700 (my XI): ABC_700

2. Setup an RFC R/3 Destination on my client 700 to client 107: ABC_107

3. Setup the IDOC processing port "SAPABC" on client 107 with RFC Destination ABC_700.

4. Define partner type LS for logical system ABCCLNT105 (Airline Lufthansa)

5. Define partner type LS for logical system ABCCLNT700 (XI)

6. Specified the ALE distribution model in client 107.

7. Execute IDX1, I input the SAPABC port created in step 3, input the client number 107 and the RFC destination ABC_107 created in step 2 and save. The result is port SAPABC_107.

AND..!! where the error occurs:

8. Execute IDX2 input port SAPABC_107 and idoc type and get the error message "No RFC Destination is maintain for SAPABC_107"

Any ideas !?

Thanks

D

The client 107 represents the Airline American Airlines and has a R/3 RFC Destination to client 700, my XI. The same way my XI has an R/3 RFC Destination to client 107.

[Former Member]

Hi,

What is showing in transaction WE21 on the XI server ?

Is there anything under 'Transactional RFC' ?

Cheers

Colin

[Former Member]

Nothing...

[Former Member]

Hi,

That's your problem.

You should have an entry for your port under transactional RFC. This links to your backend R/3 logical destination.

Let me know if this fixes the problem.

Kind regards

Colin.

Message was edited by: Colin Bickell

[former_member191029]

Hi diego

I think your problem lies in item 8 in your sequence.

You must specify the port without _107 in idx2.

If clients are available it will use the first to make the connection and maintain metadata for all clients.

I was able reproduce your error in SP9 version of XI3.0

hope this help you.

Kurt

[Former Member]

Are you sure? I doubt the guide would skip a whole step...and the error says I am missing an RFC Destination not a Processing Port...

I'll give it a try...

[Former Member]

Kurt, thanks. Question: is step 8 referencing the port created with transaction we21 for client 107? because if it is then name of it is "SAPABC_107" when I try it without the _107 I get the following error: "Incorrect password.."

Now I checked the user in my ABC_107 RFC Destination and is correct, I can login with the user manually to client 107 just fine...

[Former Member]

Colin,

I created an additional port under transactional RFC and named it SAPABC_107. Selected RFC Destination ABC_107 and still get the same error message...no luck here 😛

Thanks anyway

D

[Former Member]

<b>Diego wrote:</b> <i>Executed IDX1 and got port SAPABC_107 with RFC Dest-ABC_107, which I defined previously with transaction sm59 and the test came back ok.

When I try to execute IDX2 I get the error message...</i>

Diego,

I have got this error before, the solution is very simple. On trx IDX2 type as port: <b>SAPABC</b>

Which is the port you defined in trx IDX1 but without the appended "_107" client.

Let me know if it works for you, thanks!

Rob.

[former_member191029]

Hi Diego,

Can you logon to ABC_107 from SM59? If you entered wrong password here this could be the explanation.

If this still doesn't work have a look at the gateways tracefiles on ABC system (dev_rd, dev_rfc1, etc). This will tell you which user you are trying to connect with.

best regards

Kurt

[Former Member]

Kurt,

I can logon to ABC_107 through the remote logon option. I checked the trace files and this is what I found:

======> Name or password is incorrect. Please re-enter

ABAP Programm: SAPLIDX1 (Transaction: IDX2)

Called function module: IDX_META_SYNTAX_READ

User: XISUPER (Client: 700)

Destination: ABC_107 (handle: 3, 05448421, {AD107EA6-5B16-4D61-AAD7-6DB5370B1458})

My question is WHY! is it using XISUPER when I specified a different logon and client in the logon tab...??

THANKS!!!!!

D

[Former Member]

Kurt, THANKS for all the help. I was finally able to load the idoc, I went it and check the user I generated with the appropiate privileges for ABC_107 and the role and profile were in red, I ran the comparison check, reset the password one more time and it worked.

I then was able to load the idoc with trans idx2, it gave me a segment version warning but at least I was able to finish the configuration for the Check Availability Seat Scenario. I am now running into other issues... (neverending story!) but I will post it in a different topic.. thanks again

Diego