SAP EXIT_SAPLFMCF_BUD_002 Function Module for ISPS: FYC Budget: Can Approved/Requested Amount Be Negative









EXIT_SAPLFMCF_BUD_002 is a standard exit saplfmcf bud 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ISPS: FYC Budget: Can Approved/Requested Amount Be Negative 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 exit saplfmcf bud 002 FM, simply by entering the name EXIT_SAPLFMCF_BUD_002 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLFMCF_BUD_002 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 'EXIT_SAPLFMCF_BUD_002'"ISPS: FYC Budget: Can Approved/Requested Amount Be Negative
EXPORTING
I_F_HEADER = "General Data
I_F_OBJECT = "FM account assignment

IMPORTING
E_FLG_NEG_ALLOWED = "Negative Amounts Allowed (Approved/Requested)
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
CF_GET_PRC_AMOUNTS_BPAK
FMCFAAS_DELETE
FMCFAAS_DELETE_FROM_TABLE
FMCFAAS_READ
FMCFAAS_UPDATE_WITH_TABLE
FMCFAA_DELETE
FMCFAA_DELETE_FROM_TABLE
FMCFAA_READ
FMCFAA_UPDATE_WITH_TABLE
FMCFABS_DELETE
FMCFABS_DELETE_FROM_TABLE
FMCFABS_READ
FMCFABS_UPDATE_WITH_TABLE
FMCFAB_DELETE
FMCFAB_DELETE_FROM_TABLE
FMCFAB_READ
FMCFAB_UPDATE_WITH_TABLE
FMCFBPAKS_DELETE
FMCFBPAKS_DELETE_FROM_TABLE
FMCFBPAKS_READ
FMCFBPAKS_UPDATE_FROM_TABLE
FMCFBU_DELETE
FMCFSIF_DELETE
FMCFSIO_DELETE
FMCF_DELETE_ALL
FMCF_DISPLAY_DOCUMENT
FMCF_DISPLAY_ITEMS
FMCF_GET_USERDIM_DESCRIPTION
FM_CF_CHECK_FI_DOC
FM_CF_GET_REC_FUNDS
FM_CF_GET_REC_FUNDS_FROM_TAB
FM_CHECK_NEGBUDGET_ALLOWED

IMPORTING Parameters details for EXIT_SAPLFMCF_BUD_002

I_F_HEADER - General Data

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

I_F_OBJECT - FM account assignment

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

EXPORTING Parameters details for EXIT_SAPLFMCF_BUD_002

E_FLG_NEG_ALLOWED - Negative Amounts Allowed (Approved/Requested)

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

Copy and paste ABAP code example for EXIT_SAPLFMCF_BUD_002 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_f_header  TYPE FMCFBAH, "   
lv_e_flg_neg_allowed  TYPE FMCFBAH, "   
lv_i_f_object  TYPE FMCFBAO. "   

  CALL FUNCTION 'EXIT_SAPLFMCF_BUD_002'  "ISPS: FYC Budget: Can Approved/Requested Amount Be Negative
    EXPORTING
         I_F_HEADER = lv_i_f_header
         I_F_OBJECT = lv_i_f_object
    IMPORTING
         E_FLG_NEG_ALLOWED = lv_e_flg_neg_allowed
. " EXIT_SAPLFMCF_BUD_002




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLFMCF_BUD_002

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!