Released APIs & Extensibility Contracts

• QuestionWhat is "Where to find released APIs"?Tap to revealAnswerFind released APIs three ways: the Released Objects node in ADT, the ABAP APIs catalog at api.sap.com, and an object's API State in its Properties pane.
• QuestionIn "Where to find released APIs", explain:Tap to revealAnswerADT Project Explorer → System Library → Released Objects, filterable by type — the in-system catalog.
• QuestionIn "Where to find released APIs", explain:Tap to revealAnswerapi.sap.com → ABAP APIs — the external, release-spanning reference with signatures.
• QuestionIn "Where to find released APIs", explain:Tap to revealAnswerAn object's Properties pane shows its API State — the fastest in-code verification.
• QuestionIn "Where to find released APIs", explain:Tap to revealAnswerAll three agree; discover with Released Objects, research on api.sap.com, verify in Properties.
• QuestionAnalogy for "Where to find released APIs":Tap to revealAnswerReleased Objects is the in-store catalog, api.sap.com is the manufacturer's public spec sheet, and the Properties pane is the label on the item in your hand.
• QuestionWhat is "High-yield legacy → released replacements"?Tap to revealAnswerSwap legacy calls for released ones: BAPI_USER_GET_DETAIL→XCO_CP_USER, CONVERSION_EXIT_ALPHA_INPUT→`|{ value ALPHA = IN }|`, NUMBER_GET_NEXT→CL_NUMBERRANGE_RUNTIME, READ_TEXT→XCO_CP_LONG_TEXT, CL_BCS→CL_BCS_MAIL_MESSAGE; RFC_READ_TABLE has no API replacement — read a CDS view.
• QuestionIn "High-yield legacy → released replacements", explain:Tap to revealAnswerBAPI_USER_GET_DETAIL → XCO_CP_USER / XCO_CP factory.
• QuestionIn "High-yield legacy → released replacements", explain:Tap to revealAnswerCONVERSION_EXIT_ALPHA_INPUT → string template `|{ value ALPHA = IN }|` (C1, type-safe).
• QuestionIn "High-yield legacy → released replacements", explain:Tap to revealAnswerNUMBER_GET_NEXT → CL_NUMBERRANGE_RUNTIME; READ_TEXT → XCO_CP_LONG_TEXT; CL_BCS → CL_BCS_MAIL_MESSAGE.
• QuestionIn "High-yield legacy → released replacements", explain:Tap to revealAnswerRFC_READ_TABLE is NOT released — read a released CDS view instead; there is no generic table-read API by design.
• QuestionAnalogy for "High-yield legacy → released replacements":Tap to revealAnswerEach legacy tool has a modern equivalent in the shop — except the universal skeleton key (RFC_READ_TABLE), which simply isn't sold any more.
• QuestionWhat is "The XCO library"?Tap to revealAnswerXCO is a released, fluent library of xco_cp_* helpers for JSON, hashing, time, repository introspection, HTTP/OData, and strings — use xco_cp_json instead of the unreleased /ui2/cl_json.
• QuestionIn "The XCO library", explain:Tap to revealAnswerXCO is a released, fluent facade library (xco_cp_*) for cross-cutting concerns.
• QuestionIn "The XCO library", explain:Tap to revealAnswerCovers JSON, hashing/encoding, time/time-zone, repository introspection, HTTP/OData clients, string/file.
• QuestionIn "The XCO library", explain:Tap to revealAnswerUse xco_cp_json instead of the unreleased /ui2/cl_json for JSON.
• QuestionIn "The XCO library", explain:Tap to revealAnswerEvery facade is C1, so XCO-based code is upgrade-stable and uniform to read.
• QuestionAnalogy for "The XCO library":Tap to revealAnswerXCO is the officially supported Swiss-army knife; /ui2/cl_json is a handy blade you found in a drawer with no warranty.
• QuestionWhat is "Released DDIC artefacts — read CDS, not tables"?Tap to revealAnswerReleased I_* interface views are the contract; the tables behind them are not — `select from mara` is a violation, `select from I_Material` is the fix.
• QuestionIn "Released DDIC artefacts — read CDS, not tables", explain:Tap to revealAnswerI_* interface views are released; the underlying tables are not.
• QuestionIn "Released DDIC artefacts — read CDS, not tables", explain:Tap to revealAnswer`select from mara` in a cloud package is a violation; use `I_Material`.
• QuestionIn "Released DDIC artefacts — read CDS, not tables", explain:Tap to revealAnswerThe interface view IS the contract — the table is an implementation detail SAP may restructure.
• QuestionIn "Released DDIC artefacts — read CDS, not tables", explain:Tap to revealAnswerView-bound code survives upgrades; table-bound code is the classic regression risk.
• QuestionAnalogy for "Released DDIC artefacts — read CDS, not tables":Tap to revealAnswerRead the published API of the warehouse (the interface view), not the raw shelf layout (the table) that staff rearrange whenever they like.

1. 1Outline the core idea

   Analyse~10 min

   In your own words, outline the central idea of "Where to find released APIs". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Solve it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "Released DDIC artefacts — read CDS, not tables" applies. Solve the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.