RFC and XI

Hi everybody,
I would like to know how can I call a RFC function, that is defined in SAP XI  System from R/3. Can you provide me any information about how RFC function works with XI and how can I call them from R/3?
Many thanks!
Reyes

Hi,
you need to download RFC signature from R3 (from xi repository)
then you need to fill RFC values in your mapping
and then use RFC receiver adapter that will call it inside R3
that's all
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • What is the diffrence between BAPI and RFC and business object

    Hi Experts,
    Can anybody tel me what is the diffrence between RFC and BAPI , and also what is ther relation with business object?
    Thanx in advance.
    Nilesh Hiwale

    Hi,
    BAPI's are associated with Business Objects and also they are RFC enabled.
    But RFC's are the FM's which can be called from external systems, those FM's can be used in many places based on the applications..
    Check these Links
    whats the difference between BAPI and RFC??
    Diff. Between BAPI and RFC
    Regards
    Kiran

  • Monitoring of remote system's Transactional RFC and Queued RFC

    Hello,
    In our production system, in rz20- CCMS monitor templates- Communication-Transactional RFC and Queued RFc- outbound queues- Queues otherwise not monitored we can see blocked queues for each client.
    System is connected to solution manager and we wish the central auto reaction is implemented in solution manager
    However i am unable to find Transactional RFC and Queued RFC for the remote system, they exist only for solution manager itself
    Tell me how can i do the central monitoring

    Hello,
    First you need to check with your Landscape in solman in order to monitor any kind of activities to do so pls follow these steps.
    Go to SMSY in solman under Landscape components>Product systemsselect you satellite system example SAP ECC.
    On the main screen you will find client for which you have generated RFC connection. Please check though connection are working fine, Go to edit mode and try to click on generate button there will be a pop-up, which gives a clear picture of RFC connection which already exists, and you can also re-generate this RFC connection by clean it up when you re-generate pls select under Actions after generation assign RFC dest for system monitoring.
    But make sure there is no project impact on this RFC, like they are not using any logical components and already have some projects running on this RFC connection.
    I would advise you to first you the option of assign and check RFC button which is next to generate icon.
    Regards
    JUDE

  • File to RFC, and through RFC response i am trying to trigger the Mail adapt

    Hi All,
    Right now i am doing File to RFC, its working fine but now the requirement is when xi connect to ftp and picks the  file need to send one success mail after the file pickup and data sent to BW system again i need to send one mail and also error alerts to inbox.
    Till now i am not using BPM, can we do this without BPM pls let me know
    now i am trying to achieve this in File to RFC, and through RFC response i am trying to trigger the Mail adapter.
    or else  i need use only BPM pls share  the steps which i need to be configure.
    Am i correct or pls suggest me some idea to achive this and also pls share some smaple ones in BPM .
    Thanks in advance
    Venkat

    With BPm, follow this:
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    Instead of receiving the response in file, use mail adapter
    Regards,
    Prateek

  • RFC and Logical System names

    Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

    Hi Gaurav,
    It is recommended, but not mandatory, right, Muthuraman?
    The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
    Regards,

  • How to enable RFC and how to use it in Report..please tell its very urgent

    Dear Techie's,
    Please tell its very urgent..
    How to enable RFC and how to use it in Report. ??
    Virendra

    hi,
    pls chk any of these links.
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    rgds
    Anver

  • Exception handling in rfcs and bapis

    exception handling in rfcs and bapis

    Hi Jayakrishna,
    In General , there are non execptions in BAPIs, because of the reason, that the exception raised in a SAP envoronment may not mean anything for a non SAP initiator. All the exception situations would only fill the return table(TYpe BAPIRET2 or something like that). If you read that table after the call to the bapi, you can understand what has gone wrong.
    Regards,
    Ravi

  • Can we open a URL link from an RFC and access the data in the link.?

    Can we open a URL link from an RFC and access the data in the link.
    I have the following scenario.
    I have a URL link and it opens a KM folder in the Portal server and I need to put a PDF file in that KM folder
    Can we do that with the help of an RFC, can we deal with Links in RFC, is there any such FM??
    Regards

    >
    SAP LEARNER wrote:
    > Can we open a URL link from an RFC and access the data in the link.
    >
    > I have the following scenario.
    >
    > I have a URL link and it opens a KM folder in the Portal server and I need to put a PDF file in that KM folder
    >
    > Can we do that with the help of an RFC, can we deal with Links in RFC, is there any such FM??
    >
    > Regards
    I guess you are trying to connect from the R3/ECC to the Portal Server.
    Are these two systems in the same network? Do you have usernames (valid and fully authorized) in both systems? What is the OS on which these two systems are housed?
    Please provide these details to proceed further.
    Regards
    Sabu

  • What is adaptive RFC and How to Use it

    hi friends
    what is the adaptive RFC
    what is the use of it
    how we can use it
    explain me anyone
    and send pdf also
    thanks
    ramu.

    Hi,
    To give u a brief idea.
    rfcs are used to call data from the backend that is R/3.We use the Bapis from the R/3 system which have some pre defined functionality and data is populated in the correspoding ui elements in webdynpro interface.earlier Rfcs were used but now we have adaptive rfcs in which
    if there are changes in the backend(R/3 system) such as changes in the datatype,structures,fields would be automatically be refllected in the rfcs and there would be no errors in web dyn pro even if there is  a change in the back end
    to be more specific folow this link
    http://help.sap.com/saphelp_nw70/helpdata/EN/41/38bc8f813719488ddc9d9b21251ec3/frameset.htm
    and try out this application
    to use the rfcs firstly check out this document for configurations
    Important Configurations for Calling ABAP Function from Java Web Dynpro Application
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07753b9-fa0c-2a10-64a8-c6754c45396e
    heres the application.
    Creating a Web Dynpro Application Accessing ABAP Functions
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/355b9c90-0201-0010-d2a8-89fece426526
    regards
    Nikhil Tapkir

  • RFC AND BAPI

    Hi,
    Difference b/w the BAPI and RFC.

    Dear Bhagavan,
    Go through the following threads
    BAPI and RFC
    What is the difference between RFC and BAPI?.
    RFC AND BAPI
    BAPI& RFC
    Best Regards,
    Srikanth
    Reward the useful answers and you will get
    ONEPOINTyourself

  • RFC and SSO Configuration

    Hi guys,
    Is it possible to configure RFC and OSS connection between to sap systems that  they are not on the same domain?
    Thanks

    Hi Reza,
    I believe it should work. Pls check this also;
    http://help.sap.com/saphelp_nw04/helpdata/en/b8/9ba340fa432b54e10000000a1550b0/content.htm
    Thanks and Regards,
    Shyam.

  • Differences between rfc and ale/idoc.

    hi ..
           will u please send the differences between rfc and ale/idoc's.

    Hi,
    Please reward with points if helpful................
    ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
    For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
    Means of creating and operating distributed applications.
    The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
    Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
    Application Link Enabling comprises the following three layers:
    application services
    distribution services
    communication services
    Two Development Models
         Distribution using BAPIs
         Distribution using Message type
    The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
    Defining message types and IDoc types:
    If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
    The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
    Writing ABAP code:
             Outbound Processing
               Inbound Processing
    You can find information on other ALE functions under:
                                   Master Data Distribution
                                  Communicating with Non-R/3 Systems
    1. The Remote Function Call facility allows you to call an R/3 Function module on a “remote” machine.
    2.  To communicate between two R/3 Systems and also with an External System.  External Application program also can call these function module for integration.
    3. RFC or sRFC  - Synchronous RFC
                     aRFC - Asynchronous RFC
                      tRFC - Transactional RFC
                      qRFC - Queued RFC (I.e. Serialization of tRFC)
    Types of RFC Call
    Synchronous
    CALL FUNCTION Func Destination Dest
    CALL FUNCTION func DESTINATION 'NONE' ...
    CALL FUNCTION func DESTINATION ’BACK' ...
    Asynchronous
    CALL FUNCTION func … STARTING NEW TASK taskname
    PERFORMING form ON END OF TASK
    RECEIVE RESULTS FROM FUNCTION func
    Thanks
    sivaparvathi

  • RFC and CURP for Mexican vendors

    Hello, I would appreciate you can provide any comments  about Master data for Mexican customers/vendors.
    In Mexico companies and organizations have a Tax registration number called RFC which is ABC680504BV1 which contains 12 length characters
    The field for storing this information in SAP master vendor record is in field TAX NUMBER 1. Table-field: LFA1-STCD1
    However in Mexico the natural persons, independent professional persons, have a Tax registration record called CURP which is 13 length characters. Example PIIG720116BV1
    If I try to store the CURP in the field TAX NUMBER 1. Table-field: LFA1-STCD1 from the SAP master vendor I get and error message.
    In fact the recommendation of SAP is to store the CURP in the field called TAX NUMBER. Table-field: LFA1-STENR and to check the box NATURAL PERSON 
    However in most of the reports the field TAX NUMBER is not available for displaying information. I am thinking to store the RFC and CURP in the field called VAT Registration number which is available in most of the reports and there is not any check in this field.
    I would appreciate if somebody can provide any comments
    Thanks

    Hi,
         The CURP should be entered in Tax Number 3   (STCD3).
    Tax Number 3
    Specifies the tax number.
    Use
    Enter the tax number that applies:
    Country Tax number
    Argentina Withholding agent number
    Brazil State tax number
    Bulgaria Social security number
    Mexico CURP number
    Netherlands Tax registration number (Loonbelastingnummer) of the chain-liability vendor
    Russia KPP number
    Ukraine VAT registration number
    Kind regards

  • About RFC and BAPI

    Hello Masters,
                 What Makes the exact difference between RFC and BAPIs. Both can perfom same thing. BAPI uses the RFCs only. Then how can it justify?
    Thank you

    RFC:
    RFC --- > Function module and general will be used to make call to function
    sending the function (XI has RFC adapter)
    BAPI:
    BAPI ---> Other version of RFC (Objected oriented) mostly we will use for Sync
    calls (Mostly in XI using proxies we will call BAPI's)
    Refer these links for more details:
    http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
    http://www.sap-img.com/fu033.htm
    BAPI Vs IDOC - in detail
    http://searchsap.techtarget.com/tip/1,289483,sid21_gci824860,00.html
    /thread/127699 [original link is broken]
    IDOC,RFC,BAPI
    Re: When and Why we use BAPI, RFC and IDOC.. in XI
    Diff... between  ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify
    idoc and bapi
    Difference among  IDOCS,BAPI,RFC?
    http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
    Differences Between RFC & BAPIS
    RFC Vs BAPI
    For more details:
    refer this thread.
    What are idocs, BAPI, RFC?
    BAPI is nothing but the Business process programing interface which are standard and stable and these are store in the business object repository.
    Standardized programming interface that enables external applications to access business processes and data in an SAP System
    RFC is the remote function call which is used to call the function remotely which may be in same system or ather system
    its also used communication between SAP systems , between SAP systems ,external systems.
    idoc and bapi
    Difference among  IDOCS,BAPI,RFC?
    http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
    Differences Between RFC & BAPIS
    RFC Vs BAPI
    http://www.sap-img.com/abap/ale-bapi.htm
    RFC means remote function call,
    these are the function modules which can help u to access across the sap and from sap to third party front end,
    BAPI means Business application programing interface which is the RFC enable function module and uses in OOPS concept.
    RFC ,IDoc and BAPI
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
    This is a short description of BAPI and RFC
    BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
    RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.

  • What is RFC and IDOC Adapters in XI  ?

    Hi,
    What is the RFC and IDOC Adapters in XI , in which scenarios we use this adapter , what is the advantages and disadvantages of RFC , IDOC ? can any help me out.
    Thanks & Regards
    Surendra M

    Surendra,
    <b>What is the RFC and IDOC Adapters in XI</b> :
    <b>IDOC:</b> Generaly standard IDOCs are used to update the data in R/3 or to extarct the data from R/3.
    <b>RFC:</b> Are generally used for synchronoue scenarios.
    <b>in which scenarios we use this adapter</b>
    For example you can use the IDOC <b>ORDERS05</b> to post the sales orders.
    Similarly you can use <b>BAPI_COMPANY_GETDETAILS</b> to fetch the company details.
    <b>what is the advantages and disadvantages of RFC , IDOC ?</b>
    <b>Advantages:</b> Both can be used for data retrival and posting. RFC can be used for synchronus purpose but IDOCs are always asynchronous.
    <b>Disadvangages:</b> If you are using custome made RFC/IDOC then you have to import the RFC/IDOC into XI every time when you make any small changes in the structure.
    Also go through this blog to choose the right adapter to integrate with SAP systems.
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    Regards,
    Sarvesh

  • Regarding rfc and idoc sender

    hi
       can any one provide me with some scenarios having
    idoc and rfc as senders.

    Hi
    To Configure the RFC to FILE scenario ,Proceed as Follows
    a.       Create an RFC Destination to XI in transaction code  (SM59)
    b.       Create new destination of type T (TCP/IP)
    c.       Make sure you select Registered Server Program option before writing your program ID
    d.       Write you program ID (remember it's case-sensitive)
    e.       In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
                 Step2:Repository
    1)       From the Integration Builder page, select “Integration Repository”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server
    2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
             From the list of Software Component Versions, Choose your own software component version .Click Import.
    3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this  software component. A screen will appear .Switch to display mode. After doing this first add  a namespace under Namespaces.
             The namespace is ur:rfctofile
    4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
             After this specify the connection parameters to the R/3 system:
    4.1)     System IS  :sapfox
    4.2)     Client IS :800
             Then Save it. The new namespace will be visible under software component version node in the left frame.
             Under the namespace node,  you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
    4.3)     Application server:172.25.5.7
    4.4)     System number: 00
    4.5)     User name:developer
    4.6)     Password: Password of Sap R/3 system.
             Then click continue .You will find IDOC and RFC node. Click on this node and select the   Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the   Rfc and  Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
    5).      Under your namespace in the left frame, expand the node “Interface objects”. You will find a node “DATA TYPES”
    6)        Create new data types.
    6.1)      Right click on “Data types” and select “New”.
               Your  Data Type is. dt_file
              In the data type Editor ,Create a structure having Elements of type String  ,  integer,  Boolean , Float etc as per the requirement.
              Save the object.
    6.2)      The Import function for XSD  files enables you to upload message definitions from external sources. The object type “External Definition” is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from “External Definition
              no need to create Data types. They are imported directly as Message types.
    6.3)      To do so, In the left hand frame  Under  ” Interface objects” Create a new object of type “External Definition” and give name to it.
              Select the following.
    6.3.1)    Category: XSD.
    6.3.2)    Messages: From All Available Global Elements.
    6.3.3)    File:
              Once the XSD is imported, click on “Message” tab , You should be able to see 2 messages(Request and Response)
    7).      Create a new Message  Type.
    7.1)     In the left hand frame under “Interface objects”, right click on the “Message types” and select new.
    7.2)     Give a suitable name to the Message type.(MT_ messagetype).
    7.3)     For the section “Data type used” you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
             Save it.
    8).     Create a Message interface
    8.1)    In the left hand frame under “Interface objects”, right click on the “Message Interface” and select new and name(MI_ messageinterface) it
    8.2).   The interface Should be  Inbound  and mode should be Asynchronous  .It should reference your Message type(Use F4 or Search help).
            Save it.
    9) .    Create a graphical mapping  between the target document and the sender .
    9.1)    In the left hand frame ,expand “Mapping objects”. Right click on “Message mapping” and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
    9.2)    As Source message select  your own  Message type.You can choose “Search  for Integration Object”.As a reminder you can find your Idoc or Rfc under Software Component-  >     Namespace->Imported Objects.
    9.3)    As Target Message you can choose your  Rfc .Choose “Search  for Integration Object”.
    9.4)    Now that we have defined the  Source and Target message, we can start defining the Mapping rules.
    9.5)    Map the fields of  Source document  to the equivalent fields in  Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
            Save It.
    9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
    9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
    10).     Create an Interface Mapping.
    10.1)   In the left hand Frame  expand “Mapping objects”. Right Click on “Interface Mapping” and  Name it. You are in a Interface Mapping Editor .Assign the following References.
    10.2)   Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose” Search  for Integration Object”.
    10.3)   Target interface:    Your Inbound Interface( The Target document interface).
            Then Select  'Read Interface' and Assign your  'Mapping Program' .
            Mapping Program: Your Message mapping.
            Then Save it.
    11.)    Finally , in the left hand frame ,go to your change list and Activate it
               STEP 3: Directory
    1)      From the Integration Builder page, select “Integration Directory”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server.
            Create a Scenario Object
    2).     The First Step is to create a Scenario Object
            This will serve as container for all your configuration work. Create and save a scenario object
    3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node “Service without Party” and right –click on “Business System”->Assign Business System
    4)      In the wizard , leave the party name blank and then select  your own Business System. Uncheck the box ”Create Communication Channel Automatically”.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
    5) .    Create a Communication Channel.
    6).     Expand your service and right click on “Communication Channel”. Name your Communication Channel
            Here we need to configure the adapter.
        Since the Sender is 'RFC', Specify the following Parameters
             For the adapter type , use the F4 help  and select RFC.
             Specify “Sender” since the adapter will be  sending messages to XI
             Specify the following parameters.
             Transport Protocol: RFC
             Message Protocol:   RFC(RFC XML )
             Adapter Engine: Integration Server
             Adapter status: Active
             RFC Server Parameter:
             Application Server(Gateway):172.25.5.7
             Application Server Service(Gateway Service): sapgw00
             Program Id: Id of Registered server program ( it is case sensititve)
             And the adapter is configured. Save it
              Since the Receiver  is File , Specify the following Parameters
    6.1       For the adapter type , use the F4 help  and select FILE.
    6.2       Specify “Receiver” since the adapter will be  sending XML files from XI to the  FTP server.
    6.3       Specify the following parameters.
              Transport Protocol: File Transport Protocol.(FTP)
              Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
              Adapter Engine: Integration Server
              For the File system access Parameters, enter the following
              Source Directory:Test
              File Name: Input.txt
    6.4       For the FTP Connection Parameters, Specify the Following
              Server:172.25.5.240
              Port: 21(by default)
              Data Connection: Passive
              Connection security: None
              Connection Mode:  Permanently
              Transfer Mode: Binary
    6.5       For Processing Parameters, Specify the following
              File construction mode: Add Time Stamp
              File Type: Binary
    6.6       For Content Conversion Parameters, Specify the Following
              RecordSet Structure:
              Adapter Status: Active
              The receiver file adapter is now configured. Save your Communication Channel.
               Create an Receiver Determination.
    7).       From the left frame Create a new “Receiver Determination” object. This is the main part of routing process, where you assign a receiver for your message.
    7.1)      Select your sender service and interface.
              Sender:
              Party:  blank
              Service:  Sender service(Business system)
              Interface : Sender interface
    7.2)      In the “Configured Receivers” area ,  choose the Service for the Target System.. Save your Receiver Determination
                Create an Interface Determination.
    7.3)       Next create an “Interface Determination” object. Now that we have defined a receiver of message  ,we need to assign an Inbound interface and an Interface mapping
    7.3.1)     In the Receiver Determination   you just created, have a look at the area “Configuration Overview for Receiver Determination”   at bottom of your screen and press Refresh  for that the Business system you assigned is displayed  in that area as well.
    7.3.2)     In the column “Receiver(Partner/Service)” open the details by clicking the node .The Entry “Not defined” shows you that there is no interface determination present.
               Right click on the Entry “Not defined” and select “ New specific”,  in order to create a new interface determination object
    7.3.3)     You are now in  the screen “Edit Interface Determination”. In the section “Configured Inbound Interfaces” select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
               After choosing the Inbound Interface,  It is shown in the Interface Determination
    7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
    7.3.5)     When you are done ,  Save the Interface determination object.
    8.)         Create a Sender Agreement.
               In the left hand frame , right click on “Sender Agreement” ->New
    8.1)       Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Outbound Interface
    8.2)       In the screen “Edit Service Agreement” use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
    9.)         Create a Receiver Agreement.
               Finally you will create a  'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
    9.1)       Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of your screen click Refresh.
    9.2)       In the Column “Receiver Agreement(Communication Channel) “ right click and select “New Specific”.
               Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Inbound Interface
    9.3)       In the screen ”Edit Receiver Agreement” for the field Receiver Communication Channel use  the input help F4 and select your communication channel. Save and Close it
               Your Configuration is complete. Activate the objects.
    To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
    STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
    We need to do the following settings in XI
    1)   Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
    2) Create Port Using Transaction Code  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 Using transaction Using Transaction (IDX2)
    a)  Create new
    b)  IDOC Message Type
    c)  Enter port created in IDX1
                        SETTINGS IN SAP R/3
         We need to do the following settings in R/3
         Logon to Sap R/3 System
    1)   Create an RFC Destination to XI in transaction code  (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.Both must be succesful
    2)   Create communication Port for Idoc processing Using Transaction(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)
    d)   Enter the RFC Destination created in SAP R/3 towards other system.
    e)   Save
    3)   Create Partner Profile with Outbound Parameters (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
         Then Save
    e)   Select Partner no. and LS which were create above
    f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g)   Select Message type
    h)   Double click on Message Type and Then Enter the details  for Receiving port, Pack size=1 and Basic type
    I)   save
    4)   In Transaction SALE, Create Logical System
    a).  Go to Basic Settings-> First Define logical systems
         and then assign logical systems
    b)   Double click on Define the logical systems
    c)   Give data for your Logicaal System and Name
    d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e)   Assign the logical system name to the client
    5)   Create Customer Distribution model in the transaction code BD64
    1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3)   Save the Distribution model
        Generate Partner Profiles
    Click on Menu Item ‘Generate Partner Profiles’
        It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
        Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4)   Distribute Customer Distribution Model
        In the menu item  GO to Edit->Modal View-> ‘Distribute’ to the destination client
        Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
                 Step2:Repository
    1)       From the Integration Builder page, select “Integration Repository”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server
    2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
             From the list of Software Component Versions, Choose your own software component version .Click Import.
    3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this  software component. A screen will appear .Switch to display mode. After doing this first add  a namespace under Namespaces.
             Your NameSpace is  urn:idoctofile
    4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
             After this specify the connection parameters to the R/3 system:
    4.1)     System  :sapfox
    4.2)     Client  :800
             Then Save it. The new namespace will be visible under software component version node in the left frame.
             Under the namespace node,  you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
    4.3)     Application server:172.25.5.7
    4.4)     System number:00
    4.5)     User name: developer
    4.6)     Password: Password of Sap R/3 system.
             Then click continue .You will find IDOC node. Click on this node and select the   Idoc  which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any  Idoc Structure. We need to create a structure for file only.
    5).      Under your namespace in the left frame, expand the node “Interface objects”. You will find a node “DATA TYPES”
    6)        Create new data types.
    6.1)      Right click on “Data types” and select “New”.
               Your Data Type is :dt_file
              In the data type Editor ,Create a structure having Elements of type String  ,  integer,  Boolean , Float etc as per the requirement.
              Save the object.
    6.2)      The Import function for XSD  files enables you to upload message definitions from external sources. The object type “External Definition” is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from “External Definition
              no need to create Data types. They are imported directly as Message types.
    6.3)      To do so, In the left hand frame  Under  ” Interface objects” Create a new object of type “External Definition” and give name to it.
              Select the following.
    6.3.1)    Category: XSD.
    6.3.2)    Messages: From All Available Global Elements.
    6.3.3)    File:
              Once the XSD is imported, click on “Message” tab , You should be able to see 2 messages(Request and Response)
    7).      Create a new Message  Type.
    7.1)     In the left hand frame under “Interface objects”, right click on the “Message types” and select new.
    7.2)     Give a suitable name to the Message type.(MT_ messagetype).
    7.3)     For the section “Data type used” you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
             Save it.
    8).     Create a Message interface
    8.1)    In the left hand frame under “Interface objects”, right click on the “Message Interface” and select new and name(MI_ messageinterface) it
    8.2).   The interface Should be  Inbound  and mode should be Asynchronous  .It should reference your Message type(Use F4 or Search help).
            Save it.
    9) .    Create a graphical mapping  between the target document and the sender .
    9.1)    In the left hand frame ,expand “Mapping objects”. Right click on “Message mapping” and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
    9.2)    As Source message select  your own Idoc .You can choose “Search  for Integration Object”.As a reminder you can find your Idoc or Rfc under Software Component-  >     Namespace->Imported Objects.
    9.3)    As Target Message you can choose your Message type  .Choose “Search  for Integration Object”.
    9.4)    Now that we have defined the  Source and Target message, we can start defining the Mapping rules.
    9.5)    Map the fields of  Source document  to the equivalent fields in  Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
            Save It.
    9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
    9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
    10).     Create an Interface Mapping.
    10.1)   In the left hand Frame  expand “Mapping objects”. Right Click on “Interface Mapping” and  Name it. You are in a Interface Mapping Editor .Assign the following References.
    10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose” Search  for Integration Object”.
    10.3)   Target interface:    Your Inbound Interface( The Target document interface).
            Then Select  'Read Interface' and Assign your  'Mapping Program' .
            Mapping Program: Your Message mapping.
            Then Save it.
    11.)    Finally , in the left hand frame ,go to your change list and Activate it
               STEP 3: Directory
    1)      From the Integration Builder page, select “Integration Directory”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server.
            Create a Scenario Object
    2).     The First Step is to create a Scenario Object
            This will serve as container for all your configuration work. Create and save a scenario object
    3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node “Service without Party” and right –click on “Business System”->Assign Business System
    4)      In the wizard , leave the party name blank and then select  your own Business System. Uncheck the box ”Create Communication Channel Automatically”.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
    5) .    Create a Communication Channel.
    6).     Expand your service and right click on “Communication Channel”. Name your Communication Channel
            Here we need to configure the adapter.
         Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
              For the Receiver, Specify the following Parameters
    6.1       For the adapter type , use the F4 help  and select FILE.
    6.2       Specify “Receiver” since the adapter will be  sending XML files from XI to the  FTP server.
    6.3       Specify the following parameters.
              Transport Protocol: File Transport Protocol.(FTP)
              Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
              Adapter Engine: Integration Server
              For the File system access Parameters, enter the following
              Source Directory:Test
              File Name: Input.txt
    6.4       For the FTP Connection Parameters, Specify the Following
              Server: 172.25.5.240
              Port: 21(by default)
              Data Connection: Passive
              Connection security: None
              Connection Mode:  Permanently
              Transfer Mode: Binary
    6.5       For Processing Parameters, Specify the following
              File construction mode: Add Time Stamp
              File Type: Binary
    6.6       For Content Conversion Parameters, Specify the Following
              RecordSet Structure:
              Adapter Status: Active
              The receiver file adapter is now configured. Save your Communication Channel.
               Create an Receiver Determination.
    7).       From the left frame Create a new “Receiver Determination” object. This is the main part of routing process, where you assign a receiver for your message.
    7.1)      Select your sender service and interface.
              Sender:
              Party:  blank
              Service:  Sender service(Business system)
              Interface : Sender interface
    7.2)      In the “Configured Receivers” area ,  choose the Service for the Target System.. Save your Receiver Determination
                Create an Interface Determination.
    7.3)       Next create an “Interface Determination” object. Now that we have defined a receiver of message  ,we need to assign an Inbound interface and an Interface mapping
    7.3.1)     In the Receiver Determination   you just created, have a look at the area “Configuration Overview for Receiver Determination”   at bottom of your screen and press Refresh  for that the Business system you assigned is displayed  in that area as well.
    7.3.2)     In the column “Receiver(Partner/Service)” open the details by clicking the node .The Entry “Not defined” shows you that there is no interface determination present.
               Right click on the Entry “Not defined” and select “ New specific”,  in order to create a new interface determination object
    7.3.3)     You are now in  the screen “Edit Interface Determination”. In the section “Configured Inbound Interfaces” select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
               After choosing the Inbound Interface,  It is shown in the Interface Determination
    7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
    7.3.5)     When you are done ,  Save the Interface determination object.
    8.)         Create a Sender Agreement.
               In the left hand frame , right click on “Sender Agreement” ->New
    8.1)       Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Outbound Interface
    8.2)       In the screen “Edit Service Agreement” use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
    9.)         Create a Receiver Agreement.
               Finally you will create a  'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
    9.1)       Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of your screen click Refresh.
    9.2)       In the Column “Receiver Agreement(Communication Channel) “ right click and select “New Specific”.
               Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Inbound Interface
    9.3)       In the screen ”Edit Receiver Agreement” for the field Receiver Communication Channel use  the input help F4 and select your communication channel. Save and Close it
               Your Configuration is complete. Activate the objects.
    plz rewards points
    vikas

Maybe you are looking for