In the attributes tab make it as RFC enabled as shown below Call the normal function module it.

READ_TEXT in the source code. Save it and activate ZREAD_TEXT is ready.

Now the RFC enable function module

Now let us see how to call this from BODS designer. After dragging the source and connected to query then this RFC function call is done. In the Query edition a New Function Call ve the required importing parameters. option is available as shown below and gi

As we have table parameter available in this Function module, we need to normali ze the schema by calling one more query as shown below. Once the Job is executed we can see the result that has been extracted from the Function module. SAP-BODS integration using IDOCS By Praveen Addanki, HCL-AXON 1.Introduction: Imagine you want to build a Reporting Solution, not a Data Warehouse in pure ter ms. So somebody opens the balance sheet report and does not like the way it look s. So a booking in SAP is created to correct it and then....he has to wait the e ntire night until the Data Warehouse gets refreshed. Another option would be to configure SAP so it sends all changes to the reporting database immediately. And that is what IDOCs are for. On the downside though, to configure SAP to actually send changes is quite a cha llenge. If an IDOC is provided by SAP already it is not that bad, but if you wan t to distribute changes for data SAP never thought about, you have to write your IDOC from scratch and hook it into every single application dealing with that d ata. The basic problem is the IDOC design. It is not like a database triggers that is independent from all the applications and fires no matter who and how a change happened. It is happening on application level, so there is a common ABAP call t hat has to be done at every single application. Inside SAP, a couple of settings have to be made, this configuration is mandator y for both sending and receiving IDOCs. The following configurations steps are i nvolved to send IDOCs from BODS to SAP ECC. 1. Define Logical Systems 2. Define RFC Destination 3. Defining RFC Port(Transactional RFC) 4. Define Partner Profile Let us see in brief how to configure the above steps: 2.SAP Configuration settings: 2.1 Define Logical Systems: Defining Logical systems is done in SAP ECC with the transaction SALE . Note: This entire documentation refers to SAP IDES system refer the below screen shot for detail. Enter the Transaction SALE to define logical system and its assignment. As this co nfirmation doesn t have authorization we will request basis to create it. Hence we used the following logical system as shown below. Click on the above shown to define the logical system. The below popup come just continue

The Logical system created by basis is

ID3CLNT801 as shown below.

2.2 Define RFC Destination: Enter the transaction SM59 to configure the RFC destination in SAP ECC as shown be low. Click on TCP/IP connections as shown above and the create it. Once the RFC created with Registered Server Program (Program ID) as DI_RFC as show n here. With the defined program ID, configure this from BODS side from manageme nt console as shown below. Logon on to Management console and click administrato r. RFC server configuration is done as shown below. The configured served need to be started the interface as shown below. Now check the connection from SAP side as shown below. Click on the connection t est as shown. If the connection is fine then the following screen will appear. 2.1 Defining RFC Port (Transactional RFC): Enter the transaction WE21 to create the Port as shown. The RFC destination will b e defined here. 2.2 Define Partner Profile And finally, we can configure SAP to route all IDOCs of a given type to DI by ru nning the transaction "WE20". You click on "New", type in the Partner Number cre ated in "/nsale" (we called it ID3CLNT801) and its type is "LS"....Logical Syste m. Then you click on save. Configure the Inbound parameters as SAP need to receive the IDOCS. Note: From SAP if we need to send the IDOCS to BODS then configure outbound para meters, vice versa to receive the IDOCS (Inbound). In this case it is considered to create the customer which comes from BODS; henc e the configuration should be Inbound. It is shown below. Click on Add