SAP S/4HANA Cloud Private 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, Private Edition (single-tenant managed cloud, formerly "extended edition" / HEC)

1. Executive Summary & Capability Matrix

SAP S/4HANA Cloud Private Edition (PCE) offers the broadest integration surface of all S/4HANA deployment models. As a single-tenant, customer-dedicated instance with full ABAP stack access, it supports modern cloud APIs (OData, SOAP) and traditional SAP interfaces (BAPIs, RFC, IDocs). This makes it significantly more flexible than the Public Edition for third-party integrations like Orcha.

Capability Matrix (Orcha Use Case)

Overall assessment: SAP S/4HANA Cloud Private Edition is fully capable of supporting all Orcha integration requirements. The dual availability of modern APIs and traditional interfaces provides exceptional flexibility and fallback options.

2. API Landscape

2.1 Deployment Model Context

SAP S/4HANA Cloud Private Edition is fundamentally different from the Public Edition:

Key insight: Private Edition gives you the best of both worlds -- all cloud-era APIs available in the Public Edition, plus all traditional on-premise interfaces (BAPI, RFC, IDoc). This dramatically reduces integration risk.

2.2 API Protocols Available

OData V2 APIs (Primary for most read/write operations)

• RESTful, JSON/XML payloads
• Synchronous request/response
• CSRF token required for write operations
• Path pattern: /sap/opu/odata/sap/{SERVICE_NAME}
• Hundreds of pre-built services across all functional areas

OData V4 APIs (Newer services, RAP-based)

• Modern OData standard with batch and deep insert support
• Built on RESTful ABAP Programming Model (RAP)
• Extensible via custom fields
• Path pattern: /sap/opu/odata4/sap/{SERVICE_NAME}

SOAP APIs (Critical for journal entry posting)

• Used for complex transactional operations
• Both synchronous and asynchronous variants
• Communication Scenario-based activation
• Key for finance posting integration (SAP_COM_0002)

RFC/BAPI (Available in Private Edition only)

• Direct function module calls
• Synchronous and asynchronous (tRFC, qRFC)
• Battle-tested, widely documented
• Requires SAP JCo or RFC SDK on client side
• Available via SAP Cloud Connector or direct RFC connection

IDoc (Available in Private Edition only)

• Asynchronous document exchange
• Well-suited for batch/bulk operations
• Standard message types: INVOIC02, ORDERS05, etc.
• ALE/EDI infrastructure fully available

2.3 Authentication Methods

Recommended for Orcha: OAuth 2.0 Client Credentials Grant for OData/SOAP APIs. For RFC/BAPI access, a system user (type B) with RFC authorization.

OAuth 2.0 setup steps for Private Edition:

1. Enable HTTPS with valid SSL/TLS certificate (SAP_BASIS >= 740 SP08)
2. Activate OAuth service in SICF: /default_host/sap/bc/sec/oauth2/authorize
3. Register OAuth client in transaction SOAUTH2 (Client Type: Confidential)
4. Configure Grant Type: Client Credentials
5. Assign scope to target OData service
6. Obtain token from: https://<host>/sap/bc/sec/oauth2/token

2.4 Rate Limits & Throttling

SAP does not publish specific rate limits for S/4HANA Cloud Private Edition OData/SOAP APIs. Key considerations:

• No hard public rate limit documentation exists for PCE. Since the instance is single-tenant, capacity depends on the provisioned system sizing.
• SAP API Management (if deployed) can impose Quota Policies, Spike Arrest Policies, and Concurrent Rate Limits.
• HTTP 429 (Too Many Requests) is returned when rate limits are hit.
• Practical guidance: For a Private Edition system, the bottleneck is typically the application server capacity (number of work processes), not API-level throttling. Batch operations should use async APIs or IDocs to avoid blocking dialog work processes.

2.5 Key Portal Links

3. Write Capability Verification

3.1 Supplier Invoice Creation (Confirmed WRITE)

API: API_SUPPLIERINVOICE_PROCESS_SRV Method: POST /A_SupplierInvoice Protocol: OData V2

Required fields:

• CompanyCode (string, e.g., "1710")
• DocumentDate (string, e.g., "2026-04-01")
• PostingDate (string, e.g., "2026-04-01")
• DocumentCurrency (string, e.g., "EUR")
• InvoiceGrossAmount (string, e.g., "1511.60")

Optional fields (via supplierInvoiceAdditionalFields):

• CashDiscount1Percent, CashDiscount1Days
• CashDiscount2Percent, CashDiscount2Days
• NetPaymentDays
• PaymentBlockingReason
• AccountingDocumentType

Navigation properties for line items:

• to_SupplierInvoiceItemGLAcct -- GL account assignments
• to_SupplierInvoiceItmAcctAssgmt -- cost allocation (cost center, profit center, etc.)
• to_SuplrInvcItemPurOrdRef -- purchase order references

Additional operations on this API:

• GET -- Read supplier invoices
• POST with action Release -- Release for payment
• POST with action Reverse -- Reverse/cancel invoice

Evidence: SAP API Hub documentation confirms POST creates new supplier invoices. Multiple SAP community posts demonstrate payloads. Paragon integration platform documents required/optional fields.

BAPI fallback: BAPI_INCOMINGINVOICE_CREATE -- RFC-enabled, identical to transaction MIRO. Fully available in Private Edition.

3.2 Credit Note / Credit Memo (Confirmed WRITE)

API: Credit Memo Request API (OData V4, A2X) Method: POST

Credit memos can be created via:

1. OData V4 Credit Memo Request API -- native A2X service for credit memo request creation
2. Supplier Invoice API -- using BAPI_INCOMINGINVOICE_CREATE with document type set to credit memo
3. IDoc INVOIC02 -- with appropriate message type indicating credit

Private Edition also exposes business events for credit memo request creation/change/deletion, enabling event-driven integration via SAP Event Mesh.

3.3 Journal Entry Posting (Confirmed WRITE)

API: SOAP-based Journal Entry APIs (Communication Scenario SAP_COM_0002)

Important: Journal entry posting is SOAP-only in SAP S/4HANA. There is no OData API for creating journal entries. OData is used only for reading (API_JOURNALENTRYITEMBASIC_SRV, API_OPLACCTGDOCITEMCUBE_SRV).

BAPI fallback: BAPI_ACC_DOCUMENT_POST -- the classic accounting document posting BAPI, equivalent to FB01/F-02. Posts GL, AR, AP documents.

3.4 Cost Center Creation/Update (Confirmed WRITE)

API: Cost Center OData V4 Service (RAP-based) Operations: Create, Read, Update, Delete (full CRUD)

Built on the RESTful ABAP Programming Model (RAP), this service:

• Supports real-time synchronous interactions
• Is extensible via custom fields
• Returns immediate confirmation of changes

BAPI fallback: BAPI_COSTCENTER_CREATEMULTIPLE / BAPI_COSTCENTER_CHANGEMULTIPLE

3.5 GL Account Master Data (Confirmed WRITE)

API: API_GLACCOUNTINCHARTOFACCOUNTS_SRV Operations: Create, Read, Update, Delete

Entity operations:

• CreateRequestBuilder -- create new GL accounts
• UpdateRequestBuilder -- update existing GL accounts
• DeleteRequestBuilder -- delete GL accounts
• GetAllRequestBuilder / GetByKeyRequestBuilder -- read GL accounts

Communication Scenario: SAP_COM_0087 (SAP Business Objects Cloud for Planning Integration)

Important caveat: In S/4HANA, GL accounts are configuration objects, not transactional data. In many implementations, GL account creation is controlled via transport requests (development -> quality -> production). API-based creation may be restricted by authorization and change management policies. This needs to be validated with the customer's SAP Basis team.

3.6 Document Attachment (Confirmed WRITE)

API: API_CV_ATTACHMENT_SRV (Attachment Service) Method: POST (with binary payload)

Supports:

