S/4HANA · HCM Personnel Administration · Fiori

Digitizing paper-based personnel data changes through Fiori and workflow

A production solution for multiple HCM Personnel Administration change processes, combining a custom Fiori front end with an ABAP backend, configurable approvals, document handling and controlled background posting.

Context: Public-sector S/4HANA greenfield implementation
Role: Technical Lead · ABAP Developer
Period: Oct 2020 — Jun 2021

The challenge

What the solution needed to change.

Personnel Administration changes were initiated through paper-based processes. A single Fiori application needed to support several infotype-related requests, each with its own mandatory data, supporting documents and approval procedure.

The solution needed to separate user submission and approval from final HCM posting, while preserving traceability across request data, attachments, workflow decisions and the resulting SAP updates.

Technical approach

Architecture shaped around maintainable control points.

The Fiori application submitted requests through an OData service into custom staging tables. Document references were mapped to the staged request while the physical files were held in externally managed storage maintained by the BASIS team.

Configurable multi-level workflow routing determined approval levels through organizational rules. After approval, a background process extracted staged requests and posted the appropriate infotype changes through HCM function modules or BAPIs.

01Fiori request

Users enter infotype-specific data and attach the required supporting documents.

02OData & staging

The backend validates and records request data and document references.

03Workflow

Approval levels are resolved from configurable organizational rules.

04Background posting

Approved requests are selected by a controlled scheduled process.

05HCM update

Relevant function modules or BAPIs post the final infotype changes.

My ownership

Contribution and accountability

Designed the workflow from the ground up to support variable approval levels.
Defined the end-to-end solution architecture and data flow between Fiori and the ABAP backend.
Designed staging tables, background-posting mechanics and the attachment-reference concept.
Coordinated the integration boundary with the separate Fiori development and BASIS teams.
Led four developers across onsite and remote delivery, including estimation, work allocation and technical standards.

Outcome

What improved

Replaced a paper-driven process with a controlled digital request and approval flow.
Created a reusable architecture for several infotype-specific procedures within one application.
Separated user interaction, approval and final SAP posting into maintainable processing stages.
Delivered the solution through to production.

Next case study: S/4HANA OData delivery