Suggestions Required While Doing Idoc To File Scenario

Hi All,
My scenario is Idoc To File. I have to take the  Purchase Order Idoc from system "A" and send it as a XML file to system"B".
The problem here is, i have three types of PO Idoc's with different fields.
1) Purchase Order (Fields : PO Number, date, vendor, material and quantity)
2) Delivery with serial number ( Fields : delivery number, est date, vendor, material, serial and quantity)
3) Delivery using serial number with subcontracting repair ( Fields :
PO Number, date, vendor, material, serial and quantity).
I have to convert all the above PO Idoc's into Xml file format and send it to system "B".
Here i have three different Idocs one per Purchase Order , one per Delivery with serial number and one per  Delivery using serial number with subcontracting repair .
My question is, shall i need to create three different scenario's for the above requirement or shall i create only one scenario with all the fileds in file structure.
Is it possible by creating only scenario, to handle the above situation. If so where can i handle the conditions saying that the File Structure
for Purchase Order  should be (With Fields : PO Number, date, vendor, material and quantity) ,
for Delivery with serial number should be (With  Fields : delivery number, est date, vendor, material, serial and quantity) and 
for  Delivery using serial number with subcontracting repair should be ( With  Fields : PO Number, date, vendor, material, serial and quantity).
Please provide the solution for the above situation.
And suggest me which is the best method to follow.
Regards,
Venkat.

Prasad,
My requirement is i will process only  one Idoc at a time either it may be Purchase order or Delivery with serial number or  Delivery using serial number with subcontracting repair . So no chance of multiple targets. For example
First time i may process Idoc related to Purchase Order then at that time  only fields ( PO Number, date, vendor, material and quantity) should convert into  Xml file and pass it to system "B".
Second time i may process Idoc related to Delivery with serial number then at that time  only fields ( delivery number, est date, vendor, material, serial and quantity)  should convert into  Xml file and pass it to system "B".
Third time i may process Idoc related to Delivery using serial number with subcontracting repair then at that time  only fields ( PO Number, date, vendor, material, serial and quantity) should convert into  Xml file and pass it to system "B".
In all the cases the target is same "B" system.
I think now it is clear.
Regards,
Venkat.

