SAP GEF_BUF_RFC_GET_BUFFER Function Module for RFC function for getting the buffer
GEF_BUF_RFC_GET_BUFFER is a standard gef buf rfc get buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RFC function for getting the buffer 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 gef buf rfc get buffer FM, simply by entering the name GEF_BUF_RFC_GET_BUFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: GEF_BUFFER
Program Name: SAPLGEF_BUFFER
Main Program: SAPLGEF_BUFFER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GEF_BUF_RFC_GET_BUFFER 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 'GEF_BUF_RFC_GET_BUFFER'"RFC function for getting the buffer.
EXPORTING
IV_INSTANCE_ID = "Instance Name of Shared Buffer Object
IMPORTING
ES_EXCEPTION_ERROR = "Error for the GEF exception
ET_BUFFER_RFC = "Geometry Buffer
EV_BUFFER_START = "Time Stamp in Format YYYYMMDDHHMMSS
IMPORTING Parameters details for GEF_BUF_RFC_GET_BUFFER
IV_INSTANCE_ID - Instance Name of Shared Buffer Object
Data type: GEF_BUFFER_INSTANCE_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GEF_BUF_RFC_GET_BUFFER
ES_EXCEPTION_ERROR - Error for the GEF exception
Data type: GEFS_EXCEPTION_ERROROptional: No
Call by Reference: No ( called with pass by value option)
ET_BUFFER_RFC - Geometry Buffer
Data type: GEFT_GEO_BUFFER_RFCOptional: No
Call by Reference: No ( called with pass by value option)
EV_BUFFER_START - Time Stamp in Format YYYYMMDDHHMMSS
Data type: GEF_DATETIMEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GEF_BUF_RFC_GET_BUFFER 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_iv_instance_id | TYPE GEF_BUFFER_INSTANCE_ID, " | |||
| lv_es_exception_error | TYPE GEFS_EXCEPTION_ERROR, " | |||
| lv_et_buffer_rfc | TYPE GEFT_GEO_BUFFER_RFC, " | |||
| lv_ev_buffer_start | TYPE GEF_DATETIME. " |
|   CALL FUNCTION 'GEF_BUF_RFC_GET_BUFFER' "RFC function for getting the buffer |
| EXPORTING | ||
| IV_INSTANCE_ID | = lv_iv_instance_id | |
| IMPORTING | ||
| ES_EXCEPTION_ERROR | = lv_es_exception_error | |
| ET_BUFFER_RFC | = lv_et_buffer_rfc | |
| EV_BUFFER_START | = lv_ev_buffer_start | |
| . " GEF_BUF_RFC_GET_BUFFER | ||
ABAP code using 7.40 inline data declarations to call FM GEF_BUF_RFC_GET_BUFFER
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