Connect SAP business records with the wider organisation. Uplyst brings supplier, purchasing and financial information into a shared model with customers, contracts and operational events.
Procurement in contextSAP business objects connected through Uplyst
Purchasing, receipts and invoices.
A connected procurement view relates each commitment to its supplier, delivery status and financial position.
Purchase orders
Items, suppliers and committed quantities
Goods receipts
Received quantities and delivery progress
Supplier invoices
Billing and payment obligations
Connect SAP to Uplyst
Supported SAP business services can provide records for Uplyst's shared business model. Business partners, purchase orders, goods receipts and financial documents can be related to customer, supplier and operational records held in other systems.
The available services depend on the SAP product, release and deployment. S/4HANA exposes business APIs including OData services; the selected service and its metadata define the objects, fields and relationships available to the connection.
Preserve the meaning of SAP documents
Document numbers can depend on company codes, fiscal years and other organisational keys. Those values distinguish transactions across legal entities and link document headers, items and related records accurately.
Quantities retain their units, amounts retain their currencies and lifecycle statuses retain their process definitions. Uplyst relates these business objects to records from other sources without discarding the SAP context needed to interpret them.
Supplier invoice5100017294 / 2026 · Item 1Invoice / fiscal year
90EA invoiced
Receipt and invoice items reference 4500021840 / 00010.
Quantity position · 24 Sep 2026120 EA ordered
80 EA received40 EA difference
Invoiced quantity exceeds receipts by 10 EA
The quantities identify a difference to investigate. Payment status and approval remain separate SAP process records.
Procurement and finance in one context
Procurement teams can connect a purchase commitment to receipts, supplier activity and payment obligations. Finance can relate document balances to the customer or supplier relationships behind them.
Partial receipts, cancellations and reversals change the meaning of a commitment. Keeping those process states connected helps teams understand the outstanding position across purchasing, operations and finance.
Access through SAP business services.
The SAP product, release and deployment determine the available API, authentication method and business operations.
Authentication and connectivity
SAP BTP destinations hold a target system's URL, authentication configuration and proxy settings. Where used, they provide a managed connection configuration for requests to the selected SAP service.
The authentication method depends on the target service and the organisation's identity policy. Access through a technical user and requests carrying user context have different permissions and audit attribution.
Access through the source service
OData metadata describes the service's entities, types and relationships. Field selection and the service's continuation mechanism control the scope and size of record retrieval.
Updates, where included in a business workflow, use the controls required by the SAP service. Conditional requests and CSRF protection depend on the operation and deployment; SAP process permissions remain part of that operation.
Uplyst