Simple IDOC Structure

Hello XI folks,
I am learning and testing IDOC-TO-FILE scenario. I would appreciate if you can tell me some simple IDOC names that have very simple structures like 1 Control Record and just 1 Data Record. Then I will import them from R/3. The reason I am asking this is I could import some IDOCs from the R/3 system. When I opened these structures, I noticed they are very complex structures. I thought and felt that the mapping would be so complex becasue each of those IDOCs have so many data records. I know it would difficult for me to map those IDOCs from the file.
So please help me leanring XI by giving simplSe IDOCs so that I can start mapping easily.
Thanks in advance.

Hi vanaja,
Also go through these how to guies on service market place,
https://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202&_OBJECT=011000358700001410142005E
https://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202&_OBJECT=011000358700003604082004E
Regards,
Bhavesh

Similar Messages

How to create a simple idoc in practice? can you provide an example?

how to create a simple idoc in practice? can you provide an example with full source code?

Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ 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 ³ 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
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Take a look at this guide.
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Create The Extension Segment
Transaction: WE31
The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:
- The name of each segment type must start with Z1
- For each field in the segment you need to define a field name and a
data element.
- The data element for the segment structure must be of data type CHAR.
How to create new segments:
Run the segment maintenance transaction WE31.
Type your new segment name, and click on Create.
Define the fields of your segment:
Field name
Data Element for the field (from the ABAP dictionary).
Do not change the Export length!
Save the segment
Run Segment -->Check to check the segment for consistency.
Release the segment for transport. Select Edit -->Set Release. Note that the Release column now has a check mark.
Create the Extension IDoc Type
Transaction: WE30
After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:
Create new type: Does not refer to other extension types
Create copy: Copies info from an extension type that already exists
Create successor: Extends an extension type from a previous release
of R/3. You can only have one version of an extension type for
each release.
Enter the Basic IDoc type that this extension type will extend.
The screen now shows the structure of the IDoc type you used as
a reference.
Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.
NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).
The segment attribute screen appears. Enter the information and save.
Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, for each instance of the parent segment, how many instances of the child segment may we have?
You can press the Segment Editor pushbutton to view or change the segment definition.
Create the new Message Type
You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.
First the message type itself needs to be created.
Transaction: WE81
Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).
After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.
Transaction: WE82
Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.
One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.
regards,
srinivas
*reward for useful answers*

IDOC structure in F4 Help

Hey Guys
I m developing a search functionality where i need to search the message payload based upon a certain value in IDOC(it could be IDOC number,IDOC type,creation date etc etc).
My functionality needs complete Xpath for this search(for e.g. IDOC/EDI_DC40/DOCNUM) to be typed in manually.
Is it possible to provide IDOC structure in F4 help so that we can select the IDOC segment instead of typing it down?
Thanx
Saif

Hi Saif,
go to t-code we31--> press f1 and see the technical setting see the F4 help attached to it ..
use the same f4 help for the screen field you developed for custom Program..
For Segment F4 help...
Table Name        EDISEGMENT
Field Name        SEGTYP
for Idoc Number F4 help..
Table Name        EDIDC
Field Name        DOCNUM
for Creation Date F4 help..
Table Name        EDIDC
Field Name        UPDDAT
Regards,
Prabhudas
Edited by: Prabhu Das on May 12, 2009 12:04 AM

Trouble shooting File to Idoc scenario: wrong Idoc structure in target

Hi All,
             I am working in an file to idoc scenario. Now the scenario is running but the idoc I am sending from SAP XI is not matching with one received in SAP R/3 system. This is not a new scenario. The scenario was already existing. I have done structural changes in Idoc structure and re-imported it in SAP XI. When the iodoc reaches SAP R/3 system I check its structure and data content. 4 of its fields are missing all 4 were newly added fields. Data from some fields are getting merged into one field within Idoc. data from one field is moving onto other fields in target. I have refreshed the metadata using IDX2 transcation within SAP XI but still getting same result.

Hi All,
I am able to see the changed idoc structure in IR. I have also tried cache refresh. I am trying to explain my problem once again with example.
Source Idoc in XI
      fieldname                            data
       f1                                       d1
       f2                                       d2
       f3                                       d33
       f4                                       d4
       f5                                       d5
