SAP HR_GB_EF_BC_GETMESSAGEBOX Function Module for HR:GB e-filing: Call SAP BC GetMessageBox









HR_GB_EF_BC_GETMESSAGEBOX is a standard hr gb ef bc getmessagebox SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HR:GB e-filing: Call SAP BC GetMessageBox 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 hr gb ef bc getmessagebox FM, simply by entering the name HR_GB_EF_BC_GETMESSAGEBOX into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_GB_EF_BC_GETMESSAGEBOX 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 'HR_GB_EF_BC_GETMESSAGEBOX'"HR:GB e-filing: Call SAP BC GetMessageBox
  EXPORTING
   TICKETBOOK =  "Sesssion ID
   FOLDER =  "The folder from which serice is read
   SERVICE =  "The service that is read
   RUNTYPE =  "Run Type (Production or Test)

 IMPORTING
   XMLFILE =  " File containing Message ids that can be extracted
   RESULT =  "Status of the RPC
   LONGTEXT =  "Long Text of any error message

EXCEPTIONS
   SYSTEM_FAILURE = 1    COMMUNICATION_FAILURE = 2    NO_INPUT_GIVEN = 3    OTHERS = 4
.



IMPORTING Parameters details for HR_GB_EF_BC_GETMESSAGEBOX

TICKETBOOK - Sesssion ID

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

FOLDER - The folder from which serice is read

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

SERVICE - The service that is read

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

RUNTYPE - Run Type (Production or Test)

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

EXPORTING Parameters details for HR_GB_EF_BC_GETMESSAGEBOX

XMLFILE - File containing Message ids that can be extracted

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

RESULT - Status of the RPC

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

LONGTEXT - Long Text of any error message

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

EXCEPTIONS details

SYSTEM_FAILURE - System failure

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_FAILURE - Communication failure

Data type:
Optional: No
Call by Reference: Yes

NO_INPUT_GIVEN - No input given

Data type:
Optional: No
Call by Reference: Yes

OTHERS - Others

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_GB_EF_BC_GETMESSAGEBOX 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_xmlfile  TYPE STRING, "   
lv_ticketbook  TYPE STRING, "   
lv_system_failure  TYPE STRING, "   
lv_folder  TYPE STRING, "   
lv_result  TYPE STRING, "   
lv_communication_failure  TYPE STRING, "   
lv_service  TYPE I, "   
lv_longtext  TYPE STRING, "   
lv_no_input_given  TYPE STRING, "   
lv_others  TYPE STRING, "   
lv_runtype  TYPE I. "   

  CALL FUNCTION 'HR_GB_EF_BC_GETMESSAGEBOX'  "HR:GB e-filing: Call SAP BC GetMessageBox
    EXPORTING
         TICKETBOOK = lv_ticketbook
         FOLDER = lv_folder
         SERVICE = lv_service
         RUNTYPE = lv_runtype
    IMPORTING
         XMLFILE = lv_xmlfile
         RESULT = lv_result
         LONGTEXT = lv_longtext
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        COMMUNICATION_FAILURE = 2
        NO_INPUT_GIVEN = 3
        OTHERS = 4
. " HR_GB_EF_BC_GETMESSAGEBOX




ABAP code using 7.40 inline data declarations to call FM HR_GB_EF_BC_GETMESSAGEBOX

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!