Needed urgent clarification on FILE TO IDOC scenario

Hi Experts,
                  I need urgent clarification on FILE TO IDOC scenario plz clarify it
1.In FILE TO IDOC scenario after creation of RFC dest ,performing steps in IDX1&IDX2
what configurations to be done on target system?
2.In some blogs it is given that steps should be done in RFC dest,we21,we20  .
But is it mandatory to do so RFC dest and WE21 steps [OR] directly can we configure partner profile in WE20?
3.on integ server IDX2 has to be done (or) is it optional for FILE TO IDOC scenario?
Too many to answer plz clarify good explanations will be rewarded.
                                                                                Regards,
                                                                                Vinod.

Hi,
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
DO let me know if you need more information
Thanks and Regards,
Chirag Gohil.

Similar Messages

  • Lookup issue for File to Idoc scenario-- Urgent Pls.

    Hi All,
    Iam doing File to IDoc scenario with one file --> any of 3 R/3 systems.
    Routing has to be done dynamically using a lookup file, based on the incoming GLN code and last character of the Order Reference number.
    The last character of the Order ref Num will have A,B or C.
    Where,  ' A'  for  R/3 152 Client
                 ' B' for  R/3 142 Client
                 'C'  for  R/3  132 Client.
    1. PlantGLN_Routing lookup file :
    DestinationSystem,   Plant GLNCode,       Partner Number,  
    A,                            5000243000473,         GDKDVRC152,     
    B,                            5000243000473,         GDKDVRC142,      
    C,                            5000243000473,         GDKDVRC132,      
    A                                 500034000487           GDKDVRC152,     
    B                                 500034000487           GDKDVRC142,     
    C                                 500034000487           GDKDVRC132,
    By Using DestinationSystem and Plant GLN Code as lookup key --> I need to get the value of partner system.
    2.  IdocCtrlLookup
    Purpose: To read the IdocCtrlLookup file to populate the Idoc control segment
    Now based on the partner system from previous table --> I need to get the details of Sender Port , Sender Partner Type , Sender Partner Function , Sender Partner Number , Rx Port , Rx Partner Type , Rx Partner Function , Rx Partner Number.
    Please help me how can acheive this scenario with the help of lookups.
    Its very urgent.
    Regards
    Krupakar.

    HI,
    Here you would have to use one mapping for dynamic routing , based on this create IM and use it in receiver determination.
    the another mapping is general to file to idoc.
    see the dynamic routing link here
    Dynamic Configuration of Some Communication Channel Parameters using Message Mapping -
    /people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
    Also if you know the field name the context object can be defined for partner no that can be used in receiver determination in condition. to particular partner no in receiver determination.
    Regards
    Chilla

  • For  file to IDOC scenario, do i need to make a partner profile in XI  ?

    for a file--->XI--->IDOC scenario, do i need to make a partner profile in XI(for the R/3 system which is going to receive the IDOC),
    or only a port maintenance in idx1 will do.....

    hi Sudheer,
    yes u need to maintain partner profile in R/3
    Check below link in WIKi for complete File to IDOC
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
    Sachin

  • File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

    Hi All,
    I am doing File to IDoc scenario( Bypass) for Orders05.
    File is picking succesfully and not posting the idoc in the SAP..
    My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
    but the error it is showing is <b>" Obligatory node 'E1EDK01' missing in the structure ORDERS05 "</b>
    Please suggest me ASAP what is going wrong .
    Thanks in Advance.
    Regards
    Seema.

    The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
    This is how it should look, ( check the parts in bold),
    <?xml version="1.0"?>
    <ORDERS05>
    <IDOC <b>BEGIN ="1"</b>>
    <EDI_DC40 SEGMENT="EDI_DC40">
    <DOCNUM>1</DOCNUM>
    <DIRECT>2</DIRECT>
    <IDOCTYP>ORDERS05</IDOCTYP>
    <CIMTYP></CIMTYP>
    <MESTYP>ORDERS</MESTYP>
    <SNDPOR>XXXXXXXXX</SNDPOR>
    <SNDPRT>LS</SNDPRT>
    <SNDPFC></SNDPFC>
    <SNDPRN>XXXXXXXX</SNDPRN>
    <RCVPOR>XXXXXX</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPFC></RCVPFC>
    <RCVPRN>XXXXXXXX</RCVPRN>
    <CREDAT>20070511</CREDAT>
    <CRETIM>152803</CRETIM>
    </EDI_DC40>
    <E1EDK01 <b>SEGMENT = "1"</b>><BELNR>AAAAAAAAA123</BELNR>
    </E1EDK01<b>SEGMENT = "1"</b>>
    <E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
    </E1EDKA1>
    <E1EDKA1 <b>SEGMENT = "1"</b>><PARVW>LF</PARVW>
    <NAME1>international</NAME1>
    <NAME2>Delhi</NAME2>
    <ILNNR>2121211545</ILNNR>
    </E1EDKA1><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>002</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDP01><POSEX>45</POSEX>
    <E1EDP19 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <IDTNR>00000000002150059</IDTNR>
    <KTEXT>Reddy</KTEXT>
    </E1EDP19><E1EDP19>
    <QUALF>003</QUALF>
    <IDTNR>5484218521214</IDTNR>
    </E1EDP19></E1EDP01>
    </IDOC></ORDERS05>
    Regards
    Bhavesh
    PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

  • Exception handling in File to IDoc Scenario

    Hi,
    I have successfully configured File to IDoc Scenario. Now I want to include some exception handling which should be capable of create a mail to recipient when a mapping error occurs.
    Can anybody help me out?
    Regards,
    Suraj Kumar

    Hi Suraj,
    A few points while creating ALERTS.
    <b>TESTING YOUR ALERT CONFIGURATIOn</b>
    go to <b>se37 --></b> and <b>execute the report RSALERTTEST</b>. GIve your ALERT CATEGORY in this report. If your ALERTS are configured properly, then your Alert would be triggered and you can see the entry in ALERT INBBOX.
    <b>ALERT RULE</b>
    Make sure that in your Alert Rule, <b>the option Suppress Multiple Alerts of this rule has not been seelcted</b>.
    Finally, if you are on SP14 and above check this note <b>913858</b> for alerts.
    If you are below Sp14, then this blog can help you set the background processes needed.
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
    No BPMis needed to trigger alerts in either case.
    Do get back for any clarifications,
    Regards,
    Bhavesh

  • About FILE to IDOC scenario

    Hi Experts,
    i need some help for doing file to idoc scenario.
    1. what are the configurations we must do while doing this scenario?
    2. How to communicate with Legacy system to sap system?
    3. How to create the business and logical systems for SAP systems in SLD?
    4. How to define parameters in communcation in ID?
    5. what work shold be done using SM59 and WE20? and specify the steps please?
    6. finally if u having word file please send from the creation of logical system for sap system?
    thanx.

    Go thru below mentioned links.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34
    once you go thru them you will find answers for questions.
    thanks,
    Venkat

  • File to IDOC scenario-no messages in SXMB_MONI

    Hi all,
       I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
    I am doing a File to IDOC scenario through XI mapping.
    I am not getting any messages in SXMB_MONI.
    When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
    Please help.
    My scenario goes like this:
    Sender : Business service(Some file location)
    Used File adapter for sender communication channnel.
    Receiver : Business system(SAP R/3)
    Used IDOC Adapter for receiver communication channel.
    One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
    Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

    Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
    An inbound partner profile could not be found with the following key:
    /LSDEMO/LS//DEBMAS////
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    I already manitained following data and there is one record in EDP21.
    SNDPRN  = LSDEMO  
    SNDPRT  = LS
    SNDPFC = LS
    MESTYP   =  DEBMAS
    MESCOD = space
    MESFCT = space
    TEST = space
    EVCODE   = DEBM
    SYNCHK = X
    METHOD = space
    USRTYP = space
    USRLNG = space
    INMOD = space
    DCART = space
    And please let me know whether I have to maintain outbound parameters  also for my partner in XI system.I didn't see any difference even I maintained it.
    And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
    Edited by: Jaya on Feb 26, 2010 10:17 AM
    Edited by: Jaya on Feb 26, 2010 10:27 AM

  • Reg:file to idoc scenario

    In a file-xi-idoc scenario i created a business service for legacy
    system and a business system for R/3 receiver system
    i didn't assign logical system for the sender business service
    and assigned a logical system for the reciver business system
    so while maintaining partner profile in the R/3 system
    i have to give partner no:
                        partner type:
    here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
    so then what do i need to give in the above two fields?
    answers required briefly

    Hello,
    you know this pdf:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
    Could be helpful.
    Regards
    Patrick

  • Alert Configuration for File to IDoc scenario

    I have followed Alerts : Step-by-Step /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    and configured Alerts for file to IDoc scenario.
    But the problem is, I did not notice any alerts being generated. I could notice the IDocs being posted to destination system. So I was going through Alerts-Troubleshoute Guide. In intension to maintain monitoring level, I clicked Configuration tab. But I did not notice my sender and receiver system there to maintain.
    Can any body help me to detail out the procedure to add sender and receiver systems to maintain the monitoring level?
    Regards,
    Suraj Kumar

    hi Suraj,
    WHich SP version are you on??
    If you are on Sp14 or above, then unfortunately, Michal's Trouble Shooting for Alerts will not help.
    From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note <b>870232</b> for this info.
    Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
    If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
    Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
    If this is working fine, then the last step, implement the note 913858.
    Regards,
    Bhavesh

  • Regarding RFC connection in File to IDOC Scenario

    Hi everyone,
               I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. <i>But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. </i><b>Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario</b>
         <b>!!! Note:  RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!</b>
    Regards,
    Varun Reddy.K

    Hi Varun
    Follow these steps
    First - Maintain the Sender R/3 System:
    SM59 : Create a RFC destination to XI
    WE21 : Create a TRFC Port ->Specify the RFC Destination Created
    BD54 : Create a Logical System for the Idoc Receiver
    WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
    Second - Log on to XI System:
    SM59 : RFC Destination for Sender System
    IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
    IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
    Regards,
    Santosh

  • Receive acknowledgement in file-to-idoc scenario

    Hello!
    I'm using guide "How to handle acknowledgement for IDOC", and for the first time I want to see an acknowledgement status in sxmb_moni.
    I have passed all steps:
    In CRM I have logical system P1DFILE, this is the system that sends an idoc to CRM.
    Also, I have logical system C2DCLNT100 - this is CRM system.
    First, I go to BD64, create new model view XI_CRM. Then, add message type:
    Sender system - C2DCLNT100
    Receiver system - P1DFILE
    Message type - ALEAUD.
    Then I create RFC destination P1D_001 to my PI server.
    Then I create port SAPP1D using WE21
    Then I go to WE20, choose my Logical System - P1DFILE. I already have the inbound message types (CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M). I add new outbound message - ALEAUD with receiver port SAPP1D.
    Then I go to RBDSTATE, create variant SAP_AUDIT_SEND and enter:
    Confirmation to system: P1DFILE
    Message type: CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M
    Then, in SM36 I shedule SAP_AUDIT_SEND as a hourly job (does this mean, that I will receive confirmations only every hour?)
    So, what should I do to see ack in sxmb_moni?

    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.

  • Steps required in File to Idoc Scenario

    Hey guys i m doin a file to Idoc scenario and just wanna make sure my steps r correct.
    steps done on the XI server
    1.Create RFC destination(test the destination by giving the target host as the R/3 server).
    2.Create port for the RFC destination.
    steps on the R/3 side
    1.Create/verify logical system name.
    and finally create business system for this logical system in SLD.
    now do i need to do partner profile as well or not? and if i have to do it how is it accomplished.
    thanx
    ahmad

    Hi,
    The following are needed for idoc to file scenario...
    In R3...
    RFC dest to XI (sm59)
    Logical system (bd54)
    Port to XI (we21)
    Partner profile for the logical system (we20)
    In XI...
    RFC dest to R3 (sm59)
    Port to R3 (idx1)
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3.
    Regards,
    Uma

  • Where to define third party logical system name in file to idoc scenario

    Hi Friends,
      I am shalini shah.
    I have one doubt, where I can define the logical system name in File to Idoc scenario.
    I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
    In SALE or any where.
    Please give me solution.
    Warm Regards,
    Shalini Shah

    Hi Shalini,
    You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
    Just refer the below link for configurations with step by step solution.
    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

  • System Level Acknowledgement in File to IDOC Scenario

    Hi All,
    I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI  should send a acknowlement file back to the sender system.
    Could someone suggest how to design this scenario?
    Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

    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.

  • Doubt in file 2 idoc scenario

    hi,
    I am trying to execute to file 2 idoc scenario.
    I created DT,MT for XML file outbound system.
    After importing idoc
    how can i create DT, MT for idoc to connect oubound DT,MT (file side)?
    I am following this wiki guide
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

    hi Raj,
    It means in Idoc, for each field Mesage type, data type are defined, no need to create to once again here in XI.
    plz if i understood wrongly means correct me.
    ONE MORE THING
    i imported cremas04 idoc,
    in that EDI_DC40 contains control record
    E1LFA1M contain data record
    is it correct?

