Axya integrates with SAP environments using a cloud-to-cloud architecture via SAP Business Technology Platform (BTP) and SAP Integration Suite. This approach eliminates the need for on-premise middleware while maintaining secure connectivity to your SAP system.
| Aspect |
Details |
| Type |
Native Connector (built by Axya) |
| Architecture |
Cloud-to-cloud via SAP Integration Suite |
| Deployment |
No on-premise middleware — uses SAP Cloud Connector for on-premise SAP ECC |
| Sync Frequency |
Configurable (default: 5 minutes) |
| Direction |
Bidirectional |
- SAP S/4HANA (Cloud and On-Premise)
- SAP ECC (via SAP Cloud Connector)
- Purchase Orders — Headers, line items, quantities, prices, vendor assignments
- PO Documents — PDF generated via SAP and attached to orders in Axya
- Revisions — Modified POs detected by status changes and re-synced
- Contact Information — Buyer and vendor contact details for routing
- Multi-Level Vendor Support — Parent vendor and ordering address (branch) level assignments
- Supplier Acknowledgments — PO confirmation status
- Delivery Date Confirmations — Line-level confirmed dates
- Price Updates — Negotiated pricing
- Quantity Changes — Agreed modifications
- Buyer creates a PO in SAP and sets the custom status field to trigger sync
- Axya detects pending POs via the SAP Integration Suite
- PO data and PDF are retrieved and synced to Axya
- SAP status is updated to reflect successful sync
- Supplier interacts via Axya's portal
- Supplier responses are pushed back through the Integration Suite to SAP
- SAP status is updated to reflect acknowledgment
A custom status field in the PO tracks the integration lifecycle:
| Status |
Meaning |
| Send to Axya |
PO ready for sync |
| Success |
Successfully synced to Axya |
| Failed |
Sync failed (details in error log) |
| Acknowledged |
Supplier confirmed the PO |
| Revision |
Revised PO pending re-sync |
- No On-Premise Middleware — Leverages SAP's own cloud infrastructure for connectivity
- Secure Tunnel — SAP Cloud Connector provides secure access to on-premise SAP without opening inbound ports
- Multi-Vendor Contact Routing — Supports parent vendor, ordering address, and per-PO buyer contact assignments for flexible notification routing
- Partial Acknowledgment — Line-level supplier confirmations synced independently
- Automatic Retry — Failed syncs are retried automatically over a configurable window
- SAP Integration Suite subscription with ability to create/deploy integration flows
- SAP Cloud Connector configured for on-premise SAP ECC (if applicable)
- OAuth 2.0 credentials for API authentication
- Custom status field added to the PO
- Company code for scoping the integration
- Network connectivity between SAP BTP and Axya's cloud endpoints
- OAuth 2.0 authentication with token caching and automatic refresh
- SAP Cloud Connector ensures no direct internet exposure of on-premise SAP
- All communication over HTTPS (TLS 1.2+)
- Axya stores only synced PO data — no access to other SAP modules or data
For setup assistance, contact your Axya account representative.