Reference · built on requestConnectorERP & finance

SAP S/4HANA Cloud

Sales orders, deliveries, billing documents, business partners, and journal entries from SAP S/4HANA Cloud Public Edition.

Request accessPricing ↗

About

SAP S/4HANA Cloud Public Edition is SAP's cloud ERP. It exposes sales, delivery, billing, procurement, and finance objects through OData and SOAP APIs published on the SAP Business Accelerator Hub, and it raises business events when documents change. Access is arranged inside the system through communication scenarios, communication systems, and communication arrangements.

An operator on Fibric reads sales orders, their schedule lines, delivery and billing status, and journal entry items. It watches Sales Order events for credit, delivery, and billing block changes, and proposes order updates, rejections, or releases for your approval. Each proposal carries a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from SAP S/4HANA Cloud and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sales orders, items, and schedule lines through the Sales Order (A2X, OData V2) API, technical name API_SALES_ORDER_SRV
  • Sales Order events: Created, Changed, Delivery Status Changed, Billing Block Status Changed, Overall Credit Check Status Changed, Approval Status Changed
  • Billing documents through the Billing Document - Read, Cancel, GetPDF OData API
  • Customer returns through Customer Return (A2X, OData V2), technical name API_CUSTOMER_RETURN_SRV
  • Journal entry items through Journal Entry Item - Read (A2X), technical name API_JOURNALENTRYITEMBASIC_SRV
  • Outbound deliveries and their items through the Outbound Delivery (A2X) API

Proposed actions

  • Target capability: propose creating or updating a sales order or its items through the Sales Order (A2X, OData V2) API
  • Target capability: propose a rejection reason on a sales order item (SalesDocumentRjcnReason) by PATCH
  • Target capability: propose releasing or rejecting a sales order that sits in approval
  • Target capability: propose cancelling a billing document through Billing Document - Read, Cancel, GetPDF

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold an order when its credit check turns

    Watch Sales Order Overall Credit Check Status Changed events and open a review with the order, sold-to party, and open items, so the hold lands before picking.

    With Credit Hold, Order Risk

  • Chase a promise date that slipped

    Compare schedule lines and Delivery Status Changed events against the promised date and draft the customer notice for approval.

    With Promise Date, Backorder Notice

  • Find shipments billed after cutoff

    Read journal entry items and billing documents to flag deliveries billed after month end and invoices with no posting.

    With Month-End Cutoff, Unbilled Shipment

Requirements

  • An SAP S/4HANA Cloud Public Edition tenant with the Communication Management apps
  • A communication arrangement for communication scenario SAP_COM_0109 to use the Sales Order API
  • A communication user created in Maintain Communication Users and assigned to a communication system
Authentication
A communication user with user ID and password, or a client certificate, bound to a communication system and a communication arrangement for the API's communication scenario.

Limits

  • The Sales Order (A2X, OData V2) API handles sell-from-stock orders only; third-party and project-based order types are excluded
  • One $batch changeset cannot create or process more than one sales order
  • A response carries at most 20 messages in the sap-message header; later messages are dropped
  • SAP recommends A2A SOAP APIs for mass document processing; the OData APIs are for single-document integration

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SAP S/4HANA Cloud ↗

Questions and answers

Does SAP S/4HANA Cloud send events when a sales order changes?
Yes. The Sales Order business object raises events such as Sales Order Created, Changed, Deleted, Delivery Status Changed, Billing Block Status Changed, and Overall Credit Check Status Changed. Each carries the sales order ID, type, sales organization, and sold-to party.
Can the Sales Order API delete an order?
The OData V2 version (API_SALES_ORDER_SRV) supports create, read, update, and delete. SAP documents that the OData V4 version cannot delete entire sales orders.
How is access to the APIs set up?
Through Communication Management. You create a communication user, a communication system, and a communication arrangement for the API's communication scenario. The scenario defines the inbound and outbound services and the authentication methods allowed.
Ask about SAP S/4HANA Cloud

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SAP S/4HANA Cloud through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy