SAP FMBAS_CHECK_PA_EXISTENCY Function Module for Check if posting address exists in list of budget structure (FMBASIDX)









FMBAS_CHECK_PA_EXISTENCY is a standard fmbas check pa existency SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if posting address exists in list of budget structure (FMBASIDX) 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 fmbas check pa existency FM, simply by entering the name FMBAS_CHECK_PA_EXISTENCY into the relevant SAP transaction such as SE37 or SE38.

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



Function FMBAS_CHECK_PA_EXISTENCY 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 'FMBAS_CHECK_PA_EXISTENCY'"Check if posting address exists in list of budget structure (FMBASIDX)
EXPORTING
I_FM_AREA = "Financial management area
* I_FUNCAREA = "Functional Area
* I_MEASURE = "Measure in Funds Management
* I_USERDIM = "Customer field for FM actual and commitment data
* I_T_IGNORED_PA = "Table with FM account assignments
* I_FISCYEAR = "Fiscal Year
* I_T_RANGE_FISCYEAR = "Range for fiscal year
* I_PLDNR = "Posting Ledger Number
* I_F_ADDRESS = "FM account assignments
* I_FUND = "Fund
* I_BUDGET_PD = "FM: Budget Period
* I_FUNDSCTR = "Funds Center
* I_CMMTITEM = "Commitment item

IMPORTING
E_FLG_PA_EXISTS = "Posting address exists for the selection

EXCEPTIONS
TOO_MANY_PARAMETERS = 1 INVALID_POSTING_LEDGER = 2
.



IMPORTING Parameters details for FMBAS_CHECK_PA_EXISTENCY

I_FM_AREA - Financial management area

Data type: FIKRS
Optional: No
Call by Reference: Yes

I_FUNCAREA - Functional Area

Data type: FM_FAREA
Optional: Yes
Call by Reference: Yes

I_MEASURE - Measure in Funds Management

Data type: FM_MEASURE
Optional: Yes
Call by Reference: Yes

I_USERDIM - Customer field for FM actual and commitment data

Data type: FM_USERDIM
Optional: Yes
Call by Reference: Yes

I_T_IGNORED_PA - Table with FM account assignments

Data type: FMKU_T_DIMPART
Optional: Yes
Call by Reference: Yes

I_FISCYEAR - Fiscal Year

Data type: GJAHR
Optional: Yes
Call by Reference: Yes

I_T_RANGE_FISCYEAR - Range for fiscal year

Data type: FMBS_T_RGJAHR
Optional: Yes
Call by Reference: Yes

I_PLDNR - Posting Ledger Number

Data type: BUBAS_PLDNR
Optional: Yes
Call by Reference: Yes

I_F_ADDRESS - FM account assignments

Data type: FMKU_S_DIMPART
Optional: Yes
Call by Reference: Yes

I_FUND - Fund

Data type: BP_GEBER
Optional: Yes
Call by Reference: Yes

I_BUDGET_PD - FM: Budget Period

Data type: FM_BUDGET_PERIOD
Optional: Yes
Call by Reference: Yes

I_FUNDSCTR - Funds Center

Data type: FISTL
Optional: Yes
Call by Reference: Yes

I_CMMTITEM - Commitment item

Data type: FM_FIPEX
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMBAS_CHECK_PA_EXISTENCY

E_FLG_PA_EXISTS - Posting address exists for the selection

Data type: XFELD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

TOO_MANY_PARAMETERS - More than one dimension/address has been specifed

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

INVALID_POSTING_LEDGER - Posting ledger is not supported

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMBAS_CHECK_PA_EXISTENCY 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_i_fm_area  TYPE FIKRS, "   
lv_e_flg_pa_exists  TYPE XFELD, "   
lv_too_many_parameters  TYPE XFELD, "   
lv_i_funcarea  TYPE FM_FAREA, "   
lv_i_measure  TYPE FM_MEASURE, "   
lv_i_userdim  TYPE FM_USERDIM, "   
lv_i_t_ignored_pa  TYPE FMKU_T_DIMPART, "   
lv_i_fiscyear  TYPE GJAHR, "   
lv_invalid_posting_ledger  TYPE GJAHR, "   
lv_i_t_range_fiscyear  TYPE FMBS_T_RGJAHR, "   
lv_i_pldnr  TYPE BUBAS_PLDNR, "   
lv_i_f_address  TYPE FMKU_S_DIMPART, "   
lv_i_fund  TYPE BP_GEBER, "   
lv_i_budget_pd  TYPE FM_BUDGET_PERIOD, "   
lv_i_fundsctr  TYPE FISTL, "   
lv_i_cmmtitem  TYPE FM_FIPEX. "   

  CALL FUNCTION 'FMBAS_CHECK_PA_EXISTENCY'  "Check if posting address exists in list of budget structure (FMBASIDX)
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_FUNCAREA = lv_i_funcarea
         I_MEASURE = lv_i_measure
         I_USERDIM = lv_i_userdim
         I_T_IGNORED_PA = lv_i_t_ignored_pa
         I_FISCYEAR = lv_i_fiscyear
         I_T_RANGE_FISCYEAR = lv_i_t_range_fiscyear
         I_PLDNR = lv_i_pldnr
         I_F_ADDRESS = lv_i_f_address
         I_FUND = lv_i_fund
         I_BUDGET_PD = lv_i_budget_pd
         I_FUNDSCTR = lv_i_fundsctr
         I_CMMTITEM = lv_i_cmmtitem
    IMPORTING
         E_FLG_PA_EXISTS = lv_e_flg_pa_exists
    EXCEPTIONS
        TOO_MANY_PARAMETERS = 1
        INVALID_POSTING_LEDGER = 2
. " FMBAS_CHECK_PA_EXISTENCY




ABAP code using 7.40 inline data declarations to call FM FMBAS_CHECK_PA_EXISTENCY

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!