Eclipse ADT and ABAP OO debugging — Root-cause case, remediation and assessment

Training simulation: All sample identifiers, logs, requests, transactions, values and cases are fictional. Tools and permissions vary by SAP release; perform any changes only in approved DEV/QA environments.

Eclipse ADT and ABAP OO debugging — Root-cause case, remediation and assessment

Problem: An HTTP, class method or exception fails outside a classic report run.

Environment: ABAP Development Tools in Eclipse, appropriate development tenant and released APIs for ABAP Cloud.

Incident dossier (fabricated, for education)

METHOD read_order.  DATA(row) = mt_orders[ order_id = iv_order_id ].ENDMETHOD." Fictional test input IV_ORDER_ID='DEMO-77'" mt_orders contains only DEMO-10 and DEMO-11" Expected: controlled not-found result; actual: CX_SY_ITAB_LINE_NOT_FOUND 

Evidence observations

1. The debugger stops where a non-existent internal-table row is dereferenced.
2. The class is running the activated source; the test input and table rows are visible.
3. The final error should be a documented not-found/business response rather than an unhandled runtime termination.

Investigate the three hypotheses

1. A missing key in a table expression raises the exception.
2. The caller passed an invalid order ID but the lookup implementation is correct under a strict invariant.
3. The class was not activated, so an old version was executed and its behavior differs.

Supported hypothesis number(s): 1.

Evidence-backed cause

The synthetic method assumes that every requested key exists and uses a table expression that raises CX_SY_ITAB_LINE_NOT_FOUND when the element is absent.

Safe remediation

Clarify caller contract and handle expected absence explicitly (or raise a specific domain exception); retain authorization checks and build ABAP Unit fixtures for both outcomes.

Six-step resolution runbook

1. Activate the class in a permitted ADT development package; execute an ABAP Unit or class-run fixture with DEMO-77.
2. Set a breakpoint at the table expression, and optionally a CX_SY_ITAB_LINE_NOT_FOUND exception breakpoint.
3. Observe the Variables view and the exact key values. Confirm the key is missing from MT_ORDERS.
4. Inspect the call stack to identify the caller contract: does missing order mean normal absence or a real invariant violation?
5. Implement an explicit OPTIONAL/line_exists-style branch or documented exception mapping, not a blanket CATCH of every error.
6. Run positive, missing-key and authorization-scope tests; inspect final caller response and deactivate diagnostic breakpoints.

Regression evidence

• Positive test: Known key DEMO-10 returns its expected value and keeps normal behavior.
• Negative test: Unknown key DEMO-77 returns a controlled not-found outcome without a short dump.
• Cross-process regression: An unauthorized key is not disclosed through the error or through the query fallback.

Assessment

Question: A class method uses mt_orders[ order_id = iv_order_id ] and CX_SY_ITAB_LINE_NOT_FOUND is raised. What should you examine first?

A. The table keys and intended contract when a row is absent.
B. Disable all exception handling in production.
C. Change the value in the debugger and claim a permanent fix.

Correct: A. Table expression absence and caller semantics determine the safe, testable correction.

Safety boundary: ABAP Cloud development must use released APIs and an authorized development tenant. Do not expose internal values in HTTP errors or bypass DCL.

Synthetic support case: An HTTP, class method or exception fails outside a classic report run.

The synthetic method assumes that every requested key exists and uses a table expression that raises CX_SY_ITAB_LINE_NOT_FOUND when the element is absent.

• An exception appearing in a UI response may be a deliberately mapped business message rather than an uncaught ABAP exception.
• A breakpoint in an inactive class revision may never correspond to the executed bytecode.
• Stepping backward or jumping does not undo earlier database or object-state changes.

Clarify caller contract and handle expected absence explicitly (or raise a specific domain exception); retain authorization checks and build ABAP Unit fixtures for both outcomes.

• Positive test: Known key DEMO-10 returns its expected value and keeps normal behavior.
• Negative test: Unknown key DEMO-77 returns a controlled not-found outcome without a short dump.
• Cross-process regression: An unauthorized key is not disclosed through the error or through the query fallback.

ABAP Cloud development must use released APIs and an authorized development tenant. Do not expose internal values in HTTP errors or bypass DCL.

Show you can debug in ABAP Development Tools: setting breakpoints in Eclipse, conditional breakpoints, inspecting complex objects and internal tables, debugging RAP and ABAP Cloud code, and using exception breakpoints for modern ABAP syntax.