SAP GM_BAPI_FIELD_STATUS Function Module for Get field status for BAPI field









GM_BAPI_FIELD_STATUS is a standard gm bapi field status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get field status for BAPI field 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 gm bapi field status FM, simply by entering the name GM_BAPI_FIELD_STATUS into the relevant SAP transaction such as SE37 or SE38.

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



Function GM_BAPI_FIELD_STATUS 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 'GM_BAPI_FIELD_STATUS'"Get field status for BAPI field
EXPORTING
I_GRANT_TYPE = "Grant Type
I_LIFECYCLE_STATUS = "Lifecycle Status
I_USER_STATUS = "User-Defined State
I_BAPI_STRUCTURE = "BP: BAPI Structure Name in Database
I_BAPI_FIELD_NAME = "Field Name from BAPI Structure

IMPORTING
E_FIELD_STATUS = "Field status (req. entry, opt. entry, display, hidden)
.



IMPORTING Parameters details for GM_BAPI_FIELD_STATUS

I_GRANT_TYPE - Grant Type

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

I_LIFECYCLE_STATUS - Lifecycle Status

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

I_USER_STATUS - User-Defined State

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

I_BAPI_STRUCTURE - BP: BAPI Structure Name in Database

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

I_BAPI_FIELD_NAME - Field Name from BAPI Structure

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

EXPORTING Parameters details for GM_BAPI_FIELD_STATUS

E_FIELD_STATUS - Field status (req. entry, opt. entry, display, hidden)

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

Copy and paste ABAP code example for GM_BAPI_FIELD_STATUS 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_grant_type  TYPE GM_GRANT_TYPE, "   
lv_e_field_status  TYPE BU_FLDSTAT, "   
lv_i_lifecycle_status  TYPE GM_LIFECYCLE_STATUS, "   
lv_i_user_status  TYPE GM_USER_STATUS, "   
lv_i_bapi_structure  TYPE BU_BAPISTRC, "   
lv_i_bapi_field_name  TYPE BU_BAPIFLDNM. "   

  CALL FUNCTION 'GM_BAPI_FIELD_STATUS'  "Get field status for BAPI field
    EXPORTING
         I_GRANT_TYPE = lv_i_grant_type
         I_LIFECYCLE_STATUS = lv_i_lifecycle_status
         I_USER_STATUS = lv_i_user_status
         I_BAPI_STRUCTURE = lv_i_bapi_structure
         I_BAPI_FIELD_NAME = lv_i_bapi_field_name
    IMPORTING
         E_FIELD_STATUS = lv_e_field_status
. " GM_BAPI_FIELD_STATUS




ABAP code using 7.40 inline data declarations to call FM GM_BAPI_FIELD_STATUS

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!