Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error: The meta data for the IDoc type "DELVRY03" is unavailable

Former Member
0 Kudos

Hi,

We have an outbound interface between SAP (4.7) and a third party system. Between SAP and the 3rd party system is Business Connector, which is being used as the middleware.

The issue is that when we trigger idocs from SAP, we can see them in status 03, but the mesage does not reach the 3rd party system. In TCode SM58 in SAP we get the error message The meta data for the IDoc type "DELVRY03" is unavailable. We see the same error in business connector also.

Our doubts are:

1) How do we know which RFC is being used? In SM59, there is one RFC under R/3 and one under TCPIP, which could possibly be used. How do we exactly identify which one is being used in the idoc transmission from SAP to Business Connector?

2) In many of the threads pertaining to similar issues, it has been mentioned check the user id and password. How can we know which user is being used in this case?

3) Once we know the user which is being used in this case and we change the password for that user, will it not impact other interfaces, using the same user?

Thanks in advance.

Peter.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

Please look at SAP Note : 770239 .

Look at point 3.

Regards,

Srini.

10 REPLIES 10

Former Member
0 Kudos

Hi,

Please look at SAP Note : 770239 .

Look at point 3.

Regards,

Srini.

0 Kudos

Thanks for the reply Srini.

However the SAP solution implemented is not industry specific as mentioned in the note.

ABAP gurus, please help with answers to the questions mentioned in my post.

Regards,

0 Kudos

Hi Peter

Answer to your 1st and 2nd question is

Go to WE20 i.e. partner profile. Double click on the partner profile definition for your message type.

It will take you to detailed view of partner profile. There you will get port which is attached to message type.

You can go to WE24 and check which RFC is attached to this particular port.

Go to SM59 and see the detailed view, where all technical details like connections, SAP SID/URL and system number# etc.

there you can find out user id.

You can test your RFC in SM59 and check whether there is any issue in connections or userid and password.

Regards

Sachin

0 Kudos

Thanks Sachin. This was really helpful.

We now know the RFC and the type of RFC connection.

Based on what you have mentioned in your reply, we found that its a TCPIP RFC connection (and not a R/3 RFC connection).

Now the question is that in the TCPIP RFC connection (TCode SM59) there is no user id or password maintained.

We also did another test. We created a new idoc (copy of old one which gave the error message in SM58) using TCode WE19. The user id we were suspecting that is being used, did not get locked even after trying 4 times with WE19. So it is most likely not a password issue.

Please help on what could be wrong.

Regards,

0 Kudos

Hi Peter

If RFC is working fine in SM59, then you need to check configurations in 3rd party system.

0 Kudos

Thanks Sachin.

Doesnt the error The meta data for the IDoc type "DELVRY03" is unavailable indicate something wrong in R/3 or in Business Connector?

Please help....

Regards,

0 Kudos

Hi,

ABAP gurus please help on this one.

Regards,

0 Kudos

If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.

The program RSARFCEX restarts unsuccessful tRFC calls.

0 Kudos

Hi

This thread cab be usefull for you.

/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

0 Kudos

Thanks a lot to all who took the time out to help.

We have been able to resolve the problem.

This is what we did:

We changed the password for the RFC user in Business Connector and in R/3, so that the password was now the same in both the systems. Then we got another error, which we resolved by changing the routing settings in Business Connector.

Now we can see the idoc/mesage flowing from R/3 to Business Connector and there are no more errors in SM58 in R/3.

However the problem now is that the message does not recah the 3rd party system from Busines Connector inspite the status being confirmed in business connector.

Could this be because of any firewall related issue? How can we rectify this?

Please help.

Regards,

Peter