SAP BICS_CONS_EXECUTE_PLANNING_SEQ Function Module for Execute Planning Sequence
BICS_CONS_EXECUTE_PLANNING_SEQ is a standard bics cons execute planning seq SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute Planning Sequence 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 execute planning seq FM, simply by entering the name BICS_CONS_EXECUTE_PLANNING_SEQ 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_EXECUTE_PLANNING_SEQ 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_EXECUTE_PLANNING_SEQ'"Execute Planning Sequence.
EXPORTING
I_SEQUENCE_HANDLE = "Unique Object Handle for External Communication
* I_PROCESS_CHANGED_DATA = "Boolean
* I_AGGREGATION_LEVEL = "InfoProvider
* I_REUSE = RS_C_FALSE "Reuse Planning Sequence
IMPORTING
E_MAX_MESSAGE_TYPE = "Message Type
E_EXECUTED = "Planning Function Executed
E_DATA_AREA_CONTAINS_DATA = "Data Area Contains Data
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
EXCEPTIONS
INVALID_SEQUENCE_HANDLE = 1 VARIABLE_INPUT_NECESSARY = 2
IMPORTING Parameters details for BICS_CONS_EXECUTE_PLANNING_SEQ
I_SEQUENCE_HANDLE - Unique Object Handle for External Communication
Data type: RSBOLAP_HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
I_PROCESS_CHANGED_DATA - Boolean
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AGGREGATION_LEVEL - InfoProvider
Data type: RSINFOPROVOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REUSE - Reuse Planning Sequence
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BICS_CONS_EXECUTE_PLANNING_SEQ
E_MAX_MESSAGE_TYPE - Message Type
Data type: SYMSGTYOptional: No
Call by Reference: No ( called with pass by value option)
E_EXECUTED - Planning Function Executed
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
E_DATA_AREA_CONTAINS_DATA - Data Area Contains Data
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BICS_CONS_EXECUTE_PLANNING_SEQ
E_T_MESSAGE - Message
Data type: BICS_PROV_MESSAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_T_STATISTIC_INFO - OLAP Statistics: Mass Insert of Event Data
Data type: RSSTA_S_EVENTINPUTOptional: Yes
Call by Reference: No ( called with pass by value option)
E_T_OUT_OF_SYNC_DP - Object Name as Structure for RFC
Data type: RSBOLAP_S_OBJECT_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_SEQUENCE_HANDLE - Invalid Planning Sequence Handle
Data type:Optional: No
Call by Reference: Yes
VARIABLE_INPUT_NECESSARY - Variable Entry Required
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BICS_CONS_EXECUTE_PLANNING_SEQ 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_i_sequence_handle | TYPE RSBOLAP_HANDLE, " | |||
| lv_e_max_message_type | TYPE SYMSGTY, " | |||
| lv_invalid_sequence_handle | TYPE SYMSGTY, " | |||
| lv_e_executed | TYPE RS_BOOL, " | |||
| lt_i_t_statistic_info | TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT, " | |||
| lv_i_process_changed_data | TYPE RS_BOOL, " | |||
| lv_variable_input_necessary | TYPE RS_BOOL, " | |||
| lt_e_t_out_of_sync_dp | TYPE STANDARD TABLE OF RSBOLAP_S_OBJECT_NAME, " | |||
| lv_i_aggregation_level | TYPE RSINFOPROV, " | |||
| lv_e_data_area_contains_data | TYPE RS_BOOL, " | |||
| lv_i_reuse | TYPE RS_BOOL. " RS_C_FALSE |
|   CALL FUNCTION 'BICS_CONS_EXECUTE_PLANNING_SEQ' "Execute Planning Sequence |
| EXPORTING | ||
| I_SEQUENCE_HANDLE | = lv_i_sequence_handle | |
| I_PROCESS_CHANGED_DATA | = lv_i_process_changed_data | |
| I_AGGREGATION_LEVEL | = lv_i_aggregation_level | |
| I_REUSE | = lv_i_reuse | |
| IMPORTING | ||
| E_MAX_MESSAGE_TYPE | = lv_e_max_message_type | |
| E_EXECUTED | = lv_e_executed | |
| E_DATA_AREA_CONTAINS_DATA | = lv_e_data_area_contains_data | |
| 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 | |
| EXCEPTIONS | ||
| INVALID_SEQUENCE_HANDLE = 1 | ||
| VARIABLE_INPUT_NECESSARY = 2 | ||
| . " BICS_CONS_EXECUTE_PLANNING_SEQ | ||
ABAP code using 7.40 inline data declarations to call FM BICS_CONS_EXECUTE_PLANNING_SEQ
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_reuse) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects