Sage 100 2013 version 5 to Salesforce (CRMPro)

This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-salesforce/erps/sage-100-2013-v5". It extends the dlake-crmpro-salesforce skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/sage-100-2013-v5-salesforce/.

CRMPro → Salesforce — Sage 100 2013 version 5: 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-salesforce/erps/sage-100-2013-v5 (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-salesforce is the destination skill this page is a child of, and the authority for the Salesforce 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
GET USER	The templates push users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	users	—
Account	In addition to creating the Account record from your ERP customer records, Commercient syncs over the entire Accounting AR Customer record into a Commercient AR Customer object which is a Managed Custom Object (MCO). A lookup field is provided to lookup to the default AR Customer record MCO from the Account record. New records are created, existing ones updated, and records removed in the ERP are deleted.	Account, Commercient AR Customer Managed Custom Object, Commercient Salesperson Managed Custom Object	customers, shipping addresses, salespeople
Customer Multi Ship Addresses	If you are using multiple ship to addresses for a given AR Customer in your ERP system then you will be able to see all the addresses inside the CRM Account screen in a Commercient Multi Ship To Address MCO related list. New records are created, existing ones updated, and records removed in the ERP are deleted.	Commercient Ship-To Address Managed Custom Object	shipping addresses
Product	ERP Common information item, inventory management item warehouse data becomes Commercient Inventory Item Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Item Warehouse Managed Custom Object in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	Commercient Inventory Item Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Product	items, item warehouse quantities, dbo
Invoice	Both Open and Historical invoices are synchronized. Open invoice changes, such as a balance change, or a terms change are reflected in the CRM as they sync based on the frequency of the sync you have chosen (every hour, for example). New records are created, existing ones updated, and records removed in the ERP are deleted.	Commercient Open Invoice Managed Custom Object, Commercient Payment History Managed Custom Object	open invoices, payment history, invoice history headers
Invoice History Headers	The Invoices from the ERP invoice module are synchronized to the Commercient Invoice Header (MCO) object in CRM. Customer service and sales people can visualize the status of the Invoice such as open, closed, as well as the balance remaining and the due date. New records are created, existing ones updated, and records removed in the ERP are deleted.	Commercient Invoice History Header Managed Custom Object, Commercient Invoice History Detail Managed Custom Object	invoice history headers, open invoices, salespeople, invoice history lines, items
Pricebook	ERP Common information item data becomes Price book entry in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	Price book entry	items
Sales order	Commercient will sync the Sales Orders from the ERP Sales Order Entry module to the Commercient Sales Order Header (MCO) objects in CRM. In the CRM, customer service and sales people can visualize the status of the order such as on hold, backorder, forward order, scheduled for delivery, whether it has shipped, and completion status. New records are created, existing ones updated, and records removed in the ERP are deleted.	Commercient Sales Order Header Managed Custom Object, Commercient Sales Order Line Managed Custom Object, Commercient Sales Order History Header Managed Custom Object, Commercient Sales Order History Line Managed Custom Object	sales order headers, sales order lines, sales order history headers, sales order history lines

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
GET USER	users	—	0
Sync Salesperson	Commercient Salesperson Managed Custom Object	Commercient external key	1
Sync Account	Account	Commercient AR customer code	2
Sync Customer	Commercient AR Customer Managed Custom Object	Commercient external key	3
Sync Customer TO Account Lookup	Account	Commercient AR customer code	4
Sync Ship TO Address	Commercient Ship-To Address Managed Custom Object	Commercient external key	5
Sync Product object	Product	Commercient external key (earlier package)	6
Sync Item	Commercient Inventory Item Managed Custom Object	Commercient external keys	7
Sync Item TO Product object Lookup	Product	Commercient external key (earlier package)	8
Sync Standard Price Book Create	Price book entry	External key (custom field)	10
Sync Standard Price Book update	Price book entry	External key (custom field)	11
Sync Item Warehouse	Commercient Item Warehouse Managed Custom Object	Commercient external key	12
Sync Sales Order Header	Commercient Sales Order Header Managed Custom Object	Commercient sales order number	13
Sync Sales Order Detail	Commercient Sales Order Line Managed Custom Object	Commercient external key	14
Sync Sales Order History Header	Commercient Sales Order History Header Managed Custom Object	Commercient external key	15
Sync Sales Order History Detail	Commercient Sales Order History Line Managed Custom Object	Commercient external key	16
Sync Open invoice record sync output (generic name)	Commercient Open Invoice Managed Custom Object	Commercient external key	17
Sync invoice record sync output (generic name) History Header	Commercient Invoice History Header Managed Custom Object	Commercient external key	18
Sync invoice record sync output (generic name) History Detail	Commercient Invoice History Detail Managed Custom Object	Commercient external key	19
Sync invoice record sync output (generic name) Payment	Commercient Payment History Managed Custom Object	Commercient external key	20
(unnamed)	Commercient Inventory Item Managed Custom Object	Commercient external keys	21
Sync Item Warehouse Total Quantity Available	Commercient Item Warehouse Managed Custom Object	Commercient external key	22

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
salesperson feed	insert + update	salespeople
account feed	insert + update	customers, shipping addresses
customer feed	insert + update	customers
customer account lookup feed	insert + update	customers
shipping address feed	insert + update	shipping addresses
product feed	insert + update	items
item feed	insert + update	items
item product lookup feed	insert + update	items
standard price book feed	insert only	items
standard price book feed	insert only	items
item warehouse feed	insert + update	item warehouse quantities
sales order feed	insert + update	sales order headers
sales order line feed	insert + update	sales order lines
sales order history feed	insert + update	sales order history headers
sales order history line feed	insert + update	sales order history lines
open invoice feed	insert + update	open invoices
invoice history feed	insert + update	invoice history headers, open invoices, salespeople
invoice history line feed	insert + update	invoice history lines, items
payment history feed	insert + update	payment history, invoice history headers
item total quantity on hand feed	insert + update	items, dbo
item warehouse total quantity feed	insert + update	item warehouse quantities, dbo

4. Order of work

The templates set run sequence from 0 to 22. A run processes active rows in ascending run sequence, which is the order the templates put them in:

0 — GET USER
1 — Sync Salesperson
2 — Sync Account
3 — Sync Customer
4 — Sync Customer TO Account Lookup
5 — Sync Ship TO Address
6 — Sync Product object
7 — Sync Item
8 — Sync Item TO Product object Lookup
10 — Sync Standard Price Book Create
11 — Sync Standard Price Book update
12 — Sync Item Warehouse
13 — Sync Sales Order Header
14 — Sync Sales Order Detail
15 — Sync Sales Order History Header
16 — Sync Sales Order History Detail
17 — Sync Open invoice record sync output (generic name)
18 — Sync invoice record sync output (generic name) History Header
19 — Sync invoice record sync output (generic name) History Detail
20 — Sync invoice record sync output (generic name) Payment
22 — Sync Item Warehouse Total Quantity Available

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.

account feed reads user sync output
customer account lookup feed reads account sync output, customer sync output
customer feed reads account sync output, salesperson sync output
shipping address feed reads account sync output, customer sync output
item feed reads product sync output; no template in this set writes
item warehouse feed reads product sync output, item sync output
item total quantity on hand feed reads item sync output
item warehouse total quantity feed reads item warehouse sync output
open invoice feed reads account sync output, customer sync output
payment history feed reads account sync output, customer sync output, invoice history sync output
invoice history feed reads account sync output, customer sync output, shipping address sync output; no template in this set writes
invoice history line feed reads invoice history sync output
standard price book feed reads product sync output
standard price book feed reads product sync output
item product lookup feed reads item sync output, product sync output
sales order feed reads account sync output, customer sync output; no template in this set writes
sales order line feed reads sales order sync output
sales order history feed reads account sync output, customer sync output
sales order history line feed reads sales order history sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

Template	Object	Mapped fields	First ERP → Salesforce pairs
Sync Salesperson	Commercient Salesperson Managed Custom Object	28	Salesperson division → Commercient salesperson division, Salesperson number → Commercient salesperson number, Salesperson name → Commercient salesperson name, Address line 1 → Commercient address line 1, Address line 2 → Commercient address line 2
Sync Account	Account	12	Commercient AR customer code column → Commercient AR customer code, Billing street → Billing street, Billing city → Billing city, Billing state code → Billing state code, Billing country code → Billing country code
Sync Customer	Commercient AR Customer Managed Custom Object	63	Account → Account, AR division number → Commercient AR division number, Customer number → Commercient customer number, Address line 1 → Commercient address line 1, Address line 2 → Commercient address line 2
Sync Customer TO Account Lookup	Account	2	Commercient AR customer code column → Commercient AR customer code, Commercient Sage customer record → Commercient Sage customer record
Sync Ship TO Address	Commercient Ship-To Address Managed Custom Object	31	Account → Account, Sage 100 customer records (custom field) → Commercient Sage 100 customer records, AR division number → Commercient AR division number, Customer number → Commercient customer number, Ship-to code → Ship-to code
Sync Product object	Product	4	Commercient external key (earlier package) → Commercient external key (earlier package), Product code → Product code, Description → Description, Active → Active
Sync Item	Commercient Inventory Item Managed Custom Object	86	external keys column → Commercient external keys, Item code → Item code, Item type → Commercient item type, Item description → Item description, Extended description → Extended description
Sync Item TO Product object Lookup	Product	2	Commercient external key (earlier package) → Commercient external key (earlier package), Commercient Sage 100 inventory item (related record) → Commercient Sage 100 inventory item (related record)
Sync Standard Price Book Create	Price book entry	4	price book lookup → price book lookup, product lookup → product lookup, Active → Active, Unit price → Unit price
Sync Standard Price Book update	Price book entry	4	price book lookup → price book lookup, product lookup → product lookup, Active → Active, Unit price → Unit price
Sync Item Warehouse	Commercient Item Warehouse Managed Custom Object	21	Product → Product, Inventory item → Commercient inventory item, Item code → Item code, Warehouse code → Warehouse code, Bin location → Bin location
Sync Sales Order Header	Commercient Sales Order Header Managed Custom Object	95	Sales order number → Commercient sales order number, Account → Account, Sage 100 customer record (custom field) → Commercient sage 100 customer record, Order date → Commercient order date, Order type → Commercient order type
Sync Sales Order Detail	Commercient Sales Order Line Managed Custom Object	62	Sage 100 open sales orders (custom field) → Commercient Sage 100 open sales order (related record), Sales order number → Commercient sales order number, Line key → Commercient line key, Line sequence number → Commercient line sequence number, Item code → Item code
Sync Sales Order History Header	Commercient Sales Order History Header Managed Custom Object	88	Account → Account, Customer → Commercient customer (related record), Order status → Commercient order status, Master repeating order number → Commercient master repeating order number, AR division number → Commercient AR division number
Sync Sales Order History Detail	Commercient Sales Order History Line Managed Custom Object	61	Sales order history header (custom field) → Commercient sales order history header, Sales order number → Commercient sales order number, Sequence number → Sequence number, Line key → Commercient line key, Original line → Commercient original line
Sync Open invoice record sync output (generic name)	Commercient Open Invoice Managed Custom Object	40	Account → Account, Sage 100 customer records (custom field) → Commercient Sage 100 customer records, Terms code → Terms code, Tax schedule → Tax schedule, Salesperson division → Commercient salesperson division
Sync invoice record sync output (generic name) History Header	Commercient Invoice History Header Managed Custom Object	78	Account → Account, Sage 100 customer record (custom field) → Commercient sage 100 customer record, Shipping address (custom field) → Commercient shipping address (related record), Invoice number → Invoice number, Header sequence number → Commercient header sequence number
Sync invoice record sync output (generic name) History Detail	Commercient Invoice History Detail Managed Custom Object	57	Invoice → Commercient Sage 100 invoice (related record), Invoice number → Invoice number, Header sequence number → Commercient header sequence number, Detail sequence number → Commercient detail sequence number, Item code → Item code
Sync invoice record sync output (generic name) Payment	Commercient Payment History Managed Custom Object	28	Account → Commercient account, Sage 100 customer record (custom field) → Commercient sage 100 customer record, Invoice → Commercient Sage 100 invoice (related record), AR division number → Commercient AR division number, Customer number → Commercient customer number
(unnamed)	Commercient Inventory Item Managed Custom Object	3	Id → record identifier (custom field), external keys column → Commercient external keys, Final quantity on hand → final quantity on hand (custom field)
Sync Item Warehouse Total Quantity Available	Commercient Item Warehouse Managed Custom Object	16	Id → record identifier (custom field), Total quantity available → total quantity available (custom field), Quantity on hand → Commercient quantity on hand, Quantity on purchase order → Quantity on purchase order, Quantity on sales order → Commercient quantity on sales order

6. Community templates

The catalogue carries 30 community templates for this pair. A community template is authored in a tenant rather than shipped with the product, and it imports the same way as any other. Its own names, notes, field mapping and SQL are tenant content, so what this section states is what the set amounts to: how many templates there are, what they default to doing, which destination objects they write and which groups they fall in. They are not part of the shipped set described above.

Templates: 30
Default operations: insert on 30, update on 30, delete on 30
Marked as circular sync: 0
Licence groups they span: 9
Destination objects: Account, Product, Commercient Invoice History Detail Managed Custom Object, Commercient Invoice History Header Managed Custom Object, Commercient Inventory Item Managed Custom Object, Commercient Sales Order History Line Managed Custom Object, Commercient Sales Order History Header Managed Custom Object, Commercient Salesperson Managed Custom Object, Commercient Sales Order Line Managed Custom Object, Price book entry, Commercient AR Customer Managed Custom Object, Commercient Payment History Managed Custom Object, Commercient Open Invoice Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Sales Order Header Managed Custom Object, Commercient Ship-To Address Managed Custom Object
Object display names: Account, Customer to Account Reverse Lookup, Invoice Header, Invoice Line, Product, Sales Order History Details, Sales Order History Header, Sales Order Line, Sales Person, Sync Account, Sync Customer, Sync Customer TO Account Lookup and 18 more
Template groups: Product, Account, Sales order, Invoice, Invoice History Headers, Customer Multi Ship Addresses

7. Verifying

The detail of this section is part of the operational skill. Whitelisted customers fetch it with dlake admin get_skill dlake-crmpro-salesforce/erps/sage-100-2013-v5.

8. 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 Sage 100 2013 version 5 → Salesforce templates set up. dlake-crmpro-salesforce is the destination skill this page sits under: its own text is the authority for the Salesforce 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-salesforce/erps/sage-100-2013-v5, 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.