Remote Function Call

1) What is RFC? 2)what is the use of it? 3)Types Of RFc's? Here we go: RFC is an Application Program Interface(API)Which is used to establish connection between two systems remotely. RFC is an Remote Function Call Using RFC we can connect to the other system which is locating on the on the other application server. There are Different Kinds of RFC's: 1) synchronous RFC 2)1) asynchronous RFC 3)1) transactional RFC 4)queued RFC RFC is nothing but a normal function module which is remote enabled. Consider two SAP systems. one is R/3 system and Other is XI System. We are creating this RFC in XI System. Steps For creating RFC: 1)Go TO SE37 t-code. 2)Name of function module(any name)---------ZRFC_DEMO_FM. 3)Assign Function Group 4)After assigning function group and short text 5)click on continue button. After that in the ATTRIBUTES tab make sure that the function module must be Remote-Enabled Module Give necessary parameters like IMPORT,EXPORT and maintain a logic inthe SOURCE CODE tab ----> Now the above created RFC should call into the R/3 System . Pre-requisite for calling a RFC into R/3 System is to establish a connection between the R/3 system and XI system for this we need to create a RFC destination from R/3 to XI. Steps For Creating RFC destination: This RFC destination is creating in R/3 System . 1)Go to t-code SM59. 2)Different connection types will be there in that select ABAP COnnections or R/3 Connections 3)click on create button 4)Specify the name of the RFC destination------ZR/3TOXI 5)connection type - 3 6)Short Description:Connection between R/3 to XI 7)Click on Technical Settings tab and fill the Target Host and System Number of the XI System.Target Host is application server name of XI system 8) Click on Logon & Security tab and specify the log on details of XI System

CALL FUNCTION "ZRFC_DEMO_FM"(RFC name which is in XI system) DESTINATION "ZR/3TOXI"(RFC destination from R/3 Pointing to XI system) "CALL FUNCTION <RFC NAME> DESTINATION <DESTINATION NAME>. .9)click on save 10)click on Connection test button at the top for testing the connection. 11)Click on Remotelogon button to connect to XI system .if the connection if fine then only we can logon to XI System other wise recheck your connection parameters Go to SE38 in R/3 System and write a program to call the RFC ." This Ends up with calling a RFC.

