Idoc to idoc xml specification example

Hi,
I am a ABAP developer and have received a requirement for Writing Interface Specification. The requirement is as follows:
There are 3 outbound master data idocs MATMAS,DEBMAS & BATMAS which need to be sent from SAP (client) to XI to Warehouse. These idocs will be received by the warehouse in xml format. I need to write a specification with mappings for the XI team to do the necessary conversion of idocs to xml format. I have managed to collect all idoc related data and fields required for warehouse.I have been provided with the template for writing the specification for XI team to proceed with conversion to xml.Please advise how should i proceed?
If required, I can send the template to your email id.
If any one can help me with writing the first spec, i would manage the rest.
I simply need some sample spec to follow.
If you have some sample spec, you can even provide it to me.Kindly help.
Thanks & Best Regards,
Tejas Savla

>
Bhakti Haria wrote:
> Hi,
> I am a ABAP developer and have received a requirement for Writing Interface Specification. The requirement is as follows:
> There are 3 outbound master data idocs MATMAS,DEBMAS & BATMAS which need to be sent from SAP (client) to XI to Warehouse. These idocs will be received by the warehouse in xml format. I need to write a specification with mappings for the XI team to do the necessary conversion of idocs to xml format. I have managed to collect all idoc related data and fields required for warehouse.I have been provided with the template for writing the specification for XI team to proceed with conversion to xml.Please advise how should i proceed?
> If required, I can send the template to your email id.
> If any one can help me with writing the first spec, i would manage the rest.
> I simply need some sample spec to follow.
> If you have some sample spec, you can even provide it to me.Kindly help.
>
> Thanks & Best Regards,
> Tejas Savla
Hi Tejas,
IDocs are pulled from the SAP Back-end system onto the PI(XI) system in metadata form. You don't have to do the conversion explicitly, it is taken care! I guess your job will be done once you send the IDoc from SAP R/3 to PI (XI). It will be easy for you if you can pick up the metadata (nothing but IDoc in XML format) and try to map it with the XML that Warehouse is expecting just for the specification doc perspective.
Let me know if you need more help.
Thanks & Regards,
Anand Patil

Similar Messages

Adapter module in PI 7.1 EhP1 for Falt File Idoc to Idoc xml transformation

Hi Experts,
In PI 7.1 (EhP1) there is a java adapter module that can be added to the file adapter that automatically transforms Flat File representation of IDoc to IDoc XML. Can anyone provide the link to this particular module? Tried searching but could not get the specific module name or parameters.
The same conversion can be achieved using a standard SAP provided ABAP mapping but we need to use the module in this case.
Thanks and regards,
Shiladitya

/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
FYI~~~

Merging multiple idocs into 1 XML output

Hi Gurus,
I've got a scenario whereby i will need to send payment documents via idocs to XI and XI will output them into an XML file.
At the moment, when i perform a payment run for multiple vendors and send the idocs out, i realised that multiple idocs are being sent out and XI will output multiple XML docs.
Is there any way i can merged these idocs into a single XML document? The idocs are all from the same system.
Thanks in advance.

HI,
I think this is possible using PACKAGING.
Check this note 814393 on Service Market Place.
You want to create or process an XI message with multiple instances of an IDoc (of the same IDoc or extension type) in the mapping.
Please refer below link to follow the steps to Merge IDOCs under single XML,
SAP Network Blog: Collecting IDocs without using BPM
Collecting IDocs without using BPM
IDoc packaging
Reason and Prerequisites
The relevant IDoc is imported into the Integration Repository.
Solution
1) Log on to the Integration Repository.
2) Open the relevant IDoc in the object editor.
3) Select the "Export XSD" menu option in the "Tools" menu.
4) In the subsequent dialog box, assign a file name and save the data to the hard disk of your local PC.
5) Open the file that you have saved in step 4 in an adequate editor (for example, Notepad) for editing.
6) Locate the first entry: <xsd:element name="IDOC" type="<
Idocname>"> and add the following expression, maxOccurs="unbounded", between the value of the type attribute and the closing angular bracket.
Example:
<xsd:element name="IDOC" type="ADR2MAS.ADR2MAS02"
maxOccurs="unbounded">
7) Save the modified file to the hard disk of your local PC.
8) In the message mapping, use the file saved in step 7 instead of the imported IDoc by using the "Import XML or XSD" function in the mapping tool to select the source or target messages.
Thnaks
swarup

One IDOC to multiple XML messages

Hi! I am using the graphical mapper in XI to map the SHPMNT03 IDOC to an XML message. The IDOC has a shipment node and potentially multiple delivery nodes, for example:
E1EDT20
- E1EDL20
- E1EDL20
- E1EDL20
I need to create one XML message per E1EDL20 node. I figured I could do this in the mapper but when I execute the map for an IDOC with multiple E1EDL20 nodes, I get a 'Cannot cast 2 to boolean' error. The map executes fine when there is a single E1EDL20 in the IDOC.
As always, help is very much appreciated and points awarded.
Thx, Duncan

