IDOC to WS && WS to IDOC

Hi,
I have requirement for distributing master data(customers, vendors....) to third party systems. I planed to use an IDOC on SAP side. Other side is capable to establish communication over WSs. So IDOC is async and WS could be sync communication. Is there something to take special care about for such scenario :
1. is response neede from WS, because I don't need to send some confirmation to SAP
2. how secure is such async. communication in case that WS is unavailable
3. did anybody took response from WS and send it back to SAP - some example
The other story is WS to IDOC, is there need to say some WS client that XI requested WS  request?
thx
mario

So IDOC is async and WS could be sync communication.
In most of the cases WS will be Sync....if you dont need the response then create the Message/ Service Interface as Asynchronous and include the request message only for WS communication.
1. is response neede from WS, because I don't need to send some confirmation to SAP
It depends on the business requiremenIf Sender is not asking/ supporting response then no need to use it.
2. how secure is such async. communication in case that WS is unavailable
This is normally done by Increasing the number of Retries that are done to send the message to the WS.
you can also configure alerts for Adaptyer Engine and can get the alert message when the send to WS fails....then you can again send the message.
3. did anybody took response from WS and send it back to SAP - some example
Since your source is IDOC it cannot acept response in the same call (i.e. synchronous behavior not supported)
The other story is WS to IDOC, is there need to say some WS client that XI requested WS request?
In this case you need to create a WSDL file and provide it to the WS application developers. Based on the URL present in the WSDL file (URL pointing to the interface developed in XI/ PI) the sender WS will send message to XI/ PI which can then be mapped to IDOC and sent to SAP system using a IDOC receiver Channel.
Regards,
Abhishek.

