SAP S/4HANA Cloud Public Edition Integration Research

Date: 2026-04-01 Status: Research complete Scope: Full API integration research for Orcha AP automation use case Edition: SAP S/4HANA Cloud Public Edition (multi-tenant SaaS) -- NOT Private Edition or On-Premise

1. Executive Summary & Capability Matrix

SAP S/4HANA Cloud Public Edition exposes a rich set of APIs via the SAP Business Accelerator Hub (api.sap.com). Unlike On-Premise or Private Edition, the Public Edition does not allow direct RFC, BAPI, IDoc, or database table access. All integration must go through SAP-delivered whitelisted APIs (OData V2/V4, SOAP) or custom CDS views exposed as OData. The good news: nearly all Orcha-required write operations are supported via standard APIs, and API access is included in the base subscription (no Digital Access licensing model applies to Public Cloud).

Capability Matrix

Orcha Need	Supported?	Protocol	API / Service	Write?
Write supplier invoices	Yes	OData V2 + SOAP	`API_SUPPLIERINVOICE_PROCESS_SRV` / `II_IVE_SUPLRINVCERPCRTRC`	Yes (POST create, POST cancel, POST release)
Write journal entries	Yes	SOAP	Journal Entry - Post (Sync & Async)	Yes (POST)
Write credit/debit memos	Yes	SOAP	Journal Entry - Post API	Yes (via document type)
Attach PDF documents	Yes	OData V2	`API_CV_ATTACHMENT_SRV`	Yes (upload, rename, delete)
Read/write cost centers	Yes	OData V4	Cost Center OData V4 Service	Yes (CRUD)
Read/write GL accounts	Partial	OData V2	`API_GLACCOUNTINCHARTOFACCOUNTS_SRV`	Read primarily; GL accounts in Public Cloud come pre-delivered (YCOA)
Read chart of accounts	Yes	OData V2	`API_GLACCOUNTINCHARTOFACCOUNTS_SRV`	Read
Read/write business partners (suppliers)	Yes	OData V2	`API_BUSINESS_PARTNER` (SAP_COM_0008)	Yes (full CRUD)
Trigger/manage approvals	Partial	Config + API	Flexible Workflow + API posting of pre-approved invoices	Indirect -- post approved docs via API
Read payment status	Yes	OData V2	Supplier Invoice Read API + Payment Advice APIs	Read
Read document lifecycle/status	Yes	OData V2	`API_SUPPLIERINVOICE_PROCESS_SRV` (status fields)	Read
Event notifications (outbound)	Yes	Event Mesh / Webhooks	SAP Event Mesh via BTP	Outbound push

Key Verdict

SAP S/4HANA Cloud Public Edition is well-suited for Orcha integration. All critical write operations for AP automation are available through standard APIs. The main constraint is the pre-delivered chart of accounts (YCOA/YIKR) which limits GL account creation, but reading and mapping to existing accounts is fully supported.

2. API Landscape

2.1 API Protocols

Protocol	Status in Public Edition	Usage
OData V2	Primary, most APIs	CRUD on business objects (invoices, partners, attachments)
OData V4	Growing, newer APIs	Cost centers, some master data
SOAP	Available for specific services	Journal Entry Post/Change, some procurement
REST (non-OData)	Limited	Custom CDS view external APIs
RFC/BAPI	NOT available	Blocked in Public Edition
IDoc	NOT available	Blocked in Public Edition

2.2 Authentication

All API access in SAP S/4HANA Cloud Public Edition is governed by Communication Arrangements:

Component	Description
Communication Scenario	SAP-delivered bundle defining which APIs/permissions are exposed (e.g., `SAP_COM_0008` for Business Partner). Cannot be modified.
Communication System	Represents the external system (hostname, IP, certificates)
Communication User	Technical user for API access; NOT a licensed named user
Communication Arrangement	Runtime binding of Scenario + System + User; activates the API

Supported Authentication Methods:

