~3M year
Governed across the healthcare procurement environment
6M+ year
Processed across the electronic ordering ecosystem
18
Operating through the same regional procurement model
~10K
Participating in the healthcare procurement ecosystem
1. The Operational Challenge
A regional public authority operates a shared procurement and financial environment serving 18 public healthcare organizations, including local health authorities, hospitals, university hospitals and research institutes. Across this ecosystem, millions of orders for medicines, medical devices, healthcare supplies, goods and services must be communicated reliably to approximately 10,000 suppliers while remaining aligned with the procurement and accounting context of each individual organization.
Purchase Orders originate primarily in the regional SAP environment. But creating the Order in SAP is only the beginning of the operation.
The Order must be represented in the appropriate format, transmitted through the required procurement channel, correlated with the correct supplier and healthcare organization and kept active while acknowledgements, errors, substitutions, retries and subsequent outcomes continue to arrive.
The exchange model itself has also evolved over time. Orders were originally supported through email, certified email and standardized web services. The environment subsequently incorporated Italy’s National Order Exchange (NSO) and structured UBL documents aligned with the PEPPOL procurement model.
Today, approximately 3 million Purchase Orders every year are governed through this regional environment, producing more than 6 million exchange messages annually even before the full volume of responses, exceptions and additional lifecycle interactions is considered.
Coopera maintains the Purchase Order as the persistent operational context throughout that evolution.
2. Why it was complex
The challenge was not simply electronic order transmission. It was maintaining one coherent procurement operation while organizations, suppliers, formats, channels and external outcomes changed around the Order.
One regional model must preserve 18 organizational responsibilities
The healthcare organizations share regional procurement infrastructure but remain independent entities with their own procurement and accounting responsibilities. Every Order must therefore retain the correct: Healthcare Organization · Supplier · Procurement Context · Accounting Reference · Order Data · Current Status.
Centralization cannot erase organizational identity.
Millions of Orders create millions of asynchronous interactions
A Purchase Order can produce far more than one outbound message. Acknowledgements, responses, errors, substitutions, retries and state changes can arrive later and must remain correlated with the individual Order that gives them meaning.
The operation cannot depend on one exchange technology
Email, certified email, web services and structured national exchange have all participated in the procurement environment at different moments. The technical mechanism can evolve. The Purchase Order must not need to be reinvented every time the channel changes.
Structured and unstructured Orders must converge
Not every operational Order is necessarily available in the expected structured representation. Alternative Purchase Orders can also enter as PDF documents and be interpreted into the same procurement context rather than becoming a separate manual process.
Some procurement is operationally critical
Healthcare orders can include medicines and supplies whose timely availability affects care delivery. A temporary problem in one structured exchange path cannot be allowed to fragment or erase the procurement operation.
Continuity therefore matters beyond simple integration reliability.
3. How Coopera holds the operation together
In this scenario the Purchase Order becomes the primary Living Business Object.
Purchase Order
Every Purchase Order is maintained as a persistent Living Business Object with its own identity, current condition and operational history. It can keep connected: Issuing Organization · Supplier · Procurement References · Accounting Context · Order Lines · Products · Quantities · Current State · Source Channel · Transmission History · Exchange Messages · Errors · Retry History · Operational Evidence.
- The Order can originate in SAP.
- It can be represented as UBL/PEPPOL.
- It can travel through the national procurement infrastructure.
- It can also be reconstructed from a PDF received through an alternative channel.
The Purchase Order remains the point of continuity through all of them.
This distinction is fundamental. The XML is not the Order. The PDF is not the Order. They are representations of the same business reality.
The persistent Purchase Order is what preserves the supplier relationship, organizational context, procurement meaning, lifecycle and evidence independently of the technology currently used to represent or transport it. That allows channels and standards to evolve without forcing the procurement operation itself to lose continuity.
4. What This Looks Like in Practice
Structured National Exchange
From regional SAP to the supplier ecosystem. Purchase Orders originating in regional SAP retain the organizational and accounting context of the healthcare entity that created them. When the required conditions are satisfied, the Order can be represented in the structured format required by the national procurement infrastructure and transmitted through the appropriate electronic channel.
Subsequent responses remain correlated with that same Purchase Order. A message may: Confirm Progress · Report an Error · Change Status · Require Retry · Add New Evidence. The exchange therefore becomes part of the operational lifecycle rather than a disconnected integration event.
Alternative Document-Based Orders
Different representation but same Purchase Order. Where an Order arrives as PDF rather than structured data, the document does not have to become an exceptional manual workflow. Coopera can interpret the content and extract procurement information such as: Supplier · Organization · Products · Quantities · References · Order Data. That information is transformed into structured operational context and evaluated before subsequent synchronization with the appropriate regional SAP environment. The PDF remains supporting content.
The reconstructed Purchase Order enters the same governed operational model as a digitally structured Order. This is particularly valuable where continuity of healthcare procurement cannot depend exclusively on one source format or transport mechanism
Errors and Retries
Failure does not create a new operational reality. A failed transmission or temporary infrastructure problem does not need to create another disconnected copy of the Order.
The existing Purchase Order retains: what was attempted · what happened · what changed · what needs to happen next. Retry, remediation or alternative execution can therefore continue from the same persistent context.
This preserves both operational continuity and auditability. The execution may fail. The Order does not disappear.
Keeping SAP Aligned with External Reality
External outcomes return to the procurement context.
- Regional SAP retains responsibility for procurement and accounting.
- The national order infrastructure retains responsibility for regulated exchange.
- Suppliers retain their commercial role.
Coopera correlates the external outcomes of those interactions with the relevant Purchase Order and propagates significant state changes back into the correct SAP organizational context. The accounting and procurement system therefore remains aligned with what actually happened outside it.
Systems manage their part. The Purchase Order keeps the wider operation connected.
5. One Procurement Model Across 18 Healthcare Organizations
The same operating model supports 18 independent healthcare organizations and an ecosystem of approximately 10,000 suppliers. Common regional infrastructure provides scale without collapsing organizational responsibility. Each Purchase Order remains attributable to the organization that issued it, the supplier receiving it and the procurement and accounting context from which it originated. At the same time, the exchange layer can evolve.
- Email and certified channels can participate.
- Web services can participate.
- UBL/PEPPOL and the national procurement infrastructure can participate.
- Alternative document-based intake can participate when required.
The business object does not need a different identity for each technical path. One Purchase Order model can survive multiple generations of procurement technology.
6. The Outcome
The regional healthcare ecosystem now operates one common digital ordering model across 18 healthcare organizations, connecting them with approximately 10,000 suppliers. Around 3 million Purchase Orders every year are governed through the platform. Those Orders generate at least 6 million exchange messages annually, with additional traffic arising from acknowledgements, errors, substitutions, retries and other lifecycle events.
Orders created in regional SAP can enter the appropriate electronic exchange without procurement users having to manage the complexity of the underlying communication infrastructure. External outcomes remain correlated with the Purchase Order and relevant changes return to the correct SAP context.
At the same time, alternative document-based execution can converge on the same operational model. PDF Orders can be interpreted, transformed into structured procurement information and validated before being synchronized with regional SAP. Errors and alternative execution paths remain part of the original Order history instead of becoming disconnected integration exceptions.
This is particularly important in healthcare procurement, where continuity can matter for medicines, medical devices and other supplies whose timely availability may be operationally critical.
The result is not simply electronic Purchase Order transmission. It is a regional procurement operating model in which healthcare organizations, suppliers, regional SAP, national e-procurement infrastructure and alternative execution channels remain continuously connected around every Purchase Order.
5. What This Case Proves
A Purchase Order can be a Living Business Object
The Order maintains identity, organizational context, lifecycle, exchange history and evidence while different execution mechanisms act around it.
The business object is independent of its representation
UBL/PEPPOL and PDF can represent the same procurement reality without defining the identity of the Purchase Order itself.
Operational continuity can survive channel change and failure
Structured exchange, alternative document paths, retries and remediation can all continue around the same persistent Order.
Massive exchange volumes can remain object-centric
More than six million annual messages retain meaning because each remains correlated with the Purchase Order and organizational context that originated it.
