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

CRMPro → Salesforce — 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-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 is dlake-crmpro-salesforce/erps/sap-b1.md, and that skill’s ERP table is what points at it. What follows is only what the shipped SAP B1 → Salesforce 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
Get_Users	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, Contact, CommercientSF16__SAP_Customer__c	SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1, SF_ERP_Salesforce_Clone_OCPR
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 and existing ones updated; none are deleted.	CommercientSF16__SAP_Address__c	SF_ERP_Salesforce_Clone_CRD1
Product	ERP OITW, OITM data becomes CommercientSF16__OITM__c, CommercientSF16__OITW__c, Product2 in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF16__OITM__c, CommercientSF16__OITW__c, Product2	SF_ERP_Salesforce_Clone_OITM, SF_ERP_Salesforce_Clone_OITW
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 (e.g. every hour for example). New records are created and existing ones updated; none are deleted.	CommercientSF16__SAP_Invoice__c, CommercientSF16__SAP_InvoiceDetail__c	SF_ERP_Salesforce_Clone_OINV, CommercientFlags, SF_ERP_Salesforce_Clone_INV1
Pricebook	ERP ITM1 data becomes PricebookEntry, PriceBookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry, PriceBookEntry	SF_ERP_Salesforce_Clone_ITM1
Purchase Order	The templates push CommercientSF16__OPOR__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF16__OPOR__c	SF_ERP_Salesforce_Clone_OPOR, CommercientFlags
Purchase Order Line	The templates push CommercientSF16__POR1__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF16__POR1__c	SF_ERP_Salesforce_Clone_POR1, SF_ERP_Salesforce_Clone_OPOR
Salesorder	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 and existing ones updated; none are deleted.	CommercientSF16__SAP_SalesOrder__c, CommercientSF16__SAP_SalesOrderLine__c, CommercientSF16__ORIN__c, CommercientSF16__RIN1__c, CommercientSF16__ODLN__c, CommercientSF16__DLN1__c	SF_ERP_Salesforce_Clone_ORDR, CommercientFlags, SF_ERP_Salesforce_Clone_RDR1, SF_ERP_Salesforce_Clone_ORIN, SF_ERP_Salesforce_Clone_RIN1, SF_ERP_Salesforce_Clone_ODLN

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
GET USER	users	—	0	vw_SAPB1_User	1=0	'' / ''	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	Account:	vw_SAPB1_Account	'' / ''	—
SAPB1 Customer	CommercientSF16__SAP_Customer__c	CommercientSF16__ExternalKey__c	2	SAPB1Customer	vw_SAPB1_Customer	CommercientSF16__ / __c	—
Account Reverse lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	3	AccountReverseLookup	vw_SAPB1_AccountReverseLookup	'' / ''	—
SAPB1 Address	CommercientSF16__SAP_Address__c	CommercientSF16__ExternalKey__c	4	SAPB1Address	vw_SAPB1_Address	CommercientSF16__ / __c	—
SAPB1 Sales Order	CommercientSF16__SAP_SalesOrder__c	CommercientSF16__ExternalKey__c	5	SAPB1SalesOrder	vw_SAPB1_SalesOrder	CommercientSF16__ / __c	—
SAPB1 Sales Order Line	CommercientSF16__SAP_SalesOrderLine__c	CommercientSF16__ExternalKey__c	6	SAPB1SalesOrderLine	vw_SAPB1_SalesOrderLine	CommercientSF16__ / __c	—
SYNC CONTACT	Contact	ExternalKey__c	7	vw_SAPB1_Contact	vw_SAPB1_Contact	'' / ''	1
SAPB1 Invoice	CommercientSF16__SAP_Invoice__c	CommercientSF16__ExternalKey__c	7	SAPB1Invoice	vw_SAPB1_Invoice	CommercientSF16__ / __c	—
SAPB1 Invoice Line	CommercientSF16__SAP_InvoiceDetail__c	CommercientSF16__ExternalKey__c	8	SAPB1InvoiceLine	vw_SAPB1_InvoiceLine	CommercientSF16__ / __c	—
Product	Product2	CommercientSF__ExternalKey__c	9	Product2	vw_SAPB1_Product	'' / ''	—
Price Book Entry Create	PricebookEntry	ExternalKey__c	10	PricebookEntry	vw_SAPB1_PriceBookEntryCreate	'' / ''	—
Price Book Entry Update	PriceBookEntry	ExternalKey__c	11	PriceBookEntry	vw_SAPB1_PriceBookEntryUpdate	'' / ''	—
SAPB1 Purchase Order	CommercientSF16__OPOR__c	CommercientSF16__ExternalKey__c	12	SAPB1PurchaseOrder	vw_SAPB1_PurchaseOrder	CommercientSF16__ / __c	—
SAPB1 Purchase Order Line	CommercientSF16__POR1__c	CommercientSF16__ExternalKey__c	13	SAPB1PurchaseOrderLine	vw_SAPB1_PurchaseOrderLine	CommercientSF16__ / __c	—
SAPB1 Item Master	CommercientSF16__OITM__c	CommercientSF16__ExternalKey__c	14	SAPB1ItemMaster	vw_SAPB1_ItemMaster	CommercientSF16__ / __c	—
SAPB1 Item Warehouse	CommercientSF16__OITW__c	CommercientSF16__ExternalKey__c	15	SAPB1ItemWarehouse	vw_SAPB1_ItemWarehouse	CommercientSF16__ / __c	—
SAPB1 Sales Credit Header	CommercientSF16__ORIN__c	CommercientSF16__ExternalKey__c	16	SAPB1SalesCreditHeader	vw_SAPB1_SalesCreditHeader	CommercientSF16__ / __c	—
SAPB1 Sales Credit Detail	CommercientSF16__RIN1__c	CommercientSF16__ExternalKey__c	17	SAPB1SalesCreditDetail	vw_SAPB1_SalesCreditDetail	CommercientSF16__ / __c	—
SAPB1 Sales Delivery Header	CommercientSF16__ODLN__c	CommercientSF16__ExternalKey__c	18	SAPB1SalesDeliveryHeader	vw_SAPB1_SalesDeliveryHeader	CommercientSF16__ / __c	—
SAPB1 Sales Delivery Detail	CommercientSF16__DLN1__c	CommercientSF16__ExternalKey__c	19	SAPB1SalesDeliveryDetail	vw_SAPB1_SalesDeliveryDetail	CommercientSF16__ / __c	—

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_Active_Delete_Records 0, Sync_Batch_Size 200. Is_Create_Fields is set on Price Book Entry Create; Is_Active_Get_Records is set on Price Book Entry Create; IsAccountMatching is set on Account. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on GET USER, Price Book Entry Create — those rows read records back from Salesforce as well as pushing.

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_SAPB1_Account	insert + update	—	Account:	—	SF_ERP_Salesforce_Clone_OCRD, SF_ERP_Salesforce_Clone_CRD1
vw_SAPB1_Customer	insert + update	SAPB1Customer:	Account:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_OCRD
vw_SAPB1_AccountReverseLookup	insert + update	AccountReverseLookup:	SAPB1Customer:	—	SF_ERP_Salesforce_Clone_OCRD
vw_SAPB1_Address	insert + update	SAPB1Address:	Account:, SAPB1Customer:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_CRD1
vw_SAPB1_SalesOrder	insert + update	SAPB1SalesOrder:	Account:, SAPB1Customer:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_ORDR, CommercientFlags
vw_SAPB1_SalesOrderLine	insert + update	SAPB1SalesOrderLine:	SAPB1SalesOrder:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_RDR1, SF_ERP_Salesforce_Clone_ORDR
vw_SAPB1_Contact	insert + update	vw_SAPB1_Contact:	Account:	—	SF_ERP_Salesforce_Clone_OCPR
vw_SAPB1_Invoice	insert + update	SAPB1Invoice:	Account:, SAPB1Customer:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_OINV, CommercientFlags
vw_SAPB1_InvoiceLine	insert + update	SAPB1InvoiceLine:	SAPB1Invoice:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_INV1, SF_ERP_Salesforce_Clone_OINV
vw_SAPB1_Product	insert + update	Product2:	—	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_OITM
vw_SAPB1_PriceBookEntryCreate	insert-only	PricebookEntry:	Product2:	ExternalKey__c	SF_ERP_Salesforce_Clone_ITM1
vw_SAPB1_PriceBookEntryUpdate	insert + update	PricebookEntry:	—	ExternalKey__c	SF_ERP_Salesforce_Clone_ITM1
vw_SAPB1_PurchaseOrder	insert + update	SAPB1PurchaseOrder:	Account:, SAPB1Customer:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_OPOR, CommercientFlags
vw_SAPB1_PurchaseOrderLine	insert + update	SAPB1PurchaseOrderLine:	SAPB1PurchaseOrder:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_POR1, SF_ERP_Salesforce_Clone_OPOR
vw_SAPB1_ItemMaster	insert + update	SAPB1ItemMaster:	Product2:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_OITM
vw_SAPB1_ItemWarehouse	insert + update	SAPB1ItemWarehouse:	Product2:, SAPB1ItemMaster:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_OITW
vw_SAPB1_SalesCreditHeader	insert + update	SAPB1SalesCreditHeader:	Account:, SAPB1Customer:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_ORIN
vw_SAPB1_SalesCreditDetail	insert + update	SAPB1SalesCreditDetail:	SAPB1SalesCreditHeader:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_RIN1, SF_ERP_Salesforce_Clone_ORIN
vw_SAPB1_SalesDeliveryHeader	insert + update	SAPB1SalesDeliveryHeader:	Account:, SAPB1Customer:, SAPB1SalesOrder:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_ODLN
vw_SAPB1_SalesDeliveryDetail	insert + update	SAPB1SalesDeliveryDetail:	SAPB1SalesDeliveryHeader:	CommercientSF16__ExternalKey__c	SF_ERP_Salesforce_Clone_DLN1, SF_ERP_Salesforce_Clone_ODLN