Basic Authentication (inbound and outbound) -- simplest setup
OAuth 2.0 Client Credentials (outbound connections)
OAuth 2.0 SAML Bearer Assertion (inbound connections)
Client Certificate Authentication (mutual TLS)

Important: Communication Users are not licensed as named users. API access does not incur additional per-user licensing costs.

2.3 Rate Limits

SAP does not publicly document specific API rate limits for S/4HANA Cloud Public Edition. Key considerations:

No official published rate limit numbers
SAP recommends contacting support for specific API limits
Practical experience suggests reasonable throughput for batch operations
For high-volume scenarios, use asynchronous APIs (SOAP-based Journal Entry Post Async)
SAP Integration Suite can add rate limiting/throttling if needed

2.4 Key API Endpoints by Category

Finance - Posting Integration (SAP_COM_0002)

API	Protocol	Operations
Journal Entry - Post (Synchronous)	SOAP	Create journal entries in real-time
Journal Entry - Post (Asynchronous)	SOAP	Batch posting of journal entries
Journal Entry - Change (Asynchronous)	SOAP	Update existing journal entries (e.g., payment terms)
Journal Entry - Clearing (Asynchronous)	SOAP	Clear open items
Journal Entry by Ledger - Post (Async)	SOAP	Ledger-specific postings

Supplier Invoice Integration (SAP_COM_0057)

API	Protocol	Operations
`API_SUPPLIERINVOICE_PROCESS_SRV`	OData V2	Create, read, release, cancel supplier invoices
`II_IVE_SUPLRINVCERPCRTRC`	SOAP	Create supplier invoices (supports parking)

Business Partner Integration (SAP_COM_0008)

API	Protocol	Operations
`API_BUSINESS_PARTNER`	OData V2	Full CRUD on Business Partners, Customers, Suppliers

Attachments

API	Protocol	Operations
`API_CV_ATTACHMENT_SRV`	OData V2	Upload, list, rename, delete attachments on business objects

Cost Center

API	Protocol	Operations
Cost Center OData V4 Service	OData V4	Full CRUD on cost center master data

2.5 Key Links

SAP Business Accelerator Hub: https://api.sap.com/products/SAPS4HANACloud
All APIs listing: https://api.sap.com/products/SAPS4HANACloud/apis/all
OData V2 APIs: https://api.sap.com/package/SAPS4HANACloud/odata
OData V4 APIs: https://api.sap.com/products/SAPS4HANACloud/apis/ODATAV4
S/4HANA Cloud Help Portal: https://help.sap.com/docs/SAP_S4HANA_CLOUD

3. Write Capability Verification

3.1 Supplier Invoice -- CREATE (Verified)

API: API_SUPPLIERINVOICE_PROCESS_SRV (OData V2) Endpoint: POST /A_SupplierInvoice Communication Scenario: SAP_COM_0057 Evidence: SAP Business Accelerator Hub lists POST as a supported operation. Multiple community posts confirm creating supplier invoices with reference to purchase orders, service entry sheets, and delivery notes.

Supported operations:

POST -- Create new supplier invoice
POST .../Release -- Release a blocked invoice
POST .../Cancel -- Cancel (reverse) a posted invoice
DELETE -- Delete a parked (not yet posted) invoice

Limitation: Parking invoices is NOT supported via OData; use the SOAP service II_IVE_SUPLRINVCERPCRTRC instead.

3.2 Journal Entry -- POST (Verified)

API: Journal Entry - Post (Synchronous and Asynchronous) Protocol: SOAP Communication Scenario: SAP_COM_0002 (Finance - Posting Integration) Evidence: SAP official blog "User Guide for Journal Entry Post API on S/4 HANA Cloud" confirms posting capability.

Capabilities:

Post customer invoices, supplier invoices, debit memos, credit memos
Supports multiple document types
Asynchronous variant for batch processing

Limitation: Payment Terms cannot be set during initial posting; must use Journal Entry - Change API afterward.

3.3 Credit/Debit Memo -- CREATE (Verified)

