Skip to content

Integrations

Cohera integrates with your existing enterprise systems to create a unified data layer without replacing your current infrastructure. Our connector architecture enables bi-directional synchronization while maintaining data integrity and compliance.

Cohera follows the “orchestration layer” approach:

  • We don’t replace your existing systems (Veeva, SAP, TrackWise)
  • We connect them into a unified data model
  • We add intelligence through AI-powered automation
  • We ensure compliance with full audit trails

SAP S/4HANA

Enterprise resource planning integration for materials, suppliers, and batch data. Setup Guide

Veeva Vault

Quality management and document control synchronization. Setup Guide

  • TrackWise - Quality event and CAPA synchronization
  • LIMS Systems - Laboratory data integration
  • Loftware - Label management
  • MasterControl - Document control
  • SAP QM - Quality management module
┌─────────────────────────────────────────────────────────┐
│ COHERA PLATFORM │
├─────────────────────────────────────────────────────────┤
│ ONTOLOGY LAYER │
│ Supplier ←→ Component ←→ Certificate ←→ Product │
├─────────────────────────────────────────────────────────┤
│ CONNECTOR FRAMEWORK │
│ ┌───────────┐ ┌───────────┐ ┌───────────┐ │
│ │ SAP │ │ Veeva │ │ TrackWise │ │
│ │ Connector │ │ Connector │ │ Connector │ │
│ └─────┬─────┘ └─────┬─────┘ └─────┬─────┘ │
├────────┼─────────────┼─────────────┼────────────────────┤
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌───────────┐ ┌───────────┐ ┌───────────┐ │
│ │ SAP S/4 │ │Veeva Vault│ │ TrackWise │ │
│ │ HANA │ │ Quality │ │ Digital │ │
│ └───────────┘ └───────────┘ └───────────┘ │
└─────────────────────────────────────────────────────────┘

Data flows both directions:

  • Inbound: Import data from source systems into Cohera
  • Outbound: Push Cohera decisions and updates back to source systems

When data conflicts occur between systems:

  1. Timestamp-based: Most recent change wins
  2. Source priority: Designated system of record wins
  3. Manual review: Flag for human decision
  4. Custom rules: Define your own resolution logic

Map fields between different schemas:

{
"source_field": "LIFNR",
"target_field": "supplier_code",
"transformation": {
"type": "format",
"pattern": "SUP-{value}"
}
}

Connectors detect changes through:

  • Polling: Scheduled checks for updates
  • Webhooks: Real-time notifications (where supported)
  • Change logs: Database-level change tracking
{
"id": "conn_sap_prod",
"name": "SAP S/4HANA Production",
"type": "sap_s4hana",
"status": "active",
"authentication": {
"type": "oauth2",
"client_id": "cohera_integration",
"token_url": "https://sap.company.com/oauth/token"
},
"endpoints": {
"api_base": "https://sap.company.com/api/v1"
},
"sync_config": {
"direction": "bidirectional",
"interval_minutes": 15,
"batch_size": 100
}
}
{
"connection_id": "conn_sap_prod",
"entity_type": "supplier",
"source_object": "BusinessPartner",
"field_mappings": [
{
"source": "BusinessPartner",
"target": "supplier_code",
"required": true
},
{
"source": "BusinessPartnerFullName",
"target": "name",
"required": true
},
{
"source": "Country",
"target": "attributes.country",
"transformation": "iso_country_code"
}
],
"filters": {
"BusinessPartnerCategory": "2"
}
}
GET /v1/integrations/connections
POST /v1/integrations/connections
POST /v1/integrations/connections/{connection_id}/test
POST /v1/integrations/connections/{connection_id}/sync
GET /v1/integrations/connections/{connection_id}/history
{
"connection_id": "conn_sap_prod",
"status": "healthy",
"last_sync": {
"timestamp": "2024-01-20T14:00:00Z",
"status": "success",
"records_synced": 45,
"duration_seconds": 12
},
"next_sync": "2024-01-20T14:15:00Z",
"metrics": {
"success_rate_24h": 99.5,
"avg_sync_duration": 15,
"total_records_synced_24h": 1250
}
}

When sync errors occur:

{
"sync_id": "sync_abc123",
"status": "partial_success",
"records_attempted": 100,
"records_succeeded": 97,
"records_failed": 3,
"errors": [
{
"record_id": "SUP-001",
"error_code": "validation_failed",
"message": "Invalid country code: XX",
"field": "Country"
}
]
}
MethodUse Case
OAuth 2.0Recommended for cloud systems
API KeySimple integrations
CertificateHigh-security environments
Basic AuthLegacy systems only
  • All data encrypted in transit (TLS 1.3)
  • Credentials stored in encrypted vault
  • IP allowlisting available
  • Audit logs for all sync operations
  1. Choose your integration from the available connectors
  2. Gather credentials from your source system administrator
  3. Configure the connection following the setup guide
  4. Define field mappings for your data model
  5. Test the connection before enabling sync
  6. Monitor sync health through the dashboard

SAP S/4HANA Setup

Complete guide for SAP integration. Get started

Veeva Vault Setup

Complete guide for Veeva integration. Get started