SAP FM4B_GET_COMMITMENTS_ADD Function Module for









FM4B_GET_COMMITMENTS_ADD is a standard fm4b get commitments add 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 fm4b get commitments add FM, simply by entering the name FM4B_GET_COMMITMENTS_ADD into the relevant SAP transaction such as SE37 or SE38.

Function Group: FM4B
Program Name: SAPLFM4B
Main Program: SAPLFM4B
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FM4B_GET_COMMITMENTS_ADD 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 'FM4B_GET_COMMITMENTS_ADD'"
EXPORTING
I_GNJHR_MAX = "

TABLES
T_ASSIGNED = "
.



IMPORTING Parameters details for FM4B_GET_COMMITMENTS_ADD

I_GNJHR_MAX -

Data type: BPJA-GJAHR
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FM4B_GET_COMMITMENTS_ADD

T_ASSIGNED -

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

Copy and paste ABAP code example for FM4B_GET_COMMITMENTS_ADD 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_t_assigned  TYPE STANDARD TABLE OF FMFI_T_ASSIGNED_BUDGET, "   
lv_i_gnjhr_max  TYPE BPJA-GJAHR. "   

  CALL FUNCTION 'FM4B_GET_COMMITMENTS_ADD'  "
    EXPORTING
         I_GNJHR_MAX = lv_i_gnjhr_max
    TABLES
         T_ASSIGNED = lt_t_assigned
. " FM4B_GET_COMMITMENTS_ADD




ABAP code using 7.40 inline data declarations to call FM FM4B_GET_COMMITMENTS_ADD

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.

 
"SELECT single GJAHR FROM BPJA INTO @DATA(ld_i_gnjhr_max).
 


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!