Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 1K views

    File To RFC Without BPM

    Uploaded by

    api-3722276
    This document outlines the steps to create a simple RFC-enabled function module in SAP R/3 and configure the necessary objects in SAP XI to push vendor data from an XML file to the SAP system using this function module. Key steps include: 1. Creating a Z table in R/3 to store vendor data and the BAPI (ZVENDOR) with an import parameter to modify this table. 2. Importing the BAPI to the XI Integration Repository and creating the necessary data types, message types, and interfaces. 3. Configuring the sender and receiver communication channels in the Integration Directory. 4. Testing the scenario by checking that a sample XML file is processed and the

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    File To RFC Without BPM

    Uploaded by

    api-3722276
    1K views7 pages
    This document outlines the steps to create a simple RFC-enabled function module in SAP R/3 and configure the necessary objects in SAP XI to push vendor data from an XML file to the SAP system using this function module. Key steps include: 1. Creating a Z table in R/3 to store vendor data and the BAPI (ZVENDOR) with an import parameter to modify this table. 2. Importing the BAPI to the XI Integration Repository and creating the necessary data types, message types, and interfaces. 3. Configuring the sender and receiver communication channels in the Integration Directory. 4. Testing the scenario by checking that a sample XML file is processed and the

    Original Description:

    File to RFC Scenario in XI

    Original Title

    File to RFC Without BPM

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines the steps to create a simple RFC-enabled function module in SAP R/3 and configure the necessary objects in SAP XI to push vendor data from an XML file to the SAP system using this function module. Key steps include: 1. Creating a Z table in R/3 to store vendor data and the BAPI (ZVENDOR) with an import parameter to modify this table. 2. Importing the BAPI to the XI Integration Repository and creating the necessary data types, message types, and interfaces. 3. Configuring the sender and receiver communication channels in the Integration Directory. 4. Testing the scenario by checking that a sample XML file is processed and the

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    1K views7 pages

    File To RFC Without BPM

    Uploaded by

    api-3722276
    This document outlines the steps to create a simple RFC-enabled function module in SAP R/3 and configure the necessary objects in SAP XI to push vendor data from an XML file to the SAP system using this function module. Key steps include: 1. Creating a Z table in R/3 to store vendor data and the BAPI (ZVENDOR) with an import parameter to modify this table. 2. Importing the BAPI to the XI Integration Repository and creating the necessary data types, message types, and interfaces. 3. Configuring the sender and receiver communication channels in the Integration Directory. 4. Testing the scenario by checking that a sample XML file is processed and the

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 7

    Scenario – File to RFC without BPM

    I have tried to explain how to create a simple RFC enabled function module in R/3 and
    the steps required to push the data from XI to SAP R/3 by using this function module.

    The sender will send the vendor data to XI in XML file format. Then XI will push the
    data to R/3 by using RFC adapter.

    Following are the steps to create a BAPI in SAP R/3

    Create a Z table to store the vendor data. Created a standard table ZVENDORDATA.

    Creating BAPI in R/3 system.

    You can use transaction code SM37 to create BAPI in R/3 system. Be sure that you have
    selected the Remote Enabled Module in the Attributes tab.

    Function Module Name: ZVENDOR.


    Declare an import parameter ITAB for ZVENDOR function module. Value for the
    Associated Type column should be the Database table name.

    Source code for this BAPI

    Used MODIFY statement to do the changes in the database table ZVENDORDATA. This
    statement will modify the data if it is already present in the table. If that particular record
    is not in the table then it will create a new record.

    Till now we have discussed about R/3 stuff. Now we can see how the configuration
    objects in the Integration Repository.
    Import the BAPI (ZVENDOR) to the Integration Repository.

    Define Data Type: VendorRFC_DT.


    Create Message type: VendorSenderRFC_MT

    Create Message Interface: VendorSenderRFC_MI. We have created outbound,


    Asynchronous interface for this scenario.
    Create Mapping Program by using mapping editor: VendorRFC_MM

    Create Interface Mapping: VendorRFC_IM


    Now, we will do the configuration in the Integration Directory.

    Sender Communication Channel: VendorSenderRFC_CC

    Receiver Communication Channel: VendorReceiverRFC_CC


    Create Receiver Determination, Interface Determination, Sender Agreement and Receiver
    Agreement for this scenario.

    This is the time to test our scenario. You can see the vendor name as Rahul in
    ZVENDORDATA table

    Sample xml file that contains vendor data.

    After the successful execution you can see the result in the table. The name of the vendor
    has been changed to Bharath.

    You might also like