Not every business requirement needs a developer. A sales manager wants one extra field on the customer record. Finance wants a small validation before invoices post. In the old world, that meant a development request, a transport, and a wait. In S/4HANA, the Custom Fields and Logic Fiori app lets key users do it themselves — no ABAP, no Eclipse, no transport queue.
What key-user extensibility is
SAP's clean-core strategy draws a hard line: the core stays standard, and extensions happen at defined points. Key-user extensibility (sometimes called in-app extensibility) is the lowest rung of that ladder — changes a trained business user can make directly in the running system, through Fiori apps, without writing code in the traditional sense.
Custom Fields and Logic is the flagship app for this. It has two halves: Custom Fields for adding fields to SAP business contexts (customers, materials, sales orders, journal entries — hundreds of enabled contexts), and Custom Logic for adding small pieces of behavior at predefined enhancement points using a guided, form-based editor.
Key takeaway: Key-user extensibility = business users extending S/4HANA through Fiori apps, no developer needed. Custom Fields adds data; Custom Logic adds behavior — both within SAP-defined boundaries that keep the core clean.
Custom fields and the YY1_ namespace
Here's how it works in practice. Open the app, go to Custom Fields, and pick a business context — say, "Customer." Create a new field: give it a label, pick a type (text, number, date, checkbox, dropdown), and decide where it should appear. The system generates the field with a technical name in the YY1_ namespace, like YY1_LoyaltyTier_Customer.
That prefix matters. YY1_ is SAP's reserved namespace for key-user custom fields, and it's how the system (and every future upgrade) knows this field is yours, not SAP's. You'll never collide with a field SAP adds in a later release, because SAP will never create anything starting with YY1_. It's a small detail that prevents an entire class of upgrade headaches.
Once created, the field can be published to the places it needs to surface: the Fiori UI (it appears on the relevant object pages automatically), OData services, reports, and even forms. You control this per field — a field used only for internal segmentation doesn't need to clutter the customer-facing UI.
Custom logic without ABAP
The Custom Logic half is where it gets more interesting. SAP exposes enhancement options — predefined BAdI-like spots where custom code can run, such as "validate before saving a sales order" or "derive a value when a field changes." The key user picks an enhancement, and the app provides a guided scripting environment to implement it.
Let's be honest about the limits: this isn't a replacement for real development. The logic editor handles straightforward cases — validations, derivations, default values — and deliberately can't do the things that would threaten system stability (no direct database writes to standard tables, no wild COMMIT statements). When a requirement outgrows these guardrails, that's the signal to escalate to on-stack developer extensibility (ABAP Cloud) or side-by-side (BTP). Choosing the lowest tier that fits is the whole philosophy.
Transport and lifecycle
A common worry: "If a key user creates this in production, how does it get to the other systems?" In S/4HANA Cloud, custom fields and logic are captured in the tenant's extensibility inventory and move through the standard cloud transport mechanism — they're part of the software collection, versioned and transportable like any other configuration. In on-premise S/4HANA, they travel in regular transports.
Either way, the governance point stands: key-user extensibility still deserves oversight. Decide who may create custom fields (usually a small group of trained key users, not everyone with Fiori access), agree on naming conventions beyond the YY1_ prefix, and review the inventory periodically. A thousand orphaned custom fields is its own kind of technical debt.
It's also worth knowing which business contexts are enabled before you promise anything. SAP ships a few hundred of them, but not every object you'd like is covered — if the exact context you need isn't enabled, that's the point where key-user extensibility stops and developer extensibility begins. Check the "Business Context" view in the app first; it takes thirty seconds and saves awkward conversations later.
Used with a little discipline, Custom Fields and Logic is one of the highest-value apps in S/4HANA: real business requirements, delivered in hours instead of sprints, without touching the core. That's the clean-core promise working as intended.