CRMPro → MDC — SAP B1: what the shipped templates set up

CRMPro → MDC — SAP B1: what the shipped templates set up

Keep this skill current. dlake ships updates often and this text is embedded in the CLI you have installed. Before relying on it, compare dlake --version with npm view @commercient/dlake version; if they differ, run npm install -g @commercient/dlake@latest and then dlake skills install, which overwrites the installed skill files with the current text.

dlake-crmpro is the parent skill and the authority for everything general: the crmpro_* tools, CRM_Configuration and CRM_FieldList, TimeStampRepository, the three kinds of source view, the NULL-cursor rule and the silent zero-record run. 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 is dlake-crmpro-mdc/erps/sap-b1.md, and that skill’s ERP table is what points at it. What follows is only what the shipped SAP B1 → MDC templates themselves set, read from their Insert_Query, CreateViewQuery and MappingJson. This page grows as the catalogue does.

1. What the templates deliver

Group	Business outcome	Objects	Source tables and views
CRM UoMSchedule	The templates push uomschedule to MDC.	uomschedule	—
CRM UOM	The templates push uom to MDC.	uom	—
CRM PriceLevel	The templates push pricelevel to MDC.	pricelevel	SF_ERP_Salesforce_Clone_ITM1
CRM Product	The templates push product to MDC.	product	SF_ERP_Salesforce_Clone_OITM
CRM salesorder	The templates push salesorder to MDC.	salesorder	SF_ERP_Salesforce_Clone_RDR1, e, SF_ERP_Salesforce_Clone_ITM1, SF_ERP_Salesforce_Clone_ORDR, ctepricelist, SF_ERP_Salesforce_Clone_OCRD
CRM salesorderdetail	The templates push salesorderdetail to MDC.	salesorderdetail	SF_ERP_Salesforce_Clone_RDR1, SF_ERP_Salesforce_Clone_ORDR, SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1
CRM invoice	The templates push invoice to MDC.	invoice	SF_ERP_Salesforce_Clone_INVOICE_ITEM, e, SF_ERP_Salesforce_Clone_STOCK, SF_ERP_Salesforce_Clone_INVOICE, ctepricelist, SF_ERP_Salesforce_Clone_SALES_LEDGER
CRM invoicedetail	The templates push invoicedetail to MDC.	invoicedetail	SF_ERP_Salesforce_Clone_INV1, SF_ERP_Salesforce_Clone_OINV, SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1
CRM quotedetail	The templates push quotedetail to MDC.	quotedetail	SF_ERP_Salesforce_Clone_QUT1, SF_ERP_Salesforce_Clone_OQUT, SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1
CRM Quote and Line	The templates push quote to MDC.	quote	SF_ERP_Salesforce_Clone_QUT1, e, SF_ERP_Salesforce_Clone_ITM1, SF_ERP_Salesforce_Clone_OQUT, ctepricelist, SF_ERP_Salesforce_Clone_OCRD

2. The process rows the templates create

Each template’s Insert_Query writes one CRM_Configuration row. These are the values it sets; a column the inserts never set is not listed.

Display name	CRM_Object_API_Name	CRM_PK_API_Name	Sync_Order	TimeStamp_Prefix	SQL_Query target	field prefix / postfix	Sync_Operation_Type
CRM UoMSchedule	uomschedule	name	20	UOMSchedule:	vw_CRM_UOMSchedule	'' / ''	1
CRM UOM	uom	name	21	UOM:	vw_CRM_UOM	'' / ''	1
CRM PriceLevel	pricelevel	comrcint_externalkey	22	CRM_PriceBook:	vw_SAPB1_CRM_PriceLevel	'' / ''	1
CRM Product	product	comrcint_externalkey	23	vw_SAPB1_CRM_Product:	vw_SAPB1_CRM_Product	'' / ''	1
CRM salesorder	salesorder	comrcint_externalkey	24	vw_SAPB1_STD_SalesOrder:	vw_SAPB1_STD_SalesOrder	'' / ''	1
CRM salesorderdetail	salesorderdetail	comrcint_externalkey	25	vw_SAPB1_STD_SalesDetail:	vw_SAPB1_STD_SalesDetail	'' / ''	1
CRM invoice	invoice	comrcint_externalkey	26	vw_SAPB1_STD_InvoiceHeader:	vw_SAPB1_STD_InvoiceHeader	'' / ''	1
CRM invoicedetail	invoicedetail	comrcint_externalkey	27	vw_SAPB1_STD_InvoiceDetail:	vw_SAPB1_STD_InvoiceDetail	'' / ''	1
CRM quote	quote	comrcint_externalkey	28	vw_SAPB1_STD_Quote:	vw_SAPB1_STD_Quote	'' / ''	1
CRM quotedetail	quotedetail	comrcint_externalkey	29	vw_SAPB1_STD_QuoteDetail:	vw_SAPB1_STD_QuoteDetail	'' / ''	1

