IDOC MetaData in XML

Hello,
Is there any way to generate the IDOC structure with Values into XML format in SAP itself. For some reason, i do require the IDOC xml structure with values before sending it to XI. Do let me know
Regards,
Anandh

Hi Anadah
There is only two way to see the idoc data in xml form
One which I told u priviously that process the idoc through the xi without involving any mapping and get the output as idoc xml which is very simple as u don,t have to do any thing in IR side just create R.D,I.D,R.A in ID and use the idoc name as receiver and sender interface.
Secondly if u don't want to process it through XI and want to see the idoc XML with data then u have to use ABAP proxy in order to convert it into IDOC xml.
Award Point if u have got any idea about how to proceed for solution
Regard
Saurabh

Similar Messages

BCExeption: The IDOC metadata for null is not available in SID

<h3>Hello Guys,</h3>
we need some information about the error message:
com.wm.pkg.sap.BCExeption: The IDOC metadata for null is not available in <SID>
We use a Business Connector 4.8 and the backend is an ECC 6.0, we have an inbound xml scenario with FTP.
We pick up the ORDRSP from the vendors ftp-server and we would like to drop it to our backend system.
We can read the xml file into a string, but not send to the backend system, we use following steps:
- bytesToString
- stringToDocument
- documentToRecord
- recordToIDOC
- lockSession
- createTID
so far works perfekt
- sendIDoc
- releaseSession
On the step "sendIDoc" we see the described error message, but what is the message from the message?
Any Ideas?
Thank you and regards,
Michael

Hello Michal,
thank you for your quick answer!
In my opinion, i don't need any input for this service, because we pick up all data from the vendors ftp - server in a definied time interval.
All needed fields are available in the xml file. In the result tab is the IDocList filled correct, but no sending to the backend system because the error is displayed.
Is it a problem with my concept?
Regards,
Michael

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

Idoc metadata

hi
why should we import idoc metadata while using idoc adapter and what do we mean by metadata.even in mapping idoc structure why we assign segment and begin to constant values and disable cntrol record field.
regards
raghu

Hi Raghu,
What is Metadata:
IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types .This metadata is just a description of available structures
and fields.Using an RFC connection, metadata of this type can be either called directly at runtime or loaded to the Integration Server beforehand.Thus it can be loaded in two ways:
1. During the runtime
2. Before the actual message flow.
To find out what metadata has already been loaded, call the transaction Metadata Overview for IDoc Adapter (IDX2).The system displays a screen with the directory of all systems connected with the IDoc adapter (including a description) for which metadata has already been loaded. Choose Port Maintenance in IDoc Adapter () to call the corresponding transaction and to create additional ports.
Why to Import:
To process an IDocs in the form of an IDOCXML
message, an IDocs metadata must be loaded into
the Integration Server so that SAP XIs IDoc adapter can
change the native IDoc format into the XML representation.
All IDocs are created according to specific rules: This is the general structure (the record types) of every IDoc. Special rules affect the different IDoc types.
Segment:
Segment is like a container which strores all administration information for technical processing, as well as the actual application data.of an IDOC.
Fields :
A segment comprises segment fields as the smallest unit of the Idoc which contains the actual values and information.
control record :
The control record is identical for all IDocs and contains the administration information, for example, sender, recipient and message. Note that the control record also contains the last processing status ( STATUS field).
If you disable the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the fields are filled from the system information not from the payload as:
1. From XI sender service, configuration in Integration Directory, System Landscape Directory
2. Constant LS
3 . From XI receiver service, configuration in Integration Directory, System Landscape Directory
If you enable the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the fields are filled from the IDoc-XML payload.
**Pls: Reward points if helpful **
Regards,
Jyoti

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

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

Refresh Idoc Metadata in PI 7.31 Java Only

Hello experts,
We are facing issue to refresh the Idoc metadata every time when we change Idoc structure in ECC for Idoc outbound scenario.
We have imported the latest Idoc structure in ESR and assigned that to MM,OM and IFolw. Still in message monitoring we can see the old Idoc structure.
Is there anywhere else to import Idoc metadata like it used to be in Dual Stack idx2 ??
Regards,
Suman

Hi Suman,
If you are new with Idoc in PI you try with the sap.help documentation: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/50/980951964146f1a7f189b411796bae/content.htm
Regards

Problem in importing idoc metadata

Hi all,
i have problem in loading metadata in idx2. idoc details are AFS/ORDERS05/ZADIORDCONF port: SAPAGS client 003 . i could see an idoc metadata with name ORDERS05 under the corresponding sap system (SAPAGS with client 003) but with out any extension.
now i tried to create another with idoc type : ORDERS05
Extension: ZADIORDCONF
and Source port:SAPAGS
it is giving error msg Extension ZADIORDCONF is not assigned to basic type OREDERS05.
wat could be the reason , please help to solve it
Thanks and Regards
Jhansi

Hi,
There is no need to add anything to idx2. You could delete the existing metadata from idx2 and reimport it.
In some cases even this would not work. In that case, you could refresh the entire metadata by running report IDX_RESET_METADATA. However, use this report only if the above option does not work, since this report will reset your entire metadata.
Thanks,
Bhavish
Reward points if comments helpful

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

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

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

Error reading IDoc Metadata from CRM 5.0 (Basis 7.0) through XI 3.0

We are not able to generate the IDoc metadata from XI 3.0 through IDX2 for port/RFC destination pointing to SAP CRM 5.0 which runs on the Basis 7.0 Web application server.
Has anyone run into this issue? We get the dialog box with information "I::000" Message no. 000. The metadata is not generated at all.
We have no problem generating IDoc metadata for other SAP systems including 6.40 and 4.6C basis layers. Is there something different with 7.0 Basis?
Thanks,
Jay Malla
SAP XI Consultant
Licensed To Code

Hi Renjith,
Thanks for the suggestion. We've already tried that out - the RFC call IDX_STRUCTURE_GET works from SE37 using the RFC destination that we have defined for the CRM system which is referenced in the port. We can debug from the XI system into the CRM system and the data is returned correctly. We can also generate the IDoc schema from the Integration Builder Repository.
However, we cannot generate the metadata from IDX2. If we point the port in IDX1 to another RFC destination for a non Basis 7.0 system, the metadata generation works. So it seems that something is strange regarding generating the IDoc metadata for Basis 7.0 systems.
Regards,
Jay

IDOC MetaData in XML

Similar Messages

Maybe you are looking for