SAP FMCU_CHECK_STATUS_ASSIGNMENT Function Module for Check status assignment









FMCU_CHECK_STATUS_ASSIGNMENT is a standard fmcu check status assignment 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 status assignment 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 fmcu check status assignment FM, simply by entering the name FMCU_CHECK_STATUS_ASSIGNMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCU_CHECK_STATUS_ASSIGNMENT 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 'FMCU_CHECK_STATUS_ASSIGNMENT'"Check status assignment
EXPORTING
I_FM_AREA = "Financial management area
I_VERSION = "Version
I_FUND = "Fund
I_FISCYEAR = "Fiscal year
* I_FLG_TEXT = "Flag for status text

IMPORTING
E_STATUS = "Budgeting status
E_STATUS_TXT = "Status long text (50)

EXCEPTIONS
NO_STATUS_ASSIGNED = 1
.



IMPORTING Parameters details for FMCU_CHECK_STATUS_ASSIGNMENT

I_FM_AREA - Financial management area

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

I_VERSION - Version

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

I_FUND - Fund

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

I_FISCYEAR - Fiscal year

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

I_FLG_TEXT - Flag for status text

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

EXPORTING Parameters details for FMCU_CHECK_STATUS_ASSIGNMENT

E_STATUS - Budgeting status

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

E_STATUS_TXT - Status long text (50)

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

EXCEPTIONS details

NO_STATUS_ASSIGNED - No status assigned

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMCU_CHECK_STATUS_ASSIGNMENT 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_status  TYPE BUCU_STATUS, "   
lv_i_fm_area  TYPE FIKRS, "   
lv_no_status_assigned  TYPE FIKRS, "   
lv_i_version  TYPE BUKU_VERSION, "   
lv_e_status_txt  TYPE BUCU_STAT50, "   
lv_i_fund  TYPE BP_GEBER, "   
lv_i_fiscyear  TYPE GJAHR, "   
lv_i_flg_text  TYPE XFELD. "   

  CALL FUNCTION 'FMCU_CHECK_STATUS_ASSIGNMENT'  "Check status assignment
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_VERSION = lv_i_version
         I_FUND = lv_i_fund
         I_FISCYEAR = lv_i_fiscyear
         I_FLG_TEXT = lv_i_flg_text
    IMPORTING
         E_STATUS = lv_e_status
         E_STATUS_TXT = lv_e_status_txt
    EXCEPTIONS
        NO_STATUS_ASSIGNED = 1
. " FMCU_CHECK_STATUS_ASSIGNMENT




ABAP code using 7.40 inline data declarations to call FM FMCU_CHECK_STATUS_ASSIGNMENT

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!