Operations touchpoints
What you'll learn
RZ70 registers a system in the SLD, SE63 translates your extension texts too, and the Release Information Note lists every API-state change per FPS.
- RZ70 registers a system with the SLD — the step that makes it discoverable for integration/monitoring.
- SE63 is the translation environment; extension texts need translating just like SAP standard texts.
- The Release Information Note (RIN) lists every API-state change per FPS (758 SP01 ~3000 deltas).
Some operations touchpoints get blamed on Basis but every developer benefits from knowing they exist. RZ70 registers a system with the System Landscape Directory (SLD) — the registration that makes a system discoverable for integration and monitoring scenarios. Knowing where SLD registration lives turns a mysterious 'the system isn't showing up' into a concrete, fixable step.
Translation is a development responsibility, not an afterthought. SE63 is the translation environment, and the point most teams miss is that *extension* texts — the labels, messages and short texts your Z objects ship — need translating exactly like SAP standard texts. A Clean-Core-compliant extension that is monolingual is incomplete in a multi-language landscape; SE63 is where that gap gets closed.
The most underused planning artefact is the Release Information Note (RIN). For every Feature Pack Stack, the RIN lists *every* API state change in that FPS — what became released, what turned deprecated, what was withdrawn. The RIN for SAP_BASIS 758 SP01 alone lists on the order of three thousand deltas. Reading the RIN before an upgrade tells you exactly which contracts under your code moved, instead of discovering it from red ATC findings afterwards.
Key points
- RZ70 registers a system with the SLD — the step that makes it discoverable for integration/monitoring.
- SE63 is the translation environment; extension texts need translating just like SAP standard texts.
- The Release Information Note (RIN) lists every API-state change per FPS (758 SP01 ~3000 deltas).
- Read the RIN before an upgrade to see which contracts moved, instead of finding out from ATC after.
Examples
Before applying an FPS, scan its Release Information Note for API-state changes touching objects your code consumes — it is the proactive version of the post-upgrade ATC red wall.
Source notes: clean-core-curriculum §11.4
Ask Claude
Build a prompt from this lesson + your question and open a fresh Claude chat with it pre-filled — handy for adapting a before/after pattern to your own object.