SAP BIZC_COMMIT Function Module for









BIZC_COMMIT is a standard bizc commit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bizc commit FM, simply by entering the name BIZC_COMMIT into the relevant SAP transaction such as SE37 or SE38.

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



Function BIZC_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 'BIZC_COMMIT'"
EXPORTING
IP_USAGE = "
* IP_SYSTEM_GROUP = "
* IP_ROLE = "

EXCEPTIONS
COMMUNICATION_PROBLEM = 1 UNKNOWN_ERROR = 2 BIZC_FRAMEWORK_ERROR = 3
.



IMPORTING Parameters details for BIZC_COMMIT

IP_USAGE -

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

IP_SYSTEM_GROUP -

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

IP_ROLE -

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

EXCEPTIONS details

COMMUNICATION_PROBLEM -

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BIZC_FRAMEWORK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BIZC_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:
lv_ip_usage  TYPE BIZC_USAGE, "   
lv_communication_problem  TYPE BIZC_USAGE, "   
lv_unknown_error  TYPE BIZC_USAGE, "   
lv_ip_system_group  TYPE BIZCS_SM_SYS_GRP, "   
lv_ip_role  TYPE BIZCS_SM_SYSTEM_ROLE, "   
lv_bizc_framework_error  TYPE BIZCS_SM_SYSTEM_ROLE. "   

  CALL FUNCTION 'BIZC_COMMIT'  "
    EXPORTING
         IP_USAGE = lv_ip_usage
         IP_SYSTEM_GROUP = lv_ip_system_group
         IP_ROLE = lv_ip_role
    EXCEPTIONS
        COMMUNICATION_PROBLEM = 1
        UNKNOWN_ERROR = 2
        BIZC_FRAMEWORK_ERROR = 3
. " BIZC_COMMIT




ABAP code using 7.40 inline data declarations to call FM BIZC_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



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!