The repository key these templates build is <TimeStamp_Prefix>:<key>. The literal in the view and the TimeStamp_Prefix on the configuration row have to be the same string, case included.

4. Order of work

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

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

Several of these rows share a Sync_Order 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 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_Account reads Account:; no template in this set writes Account:
• vw_SAPB1_AccountReverseLookup reads SAPB1Customer:
• vw_SAPB1_Contact reads Account:; no template in this set writes Account:
• vw_SAPB1_Customer reads Account:; no template in this set writes Account:
• vw_SAPB1_Address reads Account:, SAPB1Customer:; no template in this set writes Account:
• vw_SAPB1_ItemMaster reads Product2:
• vw_SAPB1_ItemWarehouse reads Product2:, SAPB1ItemMaster:
• vw_SAPB1_Invoice reads Account:, SAPB1Customer:; no template in this set writes Account:
• vw_SAPB1_InvoiceLine reads SAPB1Invoice:
• vw_SAPB1_PriceBookEntryCreate reads Product2:
• vw_SAPB1_PurchaseOrder reads Account:, SAPB1Customer:; no template in this set writes Account:
• vw_SAPB1_PurchaseOrderLine reads SAPB1PurchaseOrder:
• vw_SAPB1_SalesOrder reads Account:, SAPB1Customer:; no template in this set writes Account:
• vw_SAPB1_SalesOrderLine reads SAPB1SalesOrder:
• vw_SAPB1_SalesCreditHeader reads Account:, SAPB1Customer:; no template in this set writes Account:
• vw_SAPB1_SalesCreditDetail reads SAPB1SalesCreditHeader:
• vw_SAPB1_SalesDeliveryHeader reads Account:, SAPB1Customer:, SAPB1SalesOrder:; no template in this set writes Account:
• vw_SAPB1_SalesDeliveryDetail reads SAPB1SalesDeliveryHeader:

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 → Salesforce pairs
Account	Account	14	CardCode → CommercientSF__Commercient_ArCustomerCode__c, CardName → Name, Phone1 → Phone, CardType → Type, Street → BillingStreet
SAPB1 Customer	CommercientSF16__SAP_Customer__c	11	CardCode → CommercientSF16__ExternalKey__c, CardName → Name, Address → BillingStreet, City → BillingCity, Country → BillingCountry
Account Reverse lookup	Account	2	CardCode → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF16__Customer__c
SAPB1 Address	CommercientSF16__SAP_Address__c	32	Address,CardCode,AdresType → CommercientSF16__ExternalKey__c, Address → Name, Street → Street, Block → Block, ZipCode → ZipCode
SAPB1 Sales Order	CommercientSF16__SAP_SalesOrder__c	3	DocEntry → CommercientSF16__ExternalKey__c, CardCode → CommercientSF16__Account__c, CardCode → CommercientSF16__Customer__c
SAPB1 Sales Order Line	CommercientSF16__SAP_SalesOrderLine__c	3	DocEntry, LineNum → CommercientSF16__ExternalKey__c, DocNum, LineNum → Name, SFDCID → CommercientSF16__SAP_Salesorder__c
SYNC CONTACT	Contact	7	FirstName → FirstName, LastName → LastName, Fax → Fax, Phone → Phone, MobilePhone → MobilePhone
SAPB1 Invoice	CommercientSF16__SAP_Invoice__c	24	DocEntry → CommercientSF16__ExternalKey__c, CardCode → CommercientSF16__Account__c, CardCode → CommercientSF16__Customer__c, DocNum → Name, DocType → DocType
SAPB1 Invoice Line	CommercientSF16__SAP_InvoiceDetail__c	3	DocEntry, LineNum → CommercientSF16__ExternalKey__c, DocNum, LineNum → Name, SFDCID → CommercientSF16__Invoice__c
Product	Product2	6	ItemCode → CommercientSF__ExternalKey__c, ItemName → Name, ItemCode → ProductCode, ItemName → Description, ItemClass → Family
Price Book Entry Create	PricebookEntry	5	ItemCode → ExternalKey__c, Price → UnitPrice, SFDCID → Pricebook2ID, SFDCID → Product2ID
Price Book Entry Update	PriceBookEntry	3	ItemCode → ExternalKey__c, Price → UnitPrice
SAPB1 Purchase Order	CommercientSF16__OPOR__c	4	DocEntry → CommercientSF16__ExternalKey__c, DocNum → Name, CardCode → CommercientSF16__Account__c, CardCode → CommercientSF16__SAP_Customer__c
SAPB1 Purchase Order Line	CommercientSF16__POR1__c	3	DocEntry,LineNum → CommercientSF16__ExternalKey__c, DocNum,LineNum → Name, SFDCID → CommercientSF16__SAP_Purchase_Order__c
SAPB1 Item Master	CommercientSF16__OITM__c	3	ItemCode → CommercientSF16__ExternalKey__c, ItemName → Name, SFDCID → CommercientSF16__Product__c
SAPB1 Item Warehouse	CommercientSF16__OITW__c	77	ItemCode, WhsCode → CommercientSF16__ExternalKey__c, ItemCode, WhsCode → Name, SFDCID → Product__c, SFDCID → CommercientSF16__SAP_Item_Master__c, ItemCode → ItemCode
SAPB1 Sales Credit Header	CommercientSF16__ORIN__c	3	DocEntry → CommercientSF16__ExternalKey__c, CardCode → CommercientSF16__Account__c, CardCode → CommercientSF16__SAP_Customer__c
SAPB1 Sales Credit Detail	CommercientSF16__RIN1__c	2	DocEntry, LineNum → CommercientSF16__ExternalKey__c, SFDCID → CommercientSF16__SAPB1_Sales_Credit_Header__c
SAPB1 Sales Delivery Header	CommercientSF16__ODLN__c	4	DocEntry → CommercientSF16__ExternalKey__c, CardCode → CommercientSF16__Account__c, CardCode → CommercientSF16__SAP_Customer__c, DocEntry → CommercientSF16__SAP_Sales_order__c
SAPB1 Sales Delivery Detail	CommercientSF16__DLN1__c	282	DocEntry,LineNum → CommercientSF16__ExternalKey__c, DocNum,LineNum → Name, SFDCID → CommercientSF16__SAP_Sales_Delivery_Header__c, DocEntry → DocEntry, LineNum → LineNum

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 circular-sync: 0
• Licence groups they span: 15
• Destination objects: Account, Product2, CommercientSF16__SAP_Customer__c, CommercientSF16__SAP_Invoice__c, CommercientSF16__SAP_SalesOrder__c, PricebookEntry, CommercientSF16__SAP_Address__c, CommercientSF16__SAP_InvoiceDetail__c, CommercientSF16__SAP_SalesOrderLine__c, PriceBookEntry, CommercientSF16__OITM__c, CommercientSF16__OITW__c, Contact, CommercientSF16__SAP_SalesPerson__c, CommercientSF16__ORIN__c, User, CommercientSF16__OPOR__c, QuoteLineItem, CommercientSF16__POR1__c, Opportunity, 20 more and 14 custom objects
• Object display names: Account, SAPB1 Invoice, SAPB1 Sales Order, SAPB1 Invoice Line, SAPB1 Sales Order Line, Price Book Entry Create, Product, SAPB1 Address, SAPB1 Customer, Account Reverse lookup, SAPB1 Item Master, SAPB1 Item Warehouse, 89 more and 16 further templates
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, Opportunity, CRM Quote and Line, Purchase Order, CRM Opportunity and Line, CRM Ownership

A community template is imported the way a shipped one is, and the same rules apply to what it creates: read the process it creates with crmpro_get_process, its mapping with crmpro_field_mapping, and the view it selects from, before activating it.

7. 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:

• vw_SAPB1_User
• Account:
• AccountReverseLookup
• vw_SAPB1_Contact
• SAPB1Customer
• SAPB1Address
• SAPB1ItemMaster
• SAPB1ItemWarehouse
• SAPB1Invoice
• SAPB1InvoiceLine
• PricebookEntry
• PriceBookEntry
• Product2
• SAPB1PurchaseOrder
• SAPB1PurchaseOrderLine
• SAPB1SalesOrder
• SAPB1SalesOrderLine
• SAPB1SalesCreditHeader
• SAPB1SalesCreditDetail
• SAPB1SalesDeliveryHeader
• SAPB1SalesDeliveryDetail

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 B1 → 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 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.