SAP FM4B_GET_ASSIGNED_MULTI Function Module for









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

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



Function FM4B_GET_ASSIGNED_MULTI 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_ASSIGNED_MULTI'"
EXPORTING
I_FIKRS = "
I_FUND = "
I_GJAHR = "
* I_VERSION = ' ' "
* I_COMMITMENT = 'X' "
* I_PAYMENT = 'X' "
* I_FLG_BUDGET = 'X' "
* I_FLG_INDEX = 'X' "

IMPORTING
E_WAERS = "

TABLES
T_FMBPCF = "
T_FMBPCFINDEX = "

EXCEPTIONS
PROFILE_NOT_FOUND = 1
.



IMPORTING Parameters details for FM4B_GET_ASSIGNED_MULTI

I_FIKRS -

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

I_FUND -

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

I_GJAHR -

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

I_VERSION -

Data type: BPIN-VERSN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_COMMITMENT -

Data type: FMDY-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PAYMENT -

Data type: FMDY-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_BUDGET -

Data type: FMDY-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_INDEX -

Data type: FMDY-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FM4B_GET_ASSIGNED_MULTI

E_WAERS -

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

TABLES Parameters details for FM4B_GET_ASSIGNED_MULTI

T_FMBPCF -

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

T_FMBPCFINDEX -

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

EXCEPTIONS details

PROFILE_NOT_FOUND -

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

Copy and paste ABAP code example for FM4B_GET_ASSIGNED_MULTI 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_e_waers  TYPE FM01-WAERS, "   
lv_i_fikrs  TYPE BPIN-FIKRS, "   
lt_t_fmbpcf  TYPE STANDARD TABLE OF FMBPCF, "   
lv_profile_not_found  TYPE FMBPCF, "   
lv_i_fund  TYPE BPIN-GEBER, "   
lt_t_fmbpcfindex  TYPE STANDARD TABLE OF FMBPCFINDEX, "   
lv_i_gjahr  TYPE BPIN-GJAHR, "   
lv_i_version  TYPE BPIN-VERSN, "   SPACE
lv_i_commitment  TYPE FMDY-XFELD, "   'X'
lv_i_payment  TYPE FMDY-XFELD, "   'X'
lv_i_flg_budget  TYPE FMDY-XFELD, "   'X'
lv_i_flg_index  TYPE FMDY-XFELD. "   'X'

  CALL FUNCTION 'FM4B_GET_ASSIGNED_MULTI'  "
    EXPORTING
         I_FIKRS = lv_i_fikrs
         I_FUND = lv_i_fund
         I_GJAHR = lv_i_gjahr
         I_VERSION = lv_i_version
         I_COMMITMENT = lv_i_commitment
         I_PAYMENT = lv_i_payment
         I_FLG_BUDGET = lv_i_flg_budget
         I_FLG_INDEX = lv_i_flg_index
    IMPORTING
         E_WAERS = lv_e_waers
    TABLES
         T_FMBPCF = lt_t_fmbpcf
         T_FMBPCFINDEX = lt_t_fmbpcfindex
    EXCEPTIONS
        PROFILE_NOT_FOUND = 1
. " FM4B_GET_ASSIGNED_MULTI




ABAP code using 7.40 inline data declarations to call FM FM4B_GET_ASSIGNED_MULTI

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 WAERS FROM FM01 INTO @DATA(ld_e_waers).
 
"SELECT single FIKRS FROM BPIN INTO @DATA(ld_i_fikrs).
 
 
 
"SELECT single GEBER FROM BPIN INTO @DATA(ld_i_fund).
 
 
"SELECT single GJAHR FROM BPIN INTO @DATA(ld_i_gjahr).
 
"SELECT single VERSN FROM BPIN INTO @DATA(ld_i_version).
DATA(ld_i_version) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_commitment).
DATA(ld_i_commitment) = 'X'.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_payment).
DATA(ld_i_payment) = 'X'.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_flg_budget).
DATA(ld_i_flg_budget) = 'X'.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_flg_index).
DATA(ld_i_flg_index) = 'X'.
 


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!