Hi Duncan,
Can you just check if this is what you have done,
IR
1. Message Mapping -- Occurence of the Destination message type ( file ) is unbounded
2. Interface Mapping -- Occurence of the Destination Interface ( File ) is unbounded
ID
1. No sender communication channel , sender agreement
2. Receiver communcation channel for FIle with appropriate FILE CONSTRUCTION MODE
3. Receiver Determination and Interface Determination with Sender Interface as the IDOC interface and Receiver Interface as the FILE INTERFACE.
I think there is some misunderstanding on this front.
Multimapping will work if you are trying to do an IDOC to FILE with a 1:N split
just check this and let me know if you ve missed something.
Regards,
Bhavesh

How to get IDOC schema in XML

Please tell me how to get an Idoc schema into XML from SAP.
I want all the details of an Idoc, i.e Segments and fields in one file.
Quick response will be appriciated.
Thanks
Kiran

WE60 enter the IDoc type then menu path Documentation->XML Schema. This may depend on what version of SAP you are on.

HR - XI - External System: one IDOC to multiple XML Files

Hi,
I have a scenario where I need, out of one HRMD_A07 IDOC send multiple XML files:
The IDOC and the XML files can the Master data for many employee (IDOC has max of 200 as of SAP, external system, max of 1000).
The IDOC will be generated with change pointers with all the needed filters (I can add/remove if needed).
My goal is to generate 3 types of XML files:
- 1 for the persons (containing basic info like name, firstname, persnr,etc)
- 1 for the various unit (with basic info of unit like number, description & name)
- 1 for the links between persons and units (this person is linked with that unit)
The structures of the 3 XML files are know and can be imported via XSD definition.
Do I need to use BPM for doing so or is there a way to do that with simple mapping?
If BPM is needed, as I new to that, if you have a link to a begginer guide, fell free to send it
Cheers,
greg

hi,
For your scenario there is no need of BPM.
In message mapping select the message tag.
In the target add 3 message types.
Just map the fields.Go to Interface mapping add the 3 message in the target.
Get the mapping.
In ID sender agreement,Receiver Determination is same.
In Interface Determination select extended.Get the mapping.
Create 3 Receiver agreement for each Receiver.
Regards,
Prakasu

Messagesplit of IDOC to several XML messges

Hello Folks,
I have a following issue:
I want to split an INVOICE Idoc to several XML Messages with the following condition:
If INVOICE belongs to country then the xml message should be created..
It works only if the INVOIC.xml belongs only to one country, but if the INVOIC.xml includes several IDOCs to several countries, then the message split does not work. All needed Information are mapped only to the first message instead to split to message 2 or message 3, which is found. How can I solve this?
For instance salesorg in invoice belongs to UK or Ireland, then the target-xml should be created see the mapping for the first message 1 below.
But if there several IDOCs see Picture 3 which includes IDOCs for GB, Portugal and Italy for instance, it does not work. How should the mapping step should be correct? I also change the context of the ORG field to the IDOC Segment, because it refer to E1EDK14.
Thanks in advance for your help
Kind regards,
Erkan

Hi Erkan,
Can you try with below logic,
Invoice filed-----RemoveContext--------SplitByValue(Valuechange)-------Idoc
Cheers,
Giri

Integration of Idoc to OAGIS XML...

Hi All,
Can any one please help me how to integrate IDOC to OAGIS XML for Delivery alert in sap PI.
any document or steps to integrate would be really helpful.
As a start i have done the below steps :
1. downloaded all the XSD file from OAGIS site.
2. imported the XSD as external system into PI.
3. imported required idoc into sap PI.
4. created service interface for external system (OAGIS XSD).
5. during mapping there multiple nodes that has to be selected in target, but i think this is wrong because mapping can only be done with single node.
i am stuck with the mapping of idoc to OAGIS.
any help would be appreciated.
Thanks & Regards,
akshay ruia

Hi,
I managed to Integrate Idoc to OAGIS asynchronously, but now i am getting an error for "No party or service found" in SXMB_MONI. Please find the trace below :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: SAPUSER</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Docnum 0000000001010778</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPEED</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of current IDoc</Trace>
</Trace>
<Trace level="1" type="T">party normalization error: scheme = ALE#KU#WE</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">---------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">Work Process ID: 3140</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
</Trace>
<Trace level="1" type="T">Message ID = 94DE801F74491ED48E831FB43F6DF2A8</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Hop engine name = is.00.sapsrv5</Trace>
<Trace level="1" type="T">Hop engine type = IS</Trace>
<Trace level="1" type="T">Hop adapter name = XI</Trace>
<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = EP1</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SAPUSER</Trace>
<Trace level="1" type="Timestamp">2014-09-09T12:01:12Z CET</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0003</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface CARNOT.DELVRY03</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">ALE receiver ALE#KU#WE found during inbound processing. Quit determination of receiver interface action.</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Work Process ID: 3864</Trace>
<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>
<Trace level="1" type="T">Continue single processing</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = EP1</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SAPUSER</Trace>
<Trace level="1" type="Timestamp">2014-09-09T12:01:12Z CET</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache content is up to date</Trace>
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party 0000003271 and receiver service</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT2->ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="System_Error">Party and service not defined</Trace>
</Trace>
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
-  </SAP:Trace>
Please help with the solution.
Thanks & Regards,
Akshay Ruia

