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" ?>
- <!--
Message Branch According to Receiver List
-->
- <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

Similar Messages

  • 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

  • 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

  • No service for system ..PI, client. in Integration Directory -IDOC

    Hi,
    I am getting following error when try to post IDoc frm SAP to SAP XI:
    No service for system ..PI, client. in Integration Directory -IDOC
    I have verified the following transactions:
    port,RFC destinations are correct in SAP and XI systems(verfied in SM59,IDX1,BD64 and in SLD)
    Please help me here

    This error was resoved now.
    What is the cause?
    In ID, Adapter spefic Identifiers for SAP Business System does not have R/3 System ID and Client and It has only Logical System name. Its bcoz of cache prob between XI and SLD.
    Resolution:
    There is an option to refresh, so that Adapter specific identifiers was refreshed from SLD and values got populated for R/3 System ID and Client name.
    Generally when Business System is imported from SLD to XI, these 3 parameters(Logical System name,R/3 System ID and Client) will populate automatically.
    Thanks for Inputs:)

  • TP Agreement Not Found -- OAGIS XML document over AS2

    Hi,
    I am getting TP Agreement not found error while receiving OAGIS XML document over AS2. Below is error message.
    Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND
    I am not sure why it says null-INBOUND. It appears like it is not able to identify Document Version. DOCTYPE_REVISION=7.2.1 is being passed in the AS2 transport headers but still it does not recognize the version.
    I am not sure what is missing. Please give some ideas hints.
    Below is the Business Message:----
    Id     AC12149513F1F78141400000E7DEDE00
    Message Id     AC12149513F1F78136200000E7DED800
    Refer To Message     Refer To Message
    Sender Type     AS2 Identifier
    Sender Value     SOALocal
    Receiver Type     AS2 Identifier
    Receiver Value     PowellIndustries
    Sender     SOALocal
    Receiver     Powell
    Agreement Id     
    Agreement     
    Document Type     PROCESS_INVOICE_002
    Document Protocol     OAG
    Document Version     7.2.1
    Message Type     REQ
    Direction     INBOUND
    State     MSG_ERROR
    Acknowledgement Mode     NONE
    Response Mode     ASYNC
    Send Time Stamp     06/07/2013 11:28:49 AM
    Receive Time Stamp     06/07/2013 11:28:50 AM
    Document Retry Interval(Channel)     0
    Document Remaining Retry(Channel)     0
    Document Retry Interval(Agreement)     
    Document Remaining Retry(Agreement)     
    Native Message Size     10788
    Translated Message Size     
    Business Action Name     
    Business Transaction Name     
    Xpath Name1     
    Xpath Value1     
    Xpath Expression1     
    Xpath Name2     
    Xpath Value2     
    Xpath Expression2     
    Xpath Name3     
    Xpath Value3     
    Xpath Expression3     
    Correlation From XPath Name     
    Correlation From XPath Value     
    Correlation From XPath Expression     
    Correlation To XPath Name     
    Correlation To XPath Value     
    Correlation To XPath Expression     
    Wire Message     Wire Message
    Application Message     Application Message
    Payload Storage     Payload Storage
    Attachment     Attachment
    Label     
    Collaboration Id     AC12149513F1F7813BF00000E7DEDB00
    Collabration Name     
    Collabration Version     
    Business Action Name     
    Exchange Protocol Name     AS2
    Exchange Protocol Version     1.1
    Interchange Control Number     
    Group Control Number     
    Transaction Set Control Number     
    Error Code     B2B-50547
    Error Description     Machine Info: (pwl.pri) Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    Error Level     ERROR_LEVEL_COLLABORATION
    Error Severity     ERROR
    Error Text     Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    Below is the Wire Message:----
    Id     AC12149513F1F78115400000E7DED600
    Message Id     AC12149513F1F78115400000E7DED600
    Business Message     AC12149513F1F78141400000E7DEDE00
    Packed Message     Packed Message
    Payload     Payload
    Protocol Message Id     <38383939373331343630313931303737@SOALocal>
    Refer To Protocol Message Id     
    Protocol Collaboration Id     
    Protocol Transport Binding     ChannelName=SOALocal dcID=CHANNEL_nlzbB-7511847722850817684 AS2-To=PowellIndustries DOCTYPE_NAME=PROCESS_INVOICE_002 TE=trailers, deflate, gzip, compress DOCTYPE_REVISION=7.2.1 Date=Fri, 07 Jun 2013 16:28:49 GMT AS2-Version=1.1 Accept-Encoding=gzip, x-gzip, compress, x-compress AS2-From=SOALocal url=http://pwl.pri/b2b/transportServlet Content-Transfer-Encoding=binary Message-ID=<38383939373331343630313931303737@SOALocal> Content-type=application/pkcs7-mime; smime-type="enveloped-data" MSG_RECEIVED_TIME=Fri Jun 07 11:28:49 CDT 2013 ECID-Context=1.71b9d2a41e5aaef0:-10db6371:13f1ee6cb74:-8000-000000000000276d;khvE MIME-version=1.0 tpName=PowellIndustries User-Agent=AS2 Server Oracle HTTPClient Version 10h Content-Length=13663 Host=pwl.pri:8001 Connection=close, TE useProxy=false From=SOALocal additionalHeaders=DOCTYPE_NAME=PROCESS_INVOICE_002#DOCTYPE_REVISION=7.2.1
    Message Digest     Message Digest
    Digest Algorithm     md5
    Transport Protocol     HTTP
    Transport Protocol Version     1.1
    Url     http://pwl.pri:8001/b2b/transportServlet
    security     
    Transport Headers     ChannelName=SOALocal dcID=CHANNEL_nlzbB-7511847722850817684 AS2-To=PowellIndustries DOCTYPE_NAME=PROCESS_INVOICE_002 TE=trailers, deflate, gzip, compress DOCTYPE_REVISION=7.2.1 Date=Fri, 07 Jun 2013 16:28:49 GMT AS2-Version=1.1 Accept-Encoding=gzip, x-gzip, compress, x-compress AS2-From=SOALocal url=http://pwl.pri:8001/b2b/transportServlet Content-Transfer-Encoding=binary Message-ID=<38383939373331343630313931303737@SOALocal> Content-type=application/pkcs7-mime; smime-type="enveloped-data" MSG_RECEIVED_TIME=Fri Jun 07 11:28:49 CDT 2013 ECID-Context=1.71b9d2a41e5aaef0:-10db6371:13f1ee6cb74:-8000-000000000000276d;khvE MIME-version=1.0 tpName=PowellIndustries User-Agent=AS2 Server Oracle HTTPClient Version 10h Content-Length=13663 Host=pwl.pri:8001 Connection=close, TE useProxy=false From=SOALocal additionalHeaders=DOCTYPE_NAME=PROCESS_INVOICE_002#DOCTYPE_REVISION=7.2.1
    certificates     certificates
    State     ERROR
    Reattempt Count     
    Error Code     B2B-50547
    Error Description     Machine Info: (pwl.pri) Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    Error Text     Agreement not found for trading partners: FromTP SOALocal, ToTP Powell with document type PROCESS_INVOICE_002-null-INBOUND.
    exchangeRetryInterval     
    exchangeRemainingRetry     
    Message Size     10788
    Thanks
    Ismail M.

    Hi Anuj,
    Here is the payload from the wire message. We are using 11.1.1.6.0
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <PROCESS_INVOICE_002 xmlns="http://www.openapplications.org/171_process_invoice_002">
      <CNTROLAREA xmlns="">
        <BSR>
          <VERB value="PROCESS">PROCESS</VERB>
          <NOUN value="INVOICE">INVOICE</NOUN>
          <REVISION value="002">002</REVISION>
        </BSR>
        <SENDER>
          <LOGICALID>POWELLIND</LOGICALID>
          <COMPONENT>B2B</COMPONENT>
          <TASK/>
          <REFERENCEID/>
          <CONFIRMATION>0</CONFIRMATION>
          <LANGUAGE>ENG</LANGUAGE>
          <CODEPAGE/>
          <AUTHID>oracle B2B</AUTHID>
        </SENDER>
        <DATETIME qualifier="CREATION">
          <YEAR/>
          <MONTH/>
          <DAY/>
          <HOUR/>
          <MINUTE/>
          <SECOND/>
          <SUBSECOND/>
          <TIMEZONE/>
        </DATETIME>
      </CNTROLAREA>
      <DATAAREA xmlns="">
        <PROCESS_INVOICE>
          <INVHEADER>
            <AMOUNT qualifier="DOCUMENT" type="T" index="1">
              <VALUE>5413</VALUE>
              <NUMOFDEC>2</NUMOFDEC>
              <SIGN>+</SIGN>
              <CURRENCY>USD</CURRENCY>
              <DRCR>D</DRCR>
            </AMOUNT>
            <DATETIME qualifier="DOCUMENT" index="1">
              <YEAR>2013</YEAR>
              <MONTH>03</MONTH>
              <DAY>15</DAY>
              <HOUR>00</HOUR>
              <MINUTE>00</MINUTE>
              <SECOND>00</SECOND>
              <SUBSECOND>0000</SUBSECOND>
              <TIMEZONE>-0500</TIMEZONE>
            </DATETIME>
            <DOCUMENTID>1000182</DOCUMENTID>
            <DESCRIPTN/>
            <DOCTYPE/>
            <PAYMETHOD/>
            <REASONCODE/>
            <USERAREA/>
            <PARTNER>
              <NAME index="1">Powell US Operating Unit</NAME>
              <ONETIME/>
              <PARTNRID/>
              <PARTNRTYPE>Supplier</PARTNRTYPE>
              <SYNCIND/>
              <ACTIVE/>
              <CURRENCY/>
              <DESCRIPTN/>
              <DUNSNUMBER/>
              <GLENTITYS/>
              <NAME index="1">Powell US Operating Unit</NAME>
              <PARENTID/>
              <PARTNRIDX/>
              <PARTNRRATG/>
              <PARTNRROLE/>
              <PAYMETHOD/>
              <TAXEXEMPT/>
              <TAXID/>
              <TERMID/>
              <USERAREA/>
              <CONTACT>
                <NAME index="1">No Sales Credit</NAME>
                <CONTCTTYPE/>
                <DESCRIPTN/>
                <EMAIL/>
                <FAX index="1"/>
                <TELEPHONE index="1"/>
                <USERAREA/>
              </CONTACT>
            </PARTNER>
            <PARTNER>
              <NAME index="1">PO Box 843823, Dallas, Dallas, TX, 75284-3823, United States</NAME>
              <ONETIME/>
              <PARTNRID/>
              <PARTNRTYPE>RemitTo</PARTNRTYPE>
              <SYNCIND/>
              <ACTIVE/>
              <CURRENCY/>
              <DESCRIPTN/>
              <DUNSNUMBER/>
              <GLENTITYS/>
              <NAME index="1">PO Box 843823, Dallas, Dallas, TX, 75284-3823, United States</NAME>
              <PARENTID/>
              <PARTNRIDX/>
              <PARTNRRATG/>
              <PARTNRROLE/>
              <PAYMETHOD/>
              <TAXEXEMPT/>
              <TAXID/>
              <TERMID/>
              <USERAREA/>
              <ADDRESS>
                <ADDRLINE index="1">PO Box 843823</ADDRLINE>
                <ADDRTYPE/>
                <CITY>Dallas</CITY>
                <COUNTRY>United States</COUNTRY>
                <COUNTY>Dallas</COUNTY>
                <DESCRIPTN/>
                <FAX index="1"/>
                <POSTALCODE/>
                <REGION/>
                <STATEPROVN>TX</STATEPROVN>
                <TAXJRSDCTN/>
                <TELEPHONE index="1"/>
                <URL/>
                <USERAREA/>
              </ADDRESS>
              <CONTACT>
                <NAME index="1"/>
                <CONTCTTYPE/>
                <DESCRIPTN/>
                <EMAIL/>
                <FAX index="1"/>
                <TELEPHONE index="1"/>
                <USERAREA/>
              </CONTACT>
            </PARTNER>
            <PARTNER>
              <NAME index="1"/>
              <ONETIME/>
              <PARTNRID/>
              <PARTNRTYPE>Carrier</PARTNRTYPE>
              <SYNCIND/>
              <ACTIVE/>
              <CURRENCY/>
              <DESCRIPTN/>
              <DUNSNUMBER/>
              <GLENTITYS/>
              <NAME index="1"/>
              <PARENTID/>
              <PARTNRIDX/>
              <PARTNRRATG/>
              <PARTNRROLE/>
              <PAYMETHOD/>
              <TAXEXEMPT/>
              <TAXID/>
              <TERMID/>
              <USERAREA/>
              <ADDRESS>
                <ADDRLINE index="1"/>
                <ADDRTYPE/>
                <CITY/>
                <COUNTRY/>
                <COUNTY/>
                <DESCRIPTN/>
                <FAX index="1"/>
                <POSTALCODE/>
                <REGION/>
                <STATEPROVN/>
                <TAXJRSDCTN/>
                <TELEPHONE index="1"/>
                <URL/>
                <USERAREA/>
              </ADDRESS>
              <CONTACT>
                <NAME index="1"/>
                <CONTCTTYPE/>
                <DESCRIPTN/>
                <EMAIL/>
                <FAX index="1"/>
                <TELEPHONE index="1"/>
                <USERAREA/>
              </CONTACT>
            </PARTNER>
            <DOCUMNTREF>
              <DOCTYPE>INV</DOCTYPE>
              <DOCUMENTID>10005:21009</DOCUMENTID>
              <PARTNRID/>
              <PARTNRTYPE>Supplier</PARTNRTYPE>
              <DESCRIPTN/>
              <DOCUMENTRV/>
              <LINENUM/>
              <NOTES index="1"/>
              <SCHLINENUM/>
              <SUBLINENUM/>
              <USERAREA/>
            </DOCUMNTREF>
            <INVTAX>
              <AMOUNT qualifier="TAX" type="T" index="1">
                <VALUE>413</VALUE>
                <NUMOFDEC>2</NUMOFDEC>
                <SIGN>+</SIGN>
                <CURRENCY>USD</CURRENCY>
                <DRCR>D</DRCR>
              </AMOUNT>
              <AMOUNT qualifier="TAXBASE" type="T" index="1">
                <VALUE>5413</VALUE>
                <NUMOFDEC>2</NUMOFDEC>
                <SIGN>+</SIGN>
                <CURRENCY>USD</CURRENCY>
                <DRCR>D</DRCR>
              </AMOUNT>
              <QUANTITY qualifier="PERCENT">
                <VALUE/>
                <NUMOFDEC/>
                <SIGN/>
                <UOM/>
              </QUANTITY>
              <DESCRIPTN/>
              <LINENUM/>
              <TAXCODE/>
              <TAXJRSDCTN/>
              <USERAREA/>
            </INVTAX>
            <PYMTTERM>
              <AMOUNT qualifier="DISCNT" type="T" index="1">
                <VALUE/>
                <NUMOFDEC/>
                <SIGN/>
                <CURRENCY/>
                <DRCR/>
              </AMOUNT>
              <DATETIME qualifier="DISCNT" index="1">
                <YEAR/>
                <MONTH/>
                <DAY/>
                <HOUR/>
                <MINUTE/>
                <SECOND/>
                <SUBSECOND/>
                <TIMEZONE/>
              </DATETIME>
              <DATETIME qualifier="DUE" index="1">
                <YEAR>2013</YEAR>
                <MONTH>04</MONTH>
                <DAY>14</DAY>
                <HOUR>00</HOUR>
                <MINUTE>00</MINUTE>
                <SECOND>00</SECOND>
                <SUBSECOND>0000</SUBSECOND>
                <TIMEZONE>-0500</TIMEZONE>
              </DATETIME>
              <DATETIME qualifier="PYMTTERM" index="1">
                <YEAR>1952</YEAR>
                <MONTH>01</MONTH>
                <DAY>01</DAY>
                <HOUR>00</HOUR>
                <MINUTE>00</MINUTE>
                <SECOND>00</SECOND>
                <SUBSECOND>0000</SUBSECOND>
                <TIMEZONE>-0600</TIMEZONE>
              </DATETIME>
              <DESCRIPTN>Net Due in 30 Days</DESCRIPTN>
              <TERMID>30 NET</TERMID>
              <USERAREA>
                <AMOUNT qualifier="TOTAL" type="T" index="1">
                  <VALUE>5413</VALUE>
                  <NUMOFDEC>2</NUMOFDEC>
                  <SIGN>+</SIGN>
                  <CURRENCY/>
                  <DRCR>D</DRCR>
                </AMOUNT>
              </USERAREA>
            </PYMTTERM>
          </INVHEADER>
          <INVLINE>
            <AMOUNT qualifier="EXTENDED" type="T" index="1">
              <VALUE>50</VALUE>
              <NUMOFDEC/>
              <SIGN>+</SIGN>
              <CURRENCY/>
              <DRCR>D</DRCR>
            </AMOUNT>
            <OPERAMT qualifier="UNIT" type="T">
              <VALUE>5</VALUE>
              <NUMOFDEC/>
              <SIGN>+</SIGN>
              <CURRENCY/>
              <UOMVALUE>1</UOMVALUE>
              <UOMNUMDEC>0</UOMNUMDEC>
              <UOM/>
            </OPERAMT>
            <QUANTITY qualifier="ITEM">
              <VALUE>10</VALUE>
              <NUMOFDEC/>
              <SIGN>+</SIGN>
              <UOM/>
            </QUANTITY>
            <LINENUM>1</LINENUM>
            <DESCRIPTN>11GA SHEET STEEL HOT ROLLED-PICKLED-OILED COMMERCIAL QUALITY.</DESCRIPTN>
            <ITEM>11GA SHEET STEEL HOT ROLLED-PICKLED-OILED COMMERCIAL QUALITY.</ITEM>
            <ITEMTYPE/>
            <ITEMX>11HRPO</ITEMX>
            <OPENITEM/>
            <PROJACTVTY/>
            <UNIT>LB</UNIT>
            <UPC/>
            <USERAREA/>
            <DOCUMNTREF>
              <DOCTYPE>LINE</DOCTYPE>
              <DOCUMENTID>10005:21009:19019</DOCUMENTID>
              <PARTNRID/>
              <PARTNRTYPE>Supplier</PARTNRTYPE>
              <DESCRIPTN/>
              <USERAREA/>
            </DOCUMNTREF>
            <DOCUMNTREF>
              <DOCTYPE>SalesOrder</DOCTYPE>
              <DOCUMENTID>600813</DOCUMENTID>
              <PARTNRID/>
              <PARTNRTYPE/>
              <DESCRIPTN/>
              <USERAREA/>
            </DOCUMNTREF>
            <DOCUMNTREF>
              <DOCTYPE>PurchaseOrder</DOCTYPE>
              <DOCUMENTID>TEST123</DOCUMENTID>
              <PARTNRID>N/A</PARTNRID>
              <PARTNRTYPE>Customer</PARTNRTYPE>
              <DESCRIPTN/>
              <DOCUMENTRV/>
              <LINENUM/>
              <SCHLINENUM/>
            </DOCUMNTREF>
          </INVLINE>
        </PROCESS_INVOICE>
      </DATAAREA>
    </PROCESS_INVOICE_002>

  • 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

  • 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

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

  • Splitting single idoc into multiple xml's

    Hello,
    My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process.
    and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process

    Hi Abhishek,
    [quote]My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process
    For this, you have to go for multimapping.
    The links for it are already provided in the above posts.
    and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process
    Can you please explain this requirement further?
    -Supriya.

