SAP BICS_CONS_DATA_AREA_PLAN_SYNC Function Module for Synchronize data area planning state









BICS_CONS_DATA_AREA_PLAN_SYNC is a standard bics cons data area plan sync SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Synchronize data area planning state processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bics cons data area plan sync FM, simply by entering the name BICS_CONS_DATA_AREA_PLAN_SYNC into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSBOLAP_BICS_CONSUMER
Program Name: SAPLRSBOLAP_BICS_CONSUMER
Main Program: SAPLRSBOLAP_BICS_CONSUMER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BICS_CONS_DATA_AREA_PLAN_SYNC pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BICS_CONS_DATA_AREA_PLAN_SYNC'"Synchronize data area planning state
  EXPORTING
*  I_APPLICATION_HANDLE =  "Unique Object Handle for External Communication
*  I_DATA_AREA = 'DEFAULT' "Data Area Context Within an Application

 IMPORTING
   E_MAX_MESSAGE_TYPE =  "Message Type

TABLES
*  E_T_MESSAGE =  "Message
*  I_T_STATISTIC_INFO =  "OLAP Statistics: Mass Insert of Event Data
*  E_T_OUT_OF_SYNC_DP =  "Object Name as Structure for RFC
*  I_T_DATA_PROVIDER_HANDLE =  "Structure for RSBOLAP_HANDLE

EXCEPTIONS
   INVALID_DATA_AREA = 1
.



IMPORTING Parameters details for BICS_CONS_DATA_AREA_PLAN_SYNC

I_APPLICATION_HANDLE - Unique Object Handle for External Communication

Data type: RSBOLAP_HANDLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DATA_AREA - Data Area Context Within an Application

Data type: RSBOLAP_DATA_AREA
Default: 'DEFAULT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BICS_CONS_DATA_AREA_PLAN_SYNC

E_MAX_MESSAGE_TYPE - Message Type

Data type: SYMSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BICS_CONS_DATA_AREA_PLAN_SYNC

E_T_MESSAGE - Message

Data type: BICS_PROV_MESSAGE
Optional: Yes
Call by Reference: Yes

I_T_STATISTIC_INFO - OLAP Statistics: Mass Insert of Event Data

Data type: RSSTA_S_EVENTINPUT
Optional: Yes
Call by Reference: Yes

E_T_OUT_OF_SYNC_DP - Object Name as Structure for RFC

Data type: RSBOLAP_S_OBJECT_NAME
Optional: Yes
Call by Reference: Yes

I_T_DATA_PROVIDER_HANDLE - Structure for RSBOLAP_HANDLE

Data type: RSBOLAP_S_HANDLE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INVALID_DATA_AREA - Invalid reference to a data area

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BICS_CONS_DATA_AREA_PLAN_SYNC Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lt_e_t_message  TYPE STANDARD TABLE OF BICS_PROV_MESSAGE, "   
lv_invalid_data_area  TYPE BICS_PROV_MESSAGE, "   
lv_e_max_message_type  TYPE SYMSGTY, "   
lv_i_application_handle  TYPE RSBOLAP_HANDLE, "   
lv_i_data_area  TYPE RSBOLAP_DATA_AREA, "   'DEFAULT'
lt_i_t_statistic_info  TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT, "   
lt_e_t_out_of_sync_dp  TYPE STANDARD TABLE OF RSBOLAP_S_OBJECT_NAME, "   
lt_i_t_data_provider_handle  TYPE STANDARD TABLE OF RSBOLAP_S_HANDLE. "   

  CALL FUNCTION 'BICS_CONS_DATA_AREA_PLAN_SYNC'  "Synchronize data area planning state
    EXPORTING
         I_APPLICATION_HANDLE = lv_i_application_handle
         I_DATA_AREA = lv_i_data_area
    IMPORTING
         E_MAX_MESSAGE_TYPE = lv_e_max_message_type
    TABLES
         E_T_MESSAGE = lt_e_t_message
         I_T_STATISTIC_INFO = lt_i_t_statistic_info
         E_T_OUT_OF_SYNC_DP = lt_e_t_out_of_sync_dp
         I_T_DATA_PROVIDER_HANDLE = lt_i_t_data_provider_handle
    EXCEPTIONS
        INVALID_DATA_AREA = 1
. " BICS_CONS_DATA_AREA_PLAN_SYNC




ABAP code using 7.40 inline data declarations to call FM BICS_CONS_DATA_AREA_PLAN_SYNC

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
DATA(ld_i_data_area) = 'DEFAULT'.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!