Idoc structure received in SAP R/3 system. I am seeing through we02 transcation, inbound idoc
      fieldname                            data
       f1                                       d1
       f2                                       d2
       f4                                       d33d4
I have tried cache refresh, IDx2 metadata refresh, but no improvement of the situation.

Idoc Structure From Flat FIle

Hi,
I have two queries.
1.I need to import idoc structure from excel file not from sap, is it possible ?
2 what are the detalied steps to implement following SAP note for getting processed file name at runtime.
Thanks & Regards
Tuhin
Symptom
You want to access the name of a file sent through a File Adapter Sender channel from a custom developed XI module.
Other terms
XI 3.0, XI30, File Adapter, Module Processor, Module Development, Modules
Reason and Prerequisites
The functionality described in this note requires SP 9 or higher of the component XI ADAPTER FRAMEWORK CORE 3.0.
Solution
The File Adapter passes the name of the processed file to the module processor. This information is available in a Hashtable object accessible as as supplemental module data under the name "module.parameters" within the module's 'process' method.
For further information, please take a look at the example code below:
public ModuleData process(ModuleContext mc, ModuleData md) throws
ModuleException
Hashtable mp = (Hashtable)
 md.getSupplementalData("module.parameters");
String fileName = null;
if (mp != null)
 fileName = (String) mp.get("FileName");

Hi Tuhin,

1. .I need to import idoc structure from excel file not from sap, is it possible ?
Yes and No; If the structure in the Excel sheet is defined in XSD format (XML schema) then it should be possible to import it assuming you are using XI 3.0. In 2.0 this is not possible.
Not sure if in XI 3.0 you are allowed to import Excel files straight forward into XI.
2 what are the detalied steps to implement following SAP note for getting processed file name at runtime.
I'm not quite sure but this looks to me like you have to implement this within a Java custom function/mapping...
The data (in this case the filename) is encapsulated in a Hashtable object available during runtime.
Cheers,
Rob.

Get Idoc structure and contents from Shipment Number

