OCI Interface: Integration & Implementation
Implement Your OCI Interface Correctly
From hook URL configuration to live operations
The OCI interface connects your ERP system directly to the supplier catalog. We show you how to implement, configure, and troubleshoot OCI – technically precise, DACH-practical.
The Technical Side of OCI
The OCI interface is powerful, but requires careful configuration. This guide covers the key integration points – from hook URL to session management – so your implementation runs stably.
OCI Interface in 4 Steps
Implementation overview and configuration
1. Hook URL Configuration
You configure an OCI catalog in SAP SRM or your ERP with a hook URL. This URL points to Ovenca (e.g., https://ovenca.example.com/oci/hook). The ERP sends user context and shopping cart data to this URL.
- HTTPS certificate validation
- Whitelist ERP IP address
- Log query parameters
2. User Context & Session
The ERP passes the user (name, email, cost center, buyer role) and a session token. Ovenca reads this data, creates a session, and redirects the user to catalog browse.
- User mapping against LDAP/AD
- Cost center as filter
- Inactivity timeout
3. Shopping Cart & Feedback
The user selects products in the catalog. Ovenca puts them in an OCI shopping cart, validates against availability and prices, and sends the data back to the ERP's hook URL via POST.
- Generate OCI XML payload
- Real-time price query
- Attribute mapping
4. Error Handling & Monitoring
Failed hook calls (e.g., ERP offline, certificate invalid) must be logged and monitored. Ovenca provides an audit dashboard and alert mechanisms for integration errors.
- Retry logic (exponential backoff)
- Error email notifications
- Grafana integration
Integration Quality That Counts
A poorly configured OCI interface leads to data loss, performance issues, and user frustration. Ovenca is built to be stable.
Learned from SAP SRM
Ovenca's core team has years of SRM integration experience. We know the pitfalls and deliberately build in resilience.
REST & Legacy Both
OCI is HTTP-based, but not always RESTful. Ovenca understands old SAP protocols and modern API patterns equally.
Logging & Debugging
Every OCI transaction is logged. You see exactly what data arrived, how it was processed, and where issues might occur.
Failover & Redundancy
Ovenca runs redundantly with automatic failover. Your users won't notice downtime – the integration stays stable.
SAML & OAuth Ready
You can secure OCI with additional authentication (SAML, OAuth, 2FA) – ideal for sensitive procurement data.
Technical Support 24/5
Integration issue? Our technicians can pull a trace in minutes and identify the problem. No waiting at large providers.
OCI Interface: Frequently Asked Questions
Related Solutions
Explore other solutions that complement your procurement process.
OCI Integration: We Make You Secure
A broken OCI integration costs you productivity daily. Let our tech experts audit and optimize your integration.
Technical Questions About OCI Integration?
Talk to our integration team. We diagnose errors, optimize performance, and document everything.