DOC_TYPE_UNKNOWN

[Former Member]

Hi all

rfc to db

at the sender side, the error message is appears

got unexpected document type:DOC_TYPE_UNKNOWN.

but data transfered to target system successfully.

does any one know how to fix it?

thanks in advance

[ivan_garcia2 · Accepted solution]

<b>Solved for me! :)</b>

In my case, my Interface mapping had only Mapping program to Request. Mapping program for Response was blank.

<b>Filling the Mapping program for Response in Interface Mapping solved the problem for me.</b>

Thanks!

[ivan_garcia2]

Hello people,

In my scenario, the messages appears in XI (SXMB_MONI) with "Processed successfully" and I see the correct response of the webservice in the XML, but the ABAP program says "got unexpected document type:DOC_TYPE_UNKNOWN". Please, see below the ABAP program e ABAP function.

Anyone have solved this problem? Any idea?

Thanks,

Ivan, from Brazil

<b>ABAP Program:</b>

*&---------------------------------------------------------------------*
*& Report  Z_WEBSERVICE_AUTH_USER                                      *
*&                                                                     *
*&---------------------------------------------------------------------*
*&                                                                     *
*&                                                                     *
*&---------------------------------------------------------------------*


REPORT  Z_WEBSERVICE_AUTH_USER                  .

*data: lv_response(250) type c.

data: lv_response LIKE  TDUMMY-DUMMY1.

DATA: INFO LIKE RFCSI, "Importing parameter
      MSG_TEXT(80) TYPE C. "Message text


CALL FUNCTION 'Z_WEBSERVICE_AUTHENTICATE_USER'
  destination 'BRD_XI'
  EXPORTING
    LOGIN                 = 'xxxx'
    PASSWORD              = 'xxxx'
  IMPORTING
    AUTH_RESPONSE         = lv_response
    RFCSI_EXPORT          = INFO
  EXCEPTIONS
    COMMUNICATION_FAILURE = 1  MESSAGE MSG_TEXT
    SYSTEM_FAILURE        = 2  MESSAGE MSG_TEXT.



write :   'Resposta : ' , lv_response,
        / 'Erros: ', MSG_TEXT.

<b>ABAP function:</b>

FUNCTION Z_WEBSERVICE_AUTHENTICATE_USER.
*"----------------------------------------------------------------------
*"*"Local interface:
*"  IMPORTING
*"     VALUE(LOGIN) LIKE  TDUMMY-DUMMY1
*"     VALUE(PASSWORD) LIKE  TDUMMY-DUMMY1
*"  EXPORTING
*"     VALUE(AUTH_RESPONSE) LIKE  TDUMMY-DUMMY1
*"----------------------------------------------------------------------


ENDFUNCTION.

[stefan_grube]

The RFC call seems to vary from the function itself.

The meta data of the RFC with is stored in the memory of the RFC adapter must do equal to the RFC call. When the number or types of the parameters differ, the RFC call does not work.

Regards

Stefan

[ivan_garcia2]

Hi Stefan, hi people,

I have modified the program (see below): now the parameters are identical. The metadata in the RFC Adapter is updated (I have reimported the RFC). But the problem persists. In SXMB_MONI the message is Ok! See the response XML below.

People, do you know how to solve this?

Thanks!!

REPORT  Z_WEBSERVICE_AUTH_USER                  .

data: lv_response LIKE  TDUMMY-DUMMY1.

CALL FUNCTION 'Z_WEBSERVICE_AUTHENTICATE_USER'
  destination 'BRD_XI'
  EXPORTING
    LOGIN                 = 'xxxx'
    PASSWORD              = 'xxxx'
  IMPORTING
    AUTH_RESPONSE         = lv_response.


write:   'Resposta : ' , lv_response.

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
<!--  Request Message Mapping   --> 
<AuthenticateUserResponse xmlns="http://tempuri.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<AuthenticateUserResult>d26cbfdf-e5f0-438a-b8d6-5891f63a82ae</AuthenticateUserResult> 
  </AuthenticateUserResponse>

[stefan_grube]

The RFC adapter is very restrictive how the XML data has to look like and it is not possible to differ an name or namespace of the tags.

You <b>must</b> upload the RFC structure to the mapping tool and create a mapping for the response which you assign to the interface mapping.

Compare the result of the response mapping with the RFC structure. If you see no difference, you have to clear the cache of the RFC adapter. Just deactivate and activate the communication channel.

Regards

Stefan

[ivan_garcia2]

Thanks again, Stefan,

I have uploaded the RFC structure and used it in the mapping of the response. The result of the response mapping has no diffence with RFC structure. I cant drop here an picture of the Tabular Tree view but I copy below the Source Text View. I have deactivated and activated the communication channel and made stop/start in the RFC Adapter via J2EE Visual Admin. <b>But the problem persists.</b>

Just another information: I made before the <a href="/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1&ei=kDWdRY3oHcHg4QGt2fnxAw&sig2=sAeniIhWBEBgYg-RXm5xig&zx=KaoPv5PKlAU&ct=b">example scenario</a> of Shabarish Vijayakumar and it works fine.

Other tests/verification I can do?

<b>Source Text View</b>

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions">
<xsd:element name="Z_WEBSERVICE_AUTHENTICATE_USER.Response">
<xsd:complexType>
<xsd:all>
<xsd:element name="AUTH_RESPONSE" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="250" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:schema>

[Former Member]

Hi!

I have the same problem.

Can you tell me some option to solve this problem,

you could solve the problem,

can you help me.

Message was edited by: Lizbeth Zarate

[MichalKrawczyk]

Hi Tony,

>>>got unexpected document type:DOC_TYPE_UNKNOWN.

by sender you understand jdbc receiver?

if so then does your message have one of those formats?:

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

if by sneder you understand RFC sender adapter then

maybe you've changed the RFC's signature (import. export or table parameters) since the last time

you downloaded it inside repository?

Regards,

michal

[Former Member]

Hi Michal

i already mention that data at sender side was transfered to target successfully even though sender rfc exception error comes up, that's DOC_TYPE_UNKNOWN.

regards