Every one of these inserts Is_Active as 0, so an imported process is inactive until an operator activates it. Across the set they insert Is_Create_Entity 0, Is_Create_Fields 0, Is_Active_Get_Records 0, Is_Active_Delete_Records 0, IsAccountMatching '', Sync_Batch_Size 200. Text columns a template does not use are inserted as '' rather than left NULL. On CRM invoice the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_SAPB1_STD_InvoiceHeader against vw_SAGE50UK_STD_InvoiceHeader), so check the view exists under the name the row selects from before activating it.

3. The views

Each template creates its view with CreateViewQuery, in the gateway dbo schema. “Change detection” names which of the three kinds dlake-crmpro defines the view’s own WHERE makes it; where a view’s shape is not one of those three the column is left empty and the view’s own WHERE is the authority.

View	Change detection	Repository key	Reads other prefixes	Identity column	Source tables
vw_CRM_UOMSchedule		—	—	name	—
vw_CRM_UOM		—	—	name	—
vw_SAPB1_CRM_PriceLevel		—	CRM_PriceBook:	comrcint_externalkey	SF_ERP_Salesforce_Clone_ITM1
vw_SAPB1_CRM_Product	insert + update	—	vw_SAPB1_CRM_Product:	comrcint_externalkey	SF_ERP_Salesforce_Clone_OITM
vw_SAPB1_STD_SalesOrder	insert + update	—	CRM_PriceBook:, vw_CRM_Account:, vw_SAPB1_Customer:, vw_SAPB1_STD_SalesOrder:	comrcint_externalkey	SF_ERP_Salesforce_Clone_RDR1, e, SF_ERP_Salesforce_Clone_ITM1, SF_ERP_Salesforce_Clone_ORDR, ctepricelist
vw_SAPB1_STD_SalesDetail	insert + update	—	vw_SAPB1_STD_SalesOrder:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_SalesDetail:	comrcint_externalkey	SF_ERP_Salesforce_Clone_RDR1, SF_ERP_Salesforce_Clone_ORDR, SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1
vw_SAGE50UK_STD_InvoiceHeader	insert + update	—	CRM_PriceBook:, vw_CRM_Account:, vw_SAGE50UK_Customer:, vw_SAGE50UK_STD_InvoiceHeader:	comrcint_externalkey	SF_ERP_Salesforce_Clone_INVOICE_ITEM, e, SF_ERP_Salesforce_Clone_STOCK, SF_ERP_Salesforce_Clone_INVOICE, ctepricelist
vw_SAPB1_STD_InvoiceDetail	insert + update	—	vw_SAPB1_STD_InvoiceHeader:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_InvoiceDetail:	comrcint_externalkey	SF_ERP_Salesforce_Clone_INV1, SF_ERP_Salesforce_Clone_OINV, SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1
vw_SAPB1_STD_Quote	insert-only	—	CRM_PriceBook:, vw_CRM_Account:, vw_SAPB1_Customer:, vw_SAPB1_STD_Quote:	comrcint_externalkey	SF_ERP_Salesforce_Clone_QUT1, e, SF_ERP_Salesforce_Clone_ITM1, SF_ERP_Salesforce_Clone_OQUT, ctepricelist
vw_SAPB1_STD_QuoteDetail	insert-only	—	vw_SAPB1_STD_Quote:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_QuoteDetail:	comrcint_externalkey	SF_ERP_Salesforce_Clone_QUT1, SF_ERP_Salesforce_Clone_OQUT, SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1

4. Order of work

The templates set Sync_Order from 20 to 29. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 20 — CRM UoMSchedule
• 21 — CRM UOM
• 22 — CRM PriceLevel
• 23 — CRM Product
• 24 — CRM salesorder
• 25 — CRM salesorderdetail
• 26 — CRM invoice
• 27 — CRM invoicedetail
• 28 — CRM quote
• 29 — CRM quotedetail

These views read another process’s repository prefix, which is what makes the order a dependency order: the row appears in the view only once the process that writes that prefix has run, so a parent flows on one run and its children on the next.