Similar Messages

  • Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

    Hi Experts,
    I am doing idoc to file scenario.
    I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
    In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
    I heard that, i can do in 3 ways. those are
    1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
    2. Without message type: create a message interface whose message type would be idoc itself
    3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
    If i  go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
    MY ASSUPTION:
       step1: I will import the IDOC into IR.
       step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
      Is my assuption or correct or not?, please tell me.
    So please tell me the entire scenario how to achieve this.
    Please help in this issue.

    Hi Laxmi
    1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
    -- Not Possible
    2. Without message type: create a message interface whose message type would be idoc itself
    -- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
    3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
    -- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
    Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
    While doing an IDOC -> XI -> File scenario, The Points to noted are:
    1. You don’t need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
    2. You import the IDOC and use the same in your mapping.
    3. In this configuration note that you don’t have a sender agreement as you don’t have a sender IDOC adapter.
    If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
    points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
    IDOC -> File scenario ref:
    IDoc-XI-File scenario
    File -> IDOC ref:
    File to IDOC
    To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
    You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
    Also, I would suggest that you go through this blog by michal if any issue arises,
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    I hope this answers your query.
    Award the POINTS if it is useful **
    Cheers
    Vasu

  • How to get Idoc acknowledgment in File to Idoc scenario

    Hi All,
    Please give suggestions about the below mentioned scenario:
    Scenario: File–XI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
    Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, ‘n’ were posted successfully and rest failed along with the error description. How can this be achieved?
    Regards,
    XIer

    Pls go thruough these links also
    Please see the below links
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    unable to import from SLD
    /people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    <b>IDOC Acknowledgements</b>
    R/3 IDOC ->XI-> ORACLE Error Handling
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    /people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    Regards
    Abhishek Agrahari

  • FM to get IDOC number of the created IDOC

    I am creating the idoc using FM -- >MASTER_IDOC_DISTRIBUTE
    If Idoc is created successfully I get sy-subrc = 0.
    If sy-subrc is 0 .... I need to fetch the Idoc number...
    I need a FM that will return the appropriate idoc number...
    thanks
    Warm regards,
    Karen

    Hello,
    try this FM "IDOC_INBOUND_SINGLE", this returns the IDoc number.
    Regards,
    Sachinkumar Mehta

  • Splitting multiple IDoc XML files into single IDoc messages for R/3

    Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
    What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
    Thankyou.
    Stuart Richards (Halfords, UK)

    Bhavesh,
    Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
    <WPUBON01><IDOC>....</IDOC>
                          <IDOC>....</IDOC>
                          <IDOC>....</IDOC></WPUBON01>
    .. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
    <WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
    In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
    SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Exception caught by adapter framework: SOAP Error
    Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
    Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
    Cheers
    Stuart

  • Idoc to file scenario - collect idocs

    Hi experts,
    I need help regarding collecting the idocs as per the reciver id available in idoc.
    After collecting these idocs at XI, the data of all idocs should be transferred in one text file.
    How I can do this ?
    Give me complete solution with example scenario ?
    Please do not give any example in standards scenarios as given in SAP BASIS Patterns.
    Regards,
    Study SAP

    Hi,
    Plz do refer the following links:
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
    /people/daniel.graversen/blog/2006/09/07/using-a-bpm-to-collect-messages-for-a-set-interval-of-time
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b
    Also this link,
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    Regards,
    Vinod.
    Edited by: Vinod Reddy on Jun 26, 2008 9:23 AM

  • Query realted to IDOC packaging in case of  IDOC-SAPPI- FILE scenario

    Hi,
    I have requirement related to IDOC packaging, i.e. SAP ECC -SAP PI - FTP server.
    I have done the following settings:
    1) In WE20, I put the partner profile settings to collect mode.
    2) I am using RSEOUT00 to trigger the collected IDOCs for example 2 idocs together.
    3) In SAP PI, I have done the following settings
    a) I added the the parameter in sxmb-adm, RUNTIME , PACKAGING & Value 1
    b) I have used IDXPW t-code to activate the message packages for IDOC
    c) I run the job through sxmb_adm t-code, configure event driven message filtering
    d) I exported the xsd of ORDERS05 and changed occurence of source structure to 0 to Unbounded and imported it in Integration Repository.
    e) I am not using mapping & interface mapping as I just want to post the IDOC structure as it to the receiving FTP server. Therefore when I changed the occurence of ORDERS05 xsd to 0 to unbounded my idea was that in the outbound message interface it will be reflected which will be ultimately reflected in Integration directory.
    Problem Details:
    When I test for the 2 PO idoc from SAP ECC, it generates 2 messages in SAP PI and also 2 files in FTP server but actually it should generate one output file containing both the IDOC details.
    Note: I am just trying to merge 2 idocs of PO as IDOC package into one output message.
    Can anybody what configuration settings I am missing for the packaging.
    Thanks & Regards
    Prabhat

    Hi Prabhat,
    If you are using PI 7.0 EHp1 or PI 7.1 Ehp1, you can configure packaging parameter and create single file for multiple idocs without using BPM.
    In other case, you have to use BPM.
    But recommended approach would be to create XML file port on SAP ECC and create IDOC XML file.
    You must have set collect IDOCs option in partner profile.
    Now you can execute RSEOUT00 report program and specify IDOC type and number IDOCs to be collected.
    This configuration will generate IDOC XML file for number IDOCs you specified in RSEOUT00 report program.
    In PI you can use File adapter to pick the file.
    Here is the nice blog explaining entire process:
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    Best Regards,
    Divyesh

  • In IDoc to file example if IDoc has not generated?what might be the problem

    In IDoc to file example if IDoc has not generated? what might be the problem? where we can find it?

    Hi Sudhakar,
      We need to check in sm58 of R/3 system for any errors..and according to the error message we have to fix the problem.
      It can fail with many reasons for example error in RFC destination connection etc.
    Regards,
    Prasanthi.

  • IDoc acknowledgement scenario using ALEAUD01 IDoc type

    Hi All,
    I have a query, regarding IDoc acknowledgement scenario using ALEAUD01 IDoc type as mentioned below.
    In a scenario where we configure and send ALEAUD01 to sender as acknowledgement of the IDoc’s received, is there any way how do we make sure that IDoc’s received by target SAP system has sent the acknowledgement successfully. Would there be any key information in the ALEAUD01 IDoc, which refers to the IDoc/data sent?
    Thanks
    Rajendra

    I needed 24 seconds to know the answer
    I took the word ALEAUD01 into Google and added site:help.sap.com in the search field
    Among the first 10 results was one with the subject
    Acknowledgment Messages
    one click to open and skimming through the text ....
    And opening one of the other hits in Google told me even which field is having this info

  • IDoc to XI u0096 Outbound IDoc

    hi Experts,
    Please let me know how to post IDOC to XI in R/3 Sender System?
    Please help
    Sourabh

    Hi,
    WE19 is the testing tool for the INBOUND and OUTBOUND Idocs,it will not post the data into XI.
    What type of idoc ur using,To post the data into XI u have to trigger the IDOC in the transaction.
    Suppoce u have to post the production order details then u have to go to  CO02 TC code there u have to give the production order details and release the IDOC .
    Before  release the IDOC make sure u have done the ALE settings then the Data will be posted into XI.
    Chech the ALE settings.
    IDOC
    http://msdn2.microsoft.com/en-us/library/ms942196.aspx
    Idoc configuration Required~
    in R/3
    1) RFC destination pointing to XI
    2) WE20 Partner Profile entries
    in XI
    1) RFC destination pointing to R/3
    Go thru this -
    configuration steps for receiving idoc in xi from r/3
    Go thru these for Idoc to XI scenarios-
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    These will be the Configurations needed in your R3,
    1. SM 59 - Create an RFC destination for your XI .
    2. We21 -- Create a port for XI
    3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
    Configuration on XI
    1. IDX2 - Import IDOC metadata.
    For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
    In XI :
    Step 1 : In SALE Tcode :
    a)Create Logical systems for R/3 and XI.
    EG : (QZACLNT100) and (X7ACLNT100).
    b) Assign the logical system of XI to Client.(X7ACLNT100)
    Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
    Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
    Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
    In R/3 :
    Step 1:
    In SALE Tcode :
    a) Create Logical systems for R/3 and XI for
    b) Assign the logical system of R/3 to Client.(QZACLNT100)
    Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
    Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
    a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
    b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
    c)In Menu Bar EDIT->Generate Partner Profile.
    Click on that and press Execute .
    This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
    d) Click EDIT->MODEL VIEW->Distribute.
    This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
    This configuration shall surely help u out as it worked out for me.
    Configurations required for IDocs in R/3
    In your XI system, you need to do the following.
    1. Create a RFC destination to your R/3 system
    2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
    3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
    4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
    5. Import the business system and you can use it in your configuration scenario.
    Please also refer below links for details.
    Go thru this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    SAP R3 ->Legacy system including master data using XI
    Regards,
    Phani

  • How to Create IDOCs for a Custom Basic IDOC Type

    Hi friends,
    I Have a Custom Basic IDOC Type.
    For that IDOC Type i need to Create an IDOC for every Header Item.
    The Header Item may have variation (Different) number of Line Items.
    in this case can i Use
    MASTER_IDOC_DISTRIBUTE and create the Idoc for each Header Item.
    or is there any way to create the IDOCs
    Thanks in Advance.
    Ganesh.

    Hi ,
    If I am not wrong you need to pass data via fm "MASTER_IDOC_DISTRIBUTE".
    So you can transfer row by row data into SDATA filed of structure type :EDID ,
    by concatenating the data into one field of type sdata. and passing it into the fm.
    I.e defining a internal table of type EDIDD.
    Try this :
    DATA : itab TYPE TABLE OF edid,
           itab1 TYPE TABLE OF edidc.
    LOOP AT itab2 INTO wa_itab2.
    CONCATENATE wa_itab2-t1 wa_itab2-t2 wa_itab2-t3 wa_itab2-t4 wa_itab2-t5
      INTO result.
      itab-sdata = result.
      APPEND itab.
      all function 'MASTER_IDOC_DISTRIBUTE'
       exporting
         master_idoc_control                  =itab1
      OBJ_TYPE                             = ''
      CHNUM                                = ''
       tables
         communication_idoc_control           =
         master_idoc_data                     =itab.
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL                = 1
      ERROR_WRITING_IDOC_STATUS            = 2
      ERROR_IN_IDOC_DATA                   = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
      OTHERS                               = 5
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

  • ALE /IDOC : several shipment in 1 IDOC

    Hi Everybody,
    I use on R/3 4.6, the SHPMNT05 IDOC structure to send output shipment to my EDI partner. In SAP standard the SHPMNT05 structure corresponding to one shipment number.
    Do you have a solution in order to concatanate several shipment number in one IDOC structure ?
    Thank you for your reply.
    Regards.

    Stephanie,
    The whole purpose of shipment in standard SAP is to gather all the deliveries...I dont know what the business requirement on your side is to gather all the Shipments into one,still there can be couple of ways to do it.
    1. Create a new custom Idoc with SHPMNT05 as child segments. Then read all the shipments you want to include in the IDoc and generate the custom idoc by appending them
    2. Do the above outside R/3 if you have a middleware like SAP XI. XI can gather all the Shipment Idocs and group it into a super-shipment
    3. Stupid it may sound but just create one shipment and include all the deliveries in it....
    Hope this helps

  • Communcation idoc not formed from master idocs

    Hi,
    I thoroughly searched all threads and could not find one on this.
    We have an issue where when we run RBDMIDOC program in production system only master idocs are formed, and no communication idocs are formed. There is no error message. But in testing system communication idocs gets generated from master idocs. We encounter no error.
    I checked partner profile and distribution model in testing and production, they were same.
    My query is that if the Program is successfully generating communication idocs in testing system, why not is it doing so in production system. Please help me on this.
    Thanks & Regards
    Amit Sharma

    Hi,
    We had same kind of issue. This was happend due to Distrubution channel not properly created.
    We re created the Distrubution channel agian properly then it worked fine.
    Check the distrubution channel config . this will solve the issue.
    Regards,
    Shanumgavel chandrasekaran.

  • Outbound idoc has data from previous idoc as well

    Hi Experts
    I am doing the goods receipt against a scheduling agreement using idocs. If this goods receipt is succesful, I am triggering an outbound idoc informing the WMS of the goods receipt. For example, if idoc number 1 comes in for GR , code has been mentioned in the inbound function module for trigger of an outbound idoc A. Please note that the difference that this isnt the case of an output type.
    Now the problem that arises is , the idoc data for outbound idocs is being accumulated and sent. For example, if 1 is the GR idoc, A is the outbound idoc, then 2 is the 2nd GR idoc, then AB is the data coming  2nd outbound idoc (instead of just B), then 3 is the 3rd GR idoc, then ABC is the data coming  for 3rd outbound idoc(instead of just C)
    I am a little confused about the same as to which area this pertains to and would really appreciate quick help on the same.
    Regards
    Shubhankar

    Hi,
    How are you testing this functionality ? Is it using WE19 test transaction or ??
    If that is the case then please come out of transaction everytime you process the idoc.
    Also, clarify your scenario in more detail.
    Processing of your single inbound idoc creates more than one outbound idocs or
    for every inbound idoc which is processed you are creating one outbound idoc in user exit.
    Also check if the idocdata internal table is refreshed once an outbound idoc is created.
    If possible please send your code.
    KR Jaideep,

  • Message output(IDoc) from MIGO creates multiple idocs repeats for each line

    Hi Experts,
    We want to send one idoc message thru MIGO output message control upon posting at HEADER level regardless of how many line items are there on the Purchase Order.
    Using MIGO we are doing a 101 goods receipt on a PO with 3 line items and we are getting 3 idocs created with the same information form the message output control(basically it is at item level).
    I don't know if this is how standard SAP designed the MM message output control.
    From MIGO or MB03 there is no option to display the messages at the header level because you have to go thru the line item details to see the messages
    I have also tried the collective slip option on MIGO and it did not work(help suggests that it will combine everything in one output)
    Can you please let me know if there is a config or development that needs to made on controling the message output at the header level from MIGO.
    Thanks for all your help
    Shraj

    Hi Sri hari Raju.
    Did you solve this problem?
    Can you tell me how?
    Thanks

  • Counting the number of IDocs in a package of IDocs in BPM

    Hello All,
        I need a solution where I need to count the number of EDI_DC40  segments (The IDoc Count) in a package of IDoc's. The following is the scenario
    1) We are receiving a package of IDoc's in receive step using the XI File Adapter. I was wondering if there is a way that I can count the number of IDoc's in the BPM using a container operation or some other Method. I appreciate any help.
    Thanks.

    HI,
    We have two ooptions,
    one as explained above , yu can use standard count function and that can be used.
    Second one is we have count option in file adapter to count the msgs.
    see the below link
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/9a50465ccf84479e39a6d50c90fb3f/content.htm
    Regards
    Chilla

