SAP BGRFC_CHECK_UNIT_STATE_SERVER Function Module for

Search SAP Function Modules

BGRFC_CHECK_UNIT_STATE_SERVER is a standard bgrfc check unit state server SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bgrfc check unit state server FM, simply by entering the name BGRFC_CHECK_UNIT_STATE_SERVER into the relevant SAP transaction such as SE37 or SE38.

Function Group: BGRFC_EXTERN
Program Name: SAPLBGRFC_EXTERN
Main Program: SAPLBGRFC_EXTERN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BGRFC_CHECK_UNIT_STATE_SERVER 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 'BGRFC_CHECK_UNIT_STATE_SERVER'"
  EXPORTING
*  UNIT_ID =  "
*  UNIT_KIND =  "

 IMPORTING
   STATE =  "
   MAX_WPRUN_TIME =  "
   COMMUNICATION_FAILURE =  "
   SYSTEM_FAILURE =  "
   INSTANCE_NAME =  "

EXCEPTIONS
   BGRFC_INVALID_PARAMETER = 1    BGRFC_SYS_CALL_NOT_SUPPORTED = 2 

.

IMPORTING Parameters details for BGRFC_CHECK_UNIT_STATE_SERVER

UNIT_ID -

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

UNIT_KIND -

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

EXPORTING Parameters details for BGRFC_CHECK_UNIT_STATE_SERVER

STATE -

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

MAX_WPRUN_TIME -

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

COMMUNICATION_FAILURE -

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

SYSTEM_FAILURE -

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

INSTANCE_NAME -

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

EXCEPTIONS details

BGRFC_INVALID_PARAMETER -

Data type:
Optional: No
Call by Reference: Yes

BGRFC_SYS_CALL_NOT_SUPPORTED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BGRFC_CHECK_UNIT_STATE_SERVER 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.

ABAP code using 7.40 inline data declarations to call FM BGRFC_CHECK_UNIT_STATE_SERVER

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