• Create attachments (PDF, DOC, JPG, XLS, TXT, etc.)
• Read attachment metadata and content
• Rename attachments
• Delete attachments

Attachment types supported:

• GOS (Generic Object Services) -- attach files to any business object
• DMS (Document Management System) -- for Document Info Records (DIRs)

Supported business objects: Sales Order, Purchase Order, Purchase Requisition, Supplier Invoice, Service Order, and more.

Configuration required:

1. Create Communication User
2. Create Communication System
3. Create Communication Arrangement

For Orcha: This API is the primary mechanism for attaching original invoice PDFs to the supplier invoice document in SAP after posting.

4. iPaaS & Middleware Findings

4.1 Celigo

Celigo connects to Private Edition either via direct HTTPS (if publicly accessible) or via Celigo's on-premise agent. If a needed API endpoint is not in the prebuilt connector, you can switch to HTTP mode and configure any OData/SOAP endpoint manually.

4.2 Workato

Workato is the strongest iPaaS option for Private Edition due to its SAP-certified RFC connector that supports BAPIs, RFCs, and IDocs -- covering the full integration surface available in PCE. Requires SAP JCo 3.1.7+ libraries and SAP Java IDoc Library 3.1.3+ on the OPA.

4.3 Make.com (formerly Integromat)

Make.com provides decent coverage for basic invoice and procurement operations but lacks RFC/BAPI/IDoc support needed for full Private Edition integration.

4.4 n8n

n8n does not have a native SAP S/4HANA connector. Integration requires manual HTTP request configuration or third-party middleware like CData Connect.

4.5 Zapier

4.6 iPaaS Summary

5. Alternative Integration Channels

5.1 IDoc (Intermediate Document)

Fully available in Private Edition. IDocs are SAP's traditional asynchronous document exchange format.

Relevant IDoc types for Orcha:

Setup requirements:

• Partner profile configuration (WE20)
• Port definition (WE21)
• Logical system/RFC destination (SM59, BD54)
• Distribution model (BD64)

INVOIC02 for supplier invoices:

• Simulates transaction MIRO
• Creates AP invoice in FI
• Segments: E1EDK01 (header), E1EDP01 (line items), E1EDS01 (totals), E1EDKA1 (partner data)
• Configuration via OBCA, OBCB, OBCC, OBCD, OBCE

Recommendation: IDocs are excellent for batch/bulk invoice posting and as a fallback if OData APIs have issues. Well-proven technology with decades of production use.

5.2 RFC/BAPI (Remote Function Call / Business API)

Fully available in Private Edition. Direct function module invocation.

Key BAPIs for Orcha use case:

Connection options:

• SAP JCo (Java Connector) -- for Java-based middleware
• SAP NCo (.NET Connector) -- for .NET-based middleware
• PyRFC -- for Python-based integration
• node-rfc -- for Node.js-based integration
• SAP Cloud Connector -- for BTP-mediated RFC access

5.3 SAP Cloud Connector

The Cloud Connector is a reverse invoke proxy that establishes a secure tunnel between the Private Edition instance (behind a firewall) and SAP BTP or external systems. It is the recommended connectivity approach for Private Edition.

Key characteristics:

• No inbound firewall ports needed
• Java-based, installed on-premise or in the PCE network zone
• Supports HTTP(S) and RFC protocols
• Manages virtual-to-real host mapping
• Integrates with SAP BTP Destination service

5.4 SAP Event Mesh / Business Events

S/4HANA Private Edition supports outbound business events that can be published to SAP Event Mesh (BTP service):

• Supplier invoice created/changed/deleted
• Business partner created/changed
• Credit memo request created/changed/deleted
• Purchase order created/changed

Events flow from S/4HANA -> Event Mesh topic -> Queue -> Webhook (consumer URL).

For Orcha: Useful for receiving real-time notifications about document status changes (e.g., invoice approved, payment posted) without polling.

5.5 SFTP / File-Based Integration

Available via SAP Cloud Integration (Integration Suite):