Hi all,
We have a 3rd Party Logistics company who wants to send us back minimal shipment data to enable us to update our shipment details. They want to send us the shipment number, and vehicle information. My tests (and SAP's documentation) have indicated that in order to modify a shipment via the message type SHPADV, you need to have the complete Shipment Idoc structure filled in in order for the idoc to process successfully.
My client has indicated that they want to use IDoc processing to manage the shipment updates.
Does anyone know of a FM that can be used to fill the shipment Idoc structures if only a shipment number is filled in? Or do the structures have to be modified manually? For example, these is a function called 'IDOC_READ_COMPLETELY' which populates all the segment details if an Idoc number is entered. I want something similar, but for a document number, in this instance, a shipment number.
Cheers,
Steve

Roger,
Thanks for this suggestion. I chose to go down another path which I put up here for those who have this problem in the future.
I have passed the shipment number and just the fields that require modification into user exit EXIT_SAPLV55K_020, and recorded the passed in values into variables.
I then executed the idoc_output_shpmnt idoc, which, when the shipment number is passed in to the nast-objky field, reads the required shipment data and populates the idoc_data table with the segment details as per sending the document out. But the FM doesn't actually call the ALE layer, so I then loop through the idoc_data table, modifying the fields that need to change with the values I've saved in the variables, and passed the modified idoc_data tables back into the idoc_input_shpmnt FM. Worked a treat.
Cheers,
Steve

File-to-IDoc, but the file structure is equal to the IDoc structure

hi,
we have a scenario where the incoming message has to be picked up by FTP. The incoming message is a flat file, no delimiters, no separators, nothing, however is exactly the IDoc structure.
Since the file adapter does not know how the structure is set up, because no tags are present, it can not translate the filestructure into any format. Therefore it can not be processed further.
Is there a way for a fileadapter to convert this plain file to an IDoc format, or to call the file-to-IDocadapter up front, the same way as if you would use in SAP the fileport in IDoc processing ??
thanks!

Hi Alexander,
XI understands ONLY XML. All messages to and from XI are always XML messages.
Now, if the file being placed by your Legacy System is not going to be an XML file, then you can use the content conversion of your sender File adapter to convert this non XML file to an XML file.
Same way, if the file that is required by your 3rd party application should not be in a XML format, you can use content conversion of the receiver adapter to convert XML to text and so on.
Basic point, all messages that reach the inegration engine of XI need to be in XML format and so you need content conversion to conevrt non xml to xml and vice versa.
To make note mapping cannot be performed with a flat file as XI understands only XML. Hence content conversion required.
Please go thru these links for step by step procedure to do the same:
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
http://help.sap.com/saphelp_erp2005/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
I hope I have answered your query.
Regards,
Abhy

IDOC structure for HRMD_A07

Dear All,
We want to create IDOC HRMD_A07 through SAP PI in ECC to create employee.
Please guide how we can get the output structure like
e1plogi
e1pityp
e1p0000
e1pityp
e1p0001
e1pityp
e1p0002
Whereas the standard IDOC structure is like as follows:
e1plogi
e1pityp
e1p0000
e1p0001
e1p0002
Reg,
NJ

Well, u can still create IDoc with the required structure. Thre is a test tool (tcode WE19) where u can create and populte the segments as u want for testing. Use the 'Create' button and place it in proper hierarchy.

Flat File to simple XML structure in Mail Sender Adapter

Hi,
I have a scenario, where I want to put the content of a flat file (text, no csv or similar), which is an attachement of an e-mail, into a simple XML structure: entire file content as content of one XML tag. E.g.:
file content:
"abcdefgh"
xml file:
<root>
<content>abcdefgh</content>
</root>
Do I need to use MessageTransformBean? Or is there an easiert way?
Thanks,
Torsten

Hi Dirk,
When we use MessageTransform, we can use ContentDisposition to specify, as to whether the payload has to go as an attachment or inline(as the mail itself.)
It could also be a text file. Right?
Just take a look at this..
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm
cheers,
Prashanth

Error when importing IDOC structure from SAP - Control record missing

Hi!
We are hitting problems when importing IDOCs from SAP into the Integration Builder. The import ends successfully but when we drill into the IDOC structure we get a message: Schema for type EDI_DC40.ASN_OUT.DELVRY01.Z1DELVRY (category Data Type) not found. This is only happening for one specific IDOC type only. We have checked all we can think of but cannot get this to work. Any help would be very much appreciated. Of course, points awarded for any good ideas. Thx, Duncan

Hi Duncan,
Taka a look at these threads which address similar issues:
Error during import of FIPARQ01 Idoc
Error during IDoc Import
Importing idocs:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/78/21753251ce11d189570000e829fbbd/content.htm
Hope these help!.
Cheers,
Chandra
Message was edited by: chandravadhana gopalakrishnan

Idoc structure not displying in XPATH at Receiver Determination..!!! Urgent

Hi All,
Doing Idoc to File Scenerio,
In the receiver determination, I need to select the XPATH from the Idoc structure and by based on the GLN number which is coming in one of the segment, I need to pass to different receivers.
Problem here is Iam not able to see the Idoc structure in the XPATH to provide the condition.
But when doing File to Idoc scenarios, Iam able to see the File structure.
Any idea why IDoc structure is not displaying over here??
Its a bit urgent for me..
Waiting for your replys.
Thanks&Regards
Seema.

Hi,
This will help you now
Hi,
If you get the following msg while selecting the BS in Receiver Determination and if you are unable to view the Structure of the Source
"Message interface does not exist in any software components installed on this business system"
1) Open ID-----Double click on Business system that which u are using in the scenario
2) Check whether you are able to see the SWC in the Othere attributes TAB
3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
4) Click on Installed Products TAB
5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
7) Click on Installed products and Check the check box of your Product and then finally save that.
Now you should be able to see the SWC in the Othere attributes TAB in ID
Regards
Seshagiri

File to IDOC Scenario: where to import the idoc structure?

