SAP BAPI_OBJCL_GETDETAIL Function Module for Classification BAPI: Read Classification Information on Object
BAPI_OBJCL_GETDETAIL is a standard bapi objcl 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 Classification BAPI: Read Classification Information on Object 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 objcl getdetail FM, simply by entering the name BAPI_OBJCL_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: CLBPA
Program Name: SAPLCLBPA
Main Program: SAPLCLBPA
Appliation area: M
Release date: 25-Nov-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_OBJCL_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_OBJCL_GETDETAIL'"Classification BAPI: Read Classification Information on Object.
EXPORTING
OBJECTKEY = "Object Key, Concatenated
OBJECTTABLE = "Classification BAPI - Key Fields
CLASSNUM = "Class Number
CLASSTYPE = "Class Type
* KEYDATE = SY-DATUM "Date
* UNVALUATED_CHARS = ' ' "Output Characteristics Without Assigned Values
* LANGUAGE = SY-LANGU "Language Key
IMPORTING
STATUS = "Classification Status
STANDARDCLASS = "Indicator: Standard Class
TABLES
ALLOCVALUESNUM = "Numeric Values
ALLOCVALUESCHAR = "Alphanumeric Values
ALLOCVALUESCURR = "Currency Values
RETURN = "Error Messages
IMPORTING Parameters details for BAPI_OBJCL_GETDETAIL
OBJECTKEY - Object Key, Concatenated
Data type: BAPI1003_KEY-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTTABLE - Classification BAPI - Key Fields
Data type: BAPI1003_KEY-OBJECTTABLEOptional: No
Call by Reference: No ( called with pass by value option)
CLASSNUM - Class Number
Data type: BAPI1003_KEY-CLASSNUMOptional: No
Call by Reference: No ( called with pass by value option)
CLASSTYPE - Class Type
Data type: BAPI1003_KEY-CLASSTYPEOptional: No
Call by Reference: No ( called with pass by value option)
KEYDATE - Date
Data type: BAPI1003_KEY-KEYDATEDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
UNVALUATED_CHARS - Output Characteristics Without Assigned Values
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGUAGE - Language Key
Data type: BAPIFIELDSCACL-BAPILANGUADefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_OBJCL_GETDETAIL
STATUS - Classification Status
Data type: BAPI1003_KEY-STATUSOptional: No
Call by Reference: No ( called with pass by value option)
STANDARDCLASS - Indicator: Standard Class
Data type: BAPI1003_KEY-STDCLASSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_OBJCL_GETDETAIL
ALLOCVALUESNUM - Numeric Values
Data type: BAPI1003_ALLOC_VALUES_NUMOptional: No
Call by Reference: Yes
ALLOCVALUESCHAR - Alphanumeric Values
Data type: BAPI1003_ALLOC_VALUES_CHAROptional: No
Call by Reference: Yes
ALLOCVALUESCURR - Currency Values
Data type: BAPI1003_ALLOC_VALUES_CURROptional: No
Call by Reference: Yes
RETURN - Error Messages
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_OBJCL_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_status | TYPE BAPI1003_KEY-STATUS, " | |||
| lv_objectkey | TYPE BAPI1003_KEY-OBJECT, " | |||
| lt_allocvaluesnum | TYPE STANDARD TABLE OF BAPI1003_ALLOC_VALUES_NUM, " | |||
| lv_objecttable | TYPE BAPI1003_KEY-OBJECTTABLE, " | |||
| lv_standardclass | TYPE BAPI1003_KEY-STDCLASS, " | |||
| lt_allocvalueschar | TYPE STANDARD TABLE OF BAPI1003_ALLOC_VALUES_CHAR, " | |||
| lv_classnum | TYPE BAPI1003_KEY-CLASSNUM, " | |||
| lt_allocvaluescurr | TYPE STANDARD TABLE OF BAPI1003_ALLOC_VALUES_CURR, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_classtype | TYPE BAPI1003_KEY-CLASSTYPE, " | |||
| lv_keydate | TYPE BAPI1003_KEY-KEYDATE, " SY-DATUM | |||
| lv_unvaluated_chars | TYPE FLAG, " SPACE | |||
| lv_language | TYPE BAPIFIELDSCACL-BAPILANGUA. " SY-LANGU |
|   CALL FUNCTION 'BAPI_OBJCL_GETDETAIL' "Classification BAPI: Read Classification Information on Object |
| EXPORTING | ||
| OBJECTKEY | = lv_objectkey | |
| OBJECTTABLE | = lv_objecttable | |
| CLASSNUM | = lv_classnum | |
| CLASSTYPE | = lv_classtype | |
| KEYDATE | = lv_keydate | |
| UNVALUATED_CHARS | = lv_unvaluated_chars | |
| LANGUAGE | = lv_language | |
| IMPORTING | ||
| STATUS | = lv_status | |
| STANDARDCLASS | = lv_standardclass | |
| TABLES | ||
| ALLOCVALUESNUM | = lt_allocvaluesnum | |
| ALLOCVALUESCHAR | = lt_allocvalueschar | |
| ALLOCVALUESCURR | = lt_allocvaluescurr | |
| RETURN | = lt_return | |
| . " BAPI_OBJCL_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_OBJCL_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 STATUS FROM BAPI1003_KEY INTO @DATA(ld_status). | ||||
| "SELECT single OBJECT FROM BAPI1003_KEY INTO @DATA(ld_objectkey). | ||||
| "SELECT single OBJECTTABLE FROM BAPI1003_KEY INTO @DATA(ld_objecttable). | ||||
| "SELECT single STDCLASS FROM BAPI1003_KEY INTO @DATA(ld_standardclass). | ||||
| "SELECT single CLASSNUM FROM BAPI1003_KEY INTO @DATA(ld_classnum). | ||||
| "SELECT single CLASSTYPE FROM BAPI1003_KEY INTO @DATA(ld_classtype). | ||||
| "SELECT single KEYDATE FROM BAPI1003_KEY INTO @DATA(ld_keydate). | ||||
| DATA(ld_keydate) | = SY-DATUM. | |||
| DATA(ld_unvaluated_chars) | = ' '. | |||
| "SELECT single BAPILANGUA FROM BAPIFIELDSCACL INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects