SAP /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ Function Module for Get Single Records from Database
/BA1/F4_OBJ_SEC_BUFFER_GET_OBJ is a standard /ba1/f4 obj sec buffer get obj 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 Single Records from Database 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 /ba1/f4 obj sec buffer get obj FM, simply by entering the name /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: /BA1/F4_OBJ_SEC
Program Name: /BA1/SAPLF4_OBJ_SEC
Main Program: /BA1/SAPLF4_OBJ_SEC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ 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 '/BA1/F4_OBJ_SEC_BUFFER_GET_OBJ'"Get Single Records from Database.
EXPORTING
* I_TAB_SEC_SEL = "Key for All Versions of a Security Object
* I_TAB_INTGUID = "GUID in 'RAW' Format
* I_VALID_DATE = "Date
I_REL_STATUS = "Status of the Release
IMPORTING
E_SECRATE = "Securities DB Table Structure Exchange Rate Data
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ
I_TAB_SEC_SEL - Key for All Versions of a Security Object
Data type: /BA1/F4_TAB_SECRATE_OBJKEYOptional: Yes
Call by Reference: Yes
I_TAB_INTGUID - GUID in 'RAW' Format
Data type: /BA1/F4_TAB_GUIDOptional: Yes
Call by Reference: Yes
I_VALID_DATE - Date
Data type: /BA1/F4_DTE_VALID_DATSOptional: Yes
Call by Reference: Yes
I_REL_STATUS - Status of the Release
Data type: /BA1/F4_DTE_REL_STATUSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ
E_SECRATE - Securities DB Table Structure Exchange Rate Data
Data type: /BA1/F4_TAB_SEC_EXTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - No record found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ 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_e_secrate | TYPE /BA1/F4_TAB_SEC_EXT, " | |||
| lv_not_found | TYPE /BA1/F4_TAB_SEC_EXT, " | |||
| lv_i_tab_sec_sel | TYPE /BA1/F4_TAB_SECRATE_OBJKEY, " | |||
| lv_i_tab_intguid | TYPE /BA1/F4_TAB_GUID, " | |||
| lv_i_valid_date | TYPE /BA1/F4_DTE_VALID_DATS, " | |||
| lv_i_rel_status | TYPE /BA1/F4_DTE_REL_STATUS. " |
|   CALL FUNCTION '/BA1/F4_OBJ_SEC_BUFFER_GET_OBJ' "Get Single Records from Database |
| EXPORTING | ||
| I_TAB_SEC_SEL | = lv_i_tab_sec_sel | |
| I_TAB_INTGUID | = lv_i_tab_intguid | |
| I_VALID_DATE | = lv_i_valid_date | |
| I_REL_STATUS | = lv_i_rel_status | |
| IMPORTING | ||
| E_SECRATE | = lv_e_secrate | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM /BA1/F4_OBJ_SEC_BUFFER_GET_OBJ
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