SAP FMCA_FPF_FB_HEADER_CHECK Function Module for FPF: Check Form Bundle Header









FMCA_FPF_FB_HEADER_CHECK is a standard fmca fpf fb header check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FPF: Check Form Bundle Header 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 fmca fpf fb header check FM, simply by entering the name FMCA_FPF_FB_HEADER_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_FPF_FB_HEADER_CHECK 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 'FMCA_FPF_FB_HEADER_CHECK'"FPF: Check Form Bundle Header
EXPORTING
IS_FMCA_RETURN = "Upload Structure for Process Objects
* IV_CHANGE_TYPE = 'U' "Change type (U, I, E, D)

EXCEPTIONS
INVALID_FBNUM = 1 INVALID_FBTYP_ABTYP = 2 INCOMPLETE_MASTER_DATA = 3 INVALID_MASTER_DATA = 4 ERROR_FOUND = 5
.



IMPORTING Parameters details for FMCA_FPF_FB_HEADER_CHECK

IS_FMCA_RETURN - Upload Structure for Process Objects

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

IV_CHANGE_TYPE - Change type (U, I, E, D)

Data type: CDCHNGIND
Default: 'U'
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INVALID_FBNUM -

Data type:
Optional: No
Call by Reference: Yes

INVALID_FBTYP_ABTYP -

Data type:
Optional: No
Call by Reference: Yes

INCOMPLETE_MASTER_DATA -

Data type:
Optional: No
Call by Reference: Yes

INVALID_MASTER_DATA -

Data type:
Optional: No
Call by Reference: Yes

ERROR_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMCA_FPF_FB_HEADER_CHECK 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_invalid_fbnum  TYPE STRING, "   
lv_is_fmca_return  TYPE FMCA_POBJ_S, "   
lv_iv_change_type  TYPE CDCHNGIND, "   'U'
lv_invalid_fbtyp_abtyp  TYPE CDCHNGIND, "   
lv_incomplete_master_data  TYPE CDCHNGIND, "   
lv_invalid_master_data  TYPE CDCHNGIND, "   
lv_error_found  TYPE CDCHNGIND. "   

  CALL FUNCTION 'FMCA_FPF_FB_HEADER_CHECK'  "FPF: Check Form Bundle Header
    EXPORTING
         IS_FMCA_RETURN = lv_is_fmca_return
         IV_CHANGE_TYPE = lv_iv_change_type
    EXCEPTIONS
        INVALID_FBNUM = 1
        INVALID_FBTYP_ABTYP = 2
        INCOMPLETE_MASTER_DATA = 3
        INVALID_MASTER_DATA = 4
        ERROR_FOUND = 5
. " FMCA_FPF_FB_HEADER_CHECK




ABAP code using 7.40 inline data declarations to call FM FMCA_FPF_FB_HEADER_CHECK

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.

 
 
DATA(ld_iv_change_type) = 'U'.
 
 
 
 
 


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!