OBJECTS_OBJREF_NOT_ASSIGNED — Dereferencing an Unbound Object Reference

An object reference variable in ABAP starts life as initial, the equivalent of a null pointer, until something assigns an instance to it with CREATE OBJECT, a factory method, a cast, or an assignment from another reference. OBJECTS_OBJREF_NOT_ASSIGNED is raised the moment code tries to use that still-initial reference: calling obj->method( ), reading obj->attribute, or passing it where an instance is required. The kernel throws exception class CX_SY_REF_IS_INITIAL, which is caught nowhere in the call stack, so it escalates to a short dump. It is not a syntax error and the ABAP compiler cannot catch it, because whether a reference is bound depends on runtime flow, not on the type definition. The line pointed to in the dump is the dereferencing statement, not necessarily the place where the instantiation should have happened.

If the cause is a straightforward missing or misplaced CREATE OBJECT, add it before first use, or move it out of the conditional branch so it always runs, and cover the fix with a unit test for the previously-skipped path. This is a code correction requiring a transport. If the cause is a factory or getter that legitimately returns nothing under some conditions, do not force it to always instantiate; instead add an explicit IS BOUND or IS INITIAL check at every call site and handle the empty case with a defined business outcome, such as an error message or a skip with logging, rather than assuming success. This is also a code change. If the cause is a missing BAdI implementation or missing customizing entry that the factory depends on, the code fix is the defensive check above, but the underlying gap needs a functional or configuration fix, filed as a separate customizing change request, since correcting the ABAP alone will only produce a clean error message instead of a dump, not restore the missing behavior. If the cause is an interface mismatch across custom exits, align the custom implementation's contract with what the caller expects and retest both sides together.

The near-universal first reflex is wrapping the dereferencing line in TRY...CATCH cx_root or catching CX_SY_REF_IS_INITIAL specifically and letting execution fall through silently. This stops the dump but does not create the missing instance, so the intended method call or attribute read simply never happens. Downstream logic that depended on that call's side effect, a posting, a status update, a validation, silently does not run, and the process looks like it completed successfully. This trades a visible, traceable dump for a silent data or process gap that surfaces much later and is far harder to diagnose.

Treat any factory method, getter, or BAdI handler lookup that can plausibly return nothing as requiring a mandatory IS BOUND check at the call site, and enforce this through code review or an ABAP Test Cockpit check on unchecked reference use after known factory patterns. Favor constructor-based instantiation over conditional CREATE OBJECT scattered through branches. Add unit tests that specifically exercise the branch where instantiation is skipped, since that is exactly the path production testing tends to miss.

This is an ABAP development problem in nearly all cases, since the fix is either an instantiation correction or a defensive check in code. Functional involvement is needed only when the unbound reference traces back to missing customizing or an inactive BAdI implementation that a business process owner controls. The handover note should state the reference variable name, the enclosing method, the input or customizing condition that triggers the skip, and whether the gap is coding or configuration.

Closely related to OBJECTS_OBJREF_NOT_ASSIGNED_NO, which covers a related but distinct unbound-reference scenario, and to MOVE_CAST_ERROR when a failed downcast is the reason the reference stayed initial. GETWA_NOT_ASSIGNED and ASSIGN_LENGTH_0 are the field-symbol equivalents of the same class of problem, unassigned dereferencing, but for data references and field symbols rather than object references. Any uncaught-exception dump with CX_SY_REF_IS_INITIAL in the analysis is this same runtime error surfaced through a generic handler.