BAPI_CLASS_GETSTATUS — Read Classification Class Status

Returns status information for a specified SAP Classification class. SAP lists it as a released class BAPI. It is read-only and helps integrations determine whether the class is in an appropriate state before assignment, change, deletion, or other classification processing. 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 class status lookup, provide the correct class identification and class type; status from an unrelated class type does not describe whether the intended classification object is ready for use. Confirm that the class exists and is valid for the queried configuration before interpreting a returned status value. If the result appears inconsistent with classification maintenance, compare the same object in the authorized classification display and check the SE37 function interface for release-specific parameters instead of inventing a status constant.

BAPI_CLASS_GETSTATUS 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_CLASS_GETSTATUS 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.

A class status is a governance state, not evidence that every object assigned to the class is valid or that all required characteristics are present. For a class technical key and type, retrieve its status and compare against an authorized class maintenance display. If a class is inactive, determine whether new classifications are prohibited while historical reads remain allowed in the installed configuration. Test one active and one restricted class and inspect return messages, including an unknown class type. Do not bypass release/status controls by creating equivalent duplicate classes with a new number. A correct support answer separates class status, object classification status and individual characteristic validation, because each represents a different business question.