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

Similar Messages

  • 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

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

  • How to read an IDOC flat file and send it to XI

    Hi,
    I'm looking for a way to read a complicated Idoc structured flat file sent to XI by a legacy system and then pushing that data to and R/3 system. Can anyone recommend a good technique?
    Thanks,
    Steeve

    hi steven....
    this shud help u...
    for FileXIIDoc
    File->XI->IDOC (how to start?)
    also check this blog for specifying adapter specific identifiers in this scenario
    These are steps to follow:
    STEPS IN DESIGN
    1. Import idoc from the SAP System (SAP02) through imported objects.
    2. Create Data Type, Message Type, Message Interface for the Outbound File.
    3. Create Message Mapping with file Message and idoc (Matmas04)
    5.Create Interface mapping between File Interface and the idoc.
    Steps to be followed in Creation of Technical and Business System
    Technical System
    In SLD, click on technical landscape->New Technical System->WebAS ABAP.
    Business System.
    1.Goto Business Landscape->New Business System->Name the business system.
    2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.
    Preconfiguration steps for transfer of data to IDOCS
    1.Create a RFC Destination in SM59 of XI Server of type.
    2.In transaction IDX1 ,create a port for the client of XI server.
    3. The port has to be displayed in the idx2 transaction and we should be able to view the idoc’s which we imported through integration repository.
    Steps in Configuration
    1. Goto service without party, right click->Assign a business system.
    2. Choose the business system to be added.
    3. Create a File Sender Service with communication channel for the same.
    4. Create an idoc receiver channel under the business system. Mention the RFC Destination and the port created for the same.
    5. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.
    6. Make the Sender Agreement for theFile Sender with communication channel.
    7.Create the Receiver Determination and Interface Determination for the business system.
    8.Create the Receiver Agreement for the Business system.
    TCODES for File>XI>IDoc
    SM59-rfc destination on recving side
    IDX1-port on recving side
    IDX2-load metadata
    Bus. service adapter specific Identifiers-->Logical sys name (check this blog:/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system )
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    and also go thru this blog...
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    hope it helps....
    regards...
    vishal
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

  • 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

  • Each line of a file to a single Idoc (one file to multiple IDoc)?

    Hi Community,
    I have a flat file with many lines. Each of these lines has the same structure and has to fill a separate IDoc. How can I configure XI that it creates for each line a separate IDoc?
    I already found a blog to such a topic: File to Multiple IDocs (XSLT Mapping)
    But thatu2019s not what I am looking for (or I do not get the Point).
    I also tried to set u201CRecords per Messageu201D to 1. But that is not working to. :/
    Maybe one of you guys has an idea?
    Thanks in advance,
    Udo

    Hi Udo,
    For instance if  file structure is as follows:
    <File>
    <Header>
    </Header>
    <Item>
    </Item>
    <Item>
    </Item>
    </File>
    Now if u want to genarate a new Idoc for each n every <Item> in the file. The Header Information is to be repeated for each IDOC as well.
    Then allu need to do is  import the idoc in XI, then take the idoc xsd and change the occurrence o..unbound and then create the external definition.
    Look into this blog.
    The specified item was not found.
    Now use the external definition in your mapping instead of using the original IDOC. In your mapping map the item to IDOC, and for header data you have to use the useOneAsMany function.
    Reward if found useful
    Regards,
    Vinod.

  • How to send sales orders through XI  to non sap system

    Hello Experts,
    i need to send Sales order details from ECC to non sap system.
    anybody can help me to proceed with this in detailed way.
    i know how to send idoc through xi between sap systems.
    But i need between sap to non sap system.
    Thanks & Regards,
    Lakshmi..

    Hi !!
    Check this weblog on how to enable SSL:
    /people/gregor.wolf3/blog/2005/10/11/setup-https-ssl-for-the-sneak-preview-sap-netweaver-04-abap-edition-on-windows
    refer this realtive thread which shows the .NETnet integration with XI
    Re: .NET Client Integration with SAP XI
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
    for idoc related settings in r/3 refer the below link...
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    IDoc to File scenario
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    check this out ..
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
    Also go thru this Blogs
    ALE Configuration for Pushing IDOC's from SAP to XI by Swaroopa Vishwanath
    Configuration Steps for Posting IDOC's by Ravikumar Allampalam.
    IDOC - File scenario
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    configuring IDOCS
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    IDOC scenarios
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    Idoc related setting
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    refer this thread also
    Integration between sap and non-sap
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5651.. [original link is broken] [original link is broken] [original link is broken]
    also referthe concept of SSO
    To undersand SSO scenarios gothro the links in my reply in the following thread:
    SSO scenarios and configuring steps
    Check the following link to know the procedure for user mapping:
    Procedure to follow for user mapping.
    The following link gives you more idea on User Mapping:
    More Info on User Mapping
    Pls reward if useful

  • Idoc  b/w sap(r/3) and non sap system .

    hi gurus,
    how i pass an outbound idoc  b/w sap(r/3) and non sap system .
    which  function module we will use in this scenerio for inbound and outbound idoc both
    please guide me  with an example .

    Hi Pawan,
    Non SAP system should have RFC adapter in order to receive and send Idocs from/to SAP.
    If this is not your case, you should us a Integrator Middelware with RFC and standard adapters like SAP Exchange Infrastructure.
    If for example, your non SAP system is able to process data from flat files you can build next interface: SAP send Idocs to middleware that receive them using RFC adapter, middelware maps Idocs into flat file and send it to a one of non SAP system folder using FTP adapter. Non sap system triggers the flat file into its applications.
    Reward points if useful.
    Roger

  • IDOC to FILE Scenario-Error in defining Adapter specific Identfier

    Hi All,
    I am configuring IDOC to FILE scenario where IDOC will be send from ECC to PI System.I did following configuration
    I created RFC,PORT,LS and Partner Profile on R/3 System. I had maintained SLD and IR. In ID I created Configuration scenario and business system.When I click on menu->Adapter specific Identfier where I want to specify IDOC Adapter and RFC Adapter. But it is not allowing to edit it is not editable. As we provide LOGICAL SYSTEM,sender system ID and client number of the sender system.

    Hi Kavi,
    I assume you correctly filled the Logical System of your Business System in the SLD...
    Then in Integration Direction, use menu "SLD clear cache".
    Always in Integration Direction, open your Business System, go to menu "adapter specific identifier", and... close to button "close", you should have another button like something ''check'' or "compare to SLD' or ''retreive SDL data'' (I have not an openned PI to check the right term). Use this button to get value stored in SLD to this local definition.
    Mickael

  • No message in found in XI in IDOC to FILE scenario

    Hi everybody,
              I am working on a scenario idoc to file. The idoc is sent sucessfully from R/3 , but I am not getting any message in message monitoring in XI.Can anybody help me on this?

    Hi Bhagyashree,
    Just see if the file is generated at the specified destination....
    Meanwhile please go through the info below and cross check with what you have done...
    i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
    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:
    <a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
    File -> IDOC ref:
    <a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
    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.
    Regards,
    Abhy

  • Unable to send IDOCs from SAP PI 7.3 system to a NON-SAP system

    Hi Experts,
       We have a simple file to IDOC scenario in our SAP PI system. There is no mapping as the file is already in the IDOC-XML format.
    However , the target system is a NON-SAP system. We are using a TCP/IP RFC destination to connect to it.
    Here are the settings we have done,
    1) Creates a 3rd party technical system and business system in SLD.
    2) We have assigned a logical system name for the business system (LSKABA100).
    3) Created a port in IDX1 with the same name LSKABA100 and assigned the TCP/IP RFC destination. The RFC destination is pinging fine.
    4) Imported the metadata for the IDOC from a SAP port and copied the same to LSKABA100 port.
    5) Created the sender agreement, receiver determination, interface determination and receiver agreement in ID.
    When we send the file, there is an error on SM58 transaction of our PI system. It says "RFC_ERROR_SYSTEM_FAILURE: IDocException occurred."
    Other than that it does not provide a lot of details.
    We have seen this thread and this blog but did not get any break through.
    Please help us, if someone has any ideas.
    Best Regards,
    Ravikanth Talagana

    Hi all,
        I am not using any SAP Jco user either in my config or in the RFC destination.
    What is the user id that needs to have the authorization?
    I am using a TCP/IP RFC destination and it does not have any user id/pwd.
    There is also, no problem while doing a connection test to the RFC destination.
    Best Regards,
    Ravikanth Talagana

  • IDOC to FIle Error

    Hi,
    IDOC to File Scenario
    Sender 1 IDOC, Receiver 3 Interfaces ( Munti mapping)
    Then iam getting this error in MONI
    <SAP:Code area="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Unable to find an inbound interface</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    Regards,
    Rok

    Hi Rakesh,
    Possibly i think solution for this would be :
    Go to SLD >>administration>>Content Maintainance and link the correct software component to the businesas system .
    Then refresh the SLD cache this will automatically reflect there.
    Also check the following thread it will help u:
    Error in  interface determination wiht condition
    Regards,
    Vinod.

  • Send IDoc from External System to SAP system

    Hi Folks,
        I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
       Kindly let me knowq how I can achieve it.
    Regards,
      Santosh

    Hi Satish,
    You can achieve this requirement
    1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel  to  send IDoc.
    or
    2)Use proxy program ,implement the same ALE logic in PI.
      or
    3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
    Regards,
    raj

  • Idoc to file problem.......... IDOC lost

    i have a idoc to file problem,
    the idoc is sent from R/3 to XI,
    the problem is IDOC is sent from R/3,
    it didnt reach to XI.....
    i have checked.......we05 in R/3, it gives a status 3,
    then i checked SM58 in R/3, it shows nothing,
    when i check in idx5 in XI, theres no trace of that idoc....and no trace of the scenario run in SXMB_MONI
    pls help, where can i trace the idoc.....
    pls help

    Hi sudeer,
    Did You Check It In WE19.(Test Tool For Idoc Processing)
    If Not Do The Following Steps:
    <u><b>Step1:</b></u>
      >>      Give Your Existing Idoc Number.
    <u><b>Step 2:</b></u>
      >>      Basic Type is Your Message type.
            Ex: MATMAS05 or CREMAS05.
    <u><b>Step 3:</b></u>
      >>      In Your Existing MATMAS05 or CREMAS05 Structure say EDIDC,
      >>      You Should Fill  Your Mapped Entries In Data Structure of EDIDC.
      >>      So that Those Fields Gets Framed as Segments.
    <u><b>Step 4:</b></u>
      >>      After Doing It goto  Menu Bar and Click Idoc And Goto  Edit Control Record.
    <u><b>Step 5:</b></u>
      >>      Now You Give Your Sender And Receiver Port Number Along With Your 
            Logical System And Message Type again its Your MATMAS05  or
           CREMAS05 .
    <u><b>Step 6:</b></u>
      >>      After Doing It Click Standard Outbound Processing.
    <u><b>Step 7:</b></u>
      >>      It Will Say what Happened To your Idoc.
    <u><b>Step 8:</b></u>
      >>     It Is For Sure That if This Processing Fails It Wont Go To XI..
    Regards,
    Dhayanandh .S
    Dont forget To Provide Points If Found Helpful...
    Message was edited by:
            DHAYANANDH SIVASANKARAN

  • Send IDOC from Business Connector to SAP faster

    Hi Developer!
    I need to send a very lot of IDOC converted from XML files from the Business Connector to SAP. The XML files are in different directories pro business partner, but they have a same type (ISU_MSCONS).
    My problem, that the import take a lot of time. Only in every 3 seconds (IDOC creation time) gets (or works up?) the SAP one IDOC. I start diferent services pro partner at the same time to import the IDOCs, but I couldnt short the 3 second work time in the SAP. So you can count it easy, that in 1 minute I can import 20, in 1 hour 1200, in 1 day 28800 IDOCs instead of 100.000.
    It is really parallel import? Have anybody any idea to make the import more faster. I know (asked the SAP Administrator) so, one BC - SAP connection (Program_ID) has more pools (= threads) in the SAP at the same time.
    Thanks any help,
    Charlie

    Hi Satish,
    You can achieve this requirement
    1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel  to  send IDoc.
    or
    2)Use proxy program ,implement the same ALE logic in PI.
      or
    3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
    Regards,
    raj

