SAP BAPI_RECORD_GETELEMENTS Function Module for Find Record Elements
BAPI_RECORD_GETELEMENTS is a standard bapi record getelements SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find Record Elements 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 bapi record getelements FM, simply by entering the name BAPI_RECORD_GETELEMENTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRM_BAPI_RECORD
Program Name: SAPLSRM_BAPI_RECORD
Main Program: SAPLSRM_BAPI_RECORD
Appliation area:
Release date: 09-Jul-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_RECORD_GETELEMENTS 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 'BAPI_RECORD_GETELEMENTS'"Find Record Elements.
EXPORTING
OBJECTID = "Internal ID of Record Instance
DOCUMENTCLASS = "Storage Location of Record Instance
* DOC_CONTEXT = "SRM Context for Document Access
* PARENT_ID = "Element ID of the Higher-Level Node
* OMIT_AUTHORITY_CHECK = ' ' "Perform Authority Check Yes/No
IMPORTING
RETURN = "Return Parameters
TABLES
* ELEMENT = "Elements (Basic Data)
* ELEMENT_IDENTIFICATION = "Element ID
* ELEMENT_PROPERTIES = "Element Attributes
* ELEMENT_VISIBILITY = "Element Roles
* ELEMENT_RELATIONS = "Element Relations
IMPORTING Parameters details for BAPI_RECORD_GETELEMENTS
OBJECTID - Internal ID of Record Instance
Data type: BAPISRMREC-GUIDOptional: No
Call by Reference: No ( called with pass by value option)
DOCUMENTCLASS - Storage Location of Record Instance
Data type: BAPISRMREC-DOCCLASSOptional: No
Call by Reference: No ( called with pass by value option)
DOC_CONTEXT - SRM Context for Document Access
Data type: BAPIDOCCONTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
PARENT_ID - Element ID of the Higher-Level Node
Data type: BAPISRMREC_ELEMENT-ELEMENT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
OMIT_AUTHORITY_CHECK - Perform Authority Check Yes/No
Data type: BAPISRMREC-BOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RECORD_GETELEMENTS
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RECORD_GETELEMENTS
ELEMENT - Elements (Basic Data)
Data type: BAPISRMREC_ELEMENTOptional: Yes
Call by Reference: Yes
ELEMENT_IDENTIFICATION - Element ID
Data type: BAPISRMREC_ELEMENT_IDENTOptional: Yes
Call by Reference: Yes
ELEMENT_PROPERTIES - Element Attributes
Data type: BAPIPROPELEMENTOptional: Yes
Call by Reference: Yes
ELEMENT_VISIBILITY - Element Roles
Data type: BAPIPROPELEMENTOptional: Yes
Call by Reference: Yes
ELEMENT_RELATIONS - Element Relations
Data type: BAPIPROPELEMENTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RECORD_GETELEMENTS 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_return | TYPE BAPIRET2, " | |||
| lt_element | TYPE STANDARD TABLE OF BAPISRMREC_ELEMENT, " | |||
| lv_objectid | TYPE BAPISRMREC-GUID, " | |||
| lv_documentclass | TYPE BAPISRMREC-DOCCLASS, " | |||
| lt_element_identification | TYPE STANDARD TABLE OF BAPISRMREC_ELEMENT_IDENT, " | |||
| lv_doc_context | TYPE BAPIDOCCONTEXT, " | |||
| lt_element_properties | TYPE STANDARD TABLE OF BAPIPROPELEMENT, " | |||
| lv_parent_id | TYPE BAPISRMREC_ELEMENT-ELEMENT_ID, " | |||
| lt_element_visibility | TYPE STANDARD TABLE OF BAPIPROPELEMENT, " | |||
| lt_element_relations | TYPE STANDARD TABLE OF BAPIPROPELEMENT, " | |||
| lv_omit_authority_check | TYPE BAPISRMREC-BOOLEAN. " ' ' |
|   CALL FUNCTION 'BAPI_RECORD_GETELEMENTS' "Find Record Elements |
| EXPORTING | ||
| OBJECTID | = lv_objectid | |
| DOCUMENTCLASS | = lv_documentclass | |
| DOC_CONTEXT | = lv_doc_context | |
| PARENT_ID | = lv_parent_id | |
| OMIT_AUTHORITY_CHECK | = lv_omit_authority_check | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| ELEMENT | = lt_element | |
| ELEMENT_IDENTIFICATION | = lt_element_identification | |
| ELEMENT_PROPERTIES | = lt_element_properties | |
| ELEMENT_VISIBILITY | = lt_element_visibility | |
| ELEMENT_RELATIONS | = lt_element_relations | |
| . " BAPI_RECORD_GETELEMENTS | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RECORD_GETELEMENTS
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.| "SELECT single GUID FROM BAPISRMREC INTO @DATA(ld_objectid). | ||||
| "SELECT single DOCCLASS FROM BAPISRMREC INTO @DATA(ld_documentclass). | ||||
| "SELECT single ELEMENT_ID FROM BAPISRMREC_ELEMENT INTO @DATA(ld_parent_id). | ||||
| "SELECT single BOOLEAN FROM BAPISRMREC INTO @DATA(ld_omit_authority_check). | ||||
| DATA(ld_omit_authority_check) | = ' '. | |||
Search for further information about these or an SAP related objects