BAPI_OBJCL_GETOBJECTS — Find Objects by Classification Assignment

Finds objects that satisfy a classification assignment/value selection. SAP lists it as a released ObjectClassification BAPI. It is read-only and supports classification-based discovery without requiring direct joins across classification assignment and characteristic-value tables. 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.

When listing objects assigned to a class, scope the request using the class and class type required by the classification model. A result set may reflect configuration and authorization limitations and should not be mistaken for a complete cross-system product list. Where characteristics or object keys are involved, resolve the exact object table/key formatting before correlating assignments with material or equipment masters. Cross-check with an approved classification view and use bounded pagination or selection in high-volume cases if the active interface supports it.

BAPI_OBJCL_GETOBJECTS 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_GETOBJECTS 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-to-object search can return a bounded set of classified objects, but the result is not an unrestricted list of all materials. Confirm exact class name/type, status, characteristic selection and maximum rows in the active interface. Compare a known classified material with the selected class and one material that has no matching assignment. SAP notes that classification retrieval and change-management validity can affect which objects are returned. A limit reached does not establish that no other matching objects exist; handle result limits explicitly and avoid querying thousands of objects without a bounded search. Read back a sample returned object through BAPI_OBJCL_GETDETAIL and validate the business key and type. Search BAPIs read committed classification data, so uncommitted changes are not reliably visible.