• vw_SAPB1_CRM_PriceLevel reads CRM_PriceBook:; no template in this set writes CRM_PriceBook:
• vw_SAPB1_CRM_Product reads vw_SAPB1_CRM_Product:; no template in this set writes vw_SAPB1_CRM_Product:
• vw_SAPB1_STD_SalesOrder reads CRM_PriceBook:, vw_CRM_Account:, vw_SAPB1_Customer:, vw_SAPB1_STD_SalesOrder:; no template in this set writes CRM_PriceBook:, vw_CRM_Account:, vw_SAPB1_Customer:, vw_SAPB1_STD_SalesOrder:
• vw_SAPB1_STD_SalesDetail reads vw_SAPB1_STD_SalesOrder:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_SalesDetail:; no template in this set writes vw_SAPB1_STD_SalesOrder:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_SalesDetail:
• vw_SAGE50UK_STD_InvoiceHeader reads CRM_PriceBook:, vw_CRM_Account:, vw_SAGE50UK_Customer:, vw_SAGE50UK_STD_InvoiceHeader:; no template in this set writes CRM_PriceBook:, vw_CRM_Account:, vw_SAGE50UK_Customer:, vw_SAGE50UK_STD_InvoiceHeader:
• vw_SAPB1_STD_InvoiceDetail reads vw_SAPB1_STD_InvoiceHeader:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_InvoiceDetail:; no template in this set writes vw_SAPB1_STD_InvoiceHeader:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_InvoiceDetail:
• vw_SAPB1_STD_QuoteDetail reads vw_SAPB1_STD_Quote:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_QuoteDetail:; no template in this set writes vw_SAPB1_STD_Quote:, vw_SAPB1_CRM_Product:, vw_SAPB1_STD_QuoteDetail:
• vw_SAPB1_STD_Quote reads CRM_PriceBook:, vw_CRM_Account:, vw_SAPB1_Customer:, vw_SAPB1_STD_Quote:; no template in this set writes CRM_PriceBook:, vw_CRM_Account:, vw_SAPB1_Customer:, vw_SAPB1_STD_Quote:

5. Field mapping

CRM_FieldList carries one row per pushed column, with Object_Name equal to the CRM_Object_API_Name value — as dlake-crmpro puts it, an object with no CRM_FieldList rows pushes nothing and records no error. Each template carries its intended mapping in MappingJson. Read that with dlake admin crmpro_templates, then check crmpro_field_mapping on the created process before activating it.

Template	Object	Mapped fields	First ERP → MDC pairs
CRM UoMSchedule	uomschedule	2	name → name, baseuomname → baseuomname
CRM UOM	uom	2	name → name, uomschedule__uomscheduleid__lookup → uomschedule__uomscheduleid__lookup
CRM PriceLevel	pricelevel	3	ItemCode,PriceList → comrcint_externalkey, ItemCode,PriceList → Name, ItemCode,PriceList → Description
CRM Product	product	6	ItemName → name, ItemCode → productnumber, ItemCode → comrcint_externalkey, U_LongDescr → description, DefaultUOMSchedule.SFDCID → uomschedule__DefaultUoMScheduleId__lookup
CRM salesorder	salesorder	18	DocEntry → comrcint_externalkey, DocNum → Name, Street → billto_line1, City → billto_city, State → billto_stateorprovince
CRM salesorderdetail	salesorderdetail	13	DocEntry,LineNum → comrcint_externalkey, DocNum,LineNum → name, Street → shipto_line1, City → shipto_city, State → shipto_stateorprovince
CRM invoice	invoice	22	ADDRESS_1 → billto_line1, ADDRESS_2 → billto_line2, ADDRESS_3 → billto_city, ADDRESS_4 → billto_stateorprovince, ADDRESS_5 → billto_postalcode
CRM invoicedetail	invoicedetail	13	DocEntry,LineNum → comrcint_externalkey, DocNum,LineNum → Name, Street → shipto_line1, City → shipto_city, State → shipto_stateorprovince
CRM quote	quote	18	DocEntry → comrcint_externalkey, DocNum → Name, Street → billto_line1, City → billto_city, State → billto_stateorprovince
CRM quotedetail	quotedetail	13	DocEntry,LineNum → comrcint_externalkey, DocNum,LineNum → Name, Street → shipto_line1, City → shipto_city, State → shipto_stateorprovince

6. Verifying

# per-prefix counts; every synced record carries its destination id
dlake tool query --profile <tenant> --sql "SELECT LEFT([Key], CHARINDEX(':',[Key])-1) AS prefix, COUNT(*) n, COUNT(NULLIF(SFDCID,'')) withId FROM dbo.TimeStampRepository WHERE CHARINDEX(':',[Key])>0 GROUP BY LEFT([Key], CHARINDEX(':',[Key])-1)"

withId = n for every prefix is the success condition dlake-crmpro defines. The split is on the first colon, which is the prefix boundary whether the key separator is : or ::.

The prefixes these templates set:

• UOMSchedule:
• UOM:
• CRM_PriceBook:
• vw_SAPB1_CRM_Product:
• vw_SAPB1_STD_SalesOrder:
• vw_SAPB1_STD_SalesDetail:
• vw_SAPB1_STD_InvoiceHeader:
• vw_SAPB1_STD_InvoiceDetail:
• vw_SAPB1_STD_QuoteDetail:
• vw_SAPB1_STD_Quote:

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 SAP B1 → 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 clone tables, 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.