• SFTP adapter can serve as source for file-based data import
• Migration Cockpit accepts XML/CSV file uploads (max 100 MB per file)
• SAP Cloud Integration can orchestrate SFTP -> API transformation

Not recommended as primary integration method for Orcha, but useful for bulk data migration scenarios.

5.6 SAP Integration Suite

SAP Integration Suite (part of BTP) provides:

• Cloud Integration (CPI) -- message-based integration with prebuilt content
• API Management -- publish, manage, and monitor APIs
• Open Connectors -- connect to 170+ non-SAP applications
• Integration Advisor -- B2B integration with EDI/IDoc mapping

If the customer has RISE with SAP Premium/Premium Plus, Integration Suite credits may be included.

6. Licensing & Access Requirements

6.1 What the Customer Must Have

6.2 RISE with SAP Tiers

6.3 Digital Access Licensing (CRITICAL)

This is the most important licensing consideration for Orcha integration.

When Orcha creates documents in SAP via API, each qualifying document counts against the customer's Digital Access license:

Counted document types relevant to Orcha:

• Financial Posting (type 8): Supplier invoices, journal entries, credit notes -- ALL count
• Invoice (type 2): Billing documents
• Purchase Order (type 3): If Orcha creates PO-related documents

Pricing model:

• No public price list; negotiated per customer
• Tiered pricing: first million documents at base rate, subsequent millions at lower unit cost
• Typical range: <$1 to a few dollars per document (before discounts)
• SAP offers 50-90% discounts during RISE negotiations or audit resolutions
• Read-only API calls do NOT count -- only document creation events

RISE bundle considerations:

• Standard integrations and typical document volumes are generally covered under the RISE subscription
• Exceptionally high volumes may require additional Digital Access licenses
• This should be clarified during contract negotiation

Risk mitigation for Orcha:

1. Customer must confirm Digital Access license coverage before integration goes live
2. Orcha should document expected monthly document volumes in the proposal
3. Read-only operations (syncing master data inbound) carry no Digital Access cost
4. Only the initial document creation counts, not subsequent updates

6.4 Technical Setup Requirements

6.5 No Additional API License Required

The APIs themselves are included in the S/4HANA license. There is no separate "API access" license to purchase. The licensing obligation arises from the documents created, not from API usage itself.

7. Orcha-Specific Deep Dive

7.1 Write Reference Data: Cost Centers

Primary approach: OData V4 Cost Center API (RAP-based)

POST /sap/opu/odata4/sap/API_COSTCENTER/sap/CostCenter
Content-Type: application/json

{
  "ControllingArea": "0001",
  "CostCenter": "10001",
  "ValidityStartDate": "2026-01-01",
  "ValidityEndDate": "9999-12-31",
  "CostCenterName": "Marketing DACH",
  "CompanyCode": "1000",
  "BusinessArea": "0001",
  "CostCtrResponsiblePersonName": "J. Smith"
}

Communication Scenario: Controlling - Cost Center Integration Supports: Create, Read, Update, Delete (full CRUD)

7.2 Write Reference Data: GL Accounts / Chart of Accounts

Primary approach: OData V2 API_GLACCOUNTINCHARTOFACCOUNTS_SRV

POST /sap/opu/odata/sap/API_GLACCOUNTINCHARTOFACCOUNTS_SRV/A_GLAccountInChartOfAccounts
Content-Type: application/json

{
  "ChartOfAccounts": "YCOA",
  "GLAccount": "400100",
  "IsBalanceSheetAccount": false,
  "GLAccountGroup": "SAKO",
  "ProfitLossAccountType": "X",
  "to_Text": [{
    "ChartOfAccounts": "YCOA",
    "GLAccount": "400100",
    "Language": "EN",
    "GLAccountName": "Travel Expenses",
    "GLAccountLongName": "Travel and Entertainment Expenses"
  }]
}

Communication Scenario: SAP_COM_0087

Caveat: GL accounts are config objects in S/4HANA. Many customers manage them via transport requests. Verify with customer whether API-based GL creation is permitted in their change management process.