Method: Via Journal Entry - Post API with appropriate document type Protocol: SOAP Evidence: SAP community confirms "Journal Entry Post API provides the option to post customer Invoices, Supplier Invoices, Debit Memo and Credit Memo's into S/4 Hana Cloud."

3.4 PDF Attachment -- UPLOAD (Verified)

API: API_CV_ATTACHMENT_SRV (OData V2) Evidence: Dedicated SAP blog "ODATA API 'Attachments' Service in SAP S/4HANA Cloud" and community post "Create a PDF attachment using the Attachments API in S/4HANA Cloud" confirm full support.

Supported operations:

Upload attachments (including PDF) to business objects (Supplier Invoices, Purchase Orders, Sales Orders, etc.)
Count, list, rename, delete attachments
Link files to Document Info Records (DIRs)

3.5 Cost Center -- CRUD (Verified)

API: Cost Center OData V4 Service Protocol: OData V4 Evidence: SAP blog "A Practical Guide to Cost Center APIs in SAP S/4HANA Cloud" confirms create, read, update, delete operations.

3.6 Business Partner / Supplier -- CRUD (Verified)

API: API_BUSINESS_PARTNER (OData V2) Communication Scenario: SAP_COM_0008 Evidence: Multiple SAP blogs confirm full CRUD. Service is activated automatically when SAP_COM_0008 communication arrangement is created.

Important: This API is for CRUD operations only, not for mass data replication.

3.7 GL Account Master Data -- READ (Partially Verified)

API: API_GLACCOUNTINCHARTOFACCOUNTS_SRV (OData V2) Limitation: In S/4HANA Cloud Public Edition, the chart of accounts comes pre-delivered with ~2,000 GL accounts under YCOA. Customers cannot create new charts of accounts -- only adapt descriptions and add accounts within the YCOA structure. Creating GL accounts via API may be limited; the Migration Cockpit is the primary tool for mass GL account setup.

4. iPaaS & Middleware Findings

4.1 Celigo

Connector: Native SAP S/4HANA Cloud connector Connection: Targets S/4HANA Cloud HTTP APIs (OData) Authentication: Basic Auth or OAuth via Communication Arrangement

Pre-built operations include:

Supplier Invoice: Create, read, list, delete, release, reverse
Purchase Order: Create, read, update, delete, list (items and headers)
Business Partner: CRUD operations
Custom: Can switch any flow step to HTTP mode for unlisted endpoints

Write capability: Confirmed for supplier invoices and purchase orders.

4.2 Workato

Connector: SAP OData Connector Connection: Connects to S/4HANA Cloud Public Edition via OData APIs Authentication: Basic Auth or OAuth BTP Authentication

Capabilities:

Create, Update, Delete, Get, Query, Replace operations on any OData entity
Works with hundreds of OData APIs out-of-the-box
Supports purchase orders, requisitions, invoices, products
Generic OData connector -- can target any exposed OData service

Write capability: Confirmed -- full CRUD on supported entities.

4.3 Make.com (formerly Integromat)

Connector: SAP S/4HANA Public Cloud connector Connection: Via Fiori Launchpad communication system setup

Available modules:

Invoices: Monitor, list, retrieve, update
Orders: Monitor, list, retrieve, update
Payments: Trigger on creation, list, create, retrieve, update, delete payment advices
Business Partners: Trigger on create/update, list, create, retrieve
Credit Memos: Trigger on creation, list, create, update

Write capability: Confirmed for business partners, payment advices, credit memo requests.

4.4 n8n

Connector: No native SAP connector Workaround options:

HTTP Request node targeting OData APIs directly
Community connector (NeKu AI n8n SAP Connector)
CData Connect AI integration

Write capability: Possible via HTTP node + OData, but no pre-built SAP module.

4.5 Zapier

Connector: No native SAP S/4HANA Cloud connector found Workaround: HTTP/Webhook actions could target OData APIs, but no pre-built integration.

4.6 MuleSoft

Connector: SAP S/4HANA OData Connector (v2.9+) Capabilities: Full OData operations, enterprise-grade