How can i convert flat idoc to IDOC-xml

Hi all,
I want to convert flat idoc to Idoc-xml. Suggest some methods for that....
K.S Grewal

This is the sample idoc data which i have been provided. actually i dont have much knowledge abt structure of idocs. As i have to test my scenario hich is idoc to file, i need Idoc-xml format.
ISA00 00 01006922827PCE1 126155214895 0612211736U004000004633020P|GSRE006922827PCE16155214895200612211736463302X004010ST9440001W17F20061221018085336610001 398456 1*83209N1WHWarehouseG620920061221W0740EA*PO5500203183PL000010*1MT42PF5321D/37~N9KK0180853366000001N9PEUS1TWHSW1440~SE90001~ST9440002~W17F20061221018085336710001 398448 183209N1WHWarehouseG620920061221W0756EA*PO5500203182PL000010*1MT*42PF7421D/37N9KK0180853367000001~N9PEUS1TWHS~W1456SE90002ST9440003W17F20061221018085338810001 398446 1*83209N1WHWarehouseG620920061221W071EA*PO5500205659PL000010*1MT50PF9731D/37~N9KK0180853388000001N9PEUS1TWHSW141~SE90003~GE3463302~IEA1*000463302~

IDOC to FILE(xml) graphical mapping using node function createIf

Greetings All,
            My Scenario is Idoc to File(XML)
Target Structure is
                       MO_MAT_LAN....................(0: unbound)
                            LAN_KEY.......................(0 :1)
                            DESCRIPTION.................(0 : 1)
Source MATMAS Idoc
                       E1MAKTM.........................(0 : 99)
                            SPRAS_ISO..................(0 :1)
                            MAKTX..........................(0 :1)
initially i had mapped E1MAKTM----->MO_MAT_LAN but i dont want target node MO_MAT_LAN to be created when the SPRAS_ISO is equal to EN
I have tried using node function createIf but the node is geting created only once although the input stucture is having occurance more than 5.
Can anyone please help me to achive this.
Many thanks,
Rohit

U have to use:-
SPRAS_ISO mak the context to E1MAKTM compare (Use equals) it with Constant function EN out put to be given to If without else and in then Give E1MAKTM and map out put of If node to MO_MAT_LAN.
chirag

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?

How to send a Material Idoc in format XML to SQL Server DB?

Hi,
I am creating a Material Idoc in format XML and I need send the same to a SQL Server DB.
In the transaction BD10 I create the XML Idoc, but the same is stored in the SAP Server and I need send this to an external SQL Server DB.
Somebody knows how to send automatically the XML Idoc to a SQL Server DB?
Thanks and regards!
Edited by: marcosap on Nov 11, 2010 4:00 PM

Hi,
All your XML idoc will get store in App layer,you can ask your Unix expert to write the unix code to fetch these XML idoc files and transfer to destination based on time period set by conjob.
This is simple & easy job for any UNIX expert.
Regards
Siva

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

Conv from IDoc to IDoc xml

Hello All,
When SAP is triggers an IDOC to SAP XI, the conversion from IDOC to IDOC XML takes place in SAP XI(correct me If Im wrong here).
Can some body tell me what is the mechanism behind this conversion from IDoc to IDOC xml....and there is no adapter comes to into picture as the sender is SAP....which component does this conversion in XI
Regards,
Thai

To Convert IDOC to IDOC XML and the other way around,IDOC Meta Data is required by the IDoc adapter(availabe at Integration Server).
IDoc metadata is loaded in IDX2 Using RFC connection maintained in IDX1(port maintenance in the IDoc adapter).
For more details refer http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm

IDOC-- PI-- flat xml file

Hi ,
we are working on a HR IDOC>PI>flat xml file scenario.
Idoc name is HRMD_A07.
we have consolidated some 10 interfaces together.
Plan is to,
1)(master interface) get the idoc data into a flat xml file, where flat xml consists of unique fields of all 10 interfaces.
2)Later, use flat xml as input to 10 interfaces, which are FILE>PI>FILE.
we are facing problem in master interface. The data is not coming properly in flat xml.
Can you guys suggest the proper way to do this.
should we use,
1)abap mapping, with standard functionality to convert idoc to flat file?
2)write a udf to get the proper data?
pls suggest the best approach.
san.

Hi San,
you gave us nearly no details, so it is hard to give you any recommandation.
PI provides 4 general possibilities for mappings:
Graphical: Standard and for simple cases the best solution
XSL: Webstandard, in some cases much less development time compare to graphical (if the message structure changes)
ABAP: For special cases (access to ABAP tables, operations before parsing)
Java: For special cases
Regards,
Udo

Idoc to idoc xml specification example

Similar Messages

Maybe you are looking for