BAPI_OBJCL_GETDETAIL — Read an Object's Classification Detail

Returns detailed classification information and characteristic values for a non-class object in a specified class. SAP documents separate tables for numeric/date/time, character/boolean, and currency characteristic values. The object key must follow internal-format rules; the BAPI is read-only and requires no commit. SAP's Classification documentation lists this interface in the released BAPI catalog for the corresponding class, object-classification, characteristic, or hierarchy business function. Use it instead of direct updates to classification master and assignment tables.

Classification BAPIs are sensitive to exact technical identity. The active SE37 interface is authoritative for field names, but the recurring business inputs are class name/type, object table and object key, characteristic name/value, key date/change number, language, status, and typed value tables for character, numeric/date/time, or currency values.

For an assigned object's classification, check the object table, class type, object key and class identification at the expected validity/context. A valid business material number does not always equal the concatenated technical key expected by a classification function; use the installed interface's conversion rules. Compare single-value and multi-value characteristic data separately and preserve unit/language semantics. If a characteristic is absent, confirm the class assignment and authorization before treating its value as deleted.

BAPI_OBJCL_GETDETAIL is read/check/key-conversion logic and does not require BAPI_TRANSACTION_COMMIT. Check RETURN plus the actual result because 'no matching class/object/value' can be a valid outcome distinct from a technical error.

SAP Classification documentation consistently states that a successful BAPI should not return messages of type E. Process the complete RETURN table, not only SY-SUBRC. For writes, also verify the intended class, assignment, characteristic, or hierarchy relationship after commit. For reads, treat empty result tables as meaningful only after confirming object key, class type, key date, language, and authorization.

SAP still publishes these Classification BAPIs in current support documentation, and SAP's ABAP Cloud migration guidance even demonstrates wrapping BAPI_OBJCL_CREATE behind a released wrapper when classic BAPI business logic must be reused. That does not make the BAPI itself directly released for ABAP Cloud; new clean-core code should use released wrappers/APIs where required.

Master-data/classification ownership normally sits with the functional data-governance team responsible for the object being classified. MDG/data migration teams own governance and mapping at scale. ABAP/integration developers own key construction, typed value mapping, RETURN handling, transaction control, and safe reuse in clean-core architectures.

Inspect BAPI_OBJCL_GETDETAIL in SE37 and use SAP's Classification BAPI documentation as the semantic reference. For object classification, verify class assignments and characteristic values in the standard classification transactions/apps; for class/characteristic hierarchy work, validate the affected class type and where-used relationships before and after a write.

SAP documentation specifies ObjectKey, ObjectTable, ClassNum and ClassType for BAPI_OBJCL_GETDETAIL, with optional key date and language context. The object key should use internal format, such as material numbers retaining necessary leading zeros. Result values are split by characteristic type—ALLOCVALUESCHAR, ALLOCVALUESNUM and ALLOCVALUESCURR—so reading only the character table can falsely report 'no classification.' Compare one material with a numeric characteristic and one with a character characteristic, then reconcile values with an authorized classification display. Note that assigned classification values are different from configuration values. An empty result should be investigated for wrong class type, object table, key date or authorization before diagnosing deleted master data. This is read-only; no update commit is appropriate.