Epicor ERP Integration

Which Epicor products Horizon connects to

• Epicor Kinetic (Epicor ERP 10 and 11) — the primary Epicor manufacturing ERP, deployed cloud and on-premise. REST API and Service Connect-based integration.
• Epicor Prophet 21 — used by distributors and some manufacturers in industrial supply categories. REST API and direct database access where customer prefers.
• Epicor Eclipse — used in electrical and plumbing distribution. Less common in manufacturing but supported through the same patterns.
• Older Epicor products (Vantage, Vista) — for customers still running these, direct database access through documented schemas.

Kinetic's REST API approach

Epicor Kinetic exposes a comprehensive REST API covering most operational entities. The integration uses three patterns:

• Standard REST endpoints — for item master, inventory, sales orders, purchase orders. Direct GET/POST against Kinetic's documented endpoints.
• Business Activity Queries (BAQs) — for customer-specific data aggregations. BAQs are Kinetic's saved query mechanism, similar to NetSuite saved searches. Horizon can call BAQs the customer's planning team already uses, which captures their existing business logic rather than reinventing it.
• BPM (Business Process Management) callbacks — for event-driven integration. When a sales order is approved or shipped, Kinetic can notify Horizon to trigger re-forecasting.

Kinetic-specific data objects Horizon reads

• Part master with planning attributes (Process MRP, ABC code, lead time, lot size)
• PartPlant — the per-plant override on part attributes that Kinetic supports
• PartBin records for inventory positions by bin location
• OrderHed and OrderDtl for sales order history
• POHeader and PODetail for purchase orders
• JobHead and JobMtl for production jobs and material requirements
• BOM via PartMtl records (Kinetic stores BOMs at the part level)
• Operations and resources through JobOper and Resource records

Prophet 21 distribution focus

For distributors running Prophet 21, Horizon's integration focuses on the distribution-specific entities:

• Item master with vendor-item relationships
• Multi-location inventory with branch-level positioning
• Customer order history with branch and customer dimensions
• Purchase order and receiving history
• Vendor master with multiple lead time scenarios (regular, expedited, ocean)

Distribution-heavy customers often benefit more from Horizon's replenishment planning and multi-echelon inventory optimization than from production planning — the integration scope reflects this.

Alternative integration path

For customers preferring file-based exchange — particularly common in Prophet 21 distribution environments — Horizon supports scheduled SFTP delivery of CSV extracts produced by Epicor's reporting framework. Works alongside the REST API path.

Authentication and connection

• Kinetic Cloud: API authentication using Kinetic's documented OAuth flow with service account.
• Kinetic on-premise: Basic authentication or token-based, depending on the customer's Kinetic security configuration.
• Prophet 21: REST API authentication, or read-only database access for the older deployments.

Write-back patterns

• Planned purchase orders written through standard POSuggestion records or Suggested PO mechanism
• Planned production jobs written as JobSuggestion records
• Planning parameter updates on Part and PartPlant records
• Forecast values written to the ForecastHed/ForecastDtl tables for Kinetic's own consumption

Common Epicor-specific considerations

• Multi-plant deployments — Kinetic's per-plant overrides on part attributes are powerful but require explicit mapping during integration. The connector captures plant-specific lead times, safety stocks, and planning codes accurately.
• BAQ customization — Most Kinetic customers have heavy BAQ customization for their own reporting. The integration can leverage existing BAQs rather than duplicating the logic in Horizon's queries.
• Process vs discrete deployments — Some Kinetic customers run process manufacturing (food, chemicals); most run discrete. Process customers' BOMs include yield and shrinkage that the integration captures explicitly.
• Configurator and engineered products — For Kinetic customers running heavy product configuration, the BOM data is dynamic per order. The integration handles this by pulling job-level BOMs for in-flight production rather than only standard BOMs.