SAP S/4HANA comes in three deployment editions, each with a different integration profile. All three editions support every core Orcha AP automation capability — invoice posting, PDF attachment, master data sync, and status tracking — via standard APIs. The key differences lie in available protocols (OData-only vs. full BAPI/RFC/IDoc access), licensing model (included SaaS vs. Digital Access per-document fees), and customer setup complexity. This document maps each edition's capabilities, constraints, and recommended integration architecture.
Fully managed by SAP. Quarterly mandatory updates. Standardized, cloud-native APIs only.
Dedicated instance managed by SAP/hyperscaler. Full ABAP stack. Best of both worlds.
Full control. Customer manages hardware, upgrades, and operations. Maximum flexibility.
Core AP automation capabilities mapped across all three editions
| Capability | Public | Private | On-Prem | Primary API |
|---|---|---|---|---|
| Create supplier invoices Post AP invoices with GL, cost center, VAT |
OData V2
API_SUPPLIERINVOICE_PROCESS_SRV
|
|||
| Post journal entries FI documents, credit/debit memos |
SOAP
SAP_COM_0002
|
|||
| Attach PDF documents Upload invoice originals to SAP documents |
OData V2
API_CV_ATTACHMENT_SRV
|
|||
| Manage cost centers Full CRUD on cost center master data |
OData V4
Cost Center API (RAP)
|
|||
| Manage GL accounts Read/write chart of accounts |
OData V2
API_GLACCOUNTINCHARTOFACCOUNTS_SRV
|
|||
| Manage suppliers / business partners Full CRUD with VAT ID, IBAN, address |
OData V2
API_BUSINESS_PARTNER
|
|||
| Trigger approvals Route invoices for review/approval |
Flexible Workflow (config-driven)
|
|||
| Read payment / document status Track invoice lifecycle and payment state |
OData V2
Supplier Invoice API (GET)
|
|||
| Event notifications Real-time push on document changes |
SAP Event Mesh (BTP)
|
No Digital Access fees. Communication Users are not counted as named users. Document creation via API is covered by the SaaS subscription. Lowest cost for Orcha integration.
Every invoice/journal entry Orcha creates counts against the customer's Digital Access license. Sold as volume packs (typically 1,000 docs = 1 block). No public pricing — negotiated per customer. DAAP discounts of 50–90% available.
Syncing master data (GL accounts, cost centers, suppliers) into Orcha is read-only and does not trigger Digital Access fees on any edition.
Event Mesh, Integration Suite, and Cloud Connector require BTP credits. May be included in RISE Premium/Premium Plus tiers.
How Orcha reaches the customer's SAP system — the most common pre-sales question for Private and On-Premise deployments
Cloud-to-cloud, no tunnel needed. SAP system exposes HTTPS endpoints publicly. Orcha connects directly via internet. Simplest option — zero infrastructure. Firewall whitelist Orcha's IP range. No additional SAP licenses required.
Reverse proxy — no inbound firewall ports. Lightweight Java agent on customer's network. Outbound-only TLS tunnel to SAP BTP. Virtual-to-real host mapping for security. Supports HTTP/S and RFC protocols. Requires SAP BTP subscription (may be included in RISE Premium).
Traditional network-level connectivity. IPsec or WireGuard VPN tunnel provisioned and managed by customer's IT team. Orcha gets direct network access to SAP. Supports all protocols (HTTP, RFC, IDoc). No SAP BTP dependency. Higher setup effort on customer IT side.
Unlike the Public Edition (where SAP hosts the API endpoints in the cloud), Private and On-Premise systems sit behind the customer's firewall. The customer must provision either a VPN tunnel or install the SAP Cloud Connector before Orcha can reach their system. This is typically the first item on the implementation checklist and can take 1–4 weeks depending on the customer's IT processes. Factor this into project timelines.
Cloud-native HTTPS endpoints. No middleware required. Simplest setup: Communication Arrangement in Fiori takes minutes. No extra licensing cost. Best cost profile.
Same modern APIs as Public, plus RFC/BAPI/IDoc as fallback. OAuth 2.0 via SICF. Cloud Connector for BTP connectivity. Confirm Digital Access coverage before go-live.
Activate OData services via /IWFND/MAINT_SERVICE + SICF. VPN or Cloud Connector for connectivity. Higher SAP Basis effort. Confirm Digital Access licenses and version ≥1909.
Important limitations to discuss with customers during pre-sales
| Edition | Constraint | Mitigation |
|---|---|---|
| Public | GL accounts limited to pre-delivered YCOA chart | Read and map to existing YCOA accounts. New accounts added via Fiori / Migration Cockpit. |
| Public | No RFC/BAPI/IDoc — OData and SOAP only | All Orcha needs are covered by standard OData/SOAP APIs. No fallback needed in practice. |
| Public | Invoice parking requires SOAP (not OData) | Use SOAP service II_IVE_SUPLRINVCERPCRTRC for park-then-post workflow. |
| Private On-Prem | Digital Access licensing adds per-document cost | Document expected volumes in proposal. Leverage DAAP discounts (50–90%). Read-only sync is free. |
| On-Prem | Higher setup complexity (SAP Basis admin required) | Provide step-by-step setup checklist. Require version ≥1909 and test/sandbox system. |
| On-Prem | Network connectivity (firewall, VPN) | SAP Cloud Connector (reverse proxy, no inbound ports) or VPN tunnel. |
| All editions | Approval workflows are config-driven, not API-triggered | Post invoices in blocked/parked status; let SAP workflow handle routing. Or manage approvals in Orcha before posting. |
| All editions | Journal entries are SOAP-only (no OData write) | SAP_COM_0002 SOAP API is stable and well-documented. Both sync and async variants available. |