No-Code

Key User

F1481

F1731

Key User Extensibility

No-code and low-code S/4HANA extensibility for business power users — Custom Fields, Custom Business Objects, Business Rules, and SSCUI configuration. Extend S/4HANA without writing a single line of ABAP.

Key User Extensibility Toolset

All four key user tools are Fiori apps accessible to business power users without ABAP knowledge. Extensions created through these tools automatically generate OData V4 services and integrate with Fiori Elements UIs — no UI development required.

Key User Extensibility Tools and Scope

Rendering diagram…

Executive Summary

No ABAP required

Key User extensibility allows business power users to extend S/4HANA through guided Fiori applications. The most important tools are F1481 Custom Fields and Logic (add fields to standard SAP documents), F1731 Custom Business Objects (create new transactional objects), Business Rules (decision logic without coding), and F2048 Manage Your Solution (Fiori-based configuration). All key user extensions are upgrade-safe — SAP manages the technical upgrade of the extension framework automatically.

Which Key User Tool to Use

Requirement	Recommended Tool
Add a field to a standard SAP document	Custom Fields (F1481)
Add validation logic to a standard document	Custom Fields → Logic tab
Create a completely new transactional object	Custom Business Objects (F1731)
Define routing/approval rules without coding	Business Rules (Manage Rules)
Configure standard SAP settings (like SPRO)	Manage Your Solution (F2048)
Configure output forms and layouts	Output Management (standard)
Define number ranges	Number Ranges (standard configuration)

F1481 — Custom Fields and Logic (Deep Dive)

The most widely used key user tool. Custom Fields add business-specific data attributes to standard SAP documents without any ABAP development.

Add custom fields to 40+ standard business objects: Sales Order, PO, Customer, Supplier, Plant, Material, Billing Document, and more

Field types: Text, Amount, Quantity, Date, Boolean, Dropdown (fixed values or value help)

UI integration: custom field appears automatically in the Fiori app for the business object — no UI5 development required

OData integration: field is exposed automatically in the standard OData V4 API for the business object

Field logic: simple validation rules written in a guided rule builder without ABAP expertise

Naming convention: custom fields are prefixed YY1_ (SAP-reserved namespace for key user fields — upgrade-safe)

F1731 — Custom Business Objects (Deep Dive)

Use Custom Business Objects when the requirement is a completely new transactional entity that does not fit into any existing standard SAP object.

Create completely new S/4HANA transactional objects with header + multiple node levels (similar to Sales Order header + items)

Draft workflow: built-in save + check + activate cycle — no custom coding for draft handling

Auto-generated: OData V4 service, Fiori Elements List Report + Object Page — ready to use immediately

Associations: link Custom Business Objects to standard objects (e.g., link to Sales Order, Purchase Order)

Locking: built-in optimistic locking — no custom coding needed

Workflow: integrate with S/4HANA workflow via standard hooks

Business Rules — Deep Dive

Business Rules allow business users to maintain decision logic in production without raising a transport request — the highest-velocity extension mechanism available.

Decision tables maintained by business users directly in Fiori UI — no developer involvement for rule changes

Rule changes take effect immediately — no transport request required for production rule updates

Rule types: simple conditions, multi-condition tables, and expression-based rules

Use cases: pricing adjustments, routing decisions, approval thresholds, category assignments, VAT code logic

Integration: rules can be called from BAdIs, workflow steps, or directly from S/4HANA process code

F2048 — Manage Your Solution (SSCUI) — Deep Dive

SSCUI is the cloud-ready replacement for SPRO. It presents the same configuration activities in a Fiori-native, scope-filtered, role-aware interface.

Replaces transaction SPRO for cloud-ready configuration — scoped to relevant project activities

Business process grouping: activities grouped by process (not by technical component as in classic SPRO)

Role-based access: different users see only the configuration activities assigned to their roles

Change tracking: all SSCUI configuration changes are tracked in SAP Cloud ALM for audit and rollback

Enterprise Example: DEWA UAE-Specific Customisations

Custom Fields on Purchase Order: 8 — Project code, cost centre, approval level, VAT category, and 4 more
Custom Business Objects: 2 — Plant Maintenance Checklist, Contractor Evaluation
Business Rules: 3 — PO routing by amount, approval hierarchy by dept, VAT code assignment
SPRO activities replaced by SSCUI: 100%
ABAP code written for these customisations: Zero
Upgrade rework required: Zero — fully managed by SAP framework

Best Practices

Key User tools before ABAP — always

Always try Key User tools before writing ABAP. 70% of extension requirements can be met this way — faster to build, no developer needed, and fully SAP-managed upgrade safety.

Use YY1_ naming prefix consistently

Use the YY1_ naming prefix for all Custom Fields. This is the SAP-reserved namespace for key user extensions and ensures upgrade safety.

Customising transports — not Workbench transports

Assign Custom Field and CBO changes to Customising transports. Using Workbench transports can cause import conflicts and bypass standard quality gates.

Test auto-generated UI early

Design Custom Business Objects with the end Fiori user in mind — test the auto-generated List Report and Object Page early. UI changes after go-live are painful.

Maintain a Key User extensibility catalog

Document all custom fields, CBOs, and business rules centrally — prevents duplicate creation and helps onboard new team members and SAP partners.

Common Pitfalls

Too many custom fields cluttering the UI

Creating too many custom fields clutters the standard Fiori UI — target a maximum of 5-6 visible fields per section. Use field groups and visibility conditions for the rest.

CBOs for data that belongs in standard objects

Using Custom Business Objects for data that belongs in a standard S/4 object creates orphaned data and synchronisation complexity.

Maintaining Business Rules directly in production

Always develop and test Business Rules in DEV, then transport to PROD. Direct production changes bypass testing and can cause immediate business process failures.

Missing Business Catalog assignments

Not assigning proper Business Catalogs for key user tool access means users cannot reach the Fiori apps — a common go-live blocker.

Security Considerations

PII exposure and data retention

Key User tools create data that may contain personally identifiable information (PII). Review custom field data types — fields storing names, IDs, or financial data require data protection classification in SAP's data protection framework. Custom Business Objects auto-generate OData V4 services — assign appropriate Business Catalogs to control access (do not leave these services open by default). Apply UAE PDPL data retention rules to Custom Business Object data and document the retention period in the extensibility catalog.

References

Custom Fields and Logic (SAP Help)

Full documentation for the Custom Fields and Logic Fiori app (F1481) in S/4HANA.

Custom Business Objects (SAP Help)

Step-by-step guide for creating Custom Business Objects via the F1731 Fiori app.

Manage Your Solution (SSCUI)

SSCUI documentation — scoped configuration, role assignment, and Cloud ALM integration.