Maybe you are looking for

  • Issue in attaching dynamic Query to the View Object

    Hi, We are having a View Object attached to the JRAD page. The View object is build thru as Expert mode. There is no any CDATA SQLQUERY stored in the VO.xml file. We are building the query dynamically and attaching it to the VO in RUNTIME. The code i

  • What do you do when the download is poor?

    I purchased a song, but there is a bad spot on the song. I JUST bought it and it automatically downloaded and there is a glitch in the first couple of seconds. Is there a way to fix the file or re-download without having to pay again? What is the pro

  • TS2313 My podcasts will no longer download.

    There is an exclimation mark to the left of the title of a new podcast and on the far right side shows the icloud icon.  What do I need to do to start downloading my podcasts again? Hard drive space is not an issue.

  • Cannot adjust brightness in windows 7 64bit

    Hi everyone, thanks for reading! I cannot adjust the brightness in windows 7 64bit with my keyboard. I have tried reinstalling the latest bootcamp drivers but it still did not work. The brightness of the monitor is just too bright for my eyes... Is t

  • Plantage de photoshop CC à l'enregistrement d'un PNG

    Bonjour, Photoshop plante à chaque fois que je veux enregistrer un png: "Photoshop à cessé de fonctionner" C'est systématique j'ai donc testé avec d'autres formats et ça fait la même chose avec: Les BMP Les GIFS Les DICOM Les IFF Les JPEG2000 Les TAR