Unable to interpret IDoc interface Error

Hi All,
We are getting the following error while trying to translate a X12 to IDOC , we are using Seeburger Adapters for the translation.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to interpret IDoc interface I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Reason we are using a Interface rather than using a IDOC directly is because our the IDOC Structure is 867.ORDERS01.ZORDRS1x and this is a custom IDOC in ECC and when we try to directly use the structure in the Interface Determination we get the error
Check Result for Object ARROWUS | ARROWUS_IN_AS2 | A_867_V4010_ABS | | BS_ECC_D03_DEV
First character invalid: 8 Only a(A)-z(Z), 0-9, and "/" and "_" are permitted
Has anyone faced a similar problem ? If so please let me know how you fixed it.
Appreciate your help
Regards,
Madhu

have you seend below threads:
[link1|Unable to interpret IDoc interface ZSHIPDEL_packageRD;
[link2|IDOC Error;

Similar Messages

File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

Hi All,
Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
Anyidea what might have gone wrong??
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
+<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
<SAP:Retry>M</SAP:Retry>
Waiting for your answers.
Thank You.
Seema.

Hi Seema,
I think you are using mi_Orders05_In_Asyn as the IDOC interface.
Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
Let us know if that doesnt solve your problem.
Regards,
Sumit

Unable to interpret IDoc interface ReplenishmentOrderNotification_In

Hi All,
I am trsfering orders03 idoc from r/3 4.5 B system to XI and from XI to SNC system using idoc adapter.
In sxmb_moni, When I double click on particular XML message with errors
I am getting error in call adapter
details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ReplenishmentOrderNotification_In</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface ReplenishmentOrderNotification_In</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi
I am creating JDBC to IDOC scenario but experiencing the same issue.
Can you advise how you solved this?
Thanks.

Unable to interpret IDoc interface ZSHIPDEL_packageRD

Hi,
I am doing a file-xi-idoc scenerio.
I've exported my custom idoc as an xsd and modified the schema to allow for multiple idocs to be generated for each file - as per note 814393.
However I get the following error message at runtime (Call Adapter):
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ZSHIPDEL_packageRD</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface ZSHIPDEL_packageRD</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Has anyone else experienced this error?
Regards
leenor

I have a scenario exactly like the above one.
My file structure is like
TransactionDetailList
 TransactionDetail (1:N)
 Transaction_Type (0:1)
 Transaction_Date (0:1)
 Add_Revise_Cancel_USER_ID (0:1)
 Add_Revise_Cancel_Date_Time (0:1)
My IDOC has the below structure,
ZIDOC_BDS_DIVERSION
 IDOC
 ZSEGL_DIVERSION_HEADER
 SEGMENT
 NOMNR
 NOMIT
 EVENT_DATE
 ZSEGL_ DIVERSION_ITEM
 SEGMENT
 WHO_PAYS_DIVERSI
 LOCID
 DEST_CITY
so i have to generate multiple idocs in the target side.
I have created external defination based on my IDOC.Defined mapping between File and the external defination crerated from the IDOC. also defiined interface mapping between file and external defination.
In the Integration Directory ->Interface Defination, I have used the actual Idoc as Inbound interface for which there is no mapping as we have not defined anything for this. This is exactly what you have defined above.
I am getting the following errors like,
"Error: MSGGUID A5EE4A305B4111DABFBE0002551F08EE: Tag TransactionDetailList found instead of tag IDOC BEGIN="
Please let me know if I am missing some steps while configuring or I have to do something else.
Thanks & Regards,
Mukesh

Unable to interpret IDoc interface

Hi,
I have a File to multiple IDOC scenario. I have change the IDOC occurance by creating ED.
I have developed everything but the following error is coming during my end to end testing.
Unable to interpret IDoc interface
Thanks,
Raj

Raj Says..
I have change the IDOC occurance by creating ED.
Hi Raj,
Since you have changed the IDOC occurrences by creating an ED so you have to make sure that IDOC and ED has been used properly in your scenario.
1. MM = use ED
2. IM = use original IDOC
3. ID = use original IDOC
Regards,
Madan Agrawal

File-IDOC, idoc interface error

Hi,
Scenario: File-IDOC (Multiple records in source file to be mapped to multiple CREMAS IDOCs) without BPM.
Modified the occurance(maxOccurs = 'unbounded') in XSD structure of IDOC(CREMAS) and saved it as external definition.
I have used this external definition in message mapping and interface mapping.
In configuration, i have used the same message interface (corresponding to external definition) as inbound interface.
Now, I get the following error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_Cremas04_multi_external</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_Cremas04_multi_external</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.

Hi,
>>I have used this external definition in message mapping and interface mapping.
In interface mapping you need to use Imported IDOC not External definition
This solves your problem.
let me know if you have any issues still.
Cheers,
Jag

IDOC Interface Error

Hi Experts,
I am getting the same error: and from the forums I came to know that we need to use the IDOC name in the Interface mapping.
I used the modified IDOC structure(External Definition) in mapping, but when I select the original interface in Interface mapping I am not able to get the message mapping name.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_IDOC_IA</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_IDOC_IA</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please provide me some hint.
regards,
sri.

Hi Sri,
I used the modified IDOC structure(External Definition) in mapping,
but when I select the original interface in Interface mapping I am not able
to get the message mapping name
Are you following the steps as mentioned in the blog /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change or SAP note 814393
Are you creating any separate Message interface after creating the External Definition?Pls don't create any separate interface.
just export the XSD of the IDOC and change the occurrence (dont save ED with any other name ,keep the same IDOC name)
now in message mapping import the XSD you save earlier. and do the mapping.
In Interface mapping and in the ID configuration use the imported IDOC name only
Regards,
Srinivas
Edited by: Srinivas on May 15, 2010 10:15 PM

Idoc interface not found..

I'm attempting to pull in an XML file to Idoc and I'm getting an error stating "Unable to interpret IDoc interface ZINCOMINGINVOICE_CREATEFROMD01" in the monitor.
I have imported the Idoc into XI and mapped to it and the translation is working fine. I have also gone into IDX1 and IDX2 on the target R/3 system and on the XI system and setup the port and Idoc in the inbound list. I have also managed the port and setup the inbound document in WE20 and WE21 on the target R/3 system.
I have a couple questions.
1. Have I done all the setup?
2. With the Idoc of ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 and the setup above for WE20 inbound set to ZINCOMINGINVOICE_CREATEFROMDAT is that sufficient?
3. Likewise with the ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 idoc and IDX2 set to ZINCOMINGINVOICE_CREATEFROMD01 is that sufficient?
My inbound xml document is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <ZINCOMINGINVOICE_CREATEFROMD01>
- <IDOC BEGIN="1">
- <Z1BP_INCINV_CREATE_HEADER SEGMENT="1">
<INVOICE_IND>X</INVOICE_IND>
<DOC_TYPE>ZA</DOC_TYPE>
<DOC_DATE>2001-04-20T23:59:20-07:00</DOC_DATE>
<PSTNG_DATE>2005/05/02</PSTNG_DATE>
<REF_DOC_NO>123456</REF_DOC_NO>
<CURRENCY>USD</CURRENCY>
<GROSS_AMOUNT>4900</GROSS_AMOUNT>
<HEADER_TXT>[email protected]</HEADER_TXT>
</Z1BP_INCINV_CREATE_HEADER>
- <Z1BP_INCINV_CREATE_ITEM SEGMENT="1">
<INVOICE_DOC_ITEM>1</INVOICE_DOC_ITEM>
<PO_NUMBER />
<PO_ITEM>2</PO_ITEM>
<ITEM_AMOUNT>130</ITEM_AMOUNT>
<QUANTITY>30</QUANTITY>
<PO_UNIT>EA</PO_UNIT>
</Z1BP_INCINV_CREATE_ITEM>
</IDOC>
</ZINCOMINGINVOICE_CREATEFROMD01>

Hello,
I encountered the same problem. If you are sure to have configure correctly your IDX2 transaction, be sure you have import the idoc in the repository under the good composant.
For example if IDOC is for R/3 4.6, import your idoc under SAP APPL 4.6C or SAP BASIS 4.6C to use it in the directory with a component that you defined before in your SLD as a SAP R/3 product.
Regards,
Chris

Gerneric IDoc Interface

Hi,
We have the following set up:
A JMS sender channel sends IDocs in a non XML format (some kind of flat file IDoc). I created a ABAP mapping that converts this flat IDoc to an XML IDoc. The problem is, that the sender sends diffrent kind of IDocs through the same channel.
1.try: I imported all possible IDoc types and tryed to do a content based routing. The problem is the input message. Due the fact, that this is no XML on input side, I cannot check the input data. Is there a possibility to do content based routing AFTER the mapping?
2.try: I created a dummy IDoc interface. The message type is just one tag (I created the complete IDoc XML in the ABAP mapping). So I send all data from the JMS to an IDoc receiver with the same dummy interface. The content of the receiver message contains all IDoc control data (EDI_DC40). The idea is, to use this interface as an generic IDoc interface but I get the error "ATTRIBUTE_WRONG_INTF" - "Unable to interpret IDoc interface MI_IDoc_any_IB_Async". Is there a way to set the IDoc attributes generic in the ABAP mapping or do I have to use the IDoc interface, that I imported?
Thanks for your help
JP

1. The use of BPM may ease the routing part after mapping wherein u may use transform step folowed by send step
2. While doing idoc communication, even if u change the structure, u ll have to use the interface name as the original imported idoc name only. Otherwise u ll get the same error.
Regards,
Prateek

IDOC Adapter error / ATTRIBUTE_WRONG_INTF

Hi at all,
I have a problem regarding a interface sending IDOCs ( messagetype HRMD_A ) from one R/3 to another R/3 system via XI.
I have created a new Message Interface which has the Message Type of the imported IDOC typ ( HRMD_A06 ).
When the system tries to process the inbound IDOC I get the following message :

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_HR_A_Cas</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_HR_A_Cas</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Where can the problem be located ??
Why can't the IDOC interface be interpreted ?
I hope somebody can give me an advise.
Thanks
Florian

Hi Florian,
my solution:
Create a simple BPM which will handle your situation
BPM:
reveicer step -> check step -> (transformation one or two ) -> send step
in bpm you can use as many message interfaces (abstract idoc ) as you want
Regards,
michal
Message was edited by: Michal Krawczyk

Error:Unable to interpret "TABLE".

When I use BTE, There is an error in FM Z_WRITE_TO_QUEUE in R/3.
FUNCTION Z_WRITE_TO_QUEUE.
""Local interface:
*" IMPORTING
*" REFERENCE(I_DATASOURCE) TYPE ROOSOURCE-OLTPSOURCE
*" TABLES
*" I_T_DATA OPTIONAL
TYPE-POOLS:
 sbiwa.
DATA:
 l_exstruct TYPE roosource-exstruct,
 l_initflag TYPE roosprmsc-initstate,
 l_subrc TYPE sy-subrc,
 lr_is_data TYPE REF TO data,
 lr_es_data TYPE REF TO data,
 lr_et_data TYPE REF TO data,
 l_t_fields TYPE sbiwa_t_fields,
 l_t_select TYPE sbiwa_t_select.
FIELD-SYMBOLS:
 <i_s_data> TYPE ANY,
 <e_s_data> TYPE ANY,
 <e_t_data> TYPE STANDARD TABLE.
Check to see if Delta initialization has been performed.
SELECT SINGLE initstate FROM roosprmsc INTO l_initflag
 WHERE oltpsource = i_datasource
 AND rlogsys NE space
 AND slogsys NE space
 AND initrnr NE space.
If initialization has taken place continue
IF sy-subrc EQ 0 AND l_initflag EQ 'X'.
grab the extraction structure from roosource based on the
datasource parameter input.
 SELECT SINGLE exstruct FROM roosource INTO l_exstruct
 WHERE oltpsource = i_datasource
 AND objvers = 'A'.
 CHECK sy-subrc = 0.
 CREATE DATA lr_is_data LIKE LINE OF i_t_data.
 ASSIGN lr_is_data->* TO <i_s_data>.
 CREATE DATA lr_es_data TYPE (l_exstruct).
 ASSIGN lr_es_data->* TO <e_s_data>.
 CREATE DATA lret_data TYPE STANDARD TABLE OF (l_exstruct)._
 ASSIGN lr_et_data->* TO <e_t_data>.
 LOOP AT i_t_data ASSIGNING <i_s_data>.
 CLEAR <e_s_data>.
 MOVE <i_s_data> TO <e_s_data>.
 MOVE-CORRESPONDING <i_s_data> TO <e_s_data>.
 INSERT <e_s_data> INTO TABLE <e_t_data>.
 ENDLOOP.
 CALL FUNCTION 'EXIT_SAPLRSAP_001'
 EXPORTING
 i_datasource = i_datasource
 i_isource = ''
 i_updmode = ''
 TABLES
 i_t_select = l_t_select
 i_t_fields = l_t_fields
 c_t_data = <e_t_data>
 EXCEPTIONS
 rsap_customer_exit_error = 1
 OTHERS = 2.
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
 CALL FUNCTION 'RSC1_TRFC_QUEUE_WRITE'
 EXPORTING
 i_isource = i_datasource
 i_no_flush = 'X'
 IMPORTING
 e_subrc = l_subrc
 TABLES
 i_t_data = <e_t_data>
 EXCEPTIONS
 name_too_long = 1
 OTHERS = 2.
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
ENDIF.
ENDFUNCTION.
 FORM abs_type_to_rel_type *
 The purpose of this subroutine is to convert an absolute type *
 name into a relative type name. *
--> TYPE_NAME *
form abs_type_to_rel_type changing type_name.
data junk(100) type c.
split type_name at '\TYPE=' into junk type_name.
endform.
"CREATE DATA lr_et_data TYPE STANDARD TABLE OF (l_exstruct)" makes an Error "Unable to interpret "TABLE"."
I don't why!
So anbody can help me?
Thank you!

Hi,
Use this statement.
data:begin of lr_et_data occurs 0,
include l_exstruct.
end of lr_et_data.
Ravi

Unable to interpret 1,000.000 as a number while posting IDOCs

Hi All,
I know this query has been asked multiple times but as of now I am unable to find the right match so posting this query again. We are posting an IDOC from SAP PI to SAP ECC using SAP PI IDOC Adapter. When the IDOC is sent there is one specific value in one of the fields which have value 1000.00. Now when the IDOC is received by SAP the value is received as 1,000.000. As far as I understand this is because the user configured in the RFC destination in SAP PI (which sends the IDOC to SAP) is having in its default profile the Decimal Notation as 1,234,567.89 and hence we see the value as 1,000.00.
But then the IDOC is not posted in SAP and the issue is: "Immediately processing not possible: Unable to interpret 1,000.000 as a number".
As I am not much aware about ABAP being a PI consultant, would appreciate if experts can guide me on how to resolve this issue. Thanks for taking time to read through the issue.
Thanks,
Pratik

Please check at abap end for the inbound parameters.
In we20 the message type will be assigned .Double click it and you will get the process code.Double click that and you will get the required FM.
If the inbound function module is Z ,Please do the necessary change.
OR
Else try WE19 to process the idoc (Existing).
Execute and then check the Inbound function module option and then call in debugging mode to check the where the error is happening.
Hope it helps.
Thanks!

Error: Unable to interpret / as a number

We have an R/3 Infoset that is used as a source for some Crystal Report queries -- basically it is pulling some revenue recognition data from GLPCA and pairing it with supporting tables such as billing documents, orders, customer, material, etc. This has been available in Production for a few months, but recently a user has started encountering the following messages at runtime:
Crystal Reports
Failed to retrieve data from the database.
Database Connector Error: 'Unable to interpret / as a number.'
Database Connector Error: 'RFC_INVALID_HANDLE'
So we were able to even track down the error to one specific billing document and can recreate the error when selecting only the one document number. The report errors whenever it pulls that data and if a certain amount field is brought in to the listing. Looking at the underlying data through an SQL query, we don't see a problem with the data and have been unable to figure out why only certain records are causing this short dump. The abend info in ST22 shows it is related to a CONVT_NO_NUMBER runtime error in ABAP program /CRYSTAL/SAPLFLAT - procedure /CRYSTAL/BUILD_STRING. Looking through the details did not uncover much information that would point to the problem.
Has anyone encountered this type of problem with Crystal integration to SAP data? Any suggestions on troubleshooting or identifying the problem would be appreciated.

Hi,
would suggest you open a case with support and provide the details on the steps so that the support folks can directly look at your system.
thanks
Ingo

TRFC Queue Error "Unable to interpret BGUA as a number"

Hi all,
I am getting the below error message in TRFC queue
"Unable to interpret BGUA as a number" when i do a datamart dataload from ODS to Cube. ODS is getting data from datasource 0CO_OM_CCA_9. Can anyone help how to resolve this issue?.
Thanks & Regards,
Muruganand. K

What is BGUA ??
I think you have mapped this field (BGUA holding infoobject) to number or key figure field.
Check your mapping in transformation form ODS to CUBE.
Hope this helps.

Unable to interpret "650.00u00A0 " as a number. Runtime Error : CONVT_NO_NUMBER

Hi ,
This is a issue which has to be resolved ASAP as all the checks are being thrown Dump in Production.
It would be great if any of you could help me in this regard.
I have been encountering a runtime error as "CONVT_NO_NUMBER" with
short text as "Unable to interpret "650.00 " as a number."
System versio : SAP ECC 6.0
The problem is occuring at the below code
    FORM XXXXXXXX TABLES t_XXX_in STRUCTURE itcsy
                                   t_XXX_out STRUCTURE itcsy.
      DATA: $_swnet     LIKE regud-swnet.
      DATA: $_rwbtr     LIKE reguh-rwbtr.
      DATA: $_zbukr     TYPE bukrs.
      READ TABLE t_XXXX_in WITH KEY 'REGUH-RWBTR'.
      CONDENSE t_XXXX_in-value NO-GAPS.
make sure the amount field is an amount.
      IF t_XXXX_in-value CA 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
        $_rwbtr = 0.
      ELSE.
>>>>>     $_rwbtr = t_XXXX_in-value.
      ENDIF.
Can you please help me in this regard.
regards,
bhima
Moderator message: number formatting questions = FAQ, please search before posting, do not use the term "ASAP", all threads have the same priority.
Edited by: Thomas Zloch on Nov 17, 2010 6:19 PM

This is a FAQ. Please search before posting.
Just to avoid dump catch the exception cx_sy_conversion_no_number . But you have to do some other changes like replacing the unwanted characters like comma,dot etc and then move it.

Unable to interpret IDoc interface Error

Similar Messages

Maybe you are looking for