4.7 iPaaS Summary

Platform	Native Connector	Write Support	Best For
Celigo	Yes	Yes (invoices, POs, partners)	Mid-market AP automation
Workato	Yes (OData)	Yes (full CRUD)	Enterprise workflow automation
Make.com	Yes	Yes (partners, payments, credit memos)	Low-code automation
MuleSoft	Yes	Yes (full OData)	Enterprise integration
n8n	No (HTTP workaround)	Yes (via HTTP)	Self-hosted open source
Zapier	No	No native	Not recommended for SAP

5. Alternative Integration Channels

5.1 What Is NOT Available in Public Edition

Channel	Status	Notes
RFC/BAPI	Blocked	No RFC connections in Public Cloud
IDoc	Blocked	No IDoc processing available
Direct DB access	Blocked	No access to internal tables
SAP GUI	Blocked	No SAP GUI access
Custom ABAP (full)	Blocked	Only Key User extensibility or ABAP Cloud (restricted)

5.2 Available Alternative Channels

SAP Integration Suite (BTP)

Part of BTP, basic edition included with S/4HANA Cloud subscription
Acts as middleware between external systems and S/4HANA Cloud
Supports SFTP, AS2, XI, SOAP adapters for asynchronous scenarios
Pre-built integration content packages for common scenarios
Can transform file-based inputs (CSV, XML) into OData API calls

Migration Cockpit

Primary tool for mass/bulk data loading
Supports Excel XML format, CSV files, remote HANA Cloud database
Full coverage of data objects (GL accounts, cost centers, business partners, etc.)
Not suitable for ongoing integration -- designed for one-time or periodic data migration

Custom CDS Views (Key User Extensibility)

Create custom OData V2 services on top of SAP CDS views
Scenario-specific: one CDS view per scenario (External API vs Data Extraction)
Read-only for data extraction; can be used for custom read APIs
Limitation: fields from Data Source Extensions are read-only

SAP Event Mesh (BTP)

Event-driven architecture for outbound notifications
S/4HANA Cloud publishes business events (e.g., "Invoice Created", "Business Partner Changed")
Events delivered via AMQP, MQTT, or Webhooks
Requires SAP BTP subscription
Enables real-time reaction to SAP events without polling

SFTP (via Integration Suite)

Not direct to S/4HANA Cloud -- requires SAP Cloud Integration as intermediary
Integration Suite transforms files into API calls
Useful for customers with legacy file-based workflows

6. Licensing & Access Requirements

6.1 API Access -- Included in Base Subscription

Key difference from On-Premise: In SAP S/4HANA Cloud Public Edition, there is NO Digital Access / Indirect Access licensing model. API access is included in the SaaS subscription.

Aspect	Public Edition	On-Premise (comparison)
API technical access	Included	Included
Document creation via API	Included in subscription	Triggers Digital Access license
Communication Users	Not counted as named users	Subject to user type rules
Per-document charges	None	Digital Access document blocks

This is a major advantage for Orcha's integration model -- no additional licensing costs for writing documents to SAP via API.

6.2 What the Customer Must Have / Enable

SAP S/4HANA Cloud Public Edition subscription (base requirement)
Administrator access to Fiori Launchpad for Communication Management
Communication Arrangement setup for each required API:
- SAP_COM_0057 (Supplier Invoice Integration)
- SAP_COM_0002 (Finance - Posting Integration / Journal Entries)
- SAP_COM_0008 (Business Partner / Supplier Integration)
- Attachment service scenario
- Cost Center service scenario
Communication User created for Orcha (technical user, not a named user license)
Communication System entry representing Orcha's system

6.3 Optional / Additional Purchases

Component	When Needed	Approx. Cost Impact
SAP BTP credits (beyond included)	If using Event Mesh, custom extensions, or heavy Integration Suite usage	Per-use beyond included credits
SAP Integration Suite (advanced)	If needing SFTP adapters, complex transformations, or pre-built content	Additional BTP credits
SAP Event Mesh	For real-time event notifications	BTP credits

