Help in IDoc to File scenario

Hi experts,
I just created a scenario to export IDoc to File on a FTP server through XI server. I think I configured all the necessary things, such as in SLD, in sender(ECC) and receiver (XI server), and in IR, ID. But although it sends IDoc to Port OK in sender system, in the receiver system, I cannot see anything. Pls help to find out something I missed.
Thanks in advance

HI,
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 – 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 name.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Troubleshooting File-to-IDOC Scenario in XI.                    
Troubleshooting  File-to-IDOC Scenario in XI.                    
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098                                             
Thanks,
Madhu

Similar Messages

  • Regarding IDOC 2 FILE Scenario

    Hi Friends,
                    please help on IDOC 2 File Scenario. I have done tha ALE settings in R3 system and the Idoc has been  generated out of r3 system. but how it wiil be sent to XI server can any body help me on this issue.make it as quick as possible.

    Hi,
    Goto We02 and take the IDOC number froom there.
    goto WE19, give the copied idoc number and click on execute.
    Check for Control records for that IDOC and say outbound processing
    ALE Settings
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    Check this for posting the IDOC From R/3 to XI
    /people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /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/wiki?path=/display/xi/sapR3%28Idocs%29ToXI+--
    StepsSummarized&
    Regards
    Seshagiri

  • Unable to do IDoc to File Scenario ; Please help me....

    Hi Experts!!!,
                     I am trying to convert an IDoc to an .Txt or .Xml file, But I am un able to do it. Whenever I m trying to configure the Idoc adapter , it's not allowing me to select as "sender" (default it will be on the recvr side). Please help me in this regard. 
    Do I need to use RFC adapet, or BAPI instead of IDoc or any other way..to complete IDoc to File scenario...
    THANKS IN ADVANCE!!!
    Sunil K Shetty.

    HI,
    No need to use Sender Idoc adapter , default , IDoc adapter resides on Integration Engine. No sender communication channel and sender agreement also
    see the below links
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    Idoc settings https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    Regards
    Chilla

  • 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

  • Error/Doubts in Idoc-XI-File scenario

    Dear All,
    I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
    For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
    Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
    Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
    In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
    Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
    Can anybody guide if I have followed the correct steps & where I am doing the error.
    Warm Regards,
    N.Jain

    Hi ,
    Plese refer the following blogs ,
    IDoc to File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    You have to do all this settings mentioned in the docuemnt:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    Also can you check this weblogs on the same:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Thanks ,
    Suvarna
    Award pts if  it helps .

  • How to suppress the Acknowledgement  Error in IDOC to File scenario?

    Hi -
    I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
    I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
    i tried that option but i still get the 'Acknowledgement not possible' error.
    Is there any other way to suppress this error?
    Thanks,
    Tirumal

    Hi Tirumal,
    Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
    This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
    Also go through these documents for any further help:
    http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    Regards,
    abhy

  • IDOC to file scenario

    Hi Experts,
    In IDOC to file scenario i did in this way.
    1)created logical system.
    2)Using SALE tcode I assign logical system to client ,created RFC destination,Port and Partner's profile.
    It is showing all the thing correct.
    3) In XI system , I configured using IDX1 and IDX2.
    Then I created the material and checked the status which is green in we05.
    But in tcode IDX5, the material is not coming.
    Here I am confused that why data is not coming to XI system.
    can anyone help me?
    Thanks
    Rabi

    Hi,
    The Following are the Possible checks
    1) Check in R/3 side SMQ1 & SMQ2
    2) Check in R/3 side SM58
       In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
       If the entry is available then select it and press F6, to push it manually.
        This happens normally if IDOC stuck up in queues.
    3) Check in PI SMQ2 and IDX5
    regards,
    ganesh.

  • Why we dont need sender agreement and comm channel in IDOC to file scenario

    Hi,
    there are 2 queries:
    first query :
    Scenario is "Idoc to file transfer"
    why we dont need sender agreement and communication channel for IDOC to file ,while we do need
    both of these for "File to RFC "
    Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
    Then why For "IDOC to file" we dont need that.
    Second query:
    Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
    between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
    and getting data from RFC back to File2.
    Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
    Regards,
    Mayank
    Edited by: mayank verdia on Jan 13, 2009 11:49 AM
    Edited by: mayank verdia on Jan 13, 2009 11:50 AM

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • Error in IDoc to file scenario

    Hi Experts,
    I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
      <?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>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
      <SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Please suggest me in this issue.
    Thanks,
    Bhuvan.

    Check this link:
    http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
    You might want to refer to the SAP NOTE: 316877
    Regards,
    Ravi

  • Problem in idoc to file scenario

    hi
    while creating the idoc to file scenario i am facing few problems.
    1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
    2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
    3) i am using my ecc6 training server as my sender and using my XI server as receiver.
    4) i am sending idoc from ecc6 and converting it  to file in XI server and saving it in XI server itself(my receiver in this case).
    my error:
    i send my idoc from we19 transaction, and i see a error message stating
    that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
    my doubts.
    1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
    2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
    3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
    kindly help me with this issue.
    regards
    manoharan

    >
    manoj murugesan wrote:
    > 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
    >
    > 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
    >
    > 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
    >
    >
    > kindly help me with this issue.
    >
    >
    > regards
    > manoharan
    and to 1 & 2 ref. below,
    Configuration steps required for posting idoc's(XI) -
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    ALE configuration for pushing idocs from SAP to XI -
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

  • Issues in IDOC to File scenario using bussiness service

    Hi Team
    I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent).  The setting which have done on SAP side are as below
    SAP SIDE CONFIGURATIONS
    1. Created RFC destination : RFC_XI_SYSTEM
    2. Created port : PORT_TEST
    3. created logical system: IDOC2FILE
    4. created partner profiles: IDOC2FILE
    XI side configurations
    1. Created RFC destination: RFC_SAP_SYSTEM
    2. Created port : by using IDX1 t-code
    DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
    3. metadata: by using idx2.
    DOUBT: here it is asking for IDOC type and source port,  i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know,  please find the SAP and XI system details below and suggest accordingly.
    SAP system details
    Client: 800
    User name: sapuser
    system id: DEV
    system number:10
    XI system details
    Client:100
    username:xisuper
    system id: SXI
    system numebr: 00
    I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
    Thanks in advance.
    Raju

    To complete your scenario successfully with better understanding of Idoc adapter
    read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
    for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

  • Alerts when the acknowledgement fails in IDOC to File Scenario

    Hi All,
    could you let me know how to handle Alerts for Idoc to File scenario.
    My Scenario uses BPM as well.
    Thanks,
    Srini

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

    Hi All,
    I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an error
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>FILE_BC</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are  getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
    Thanks,
    Geetha

    Thanks everybody! It has got fixed. I just requested No acknowledgements.
    Geetha
    Edited by: Geetha on Nov 11, 2009 5:45 PM

  • Idoc to file scenario error

    Hell Experts,
    I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
    Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But  I didn't get successful results, always the error message shows in SXMB_MONI as follows:
    Ackn Status  contains system error
    During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
    tion in Message-Mapping transformatio~
    Exception of class CX_XMS_SYSERR_MAPPING
    My system Patche level as follows:
    SAP_BASIS     640        0012        SAPKB64012
    SAP_ABA     640     0012                SAPKA64012
    PI_BASIS     2004_1_640 0009        SAPKIPYI69
    SAP_BW     350     0009                SAPKW35009
    The above error is related to patches problems or any Mapping  problems ?
    Please  help me.
    Advanced Thanks.
    Regards,
    Chandra

    Hi,
      This may be a mapping issue, try this:
    a)in interface mapping see if grids are formed at source and target after executing the test option,
    b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
    i am not sure of the patch levels.
    Regards,
    Anirban.

  • IDoc-to-File scenario with external Partner ... PCK necessary?

    Hi all,
    I have a question concerning to a IDoc-to-File Scenario with an external Partner. Here is a short Description of the Scenario:
    The SAP ERP System creates an IDoc which should be send to the SAP Integration Server. The Integration Server respectively the IDoc-Adapter transform the IDoc in IDoc-XML. The Integration Server executes a Mapping and so on. In the final step the Integration Server should send the XML-File to a FTP Server in New York (external Partner) with the File/FTP-Adapter.
    Have I to install the Partner Connectivity Kit at a Server in New York or is it working without the PCK? Which are my possibilities?
    Thanks for your help
    with kind regards
    Christopher

    Hello,
    If the FTP server has connectivity to XI and if the
    port is open XI can directly do the FTP using File
    Adapter.
    Thanks,
    Himadri
    Hi,
    thanks for your quick answer.
    What means "connectivity to XI"? Our SAP-Environment is in Germany and the FTP-Server is in New York. Is it enough to open the port in the firewall?
    Thanks for your answer
    Christopher Kühn

Maybe you are looking for