Migrate from Edicom to Epicor Prophet 21

Edicom trading partner profiles (connection settings, supported document types, certification status, contact information) map to Epicor ERP Customer records for buyers and Supplier records for vendors. We export each partner profile and create the corresponding Epicor record with Address, Contact, and default terms populated. Trading partner EDI identifiers (AS2 ID, VAN ID) are stored in custom fields on the Customer or Supplier record for reference during EDI configuration.

Edicom message flows define which transaction types (ORDERS, INVOIC, DESADV, etc.) are active per trading partner. We export flow configurations as structured metadata and map them to Epicor EDI document type assignments per Customer or Supplier. We document the standard (X12, EDIFACT, VDA, ODETTE) and version for each active flow so the Epicor admin can enable the equivalent EDI module configuration post-migration.

Edicom translation maps translate between partner EDI formats and ERP data structures. Each map has source/destination field mappings and transformation rules that do not have a direct Epicor equivalent. We export map definitions as structured data, identify the ERP fields they reference, and document a BAQ or DMT import template that achieves the same transformation at the destination. Complex maps with conditional logic are flagged for manual rebuild by the customer's Epicor admin.

Edicom ORDERS inbound messages map to Epicor POHeader and POLine records. We extract the supplier, line items, quantities, and prices from the Edicom transaction archive and load them via Epicor DMT using the POHeadExcel and POLnExcel templates. SupplierNum and Plant resolve via the Supplier mapping from object 1.

Edicom INVOIC outbound messages map to Epicor InvoiceHead and InvoiceLoc records. We extract invoice headers, line items, tax amounts, and payment terms from the Edicom archive and load via DMT using the InvoiceHeadExcel template. CustomerNum resolves via the Customer mapping. Archived PDF attachments migrate as Document records linked to the Invoice.

Edicom DESADV (Advance Ship Notices) map to Epicor ShipHead, ShipCoHead, and ShipDtl records. We extract ship-from, ship-to, carrier, tracking numbers, and line-level quantities and load via DMT using the ShipHeadExcel and ShipDtl templates. PackSlip and CtnCount transfer as structured data.

Edicom connects to ERP systems via middleware, intermediate data tables, or direct API/WebService calls. The specific integration layer must be re-established at Epicor. We document each Edicom integration endpoint, the data it exchanges, and the transfer frequency, then map it to an Epicor IaaS connection definition or a REST API call configured in Epicor. Any intermediate data tables referenced by map logic are exported as lookup tables for re-implementation at the destination.

Many Edicom customers have customer-developed intermediate data tables and equivalence lists referenced in their map logic. We export these as structured lookup tables and document their update frequency and dependencies. At Epicor, these are re-created as UD (User-Defined) tables or standard Epicor lookup tables, with the update frequency documented for the customer's admin to configure as part of the new integration layer.

Edicom supports multiple EDI standards (X12, EDIFACT, VDA, ODETTE) and version variants per partner. We capture the standard and version for each active connection and map to Epicor EDI module-compatible equivalents. VDA and ODETTE, which are automotive and logistics-specific standards, require a third-party middleware assessment at Epicor as they are not natively supported.

TLS certificates, AS2/AS4 identifiers, and signing keys are provisioned under Edicom's account structure and cannot be transferred directly. We flag every certificate-bound connection during scoping and document the re-issuance timeline required for each trading partner. The customer's Epicor admin must coordinate AS2 re-configuration with each partner post-migration. This is a manual step that falls outside data migration scope.

Edicom EDICOMLta archive stores transaction evidence with timestamping and digital signatures. We export archive records as structured data (headers, line items, totals, timestamps, partner references) and re-index them in Epicor Document records and custom audit tables. The embedded signature-validity context does not transfer; the customer is advised to retain archive access or re-validate signatures before treating exported files as standalone legal records.

Edicom transaction logs capture timestamp, status, and content hash for each processed document. We export historical logs for the retention period the customer specifies and load them into a custom audit table in Epicor with original timestamps, partner ID, document type, and status preserved. The custom table is indexed for BAQ-based querying by the customer's reporting team.

Edicom Managed Services provides 24x7 monitoring and administration of active EDI connections. Migration requires a handoff plan so that Edicom's support team stops monitoring transferred connections and Epicor Support takes over active monitoring. We document the active monitoring schedule, escalation contacts, and response-time SLAs for handover to Epicor Support or a third-party managed services partner.

Edicom ORDRSP (order response) transactions map to POHeader POAckEmailed and POChange records in Epicor. We extract acknowledgement status, confirmed quantities, and confirmed dates from the Edicom archive and update the corresponding POHeader and POLine records with confirmation data via DMT. Partner-level confirmation requirements are documented for Epicor admin configuration.