Axya integrates with Oracle E-Business Suite (EBS) R12.x for secure, bidirectional PO synchronization. A lightweight on-premise middleware handles reliable data exchange between Oracle EBS and Axya.
| Aspect |
Details |
| Type |
Partner-Delivered Integration |
| Architecture |
On-premise middleware |
| Deployment |
Windows service on customer VM |
| Sync Frequency |
5 minutes (configurable) |
| Direction |
Bidirectional |
- Purchase Orders — Headers, lines, and line locations
- PO Documents — PDF generated and attached
- Revisions — Modified POs detected via custom status field
- Reception Data — Receipt transactions for delivery tracking
- Supplier Acknowledgments — PO confirmation status
- Delivery Date Updates — Promise dates written back
- Price and Quantity Changes — Negotiated modifications applied
- Buyer creates a PO in Oracle EBS and sets the custom status field to trigger sync
- The middleware detects pending POs during its 5-minute sync cycle
- PO data and PDF are retrieved and sent to Axya
- Supplier interacts via Axya's portal
- Supplier responses are applied back to Oracle EBS using Oracle's standard change APIs
- Receipts are tracked and POs auto-archive when fully received
- Controlled Data Access — Secure access layer to Oracle EBS data without direct database exposure
- Standard Oracle APIs — Uses Oracle's own PO Change APIs for write-back, ensuring data integrity and validation
- Receipt Tracking — Full receipt lifecycle visibility from Oracle's receiving module
- Custom Status Field — Simple PO-level field for buyer-controlled sync triggering
- Automatic Archiving — POs archived when all lines are fully received
| Resource |
Minimum |
Recommended |
| OS |
Windows Server |
Windows Server |
| RAM |
8 GB |
16 GB |
| Disk |
40 GB |
80 GB |
| CPU |
2 vCPU |
4 vCPU |
- Oracle EBS database workspace for secure API access
- Database schema with appropriate privileges for PO data
- Access to Oracle standard PO change APIs
- Read access to receipt data
- VPN access to Oracle EBS environment
- Windows VM provisioned per requirements above
- Controlled access layer — no direct database exposure to external systems
- Middleware communicates outbound only over HTTPS
- Database service account with read-only access to PO tables
- Write operations use Oracle's validated standard APIs
For setup assistance, contact your Axya account representative.