Source ERP · 4 of 11
CRMPro → MDC — IFS: what the shipped templates set up
This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-mdc/erps/ifs". It extends the dlake-crmpro-mdc skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/ifs-mdc/.
CRMPro → MDC — IFS: what the shipped templates set up
This is a capability summary, not an operating guide. To receive the operational skill you must be a
registered, whitelisted Commercient customer. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-mdc/erps/ifs (or list_skills) against the Commercient admin
plane. Existing customers who need access or help: contact support@commercient.com. New customers:
contact sales@commercient.com to become a customer and be whitelisted.
dlake-crmpro is the parent skill and the authority for everything general: the CRMPro tools, process configuration and field list, the sync history, how source data is selected, and what a run that finds nothing does. Read it first; this page does not repeat it. dlake-crmpro-mdc is the destination skill this page is a child of, and the authority for the MDC conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page grows as the catalogue does.
1. What the templates deliver
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| CRM Unit of measure schedule | The templates push unit of measure schedule to MDC | unit of measure schedule | — |
| CRM unit of measure | The templates push uom to MDC | uom | — |
| CRM Price level | The templates push price level to MDC | price level | part catalog |
| CRM Product | The templates push product to MDC | product | part catalog |
| CRM sales order | The templates push sales order to MDC | sales order | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| CRM sales order detail | The templates push sales order detail to MDC | sales order detail | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| CRM invoice | The templates push invoice to MDC | invoice | customer information addresses, customer address types, invoice items, invoices for CRM sync, customer information for CRM sync |
| CRM invoice detail | The templates push invoice detail to MDC | invoice detail | customer information addresses, customer address types, invoice items, invoices for CRM sync, customer information for CRM sync |
| IFS ERP Sales Order | The templates push Commercient IFS ERP sales order object to MDC | Commercient IFS ERP sales order object | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| IFS ERP Sales Order Detail | The templates push Commercient IFS ERP sales order detail object to MDC | Commercient IFS ERP sales order detail object | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| IFS ERP Invoice | The templates push Commercient IFS ERP invoice object to MDC | Commercient IFS ERP invoice object | — |
| IFS ERP Invoice Detail | The templates push Commercient IFS ERP invoice detail object to MDC | Commercient IFS ERP invoice detail object | — |
2. The process rows the templates create
Each template’s setup writes one process configuration row. These are the values it sets; a column the inserts never set is not listed.
| Display name | Destination object | Matching key | Run sequence |
|---|---|---|---|
| CRM Unit of measure schedule | unit of measure schedule | name | 20 |
| CRM unit of measure | uom | name | 21 |
| CRM Price level | price level | Commercient external key | 22 |
| CRM Product | product | Commercient external key | 23 |
| CRM sales order | sales order | Commercient external key | 24 |
| CRM sales order detail | sales order detail | Commercient external key | 25 |
| CRM invoice | invoice | Commercient external key | 26 |
| CRM invoice detail | invoice detail | Commercient external key | 27 |
| IFS ERP Sales Order | Commercient IFS ERP sales order object | Commercient external key | 28 |
| IFS ERP Sales Order Detail | Commercient IFS ERP sales order detail object | Commercient external key | 29 |
Every one of these inserts the active setting as 0, so an imported process is inactive until an operator activates it.
3. The views
“Change detection” names which of the three kinds dlake-crmpro defines the view’s own filter makes it; where a view’s shape is not one of those three the column is left empty and the view’s own filter is the authority.
| View | Change detection | Source tables |
|---|---|---|
| CRM unit of measure schedule feed | — | — |
| CRM unit of measure feed | — | — |
| price level feed | — | part catalog |
| product feed | insert + update | part catalog |
| sales order feed (standard objects) | insert + update | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| sales order line feed (standard objects) | insert + update | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| invoice feed (standard objects) | insert + update | customer information addresses, customer address types, invoice items, invoices for CRM sync, customer information for CRM sync |
| invoice line feed (standard objects) | insert + update | customer information addresses, customer address types, invoice items, invoices for CRM sync, customer information for CRM sync |
| sales order feed (Commercient objects) | insert + update | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
| sales order line feed (Commercient objects) | insert + update | customer information addresses, customer address types, customer order lines, customer orders, customer information for CRM sync |
4. Order of work
The templates set run sequence from 20 to 29. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 20 — CRM Unit of measure schedule
- 21 — CRM unit of measure
- 22 — CRM Price level
- 23 — CRM Product
- 24 — CRM sales order
- 25 — CRM sales order detail
- 26 — CRM invoice
- 27 — CRM invoice detail
- 28 — IFS ERP Sales Order
- 29 — IFS ERP Sales Order Detail
These views read another process’s sync output, which is what makes the order a dependency order: the row appears in the view only once the process that writes that sync output has run, so a parent flows on one run and its children on the next.
- price level feed reads CRM price book sync output (generic name); no template in this set writes CRM price book sync output (generic name)
- product feed reads product sync output; no template in this set writes product sync output
- sales order feed (standard objects) reads CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, sales order sync output (standard objects); no template in this set writes CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, sales order sync output (standard objects)
- sales order line feed (standard objects) reads sales order sync output (standard objects), product sync output (IFS name), sales order line sync output (standard objects); no template in this set writes sales order sync output (standard objects), product sync output (IFS name), sales order line sync output (standard objects)
- invoice feed (standard objects) reads CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, invoice sync output (standard objects); no template in this set writes CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, invoice sync output (standard objects)
- invoice line feed (standard objects) reads invoice sync output (standard objects), product sync output (IFS name), invoice line sync output (standard objects); no template in this set writes invoice sync output (standard objects), product sync output (IFS name), invoice line sync output (standard objects)
- sales order feed (Commercient objects) reads CRM account sync output (generic name), customer sync output, sales order sync output (Commercient objects); no template in this set writes CRM account sync output (generic name), customer sync output, sales order sync output (Commercient objects)
- sales order line feed (Commercient objects) reads sales order sync output (Commercient objects), product sync output (IFS name), sales order line sync output (Commercient objects); no template in this set writes sales order sync output (Commercient objects), product sync output (IFS name), sales order line sync output (Commercient objects)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → MDC pairs |
|---|---|---|---|
| IFS ERP Invoice | Commercient IFS ERP invoice object | 9 | Customer identifier, Ship to identifier → Commercient AR customer code, Bill to address line 1, Bill to address line 2, Bill to address line 3 → Billing street, Bill to address city → Billing city, Bill to address state → Billing state, Customer bill to country → Billing country |
| IFS ERP Invoice Detail | Commercient IFS ERP invoice detail object | 9 | Customer identifier, Ship to identifier → Commercient AR customer code, Bill to address line 1, Bill to address line 2, Bill to address line 3 → Billing street, Bill to address city → Billing city, Bill to address state → Billing state, Customer bill to country → Billing country |
| CRM Unit of measure schedule | unit of measure schedule | 2 | name → name, Base unit name → Base unit name |
| CRM unit of measure | uom | 2 | name → name, unit of measure schedule lookup → unit of measure schedule lookup |
| CRM Price level | price level | 3 | Inventory part number → Commercient external key, Inventory part number → name, Description → description |
| CRM Product | product | 6 | Inventory part number → name, Inventory part number → Product number, Inventory part number → Commercient external key, Description → description, the linked default unit of measure schedule → default unit of measure schedule lookup |
| CRM sales order | sales order | 20 | Address 1 → Bill to street 1, Address 2 → Bill to street 2, City → Bill to city, State → Bill to state or province, Postal code → Bill to postal code |
| CRM sales order detail | sales order detail | 12 | Order number, Line number, Release number, Line item number, Contract → Commercient external key, Address 1 → Ship to street 1, Address 2 → Ship to street 2, City → Ship to city, State → Ship to state or province |
| CRM invoice | invoice | 20 | Address 1 → Bill to street 1, Address 2 → Bill to street 2, City → Bill to city, State → Bill to state or province, Postal code → Bill to postal code |
| CRM invoice detail | invoice detail | 13 | company,Invoice identifier,Item identifier → Commercient external key, Address 1 → Ship to street 1, Address 2 → Ship to street 2, City → Ship to city, State → Ship to state or province |
| IFS ERP Sales Order | Commercient IFS ERP sales order object | 4 | Order number, Customer number (IFS) → external key property, Order number, Customer number (IFS) → Name, Customer number (IFS) → customer account lookup, Customer number (IFS) → Commercient IFS ERP customer lookup |
| IFS ERP Sales Order Detail | Commercient IFS ERP sales order detail object | 4 | Order number, Line number, Release number, Line item number, Contract → external key property, Order number, Line number, Release number, Line item number, Contract → name, the linked Salesforce record → Commercient IFS ERP sales order lookup, the linked Salesforce record → product lookup |
6. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-mdc/erps/ifs.
7. Where this sits
dlake-crmpro is the general operating surface — the CRMPro tools, the setup and transaction tables, field mapping, and the source view contract that applies to every destination. This page adds what the shipped IFS → MDC templates set up. dlake-crmpro-mdc is the destination skill this page sits under: its own text is the authority for the MDC conventions that hold across every ERP, and its ERP table lists this page alongside every sibling ERP page for this destination. For the extract leg that fills the source data, see dlake-normalsync; for the on-premises agent that runs it, dlake-syncagent; for the writeback leg, dlake-txdownloaderpro; for standing an integration up, dlake-integration-setup.
How to get started
- Already a customer: the operational skill tells you how to connect, choose what to sync and run it.
Fetch it with
dlake admin get_skill dlake-crmpro-mdc/erps/ifs, or ask support@commercient.com. - New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.