Maybe you are looking for

  • How can I convert OPENGL canvas graphics into bitmap image format.

    I used the following code... but no conversion made... plz tell the write way.. public static void savePaintingJPG(GLCanvas canvas, String fileName) {         // saves the content of the 'panel' in a file 'file'.jpg         String name = ""; int fram

  • Error while saving RTOM based campagin when creating the rules

    Hi Experts, My requirement is to configure RTOM in the system. I have created RTOM based campaign and when I maintain conditions in u201CEligibility and Agent skills Rulesu201D assignment block, I am unable to save the campaign. It throws the followi

  • Material Master Replication R/3 to SRM

    Hello SRM Experts, I am in a process of replicating MM from R/3 to SRM server. This is not a new one,already some materials are loaded into SRM. Ths issue what I am trying to understand is I have many materials,material Types and  material groups add

  • Routine help - urgent

    Hi guys, Need help for routine code, i have rquirement currency translation based on currency type  In the cube we having the Amount Key Figure in USD. i want to convert these values based on currency type or company code . ..GBP,JPY,INR,KRW..etc. ca

  • Mac Pro & RAID Card configuration

    hello- i've got a 2 x 2.26 Quad Core Xeon Mac Pro with an Apple RAID card in it 1 x 1TB system drive and 3 x 2TB media drive for video question: can i have the system drive separate from the RAID card and just create a 6TB RAID0 array for the media d