Similar Messages

  • Error Resource not Found in SXMB_MONI while doing IDoc to File Scenario

    Hi Experts,
    I am doing IDoc to File Scenario and I am facing Following Error in SXMB_MONI,
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>
      <SAP:P1>193c0e01-bd37-11dd-850c-d879ac131b1f</SAP:P1>
      <SAP:P2>http://clarityPOC</SAP:P2>
      <SAP:P3>com/sap/xi/tf/_MM_Timesheets_iDocToFile_.class</SAP:P3>
      <SAP:P4>-1</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have tested the same file in test tab of mapping, execution of  mapping is successful there.
    Regards,
    Nitin Patil
    Edited by: Nitin Patil on Dec 5, 2008 7:09 AM

    Hi Dharmveer I have done the cache refresh ID in XI Data Cache Refresh using link
    http://sapnbipoc:50000/rep/support/admin/index.html
    but still same error persisting
    and in Integration Builder> Environment>Cache Status Overview >Problem tab
    following error (initial part of the error pasted) is shown
    Thrown:
    com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Adapter Engine af.npi.sapnbipoc not found in SLD
         at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:56)
         at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:41)
         at com.sap.aii.ib.server.abapcache.logons.IR_LogonData.<init>(IR_LogonData.java:26)
    Regards,
    Nitin Patil

  • FIle Content Conversion Problem in IDOC-XI-File Scenario

    Dear All,
    I am doing IDOC-XI-FILE scenario.
    I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like <b>%store_code%_%current_date%_sitemaster.xml</b> , I have completed the dynamic generation successfully .
    Now there is slight change in the requirement ,<b>we have to suppress the current_date node of the xml content</b> . i have tried to suppress the current_date using these <b>DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut</b> , But I am unable to suppress it Can some body provide me the details on this .
    The output xml version generated by Reciever file adapter is as below :
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    </ns0:MT_SITE_MASTER>
    Plz provide me the code I have to write in the file content conversion .
    Thanks in advance
    Regards
    Prabhat

    If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
    My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier.  Then use the Suppress Logic for the Current Date.
    So it will look like this-
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    <CURR_DATE>
       <CURRENT_DATE>20051105</CURRENT_DATE>
    </CURR_DATE>
    </ns0:MT_SITE_MASTER>
    So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
    CURR_DATE.fieldFixedLengths - 0
    CURR_DATE.fixedLengthTooShortHanling - Cut
    And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
    Hope this solves ur problem.
    Regards,
    Moorthy

  • IDOC to File scenario Configuraton settings

    hi,
       I am doing IDOC to FILE scenario.I am sending IDOC from R/3 to XI and then to XML file.That mean smy scenario is as Follows (  R/3XIfile ) These are my queries
    -->I have created RFC Destination from R/3 to XI.should I need to create RFC destination from XI to R/3 ( i mean In  XI )??
    -->I have created one Port in R/3 and I have linked that port with RFC Destination that i have created.here i am sending IDOC from R?# to XI...SO we call this PORT as SENDER PORT or RECEIVER PORT??
    -->and DO we need to create PORT in XI also??is it require for my scenario??
    -->DO we need to create Partner Profiles in XI also??
    -->DO we need to create LOgical system in XI to represent the XI system?? (as we created LS in R/3 to represent sender system)
    --->Here is my big doubt..
                   when we test IDOC ..by sing we19 TCODE,
       We need to fill the corresponding details as below,
    Receipent                                  Sender
    Port                                              Port
    PartnerNo                                      PartnerNo
    PartnerType                                   PartnerType
    my Doubt is,
    -->>In which field we need to specify the Port that we have created in R/3..Receipent side OR Sender Side..?? and Why??
    -->>Same for ParnerNo..where we need to specify the Logical system which we have created in R/3 should specify??Why??
    Please give reply ASAP..with detailedexplanation..
    points will be rewarded..
    regards,
    murali

    HI
    SLD-
    1) Create a Product/Software Component
    2) Technical System pointing to R/3 system
    3) Business System for the above technical system
    In the Repository
    1) Import the Software component created in the sld
    2) Create a namespace,
    3) import the idoc and then create sender data type/message type etc and mapping
    4) Mapping Rules is depends on the requirement
    In the Directory
    1) Create a Scenario /import the business system
    2) Create Receiver/Interface determination
    3) Create communication channels for sender and receiver
    4) Sender Agreeement and Receiver Agreement.
    Then the file adapter configuration is depend on the input file format.
    Also you need to have Logical destionation created in the XI , and the IDX1 entry
    In R/3 Port, Partner profiles etc should be created
    Have a look into this document~
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    While doing an File -> XI -> IDoc scenario, The Points to noted are:
    1. You donu2019t 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 will need a sender agreement for the file.
    4. In this configuration note that you will also need a receiver agreement for the IDOC.
    For any File -> XI -> IDoc scenario ref:
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    While doing an File -> XI -> IDoc scenario, The Points to noted are:
    1. You donu2019t 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 will need a sender agreement for the file.
    4. In this configuration note that you will also need a receiver agreement for the IDOC.
    For any File -> XI -> IDoc scenario ref:
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    /people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
    /people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD u2013 System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system names
    cheers
    reward poins if found useful

  • Error in Operation Mapping for Idoc to File Scenario

    Hi Experts,
    I am doing Idoc to File Scenario for Timesheet IDoc "HRSM_C" and following step are through,
    Sender agreement --> Receiver Determination --> Interface Determination
    got stuck in Operation mapping, it sahows error
    "Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1"
    Also not all the fields of IDoc HRSM_C are transferred to the XI server as I am unable to see all the fields in xml file using transaction idx5, as I suppose the reason behind may be there are no values in those fields.
    Please suggest how to resove the issue and transfer all the fields from R3 to XI in Idoc eventhough it doesn't contain any value.

    Hi
    Refresh CPA cache using user PIDIRUSER.
    Look Note 951318 for Mapping Cache Refresh.

  • Problem with IDOC TO FILE Scenario

    Hi Experts,
    I am doing IDOC TO FILE Scenario.
    I have done all the configuration.I have cretaed RFC,PORT,LS and Partner profile at both R/3 and
    XI Side.
    when I am trying to generate IDOC using we19 and I put the r/3 port,partner in sender and XI
    port and partner in receiver it gives me error as "Port 'SAPCU6_100' does not exist in the table
    of port descriptions.
    Please help me.....
    Regards

    HI Saras,
    Please go through the below weblog which has all the stpes which is required for ur scenario...I think screen by screen help u to debug ur problem and it will help u to find out the msitake which u have made.
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Thnx
    Chirag

  • Test IDOC to File scenario

    Hey guys
    i m doing a IDOC to File scenario and am stuck at testing it.i went in we19 but dont know how should i test my scenario there.
    any idea how should i test my scenario
    thanx
    ahmad

    Hi Ahmad,
    IDOC to File
    R3 system.
    1. Create SM 59 RFC destination to XI,.
    2. We21 - Create port to XI.
    3. We 20 -- Maintain Partner Profile for the outbound Idoc.
    XI SLD
    1. Create technical system for R3 system
    2. Create Business System for the Client of the R3 system.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    These are the required steps for IDoc to File scenario...
    In R3 (i.e., your IDES system)...
    RFC dest to XI (sm59) - any name
    Logical system (bd54) - any name
    Port to XI (we21) - any name
    Partner profile for the logical system (we20) - use Logical system name created in bd54
    In XI...
    RFC dest to R3 (sm59) -
    Port to R3 (idx1) -
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3 with Logical system name as r3 sys.
    In we19
    and give in control record as
    Sender : Port ; Partner
    Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
    Regards..
    Ramesh.

  • Unable to Test Idoc to File scenario

    Hi All,
    I am doing Idoc to file scenario.But dont know how to test this scenario.
    I have done all the configuration in Backend and XIServer system.
    Please help me out.
    Thanks in Advance.
    Regards,
    Vikas

    HI
    Chech that these steps have been done
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    One these are done
    1) U can trigger the the IDOC by scheduled job in BD87 immediately after the       document is saved in R/3
    2) Using transactions like bd10 and bd12 u can trigger IDOC for master data
    3) While creating the partner profile there is a option “trigger immediately” . By enabling this option the idoc gets triggered.
    4) Using the transaction WE19 u can trigger the IDOC mannually
    Regards
    Santhosh

  • How to eliminate empty tags in out put XML file in IDOC to File scenario

    Hi Experts,
    I am doing IDOC to File scenario.
    My Out put XML is in to FTP is as below
    <ITEMS>
        <item>
              <A>asdf<A>
              <B>GHIJ<B>
        </item>
        <item>
              <A>123<A>
              <B>G098<B>
        </item>
    </ITEMS>
    <ITEMS/>   -
    > Means no data
    <ITEMS/> -
    > Means no data
    <ITEMS>
        <item>
              <A>yyy<A>
              <B>zzz<B>
        </item>
        <item>
              <A>arrr<A>
              <B>Ghhh<B>
        </item>
    </ITEMS>
    Now I want to eliminate tages <ITEMS/> in out out put XML file ( PIwhich writes in File server).
    1) Is there any setting in communication channel to do this
    2) Is there any settings in Mapping proram to suppress parent tag if child tags are not available.
    I want output as below .
    <ITEMS>
        <item>
              <A>asdf<A>
              <B>GHIJ<B>
        </item>
        <item>
              <A>123<A>
              <B>G098<B>
        </item>
    </ITEMS>
    <ITEMS>
        <item>
              <A>yyy<A>
              <B>zzz<B>
        </item>
        <item>
              <A>arrr<A>
              <B>Ghhh<B>
        </item>
    </ITEMS>
    Thanks,
    Subbu

    items->mapwithdefalut(just empty in the value)-> euqals(check with empty constant)->not->createif->target node
    and make sure that as Ravi kanth said ...occurance is  min is 0 at target side
    Regards,
    Prasad.
    Edited by: PRASAD KONDA on May 21, 2009 1:50 PM

  • Regarding remote login in IDOC to FILE Scenario

    Hi Friends,
          I have been struggling from this issue from many days.
    when i am doing IDOC to FILE Scenario, i was posting an CREMAS03 IDOC from ECC client 800 to SAP XI Client 001.
          After executing WE19 in SAP ECC, its automatically asking for XI login detals.
    will it really ask for login details.
      <b>Because if we do  FILE to IDOC Scenario, it wont ask for login details.</b>
        If i check RFC destination from XI to ECC, we could easily remote logon to ECC without asking for any logon  details, but if i check RFC destination from ECC to XI, <b>its asking for Lodin ID and Password</b>.
    Regards,
    Varun Reddy.K

    HI Varun
    Check the roles assigned to you.
    The roles are...SAP_XI_ADMINISTRATOR and SAP_XI_DEVELOPER.
    If u have created the user in SU01 just now..and checking logon to IB immediately ..it will not come cos it takes some time for the users to get reflected in JAVA stack.
    Cheers..
    Vasu
    <i><u>** Reward Points if found useful **</u></i>

  • Idoc 2 File Scenario

    Hi Experts,
      I am doing Idoc to file scenario (bypass).
      I got below error in sxmb_moni. Plz tell me what might be the proble?
    <b>Unable to convert the sender service BS1_SENDER to an ALE logical system</b>

    Hi Moorthy,
      I am explaining my total scenari here.....
      Its Bypass, Idoc to file.
      I am sending idoc-xml as it is to receiver as file-xml.
      I am not doing any IR objects.
      I have configured ID (RD, ID & RA) objects.
      I have used Idoc name(i.e Orders.Orders05) as Inbound & Outbound Interfaces.
      But in SXMB_MONI, the error was showing as
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Identification
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION"><b>NO_RECEIVER_CASE_ASYNC</b></SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack><b>No receiver could be determined</b></SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
      Please provide the solution.
      Thanks in advance.

  • Error in TRFC for IDoc to File scenario while sending IDoc

    Hi,
    Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
    Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
    When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
    For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
    Can anybody help me out in resoving the error?
    Regards,
    Suraj Kumar

    Hi,
    Thanks for your reply.
    It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
    Hope I am clear.
    Please let me know, if you need any further information.
    Regards,
    Suraj

  • IDOC to File Scenario. Acknowledgement help required

    Hi All,
    I have made a IDOC to file scenario  (IDOC has business system and file has business service) which is working fine.
    But In sxmb_moni of XI it says Acknowledgement not possible.
    "<SAP:Stack>Unable to convert the sender service File_Receiver_BusService to an ALE logical system</SAP:Stack>"
    Please explain me and send be blogs to send Acknowledgement back to R/3.
    Regards

    Hello Rick,
    "<SAP:Stack>Unable to convert the sender service File_Receiver_BusService to an ALE logical system</SAP:Stack>"
    Check the Logical system name in SLD and in ID's Service->AdapterSpecific Identifies matches are not, go through the following link for step by step prcedure.
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
    Check this for providing Acknowledgments.
    https://wiki.sdn.sap.com/wiki/display/ABAP/HandlingIdocAcknowledgements
    Regards,
    Prasanna

  • IDOC to File Scenario - Configuration steps need to be done in R3 and XI

    Hi Experts,
    I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
    Thanks in advance.
    Regards,
    Sree

    Hi Sree,
    I thought 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
    Also have a look at these forum threads...
    IDOC TO FILE SCENARIO
    idoc to file scenario
    I hope this answers your query.
    Regards,
    Abhy Thomas

  • Setup for IDoc-XI-File scenario

    Hi All,
       Please provide info where can I find, step by step  documentation for the basic setup on R/3 and XI areas, before start developing IDoc-XI-File or File-XI-IDoc scenarios.
    Thank you,
    Sree

    Hi,
    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:
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    File -> IDOC ->
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    (It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
    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 I have answered your query.
    Regards,
    Abhy
    PS: AWARD POINTS FOR HELPFUL ANSWERS.

Maybe you are looking for

  • Errors and Queries regarding manually create database in oracle 9i

    Create database manually with following steps: 1) Create SID C:\> set ORACLE_SID=mynewdb 2)Create suitable database directories within oracle directory. Create folders udump,cdump,bdump within C:\oracle\admin\mynewdb\ 3)Create PFILE 4)Create a passwo

  • ITunes sound crack / Pop when changing song

    Hello I'm having iTunes Crack / Pop everytime i change a song. It doesn't occur with Windows Media player. I'm using Windows 7 x64 Soundcard: ASUS XONAR D2X anyone got idea on how to remove the crack / pop everytime i change song?

  • A question mark folder appears on the start up after the sound ... with white back ground

    im using macbook pro 11in ... i had recently ungraded to os x lion through app store .... i was working on my laptop with firefox open .. i closed my macbook just as i normally do to make it go to sleep (not shutdown) ... i went hope i opend it and i

  • System restarting by its self?????

    hi there , specs are psu hyena 350w , 3.3v-28a ,5v-35a ,12v-16a km4m-v mobo amd athlon xp 2800+ 80g samsung ata hdd btc 16x dvd burner cyberdrv 52-24-52 cd burner lcd temp display thermaltake hsf northbridge fan win 98se nortons internet security tem

  • How to add ANY class to my project?

    Greetings. I am begining my adventure with java. Now I am wasting 2 days because i can't add class to my program. I would like to use floating-point numbers so I've found MathFP.class on the Internet. But I've no idea how to link this class with my p