Dear all,
I have a short organizational question for you all. I have created a scenario where the MDM server places a file in a FTP directory and XI will take it from there for processing to IDOC towards the SAP system.
During design time I need to import the IDOC structure as the inbound interface for the SAP system.
My question in this situation is: do I import the IDOC into the namespace of the MDM (in which I keep the outbound interface and the mappings) server or do I place it in the namespace of the SAP system?
I ask this because in the latter case the IDOC structure will be the only object in the SAP namespace. If I do not do this, I don't have to create this.
What is the right thing to do from an organizational point of view?
Thanks in advance for your input.

Hi Yomesh and Sudheer,
thanks for your answers. To conclude this topic I will demonstrate how I have understood this all by giving you a short overview of how I will proceed now. Could you please comment???
Sender system is a SAP MDM system. For which I will create a SWC called <Company name>_MDM_DEV version 1.0.
For the receiving SAP Enterprise system I will create an additional SWC called <Company name>_SAP_DEV version 1.0.
And thus I do not put any objects under SWCs from the original installed product components.
Then I create a SWC for common objects as IDOCs (to what product does that need to be assigned???)
Then I will put the interface and message types in the corresponding SWCs and put the mappings in the source SWC as our landscape is not that huge.
How's that???
So under which product to create the SWC for common objects is my final question...
I will provide points to you both.
Cheers,
Auke
Message was edited by:
A. Schotanus

How to see the IDOC structure in XML format

Hi, I am ver new to MII. I configured connection between SAPand SAP MII and IDOC is triggering in SAP MII. I can see the idoc triggered in Message monitor.
Now my query is how to see the IDOC structure in XML format? I written a transaction where I am assigning transaction.xml to my Local.xml and trying to display with message action block. When I display the message I am getting message as below
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
There is no data in the xml, but in SAP side i seen data and segment which sent to MII as a IDOC. Please help me how to resolve this issue.

Hi, Thanks for quick response.
In Message monitor I seen the IDOC list after executing POIT transaction code in SAP.
But the display button is disabled always in message monitor screen. I want to take this IDOC and save it in my SQL database. So I want to see this IDOC structure in XML format. Where i can see this structure?

The XI does not send messages with correct IDOC structure

SAP XI 3.0 sends to ECC IDOC HRMD_A07
The XI does not send messages with correct IDOC structure.
In XI Design, Software Component RHEVOLU, Ive imported the Objects
HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved
HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At
Message Mapping -> mmAdmissao, in Imported Message -> Import XML or
XSD, I imported the reduced Idoc file generated above, mapping source
fields to target fields.
The IDOC sent from XI to ECC has this structure (template: 22122)
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1P0001
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
But does not update HR Master data.
The structure expected in ECC side (template: 20376) is:
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PITYP
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
By using WE19 transaction, this structure was changed manually; so, the
HR Master data was updated.
Witch kind of customizing or correction could be made in XI, to send
the correct structure to ECC?
Best Regards
Claudio

Hi Claudio,
In your case, there are perhaps two causes:
1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode IDX2 (Idoc metadata cache).
2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?
Regards
Mickael

IDoc structure mismatch between SAP R/3 and PI

Hi,
There is an interface in PI which receives IDoc from SAP R/3 system. I have been facing an issue of IDoc structure mismatch (in terms of data present in it) between SAP R/3 and when PI receives the IDoc.
To be more precise,
In SAP R/3 system, the value ABC is present in the field DOCNUM in the IDoc.
But when the PI receives the same IDoc from SAP R/3 (as seen in Integration Engine), the value ABC is present in a different field and the DOCNUM field is empty.
<DOCNUM></DOCNUM>
<ARCKEY>ABC</ARCKEY>
The first step towards resolution was to delete and reimport the IDoc metadata from SAP R/3 in PI system using IDX2, which did not help in this case.
Could anyone please help in resolving the field mismatch between the IDoc triggered from SAP R/3 and the IDoc received by PI.
Regards,
Prajeet

Hi Prajeet,
it's long ago but your question has not been finally solved, so let me try to give you an answer. We are facing the same problem after patching our PI.
I think the reason for the different behaviour is related to SAP note 1233908, where SAP has changed the IDoc adapter.
https://service.sap.com/sap/support/notes/1233908
Regards,
Lars

Simple IDOC Structure

Similar Messages

Maybe you are looking for