XML to IDOC scenario in SAP PI 7.31

HI Team,
  I am new to Sap PI. I have one scenario xml to idoc in sap pi. Can anyone please help me step by step for this scenario.
Thanks in Adnavce
Kallu

There are ample examples on the internet. Search by giving your exact requirement.
Try this and see if it helps.
XI/PI: Simple IDoc Communication using SAP XI

Similar Messages

  • XML to IDoc scenario

    Hi all,
    for a customer I'm building an xml to IDoc scenario. The xml-file looks like this:
    <?xml version="1.0" encoding="UTF-8" ?>
    <ROOT>
      <ROW>
        <_5731 />
        <_5735 />
        <EMPLOYEE_SALARYNR>test</EMPLOYEE_SALARYNR>
      </ROW>
    </ROOT>
    The message type I created in the message mapping looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:ROOT xmlns:ns0="http://wartsila.com/i-protect">
       <ROW>
        <_5731 />
        <_5735 />
        <EMPLOYEE_SALARYNR>test</EMPLOYEE_SALARYNR>
      </ROW>
    </ROOT>
    My problem is I'm not able to translate the customer xml-file in my message mapping, unless I add the namespace "xmlns:ns0="http://wartsila.com/i-protect"" to the file. I tried to solve the problem by deleting the namespace declaration in the message mapping. After that I receive an error when I import the changed structure into the message mapping.
    Is anyone familiair with this problem? Is there someway to add a namespace to the sourcefile or to change the message mapping such a way that it corresponds to the source file?
    Thanks in advance!
    Regards,
    Ivo van Ee

    My problem is I'm not able to translate the customer xml-file in my message mapping, unless I
    add the namespace "xmlns:ns0="http://wartsila.com/i-protect"" to the file. I tried to solve the problem by
    deleting the namespace declaration in the message mapping. After that I receive an error when I import
    the changed structure into the message mapping.
    Since you have created a Message Type corresponding to the sender structure you have the option of deleting the namespace from the Message Type itself.....it is not to be deleted from the message mapping as you mentioned above.....changes made to the MT may cause an initial inconsistency in the mapping......but once done it will be fixed :)...just refer the blog given by Aamir...
    Regards,
    Abhishek.

  • Idoc Scenario from SAP to SAP  via PI 7.1o

    Q: Two idocs will process from SAP to SAP via SAP-PI 7.1o and generated together.
    Requirement :
    Sync
    2 IDOCs – as we explained our design will require two IDOCs. The first IDOC will be developed by a Z code and the second IDOC is generated by 100% Standard SAP BAPIs and 2 IDOCs  send them to PI. Both IDOCs will be generated together by  process code in sap and must be moved to PI and later to the receiver client together(SAP). The process can only be 100% completed when both IDOCs will be processed with success in the receiver side. Any one of the IDOC among 2 idoc's failed all the process should stop.
    i think that is not possible , PI will not be able to stop successfull IDOC If another IDOC get fails .
    Please give me approaches if any chance .
    Thanks, Sanakr

    Hi Bhavani,
    You can use BPM with correlation to achieve this scenario:
    Demonstration of ccBPM Scenario: SAP PI 7.1
    **************** - BPM Scenario using Fork and correlation
    Regards,
    Suman

  • Simple IDoc to IDoc scenario with SAP PI

    Hi!
    I would like to implement a very simple IDoc_to_IDoc scenario.
    i have two clients in SAP ECC 6.0 and would like to send/receive IDoc (e.g. material) with SAP PI.
    Can some one please give exact the technical steps(tcodes, action in XI Tools) to realize this issue?
    Any helpful information/documentation/SDN blogs will be very appreciated.
    Thom

    hi,
    Communication Channels:
    1) No Sender Channel is required as we are using IDOC.
    2) CC_OUT_IDOC_MATMAS05 [Send the data from Xi to CGNSAP01]. 
    Transaction Codes Used: 
    SM59- To Create RFC Destinations
    WE21- To Create IDoc Ports
    SALE- To Create Logical System
    WE20- To Create Partner Profiles
    BD64- Display Distribution Model
    WE19- To Trigger an IDoc 
    IDX1- Port Maintenance in IDoc Adapter
    IDX2- Metadata Overview for IDoc Adapter 
    Regards.

  • IDOC Scenario: System not configured as XI integarton engine

    Hello Experts,
    I have beeen trying to solve this since a few days.
    I have created an IDOC scenario  from SAP ECC s/m to PI 7.0.
    The IDOC is being sent successfully fron SAPECC with status 03 in Transaction WE05.
    But in PI 7.0 I am not able to view these messages anywhere in WE05.
    SXMB_MONI of PI 7.0 shows an error record for previous trials and shows error status (red) as "System not configured as XI integration engine"
    I have already set configuration parameters on PI7.0 in SXMB_adm.
    Your suggestions will be appreciated.
    Thanks in advance,
    Elizabeth.

    Hi,
    you can check in PI:
    - TCODE - SXMB_ADM
    - integration server
    - edit - change global config - check if you have: integration server set
    Regards,
    Divya

  • File to idoc scenario (split message)

    hello everybody
    i have a file (xml) -> XI -> Idoc scenario
    sometimes idoc message is so much big and i have problem to process it.
    so i would like split message in more idoc but i need decide a cut-point
    example in file i have 200 row and i don't want create 200 idocs but example 4.
    So i need cut file every 50 rows.
    It's possible?
    thanks
    Alex

    Hi Alessandro ,
    We had the same problem in HR implementation where we used to get data for thousands of employees in a single file.
    As Idoc was not able to hold this much of data,data used to be truncated.
    Then we had taken a field (employee number) as a criteria to generate IDocs,and now we have an IDoc generated for each employee record.
    This was helpful as for a single employee,there were a number of change records.
    The logic used was:
    Employeecode -> splitByValue(value changed) -> collapseContexts -> IDoc.
    Does it suit your requirement as well?I mean,may be you can find such field for splitting IDocs.
    Kindly let us know.
    Thanks.
    Regards,
    Shweta

  • IDoc to IDoc scenario: distribute the model view

    Hi!
    I try currently to  configure a IDoc to IDoc scenario for SAP ECC 6.0 system with following business 2 systems:
    ERP:100 (Sender)
    ERP:200 (Receiver)
    and XIB:100 (XI system)
    I successfuly created  a message type and generated the model view in tcode BD64.
    Question:
    When I try to distribute the model view which system should I choose?
    a) XI System or
    b) Receiver system ERP:200
    When  I choose the receiver system ERP:200 and get the following error
    Target system: ERP:200
    Model view ECCCLNT100 has not been updated
    Reason: Distribution model is currently being processed
    When I try to choose my XI system I get the following error:
    Target system: XIB:100
    RFC destination for synchronous communication (message type SYNCH)
    Partner profile LS PIBCLNT100 SYNCH does not exist
    Generate partner profile
    or specify outbound partner profiles for message type SYNCH
    Is that an error? If yes, how can I fix them?
    Thank you very much
    Thom

    Hi
    Look my reply on this thread regarding SYNC Message Type.
    Re: problem while distribute model view
    When I try to distribute the model view which system should I choose?
    a) XI System or
    b) Receiver system ERP:200
    You are sending IDoc to XI then R/3 so select XI system. because receiver of IDoc is XI then IDoc would be send from XI.

  • Very simple and working IDoc to IDoc scenario

    Hi!
    I would like to implement for demo issues a working IDoc to IDoc scenario with SAP XI 7.0.
    The IDocs sohuld be send from SAP ECC 6.0 system client 100 to SAP ECC 6.0 system client 200.
    Questions:
    - which material type should be used (e.g. MATMAS02,..)
    - how should the message mapping (e.g. MATMAS02 to MATMAS02) look like
    - what are the other settings in IB Repository and IB Configuration
    - how should the test from WE19  look like?
    Thank you very much!

    Hi Holger,
           No issues for that , U can use the MATMAS 02 or MATMAS 03.
    Setting in R/3 system:
    1) Create the RFC Destination(SM59).
    2) Create the tRFC port(WE21)
    3) Create the Partner profiles( WE20)
    4) Create the Distribution Model(BD64)
    Setting in XI:
    1) Create the RFC Destination
    2) Create the IDOC Port into IDOC Adapter(IDX1)
    3) Load the Metadata into IDOC into IDOC Adapter(IDX2).
    Same settings happened in Receiver IDOC also.
    Directory : No need to create the Sender agreement & no need to create the Sender Communication Channel.
    Repoistery: Import the Sender IDOC and Receiver IDOC from R/3 system.
    In WE19 Testing tool we can test IDOC generated or not.
    Regards,
    Sateesh
    D

  • Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

    Hi Experts,
    Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
    What objects i can skip.
    My PI system is 7.3 dual stack.
    I have seen below blogs, still its confusing to me.
    When and how to create an scenario in SAP PI without mapping objects.
    Pass Through Scenario with no Mapping in PI 7.1
    Appreciate your help on this.
    Regards,
    Mohan.

    Hi Mohan
    In pass thru interface you don't need to create any ESR objects, only ID objects are required.
    Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
    Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
    Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
    Regards
    Osman

  • Multimapping n:1 (XML to IDOC) Issue - Cannot use map in the scenario

    Hi! I have created a multimapping in the directory. Source message is 0...unbounded and destination message is 1. The intention is to bring a single file into XI that contains mutliple XML messages. I then need to map this into a single IDOC. I have the mapping working. However, when I try and bring this into my integration scenario, XI cannot find the message interface.
    I am not 100% convinced that this will all hang together =) But Cannot even prove that 'cos I cannot set this up in the scenario.
    Any ideas would be greatly appreciate and rewarded.
    Thx
    Duncan

    Apologies for getting all my terminology screwed up. Here is what I have:
    <u>Integration Repository</u>
    Imported Objects - Target IDOC
    Interface Objects : External Definitions - XML schema of source message
    Interface Objects : Message Interface - For source XML; Outbound + Asynch
    Message Objects : Message Mapping - XML (0..unbounded) to IDOC (1) map
    Message Objects : Interface Mapping - XML message interface (0..unbounded) -> XML to IDOC mapping -> IDOC (1)
    <u>Integration Directory</u>
    Interface Determination...
    I select Type of Interface Determination = Extended but when I pull down the dropdown I do not see the multimap.
    I have this working OK for one IDOC to multiple XML messages, doing the same as above. I have checked SCV, namespace etc... and they are correct. I am sure I am missing something very simple.
    Again, any ideas appreciated.
    Thx
    Duncan

  • Sap Xml Idoc Inbound in Sap

    Hi all
    If I have to receive an Edi message from an external system (for example an Invoice from a vendor), could I get in Sap an Idoc from a flat file formatted as a Sap Xml format?
    As Sap Xml format I mean the same structure of an xml file generated in Sap to the Xml file port.
    (The sap r/3 system is a Sap Enterprise version)
    Thanks in advance
    Bye
    Carlo
    Message was edited by: carlo pergola

    Hi
    Thanks for the answer.
    Regarding the FM IDX_XML_TO_IDOC, I thing that I can't use it directly because I have to write a program, I have to read the Xml file (that is located in a special directory of the operative system) and then use the FM putting xml data in the XML_DATA import parameter.
    It's correct?
    Bye
    Carlo

  • 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

  • Import  XML format IDOC to SAP

    Hi Gurus,
    Need to import an XML format IDOC into SAP,
    does anyone has any idea???
    Thanks,
    sachin soni

    Hi sachin,
    If u want to import the from Prsentation server just follow these procedure.
      frist use the gui_upload  function module..
    data type is  .dat....
    Earilier i have done same requirement plz gimme ur mail id so that iwl sendu  that code to ur mail........
    Regards,
    jayan.

  • Incomplete Idoc received in SAP R/3

    Hi XI Gurus
    I am working on a File to Idoc scenario and stuck because of a strange issue.
    The output Idoc structure sent from XI and as viewed in IDX5 / SXMB_MONI is as below
    <?xml version="1.0" encoding="UTF-8"?>
    <ACC_DOCUMENT01>
         <IDOC BEGIN="1">
              <EDI_DC40 SEGMENT="1">
                   <SNDPRT>LI_SND</SNDPRT>
                   <SNDPFC>LF_SND</SNDPFC>
                   <SNDPRN>0000000100</SNDPRN>
              </EDI_DC40>
              <E1BPACHE09 SEGMENT="1">
                   <OBJ_TYPE>BKPFF</OBJ_TYPE>
                   <OBJ_KEY>PR2000627830002007</OBJ_KEY>
                   <OBJ_SYS>T47CLNT800</OBJ_SYS>
                   <BUS_ACT>RFBU</BUS_ACT>
                   <USERNAME>lovein</USERNAME>
                   <COMP_CODE>3000</COMP_CODE>
                   <DOC_DATE>2007-09-11T05:18:52-07:00</DOC_DATE>
                   <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
                   <DOC_TYPE>SA</DOC_TYPE>
              </E1BPACHE09>
              <E1BPACCAHD/>
              <E1BPACGL09>
                   <ITEMNO_ACC>1</ITEMNO_ACC>
                   <GL_ACCOUNT/>
                   <ACCT_TYPE>S</ACCT_TYPE>
                   <DOC_TYPE>SA</DOC_TYPE>
                   <COMP_CODE>3000</COMP_CODE>
                   <PSTNG_DATE>2007-09-11T05:18:52-07:00</PSTNG_DATE>
                   <VENDOR_NO/>
              </E1BPACGL09>
              <E1BPACAP09>
                   <ITEMNO_ACC>00001</ITEMNO_ACC>
                   <VENDOR_NO/>
                   <COMP_CODE>3000</COMP_CODE>
                   <PYMT_METH>ach</PYMT_METH>
              </E1BPACAP09>
              <E1BPACCR09>
                   <ITEMNO_ACC>1</ITEMNO_ACC>
                   <CURR_TYPE>00</CURR_TYPE>
                   <CURRENCY>USD</CURRENCY>
                   <CURRENCY_ISO>USD</CURRENCY_ISO>
                   <AMT_DOCCUR>-30000</AMT_DOCCUR>
              </E1BPACCR09>
              <E1BPACCR09>
                   <ITEMNO_ACC>Constant</ITEMNO_ACC>
                   <CURR_TYPE>00</CURR_TYPE>
                   <CURRENCY>USD</CURRENCY>
                   <CURRENCY_ISO>USD</CURRENCY_ISO>
                   <AMT_DOCCUR>0</AMT_DOCCUR>
              </E1BPACCR09>
              <E1BPACCR09>
                   <ITEMNO_ACC>Constant</ITEMNO_ACC>
                   <CURR_TYPE>00</CURR_TYPE>
                   <CURRENCY>USD</CURRENCY>
                   <CURRENCY_ISO>USD</CURRENCY_ISO>
                   <AMT_DOCCUR>30000.00</AMT_DOCCUR>
              </E1BPACCR09>
         </IDOC>
    </ACC_DOCUMENT01>
    But the Idoc received in SAP R/3 as viewed in Transaction WE02 or table EDID4 has only one node E1BPACHE09
    and because rest of the nodes are missing SAP R/3 fails to process the Idoc .
    Any help to analyse the issue will be highly appreciated.
    Thanx
    Lovein

    Hi Lovein,
    What you can do is:
    1. Go to SXMB_MONI and take the output xml.
    2. Now go to your mapping under TEST tab and test the above mentioned output xml and see what is the output, i mean are you able to see all the desired output as per you mapping or not.
    3. If not then probabily you will get an error message, then try to find out the solution in your mapping only.
    4. If you are not able to do that, kindly send the error message, which you got in mapping.
    I hope this will solve your issue.
    Regards,
    Sarvesh
    ****Reward points, if found helpful. 

  • Error in File to IDOC Scenario

    Hi,
    I have File to IDOC scenario.
    I am getting error in sender file channel.
    "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
    Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
    Despite of this error in sender channel I am receiving the message in XI.
    But in XI also it throws error :
    "Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
    Any help on this ?
    Thanks,
    Vikas

    Hello Vikas,
    I am getting error in sender file channel.
    "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
    Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
    Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e.  keyFieldValue.
    "Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
    regarding the above error refer this
    https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
    Regards,
    Prasanna

Maybe you are looking for