Professional Documents
Culture Documents
File To RFC Without BPM PDF
File To RFC Without BPM PDF
e 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.
Create Message Interface: VendorSenderRFC_MI. We have created outbound, Asynchronous interface for this scenario.
Now, we will do the configuration in the Integration Directory. Sender Communication Channel: VendorSenderRFC_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
After the successful execution you can see the result in the table. The name of the vendor has been changed to Bharath.