SAP · Ariba & SuccessFactors
Two applications that own a process, and the seams to everything the process touches.
Noble implements, extends and connects SAP Ariba for sourcing and procurement and SAP SuccessFactors for the workforce record and the workflows around it. The applications are configured to how the organisation buys and employs; the larger part of the work is the joins — to the S/4HANA core, to finance, to suppliers, and to the enterprise identity that decides who may approve what.
The modules named on this page are the ones the work is established on.
Where the work is
A line-of-business application is bought for the process it owns and judged by the processes it interrupts. Ariba owns sourcing and procurement; the moment a purchase order is approved it has to become a commitment in the ledger, a goods receipt has to close it, and an invoice has to match it — none of which happens in Ariba. SuccessFactors owns the workforce record; a new employee’s first day depends on that record reaching identity, payroll, the directory and the systems that give access, on the day and not the week after.
That is why this page describes both applications alongside their seams. The configuration is the smaller half. The integration design, the master data the two applications share with the core, and the identity model that decides who may approve a purchase or see a salary are where an implementation succeeds or quietly fails.
What the service covers
Ariba — sourcing and procurement
Sourcing events, contracts, catalogues and the guided buying that keeps purchases inside them; approval flows configured to the organisation’s delegation of authority; and the supplier-facing side of the process — onboarding, qualification and the portal through which suppliers respond, invoice and are paid.
- Sourcing, contracts and catalogue management
- Guided buying and approval flows to the delegation of authority
- Supplier onboarding, qualification and the supplier portal
- Invoice matching against orders and receipts
Ariba to the core and to finance
The procure-to-pay flow across Ariba and S/4HANA: requisitions and orders becoming commitments, receipts closing them, invoices matched and posted, and the supplier and material master shared rather than duplicated. Built on SAP’s integration content where it fits and extended where the organisation’s process departs from it.
- Procure-to-pay integration with S/4HANA
- Commitments, receipts and invoice posting to the ledger
- Supplier and material master shared with the core
- Exception handling with an owner for each case
SuccessFactors — the workforce record
Employee Central as the system of record for the organisation’s people: the organisational structure, positions, employment data and the events of a working life — hire, move, promote, leave — configured to the organisation’s policies and to the regulatory requirements of the countries it employs in.
- Employee Central — structure, positions and employment data
- Hire, move and leave events configured to policy
- Country-specific requirements where the organisation employs
- Bilingual employee experience, composed for Arabic
Workforce workflows around the record
The workflows that read and write the record: time and absence, performance and goals, and the manager and employee self-service through which most of the organisation meets the system. Each is enabled where the organisation’s process is ready for it, and configured to that process rather than to a reference model.
- Time, absence and the calendars behind them
- Performance, goals and the review cycle
- Manager and employee self-service
- Workflows enabled where the process is ready
SuccessFactors to identity, payroll and the core
The record reaching everything that depends on it: the identity system that creates, changes and removes access on the day the record changes; payroll, whether SAP or not; and the cost centres and organisational structure the S/4HANA core needs to agree with. The joiner, mover and leaver process is designed as one flow with identity and access management, because that is where it is audited.
- Joiner, mover and leaver tied to the record
- Access provisioning and removal on the day
- Payroll and cost-centre integration with the core
- Organisational structure agreed once across systems
Releases and support
Both applications are updated on SAP’s release cadence, and each release is reviewed for what it changes in the configured process and the interfaces. Support after go-live covers configuration, the interfaces and the questions a workforce or procurement team raises in the first year of a new system.
- Release review against configuration and interfaces
- Application support for both suites after go-live
- Interface monitoring shared with the managed service
One process, three systems
Procure-to-pay as it actually runs: the process starts in Ariba, becomes a financial fact in the core, and is closed by a document that has to match. The gate is the three-way match — order, receipt and invoice agreeing before anything is paid.
- 01Source and contractAriba
- 02Requisition and approvalAriba, to the delegation of authority
- 03Order and commitmentS/4HANA ledger
- 04Goods receiptS/4HANA
- 05Three-way matchOrder, receipt, invoice
- 06Post and paySupplier paid through the portal
Where this connects
The services alongside
- SecurityIdentity and access management — the joiner, mover and leaver process is designed with that service, because it is audited there.
- Digital TransformationProcess transformation — the procurement and workforce processes are mapped as they are actually done before an application is configured to them.
SAP Ariba, SAP SuccessFactors, Employee Central and S/4HANA are products of SAP SE, named to identify what the work is done on. All marks belong to their owners.
Describe the process, not the module.
How a purchase is approved today, or how a new employee gets access on their first day, says more about the work than a module list does. Start there.