CRMPro → Salesforce — SAP Business One: what the shipped templates set up

CRMPro → Salesforce — SAP Business One: 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/sap-b1 (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

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.

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.

4. Order of work

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

• 0 — GET USER
• 1 — Account
• 2 — SAP Business One Customer
• 3 — Account Reverse lookup
• 4 — SAP Business One Address
• 5 — SAP Business One Sales Order
• 6 — SAP Business One Sales Order Line
• 7 — Sync Contact, SAP Business One Invoice
• 8 — SAP Business One Invoice Line
• 9 — Product
• 10 — Price Book Entry Create
• 11 — Price Book Entry Update
• 12 — SAP Business One Purchase Order
• 13 — SAP Business One Purchase Order Line
• 14 — SAP Business One Item Master
• 15 — SAP Business One Item Warehouse
• 16 — SAP Business One Sales Credit Header
• 17 — SAP Business One Sales Credit Detail
• 18 — SAP Business One Sales Delivery Header
• 19 — SAP Business One Sales Delivery Detail

Several of these rows share a run sequence value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.

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 reverse lookup feed reads customer sync output
• item master feed reads Product
• item warehouse feed reads Product, item master sync output
• invoice line feed reads invoice sync output
• price book feed (new entries) reads Product
• purchase order line feed reads purchase order sync output
• sales order line feed reads sales order sync output
• sales credit line feed reads sales credit sync output
• sales delivery line feed reads sales delivery sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

6. Community templates

The catalogue carries 437 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: 437
• Default operations: insert on 437, update on 437, delete on 437
• Marked as circular sync: 0
• Licence groups they span: 15
• Destination objects: Account, Product, Commercient SAP Customer Managed Custom Object, Commercient SAP Invoice Managed Custom Object, Commercient SAP Sales Order Managed Custom Object, Price book entry, Commercient SAP Address Managed Custom Object, Commercient SAP Invoice Detail Managed Custom Object, Commercient SAP Sales Order Line Managed Custom Object, Commercient Item Master Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Contact, Commercient SAP Salesperson Managed Custom Object, Commercient Sales Credit Header Managed Custom Object, User, Commercient Purchase Order Managed Custom Object, Quote line item, Commercient Purchase Order Line Managed Custom Object, Opportunity, 20 more and 14 custom objects
• Object display names: Account, SAP Business One Invoice, SAP Business One Sales Order, SAP Business One Invoice Line, SAP Business One Sales Order Line, Price Book Entry Create, Product, SAP Business One Address, SAP Business One Customer, Account Reverse lookup, SAP Business One Item Master, SAP Business One Item Warehouse, 89 more and 16 further templates
• Template groups: Account, Product, Invoice, Sales order, Customer Multi Ship Addresses, Opportunity, CRM Quote and Line, Purchase Order, CRM Opportunity and Line, CRM Ownership

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/sap-b1.

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 SAP Business One → 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/sap-b1, 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.