IDoc Interface Creation

Hi,
Can somebody tell me the procedure in detail, how to create an IDOC interface for Order/Quote Confirmation including the transaction codes? I'll be very greatful.
Thanks,
John.

The first step in creating a new IDOC is to create all the segments that go into that IDOC. There are some rules that have to be followed while creating the segments:
The name of that segment type must start with Z1
For each field in the segment you have to define a field name, a data element for the segment structure and a data element for the segment documentation.
The data element for the segment structure has to be of data type CHAR
The IDOC tools create overall three structures:
Z1nnnnn - field names
Z2nnnnn - data elements for structure definition
Z3nnnnn - data elements for documentation
IDoc type
IDoc structure type
Receiver port/partner type/partner number
Sender port/sender type/sender number

Similar Messages

Vendor Credit Memo creation in SAP via IDOC Interface (Inbound)

Hello Team,
I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
Regards,
Vijay

Hello Team,
I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
Regards,
Vijay

ALE, IDoC Interfaces

Hi Experts,
            I am working on ALE IDoCS Interfaces... Can anyone send me the step by step procedure for creating a sample ALE,IDOC scenario where i can send a message from client1(800) to client(810).
I need the following
1.complete ALE configuration setting between two clients.
2.Creation of Idoc , segment, filling the idoc from scratch.
3.Dispatching the Idoc on the ALE Interface
4.Handling any exceptions
Is it possible to create an ALE Interface to the same client(800 to 800) for sample testing
Thanks and Regards
AK

Hai Ashok
Go through the following Steps
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
   select all what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
Thanks & regards
Sreenivasulu P

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

Reg idoc interface

hi all,
its regarding idoc interface,try to help me.
i have a programRHALEINI and defined in Work Item WA00012 - "IDOC Extract for HR Master Data"
This IDoc will be created in SAP but not delivered to any external system.
The interface created in this work item will then read these IDOCs and the required fields will be identified and reformatted so that it can be processed by the FMS system.
Program RHALEINI is executed to create the IDocs for all employees. Refer to Work Item WA00012 - "IDOC Extract for HR Master Data
WI WA00012 will also provide Function Module Z_TP_INI_IDOCS to pull all the IDOCs needed to extract all of the employee data (latest employee extract).
The purpose of this interface program is to read all IDOCs created by program in WA00012 and map the required data into a flat file structure.
here to map i have header trailor and body data how to do this.
provide me solution asap with an example
thanking u

Hi,
Once you get the idocs then you have to read the info from these idocs and then you have to populate it into your file.
It depends on the data format that they want to create it.
cretae a file of type l_v_filename TYPE draw-filep,
then start creating header structure item structure and footer structure.
keep passing data to these structures and transfer it to file
TRANSFER l_wa_header TO l_v_filename_temp
same thing you cna do for ur item data,
loop on this and pass line by line to the file.
same way populate the footer data also.
It entirely depends ont he way they want to populate in the final file.
Reward points if you find useful.
Regards,
Sasi

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

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

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.

Regarding AS2 seeburger to idoc interface

Hi Team,
I hope you are doing well.
I am working on as2 seeburger to idoc interface.
what are the steps required for this in IR and ID ?
where can we monitor if we get the error in as2 adapter side?
Regards
ANJAN

Hi,
>>>what are the steps required for this in IR and ID ?
In ESR:
1.First you need to get the xsd of EDI document and import it into ESR under External definitions and import the IDoc also into ESR.
2. Create a service interface for the EDI document structure.
3.create message mapping between the ED(xsd of EDI doc) and Idoc.
4.Create operation mapping.
In ID:
1.Configure the parties using the AS2 IDs.
2.Create an AS2 sender communication channel(refer the configuration guide that you receive from seeburger).
3.Create an IDOC receiver communication channel.
All the remaining steps are same what we do for normal scenarios like receiver determination,interface determination and agreements.
>>>where can we monitor if we get the error in as2 adapter side?
In Seeburger workbench
Regards,
Priyanka

Query on idoc interface

Hi Experts,
i have doubt on idoc interface.we have 10 records in a idoc outbound side.
how can we send particular 3 records from those 10 records to pi
Thanks in advance
suresh

hi,
might be below blog and content those are helpful for your requirement:
Need list of Idocs for a particular Order Number
Search for a particular IDOC :
- Choose the transaction WE09 (SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Services -> IDoc Search by Contents -> WE09).
- Choose the Data Source button to specify whether you want to search for IDocs from the database or the archive (or both).
- If you have set the Archive flag, you can select files in the archive information system or manually.
http://www.sap-img.com/basis/how-to-search-by-value-a-particular-idoc.htm
thanks

ALE/IDoc interface for Special Ledger Data

Anybody has experience with extracting Special Ledger data from ECC through ALE/IDoc interface?
Because Special Ledger is cutom to any client, I'm thinking we need to create a custom IDoc type. I didn't notice any standard IDoc type. Any documentation or any tips on this will be appreciated.
Thanks,
Srinivas

problem has been solved
thanks

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 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

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;

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

IDoc Interface Creation

Similar Messages

Maybe you are looking for