0. I would like to highlight that the system has the latest patch level and support packages installed. connection type to 3 (abap / R/3 connection) and fill target host to your backend system. Name R3DCLNT200 R3DCLNT200 o Create logical system name in backend. This user must have SAP_ALL authorisation. Middleware parameters setup Go to transaction SM30 on backend system and choose table CRMCONSUM. Go to transaction SM59 on backend side and click on 'create' button. Save your settings. including all the BASIS(BC) activities. Create RFC connections in SRM system. Save your settings. Basis Setup Create system users for remote connection (RFC_CONN). SR1CLNT300).How to replicate material master from R/3 to SRM I am going to present a quick guide to replicate material master from backend system to SRM 5. Set RFC destination name to SRM system CLNT (eg. Name SR1CLNT300 SR1CLNT300 First of all you must set a RFC connectivity between SRM and backend system: 2. connection type to 3 (abap / R/3 connection) and fill target host to your backend system. On tab Logon/Security add RFC_CONN user created in previous step.System o Save your settngs. Add the following values: User Active Description Q Prefix CRM checked SRM connection R3A . R3DCLNT200). Go to transaction SM59 on SRM side and click on 'create' button. Set RFC destination name to backend system CLNT (eg.System o Save your settngs. Create RFC connections in backend system. Go to transaction SPRO -> SAP Implemantation Guide -> Supplier Relationship Management -> SRM Server -> Technical Basic Settings -> ALE Settings -> Distribution -> Basic Settings -> Logical Systems -> Define Logical System Add a new value: o o o o Log. Create a logical system name in SRM. Go to transaction SPRO -> SAP Customizing Implemantation Guide -> SAP Web Application Server -> Application Ling Enabling -> Sending and Receiving Systems -> Logical Systems -> Define Logical System Add a new value: Log. On tab Logon/Security add RFC_CONN user created in previous step. so here we go: 1.

If you are using CRM in the client. Value Param. Class Obj. Go to transaction SE16N on backend side and choose table TBE11. Now. Functio Typ Funct. In SRM system run transaction BBP_PRODUCT_SETTINGS. configure filtering for material master: Choose CRMPAROLTP table for CRM OLTP Parameters and add the following values: Parameter name Param. you define whether you are running the Enterprise Buyer and CRM in the same system. The system generates a report containing all tables that have been deactivated. deselect 'Test mode' and choose Execute button. choose CRMRFCPAR for definitions of RFC Connections and add following values: User ObjectName Destination CRM * CRM * SR1CLNT300 Load Type INFO Initial Download InQueue Flag SR1CLNT300 X SR1CLNT300 X SR1CLNT300 X Send XML Send XML Send XML Send XML SR1CLNT300 Request Delta Download CRM MATERIAL SR1CLNT300 All other fields leave empty. Name 3 User Param. Value 2 empty CRM_FILTERING_ACTIVE MATERIAL empty CRM X Now we must edit the table for application indicator. 4. Name 2 Param. Generate Repository Objects . Search or add an application component BC-MID and edit activity settings (field AKTIV = X). 3. Enterprise Buyer with/without CRM In this activity. Name n e empt CRS_MATERIAL_EXTRACT y empt CRS_CUSTOMIZING_EXTR y ACT empt CRS_SERVICE_EXTRACT y Downloa Materi empty d al Downloa Materi empty d al Downloa Materi empty d al Next. Save your settings. choose CRMSUBTAB for subscription table for Up and Download Object and add the following values: User CR M CR M CR M ObjectNa me empty empty empty U/D Obj. This might accelerate the Master Data download performance.Next. then skip this activity.

Go to transaction SMOGGEN and choose object PRODUCT_MAT and PRODUCT_SRV. Number Range Object Maintenance On SRM system go to transaction SRNO and assign number ranges for all CRM Replication and Realigment Queues. Choose R/3 for 'Type' parameter and click on Site Attributes. Administration Console shows up. CRM Middleware Monitoring Cockpit On SRM side go to transaction SMWP. Output format of Product ID Check Your output format for Product ID in backend and SRM system. . 7. you generate the middleware function modules (BDoc Object Type) for the material master. Open System Settings and double-click on 'Number of sites per site type' name. Enter in object field RRSEQ*and hit F4 button.With this procedure. Go to transaction COMCPRFORMAT in SRM and check product ID lenght and values for displaying leading zeroes. 5. 6. Save your settings. Generate services for all Object Categories. Choose the first object (RRSEQ_AC) and click on 'change' button. Click on 'Create Object' icon and fill Name and description. On next screen click button 'Number Ranges' and add the following range: No From number To Number Ext. This values must be the same for both systems. Enter and created RFC destination to backend system (R3DCLNT200). 01 00000000000000000001 99999999999999999999 no Repeat these steps for all of RRSEQ* objects.

Click on 'Execute' button. If you have a green light. go to transaction R3AS again and repeat steps for objects: . 8. Start of download material DNL_CUST_PROD0 DNL_CUST_PROD1 DNL_CUST_SRVMAS MATERIAL Go to transaction R3AS on SRM side and choose first object to download (DNL_CUST_BASIS3). go to transactionR3AM1 for monitoring object. source site and desitination site on data flow should fill with proper values. o o o o After this.Save your settings. After this.

go to transaction COMM_HIERARCHY to see what kind of Categories are replicated from backend system.After this. go to transaction R3AC1 on SRM side. Go to transaction COMMPR01 to see what kind of Products are replicated from backend system. You will see the following table: . 9. Filtering Material Master records If you want to filter material master or other objects.

run Report: If You want to delete all or selected product. run Report: . If you want to download only one material enter the following values: 10.Click on filter icon on object MATERIAL. Deleting Material Master from SRM o o o o COM_HIERARCHY_DELETE_SINGLE . Object filter settings table corresponds fields and tables/structures from backend system.Deletion of All Product Master Data If you want to delete hierarchy of product.Deletion of a product from the database COM_PRODUCT_DELETE_ALL .Deletes All Hierarchy and Category Data COM_PRODUCT_DELETE_SINGLE . On filter settings tab choose Source Site Name and click edit button.Deletes All Hierarchy and Category Data COM_HIERARCHY_DELETE_ALL .

For creating follow-on documents in backend system: Enter the logical system. system type of the SRM system and define SRM system as local.Configuring connections to Backend system in SAP SRM For configuring communication with backend systems from SAP SRM first we should define following steps: Defining Logical system: Define logical system in below mentioned path: SPRO → Supplier Relationship Management → SRM Server → Technical Basic Settings → ALE Settings (Logical System) → Distribution (ALE) → Basic Settings → Logical Systems → Define Logical System. Define RFC connections in SRM in below path: Supplier Relationship Management → SRM Server → Technical Basic Settings → Define RFC Destinations. For creating follow-on documents in SRM: Enter the logical system. We also have to define RFC destination for SAP Enterprise buyer in R/3. destination. define an RFC destination for each one. Defining Backend System Please follow below path to define backend systems in SAP SRM: SPRO → Supplier Relationship Management → SRM Server → Technical Basic Settings → Define Backend Systems. If we have more than one R/3 backend system. destination and system type of the backend system and select the RFC indicator if the logical system is RFC-compatible. Defining RFC destination: SAP Enterprise Buyer communicates with any backend system using RFC. .We can determine which backend system should be used to create follow-on documents as mentioned in my previous blog determining backend systems. Now connections are defined from SRM to R/3.

Sign up to vote on this title
UsefulNot useful