Maybe you are looking for

  • Is it ok to put MBP on overnight charging?

    hi... pls guide me is it ok if i put my MBP on charging for whole night? after reaching 100% & getting green light on plug. will it damage the battery in any way.. pls guide me. thanks

  • Temporary files generated by Headstart (?!)

    Hi everyone, I am working at a certain company which uses Designer 2.1.2 with Headstart. We have had certain complaints from users whose harddrives were full. In their TEMP directory there are dozens of files starting with dat, idx or s. Some of thes

  • How to avoid the Amount and Date values for VOID Cheques

    Hi All, I had created a two window i.e For Amount and Date. If I process the cheque the Amount value and Date should not trigger for VOID CHEQUES. Can any one tel me how to avoid the Amount and Date values for VOID Cheques Your help will be greatly a

  • Individual inventory is failing

    Hello, When running the daily inventory as usual everything is working fine. When I try to run the inventory manually through the Action > Hardware Inventory I am getting an error in the Application Log: Event Type: Error Event Source: SmsAdminUI Eve

  • Création commande true/false d'un bouton stop ?

    Bonjour, Etant en train de réaliser un programme, je voudrais savoir comment créer une commande TRUE/FALSE (TF) à l'aide d'un bouton STOP. Sachant qu'il m'ai impossible de supprimer le bouton STOP déjà existant. Merci d'avance. Cordialement.