on 2025 Apr 21 8:00 AM
Summary
This article seeks to provide guidance on deciding the most suitable target application architecture to support Procure to Receipt needs of an organization, in the context of Source to Pay end to end cycle.
With SAP Ariba, SAP Fieldglass and S/4HANA, all delivering solution capabilities around Procure to Receipt, enterprises now have multiple options to choose from and need to make their selection by comparing their organization’s business capability requirements to the solution capabilities the different applications offer.
The licensing aspects of the components discussed should be considered during target architecture design and is beyond the scope of this evaluation.
Business Requirements
Purpose
Procure to Receipt is the cycle of requesting, ordering and receiving physical items or services from suppliers. The Deliver to Fulfill cycle, dealing with transportation and warehousing and the Invoice to Pay cycle, dealing with supplier payment are tightly interwoven with the execution of the Procure to Pay process.
Basic Process
Applicable SAP Best Practices
Business Capabilities
Solution Options
Characterization of the Solution Options
Critical Process Variant 1 - Direct Physical Products : Capability Distribution
Critical Process Variant 2 - Direct Physical Products Scheduling Agreements : Capability Distribution
Critical Process Variant 3 – Indirect Products and Services : Capability Distribution
Critical Process Variant 4 – Subcontracting : Capability Distribution
Critical Process Variant 5 – Services Self-Billing : Capability Distribution
Critical Process Variant 6 – Indirect Products and Services Tactical Sourcing : Capability Distribution
Critical Process Variant 7 – Direct Physical Products Scheduling Agreement Subcontracting : Capability Distribution
Criteria to determine the most suitable target solution
Critical Process Variant 1 – Direct Physical Products : Application Map
Critical Process Variant 2 – Direct Physical Products Scheduling Agreement : Differential Applications Only
Critical Process Variant 3 – Indirect Products and Services : Differential Applications Only
Critical Process Variant 4 – Subcontracting : Differential Applications Only
Critical Process Variant 5 – Services Self-Billing : Differential Applications Only
Critical Process Variant 6 – Indirect Products and Services Tactical Sourcing : Differential Applications Only
Critical Process Variant 7 – Direct Physical Products Scheduling Agreement Subcontracting : Differential Applications Only
Critical Process Variant 8 – Direct Physical Products Consignment : Differential Applications Only
Evaluation Table
As one can observe from the previous section, the same set of business capabilities are often enabled by multiple solution capabilities, and thus the choice of application would require more than just an identification of differential business capabilities across the critical process variants.
The following additional business and IT considerations should therefore be applied in order to determine the most appropriate application architecture for Procure to Receipt :
Conclusion
How can we easily and pragmatically compare/test the process variants and pick the best fit option?
Picking the best fit variants for an organisation depends on its business practices, e.g. a company heavily engaged in contract manufacturing needs to consider the subcontracting variant.
Testing the variants can be done by following the test scripts of the appropriate best practices, e.g. BMY for subcontracting.