7.3 Write Transactional Data: Supplier Invoices

Primary approach: OData V2 API_SUPPLIERINVOICE_PROCESS_SRV

POST /sap/opu/odata/sap/API_SUPPLIERINVOICE_PROCESS_SRV/A_SupplierInvoice
Content-Type: application/json
X-CSRF-Token: <fetched-token>

{
  "CompanyCode": "1000",
  "DocumentDate": "2026-04-01",
  "PostingDate": "2026-04-01",
  "SupplierInvoiceIDByInvcgParty": "INV-2026-0042",
  "InvoicingParty": "VENDOR001",
  "DocumentCurrency": "EUR",
  "InvoiceGrossAmount": "1190.00",
  "AccountingDocumentType": "RE",
  "to_SupplierInvoiceItemGLAcct": [{
    "CompanyCode": "1000",
    "GLAccount": "400100",
    "DocumentCurrency": "EUR",
    "SupplierInvoiceItemAmount": "1000.00",
    "TaxCode": "V1",
    "CostCenter": "10001"
  }]
}

CSRF token flow:

1. GET /API_SUPPLIERINVOICE_PROCESS_SRV/ with header X-CSRF-Token: Fetch
2. Extract X-CSRF-Token and cookies from response
3. Include both in POST request

Additional operations:

• Release: POST /A_SupplierInvoice('{key}')/Release
• Reverse: POST /A_SupplierInvoice('{key}')/Reverse
• Read status: GET /A_SupplierInvoice('{key}')?$select=StatusCode,PaymentBlockingReason

7.4 Write Transactional Data: Credit Notes

Option 1: Via Supplier Invoice API with credit memo document type

• Same endpoint as supplier invoice
• Set AccountingDocumentType to credit memo type (e.g., "KG" for vendor credit memo)
• Amount is negative or document type indicates credit

Option 2: Credit Memo Request API (OData V4)

• Creates a credit memo request in the SD flow
• More appropriate for sales-side credit memos

Option 3: BAPI BAPI_INCOMINGINVOICE_CREATE

• Parameter INVOICEDOCTYPE set to credit memo type
• Fully available in Private Edition

7.5 Attach Documents (PDF Upload)

Primary approach: OData V2 API_CV_ATTACHMENT_SRV

POST /sap/opu/odata/sap/API_CV_ATTACHMENT_SRV/AttachmentContentSet
Content-Type: application/pdf
Slug: "invoice-2026-0042.pdf"
BusinessObjectTypeName: BUS2081
LinkedSAPObjectKey: <SupplierInvoice key>
X-CSRF-Token: <fetched-token>

<binary PDF content>

Business Object Types for Orcha:

• BUS2081 -- Supplier Invoice (MM Invoice Verification)
• BKPF -- Accounting Document (FI)

Supported formats: PDF, DOC, JPG, XLS, TXT, and more.

Workflow:

1. Create supplier invoice via API_SUPPLIERINVOICE_PROCESS_SRV -> get document key
2. Attach PDF via API_CV_ATTACHMENT_SRV using the document key as LinkedSAPObjectKey

7.6 Trigger/Manage Approvals

SAP offers multiple approval mechanisms in Private Edition:

1. Flexible Workflow (built into S/4HANA)

   • Configurable approval rules based on amount, company code, etc.
   • Multi-stage approval chains
   • User determination rules
   • No additional license required

2. SAP Build Process Automation (BTP)

   • Visual workflow designer
   • API-triggered workflows
   • Requires BTP credits / RISE Premium
   • Communication Arrangement exposes S/4HANA APIs for BPA to call

3. Classic SAP Workflow (WS01000XXX)

   • Full ABAP workflow engine
   • Customizable via transaction SWDD
   • Available in Private Edition

For Orcha integration:

• Orcha posts the invoice via API (it enters SAP in "Parked" or "Blocked" status)
• SAP's internal workflow handles approval routing
• Orcha can poll for status changes via GET on the Supplier Invoice API
• Alternatively, SAP Event Mesh can push status change events to Orcha