Maybe you are looking for

  • Custom report based on function returning cursor

    Hi, I'm trying to create a generic function that will be the basis of a custom report in Grid Control. The idea is to pass in a database link name, then the function builds a cursor to select using that name, and returns the result to Grid control to

  • Adobe premiere pro cc 2014 freezing with magic bullet looks

    Hi- I'm running windows 8 with this software and I'm getting intermittent crashing when trying to work on any project when I'm also using magic bullet Looks on it.  The frustrating thing is that it used to work fine in premiere Pro CC, but using the

  • ACS 5.1, ASA 8.2.2, AD, Device Access. Can't get it to work...

    Does anyone have any direction/pointers on how to configure ACS 5.1 to use AD to authenticate and authorize device admin access for Cisco ASA firewalls running 8.2.2? The only way I can seem to get it to work is to tell it to continue if authenticati

  • Phishing attempt via email.

    I've just received an email from ''[email protected]'' telling me that my iCloud has been frozen and to click on a link on the email. The email has no Apple or iCloud branding included which made me very suspicious. Also I've just checked my icloud a

  • Need An SQL Query

    Hello, Kindly have a look at two tables… Item_Master Item_Code Item_Name     1          ParentA     2          ChildA          3          ChildB          4          ChildC          5          ParentB     BOM_Relation Parent_ID Child_ID Quantity 1