Remote Function Module

Using Remote FM to trigger jobs in another system.

In this scenario, we will see how to trigger a functional module from BW to ECC.

1) Create Function Module in ECC - SE37
   Go to Attributes -> Make it Remote-Enabled Module
   Add parameters - The attributes need to be 'Pass Value' - Check the  
   box

2) Write code as any other ABAP Code.

3) In BW, create a program in SE38
   Below is some sample code
   parameters: p_rfcdest like rfcdisplay-rfcdest,
               p_value type CHAR3.
   call function 'ZECC_FM_IN_ECC' destination p_rfcdest
     exporting
       value = p_value


You can also trigger an event from one system to another using Remote Function Modules. Below are the steps.

1) Create an event in SM62

2) Create a job in SM36 and give the start parameter as the event.

3) Create program in BW. You can use FM 'RSSM_EVENT_RAISE' which is a standard  Remote enable FM.

FM Based datasources

Description
This document gives details on creating a BW datasource based on different delta fields


Create Structure
This datasource will be based on a function module. Create a structure will all the fields you need in your datasource and also add an extra field - ZDATE type DATUM which would be used as the delta field going forward.

Create a FM
Copy FM RSAX_BIW_GET_DATA_SIMPLE to a new function module and assign it to any z function groups.Once the FM is copied, go to the 'Tables' tab and assign 'E_T_DATA' with the structure created above.

--------- TO BE UPDATED ---

BW Questions

Difference between Master data Activation and Attribute Change Run

• Master Data Activation = Activation
• Attribute Change Run = (Master Data Activation) + Extra features
• Master Data Activation
• When the data is loaded to the InfoObject, it is present in ‘M’ Version, which is modified version. Only after the infoObject is activated, it changes to Active (A) version and is available for reporting.
• Attribute Change Run
• It does the Master data activation, along with the following tasks
• It realigns the Aggregates for the changed attributes. 
• It is also used when Navigational Attributes are used in the Aggregates. Once the request is loaded to cube and Roll up has been done. So after doing Rollup, if the value of the Master Data changes, that will not be reflected in the aggregates. As, when a query is executed, it gets the data from the Aggregates. In our case, the master data value changed after rollup, so the value is different in Aggregate and Cube. So, if we do Attribute Change Run, whenever there is a change in the master data value, it informs the change of master data value.