6.4 Setup Steps for Customer

Login to SAP Fiori Launchpad as administrator
Create Communication User (Maintain Communication Users app) -- set password or upload certificate
Create Communication System (Communication Systems app) -- enter Orcha system details (hostname, etc.)
Create Communication Arrangement for each scenario:
- Select Communication Scenario (e.g., SAP_COM_0057)
- Assign Communication System
- Assign Communication User
- Configure authentication (Basic Auth or OAuth)
Note the Service URL from the arrangement -- this is the API endpoint
Share credentials securely with Orcha

6.5 Quarterly Update Consideration

SAP S/4HANA Cloud Public Edition receives mandatory quarterly updates. This means:

APIs are upgrade-stable (SAP's commitment)
New APIs/features are added quarterly
Deprecated APIs follow a deprecation timeline
Integration should use only released/stable APIs to avoid breakage

7. Orcha-Specific Deep Dive

7.1 Write Supplier Invoices

Primary path: OData V2 via API_SUPPLIERINVOICE_PROCESS_SRV

Communication Scenario: SAP_COM_0057
Endpoint: POST /sap/opu/odata/sap/API_SUPPLIERINVOICE_PROCESS_SRV/A_SupplierInvoice
Payload: Header data (supplier, amount, currency, dates, company code) + item data (GL account, cost center, tax code) + optional PO reference
Response: Returns created invoice number and fiscal year

For parking invoices: Use SOAP service II_IVE_SUPLRINVCERPCRTRC (same communication scenario SAP_COM_0057)

For credit/debit memos: Use Journal Entry - Post API (SOAP, SAP_COM_0002) with appropriate document type

7.2 Attach PDF Documents

API: API_CV_ATTACHMENT_SRV (OData V2)

Endpoint: POST /sap/opu/odata/sap/API_CV_ATTACHMENT_SRV/AttachmentContentSet
Method: HTTP POST with binary content in request body
Headers: Content-Type for the file (e.g., application/pdf), slug header with filename
Links to: Business object key (e.g., Supplier Invoice number + fiscal year)
Supported objects: Supplier Invoice, Purchase Order, Sales Order, Service Order, Purchase Requisition

7.3 Write Reference Data (Cost Centers)

API: Cost Center OData V4 Service

Operations: Create, Read, Update, Delete
Synchronous: Real-time feedback on changes
Note: Also available as OData V2 read-only API and business events for outbound notifications

7.4 Write Reference Data (GL Accounts)

Constraint: In Public Edition, SAP delivers pre-configured chart of accounts (YCOA with ~2,000 accounts + YIKR as alternative). Customers cannot create arbitrary new charts of accounts.

Options:

Read existing GL accounts via API_GLACCOUNTINCHARTOFACCOUNTS_SRV
Add new accounts within the YCOA structure via Fiori apps or Migration Cockpit
Map Orcha's account references to existing YCOA accounts

Recommendation for Orcha: Read GL account master data via API for mapping/validation; do not attempt to create GL accounts via API. Use existing YCOA structure.

7.5 Trigger/Manage Approvals

SAP's approach: Flexible Workflow for supplier invoice approval is configured in S/4HANA Cloud directly (Manage Workflows app). It supports:

Condition-based routing (by amount, company code, blocking status)
One-step or multi-step approval chains
My Inbox app for approvers

Orcha integration pattern:

Option A (Recommended): Orcha performs its own approval workflow externally, then posts the approved invoice via API. The S/4HANA system receives a completed, approved invoice that goes straight to payment.
Option B: Post invoice to S/4HANA in "blocked" status, then use the Release endpoint (POST .../Release) after external approval.
Option C: Let S/4HANA handle approval internally via Flexible Workflow after Orcha posts the invoice.

No direct "trigger workflow" API exists. Workflows are triggered automatically based on configured conditions when documents are created/changed.

7.6 Read Payment Status & Document Lifecycle

Supplier Invoice status:

API_SUPPLIERINVOICE_PROCESS_SRV -- GET operations return status fields including posting status, payment block, clearing status
Filter by supplier, date range, company code, etc.

Payment information:

Payment Advice APIs (AP/AR) allow reading payment advice data
PaymentAdviceAccountType = K for vendor/supplier accounts
PaymentAdviceAccountType = D for customer accounts

Billing documents:

API_BILLING_DOCUMENT_SRV -- Read, Cancel, GetPDF operations

Journal entries:

Operational Journal Entry Item - Read API (OData V2, A2X) for querying posted journal entries

7.7 Sync Reference Data Inbound (Read)

Data Type	API	Protocol	Notes
Chart of Accounts / GL Accounts	`API_GLACCOUNTINCHARTOFACCOUNTS_SRV`	OData V2	Read YCOA structure
Cost Centers	Cost Center Read API (OData V2)	OData V2	Read-only variant
Suppliers / Business Partners	`API_BUSINESS_PARTNER`	OData V2	Full read with filtering
Company Codes	Available via configuration APIs	OData V2	Part of organizational data
Tax Codes	Available via finance configuration APIs	OData V2	For tax determination mapping

8. Recommended Architecture

8.1 Recommended Integration Path

Orcha Cloud ──[HTTPS/OData V2]──> SAP S/4HANA Cloud Public Edition
                                     │
                                     ├── API_SUPPLIERINVOICE_PROCESS_SRV (invoices)
                                     ├── API_CV_ATTACHMENT_SRV (PDF attachments)
                                     ├── API_BUSINESS_PARTNER (suppliers)
                                     ├── Journal Entry Post SOAP (journal entries)
                                     └── Cost Center OData V4 (cost centers)

8.2 Direct API Integration (Recommended)

Why direct API is best for Orcha:

No middleware needed -- S/4HANA Cloud Public Edition APIs are cloud-native HTTPS endpoints
No additional licensing -- API access included in customer's subscription
No Digital Access fees -- unlike On-Premise, no per-document charges
Standard protocols -- OData V2/V4 and SOAP are well-documented and tooling-rich
Simple setup -- Communication Arrangement takes minutes to configure

Architecture:

Orcha calls S/4HANA APIs directly over HTTPS
Authentication via Basic Auth (simplest) or OAuth 2.0 (more secure)
No SAP BTP, Integration Suite, or middleware required for basic scenarios

8.3 When to Consider Middleware

Scenario	Solution
Customer needs SFTP-based file exchange	SAP Integration Suite
Complex data transformation required	SAP Integration Suite or Workato
Customer already uses Celigo/Workato	Leverage existing iPaaS
Real-time event notifications needed	SAP Event Mesh (BTP)
Mass data migration (one-time)	Migration Cockpit

8.4 Implementation Phases

Phase 1: Reference Data Sync (Read)

Read GL accounts, cost centers, suppliers from S/4HANA
Build mapping tables in Orcha
Low risk, read-only operations

Phase 2: Invoice Posting (Write)

Post supplier invoices via API_SUPPLIERINVOICE_PROCESS_SRV
Attach PDF originals via API_CV_ATTACHMENT_SRV
Include PO references where applicable

Phase 3: Status Monitoring (Read)

Poll for invoice status changes (posted, paid, blocked)
Read payment information
Update Orcha dashboard with SAP status

Phase 4: Advanced (Optional)

Event-driven notifications via SAP Event Mesh
Journal entry posting for non-PO invoices
Credit/debit memo automation

8.5 Risk Assessment

Risk	Severity	Mitigation
Quarterly mandatory updates break APIs	Low	SAP commits to API stability; use only released APIs
Rate limiting on high-volume posting	Medium	Use async SOAP APIs for batch; test throughput early
GL account structure mismatch (YCOA)	Medium	Map Orcha accounts to customer's YCOA during onboarding
Customer lacks admin access for setup	Low	Provide step-by-step setup guide
OAuth token management complexity	Low	Start with Basic Auth; upgrade to OAuth later