SAP BAPI_ODSO_GETDETAIL Function Module for Read Details for a DataStore
BAPI_ODSO_GETDETAIL is a standard bapi odso getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Details for a DataStore 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 odso getdetail FM, simply by entering the name BAPI_ODSO_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAB
Program Name: SAPLRSAB
Main Program: SAPLRSAB
Appliation area: B
Release date: 25-Jul-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_ODSO_GETDETAIL 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_ODSO_GETDETAIL'"Read Details for a DataStore.
EXPORTING
* OBJVERS = RS_C_OBJVERS-ACTIVE "Object version
ODSOBJECT = "DataStore
IMPORTING
DETAILS = "DataStore Object - Details
RETURN = "BAPI return parameter
TABLES
* INFOOBJECTS = "InfoObjects in DataStore Object
* NAVIGATIONATTRIBUTES = "Navigation Attributes for the DataStore Object
* INDEXES = "Indexes for a DataStore Object
* INDEXESINFOOBJECTS = "DataStore Object InfoObjects in Indexes
IMPORTING Parameters details for BAPI_ODSO_GETDETAIL
OBJVERS - Object version
Data type: BAPI6116-OBJVERSDefault: RS_C_OBJVERS-ACTIVE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ODSOBJECT - DataStore
Data type: BAPI6116-ODSOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_ODSO_GETDETAIL
DETAILS - DataStore Object - Details
Data type: BAPI6116Optional: No
Call by Reference: No ( called with pass by value option)
RETURN - BAPI return parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_ODSO_GETDETAIL
INFOOBJECTS - InfoObjects in DataStore Object
Data type: BAPI6116IOOptional: Yes
Call by Reference: Yes
NAVIGATIONATTRIBUTES - Navigation Attributes for the DataStore Object
Data type: BAPI6116NAOptional: Yes
Call by Reference: Yes
INDEXES - Indexes for a DataStore Object
Data type: BAPI6116INOptional: Yes
Call by Reference: Yes
INDEXESINFOOBJECTS - DataStore Object InfoObjects in Indexes
Data type: BAPI6116IIOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_ODSO_GETDETAIL 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_details | TYPE BAPI6116, " | |||
| lv_objvers | TYPE BAPI6116-OBJVERS, " RS_C_OBJVERS-ACTIVE | |||
| lt_infoobjects | TYPE STANDARD TABLE OF BAPI6116IO, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_odsobject | TYPE BAPI6116-ODSOBJECT, " | |||
| lt_navigationattributes | TYPE STANDARD TABLE OF BAPI6116NA, " | |||
| lt_indexes | TYPE STANDARD TABLE OF BAPI6116IN, " | |||
| lt_indexesinfoobjects | TYPE STANDARD TABLE OF BAPI6116II. " |
|   CALL FUNCTION 'BAPI_ODSO_GETDETAIL' "Read Details for a DataStore |
| EXPORTING | ||
| OBJVERS | = lv_objvers | |
| ODSOBJECT | = lv_odsobject | |
| IMPORTING | ||
| DETAILS | = lv_details | |
| RETURN | = lv_return | |
| TABLES | ||
| INFOOBJECTS | = lt_infoobjects | |
| NAVIGATIONATTRIBUTES | = lt_navigationattributes | |
| INDEXES | = lt_indexes | |
| INDEXESINFOOBJECTS | = lt_indexesinfoobjects | |
| . " BAPI_ODSO_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_ODSO_GETDETAIL
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 OBJVERS FROM BAPI6116 INTO @DATA(ld_objvers). | ||||
| DATA(ld_objvers) | = RS_C_OBJVERS-ACTIVE. | |||
| "SELECT single ODSOBJECT FROM BAPI6116 INTO @DATA(ld_odsobject). | ||||
Search for further information about these or an SAP related objects