7.7 Read Status/Lifecycle

Payment status:

GET /sap/opu/odata/sap/API_SUPPLIERINVOICE_PROCESS_SRV/A_SupplierInvoice('{key}')
  ?$select=StatusCode,PaymentBlockingReason,AccountingDocExternalReference

Accounting document status (deeper view):

GET /sap/opu/odata/sap/API_OPLACCTGDOCITEMCUBE_SRV/A_OperationalAcctgDocItemCube
  ?$filter=CompanyCode eq '1000' and AccountingDocument eq '{doc_number}'
  &$select=ClearingDate,ClearingAccountingDocument,IsCleared

Payment processing status:

• OData: Payment Item API (Read/Update) -- API_PAYMENTITEM_SRV
• Fields: ClearingDate, ClearingDocument, IsCleared

Note: API_OPLACCTGDOCITEMCUBE_SRV reads from BSEG (Entry View) only. For ledger-specific data (e.g., asset postings), use API_JOURNALENTRYITEMBASIC_SRV which reads from ACDOCA (Ledger View). However, the latter is officially intended for SAP Analytics Cloud integration only.

7.8 Sync Reference Data Inbound (Read)

Chart of Accounts / GL Accounts:

GET /sap/opu/odata/sap/API_GLACCOUNTINCHARTOFACCOUNTS_SRV/A_GLAccountInChartOfAccounts
  ?$filter=ChartOfAccounts eq 'YCOA'
  &$expand=to_Text
  &$select=GLAccount,GLAccountName,IsBalanceSheetAccount,ProfitLossAccountType

Suppliers / Vendors:

GET /sap/opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner
  ?$filter=BusinessPartnerCategory eq '2'
  &$expand=to_Supplier,to_Supplier/to_SupplierCompany,to_Supplier/to_SupplierPurchasingOrg
  &$select=BusinessPartner,BusinessPartnerFullName,to_Supplier/SupplierAccountGroup

Communication Scenario: SAP_COM_0008 (Business Partner, Customer and Supplier Integration)

Cost Centers:

GET /sap/opu/odata/sap/API_COSTCENTER_SRV/A_CostCenter
  ?$filter=ControllingArea eq '0001'
  &$expand=to_Text
  &$select=CostCenter,CostCenterName,CompanyCode,ValidityStartDate,ValidityEndDate

All read operations are Digital Access-free -- no document creation, no licensing impact.

8. Recommended Integration Architecture

8.1 Recommended Path: Direct OData/SOAP API Integration

┌─────────────┐     HTTPS/OAuth 2.0     ┌──────────────────────┐
│             │ ──────────────────────── │                      │
│   Orcha     │   OData V2 (invoices)   │  SAP S/4HANA Cloud   │
│   Platform  │   SOAP (journal entries)│  Private Edition     │
│             │   OData V2 (attachments)│                      │
│             │ ◄────────────────────── │  (Single-tenant,     │
│             │   OData V2 (read master)│   full ABAP stack)   │
└─────────────┘                         └──────────────────────┘
       │                                          │
       │  Webhook / Event Mesh (optional)         │
       │ ◄────────────────────────────────────────┘
       │  (status change notifications)

Why this approach:

1. Simplest architecture -- direct HTTP(S) calls, no middleware required
2. Full write capability -- OData for invoices/master data, SOAP for journal entries
3. Standard authentication -- OAuth 2.0 Client Credentials
4. Attachment support -- native via Attachment Service API
5. No additional SAP licenses beyond existing PCE + Digital Access
6. Well-documented -- extensive SAP community and official documentation

8.2 Alternative Path: Via SAP Integration Suite (CPI)

If the customer already has SAP Integration Suite:

• Use prebuilt iFlows for common patterns
• Centralized monitoring and error handling
• Message transformation and routing
• Adds a layer of complexity but provides SAP-native observability

8.3 Fallback Path: BAPI/RFC via Middleware

If OData/SOAP APIs are insufficient or have issues:

• Use Workato with SAP RFC connector (SAP-certified)
• Or custom middleware with SAP JCo/PyRFC
• Full BAPI access as proven alternative
• Higher setup complexity but maximum flexibility

8.4 Implementation Priority

8.5 Pre-Sales Checklist for Customer

Before proposing integration, validate with the customer:

• SAP S/4HANA Cloud Private Edition version (2023, 2025, etc.)
• RISE tier (Base, Premium, Premium Plus) -- affects BTP credit availability
• Digital Access license status -- do they have it, what volume?
• Network accessibility -- is the PCE instance reachable via HTTPS from the internet, or is Cloud Connector needed?
• OAuth 2.0 readiness -- is HTTPS enabled with valid certificates?
• Change management policy -- can reference data (GL accounts, cost centers) be created via API, or must it go through transport?
• Approval workflow -- is Flexible Workflow or SAP Build Process Automation already configured for supplier invoices?
• Existing integration middleware -- do they have Integration Suite, Workato, or other iPaaS?
• Invoice posting process -- PO-based (3-way match) or non-PO (direct GL posting)?

9. Sources

SAP Official Documentation

• SAP Business Accelerator Hub -- S/4HANA Cloud Private Edition APIs
• SAP Business Accelerator Hub -- S/4HANA Cloud Private Edition Overview
• Supplier Invoice API
• Supplier Invoice API -- POST Resource
• Supplier Invoice -- OData V2 Documentation
• API for Supplier Invoice
• G/L Account - Read API
• Cost Center - Read API
• Credit Memo Request API (A2X, OData V4)
• OData API Attachments Service in S/4HANA Cloud
• APIs in Finance
• APIs for General Ledger Accounting
• Journal Entry APIs -- APIs for General Ledger Accounting
• Cloud Connector Documentation
• Flexible Workflow
• SAP S/4HANA Cloud Private Edition 2025 FPS00 What's New
• SAP S/4HANA Cloud Private Edition 2025 FPS01 What's New
• ABAP Platform in S/4HANA Cloud Private Edition 2025

SAP Community & Blogs

• Step-by-Step: Calling S/4HANA Private Cloud OData APIs with OAuth 2.0
• SAP Integration Suite -- Connecting to S/4HANA Private Cloud OData with OAuth
• A Practical Guide to Cost Center APIs in SAP S/4HANA Cloud
• APIs for Journal Entries -- The Collection (Updated July 2025)
• User Guide for Journal Entry Post API on S/4HANA Cloud
• Payload Examples for API Journal Entry -- Post
• Create a PDF attachment using the Attachments API in S/4HANA Cloud
• OData Service of Business Partner in SAP S/4HANA Cloud
• Maintain BusinessPartner Master Data using OData APIs
• IDocs in SAP S/4HANA -- Differences to SAP ECC 6.0
• Invoice Processing with S/4HANA Public Cloud & Private Cloud
• SAP S/4HANA Rate Limiting Discussion

Licensing & Commercial

• SAP S/4HANA Licensing in 2025 -- Complete Guide
• SAP Digital Access Licensing 2025
• SAP S/4HANA Licensing Costs and Models
• RISE with SAP S/4HANA Cloud Licensing Overview (PDF)
• RISE with SAP Pricing and Packaging (PDF)
• SAP Indirect Access Licensing in RISE with SAP 2024-2025
• RISE with SAP and SAP Private Cloud License Models and Costs

iPaaS Documentation

• Celigo -- Set up a connection to SAP S/4HANA Cloud
• Celigo -- Available SAP S/4HANA Cloud APIs
• Workato -- SAP RFC Connector
• Workato -- Configure SAP system for IDoc integrations
• Make.com -- SAP S/4HANA Public Cloud App
• SAP S/4HANA Cloud API Essentials Guide -- Rollout

Third-Party References

• Create Supplier Invoice -- Paragon Documentation
• Complete Guide to SAP S/4HANA APIs -- Apideck
• BAPI_ACC_DOCUMENT_POST Documentation
• SAP Nango Integration -- OAuth 2.0 Client Credentials