SAP RSCRM_IMP_COMMIT Function Module for To commit planning data on BI
RSCRM_IMP_COMMIT is a standard rscrm imp commit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for To commit planning data on BI 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 rscrm imp commit FM, simply by entering the name RSCRM_IMP_COMMIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSCRM_IMP_RFC_FACADE
Program Name: SAPLRSCRM_IMP_RFC_FACADE
Main Program: SAPLRSCRM_IMP_RFC_FACADE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSCRM_IMP_COMMIT 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 'RSCRM_IMP_COMMIT'"To commit planning data on BI.
IMPORTING
EV_RETURN_CODE = "Return Code
TABLES
ET_MESSAGES = "Table with BAPI Return Information
EXCEPTIONS
REMOTE_ERROR = 1 REMOTE_CRITICAL_ERROR = 2
EXPORTING Parameters details for RSCRM_IMP_COMMIT
EV_RETURN_CODE - Return Code
Data type: RSCRM_IMP_RETURN_CODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RSCRM_IMP_COMMIT
ET_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
REMOTE_ERROR - A critical error has occurred during remote execution.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REMOTE_CRITICAL_ERROR - An unexpected critical error has occurred during remote execution.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSCRM_IMP_COMMIT 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_et_messages | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_remote_error | TYPE BAPIRETTAB, " | |||
| lv_ev_return_code | TYPE RSCRM_IMP_RETURN_CODE, " | |||
| lv_remote_critical_error | TYPE RSCRM_IMP_RETURN_CODE. " |
|   CALL FUNCTION 'RSCRM_IMP_COMMIT' "To commit planning data on BI |
| IMPORTING | ||
| EV_RETURN_CODE | = lv_ev_return_code | |
| TABLES | ||
| ET_MESSAGES | = lt_et_messages | |
| EXCEPTIONS | ||
| REMOTE_ERROR = 1 | ||
| REMOTE_CRITICAL_ERROR = 2 | ||
| . " RSCRM_IMP_COMMIT | ||
ABAP code using 7.40 inline data declarations to call FM RSCRM_IMP_COMMIT
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.Search for further information about these or an SAP related objects