CRMPro → Salesforce — Infor LN 6: what the shipped templates set up

CRMPro → Salesforce — Infor LN 6: 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/infor-ln-6.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor LN 6 → 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
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, CommercientSF14__BAAN_CUSTOMER__c, CommercientSF14__BAAN_SALESPERSON__c	SF_ERP_Salesforce_Clone_LN_Tccom100, SF_ERP_Salesforce_Clone_LN_Tccom112, SF_ERP_Salesforce_Clone_LN_tccom130, SF_ERP_Salesforce_Clone_LN_tccom139, SF_ERP_Salesforce_Clone_LN_tcmcs143, SF_ERP_Salesforce_Clone_LN_tcmcs010
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.	CommercientSF14__BAAN_CUSTOMERADDRESS__c	SF_ERP_Salesforce_Clone_LN_tccom130, SF_ERP_Salesforce_Clone_LN_Tccom100
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF14__BAAN_INVOICEHEADER__c, CommercientSF14__BAAN_INVOICEDETAIL__c, CommercientSF14__BAAN_InvoicePayment__c	SF_ERP_Salesforce_Clone_LN_Cisli305, CommercientFlags, SF_ERP_Salesforce_Clone_LN_Cisli310
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF14__BAAN_SALESORDERHEADER__c, CommercientSF14__BAAN_SALESORDERDETAIL__c	SF_ERP_Salesforce_Clone_LN_Tdsls400, CommercientFlags, SF_ERP_Salesforce_Clone_LN_Tdsls401

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
Sales Person Sync	CommercientSF14__BAAN_SALESPERSON__c	ExternalKey__c	2	vw_INFORLN6_SalesPerson	vw_INFORLN6_SalesPerson	CommercientSF14__ / __c	1
Account Sync	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_INFORLN6_Account	vw_INFORLN6_Account	'' / ''	1
Customer Sync	CommercientSF14__BAAN_CUSTOMER__c	CommercientSF14__ExternalKey__c	6	vw_INFORLN6_Customer	vw_INFORLN6_Customer	CommercientSF14__ / __c	1
SalesOrder Header Sync	CommercientSF14__BAAN_SALESORDERHEADER__c	CommercientSF14__ExternalKey__c	7	vw_INFORLN6_SalesOrderHeader	vw_INFORLN6_SalesOrderHeader	CommercientSF14__ / __c	1
SalesOrder Line Sync	CommercientSF14__BAAN_SALESORDERDETAIL__c	CommercientSF14__ExternalKey__c	9	vw_INFORLN6_SalesOrderLine	vw_INFORLN6_SalesOrderLine	CommercientSF14__ / __c	1
Invoice Header Sync	CommercientSF14__BAAN_INVOICEHEADER__c	CommercientSF14__ExternalKey__c	10	vw_INFORLN6_InvoiceHeader	vw_INFORLN6_InvoiceHeader	CommercientSF14__ / __c	1
Invoice Line Sync	CommercientSF14__BAAN_INVOICEDETAIL__c	CommercientSF14__ExternalKey__c	11	vw_INFORLN6_InvoiceLine	vw_INFORLN6_InvoiceLine	CommercientSF14__ / __c	1
Invoice Payment Sync	CommercientSF14__BAAN_InvoicePayment__c	CommercientSF14__ExternalKey1__c	12	vw_INFORLN6_InvoicePayment	vw_INFORLN6_InvoicePayment	CommercientSF14__ / __c	1
Address Sync	CommercientSF14__BAAN_CUSTOMERADDRESS__c	CommercientSF14__ExternalKey__c	15	vw_INFORLN6_Address	vw_INFORLN6_Address	CommercientSF14__ / __c	1
Account To Customer Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	21	vw_INFORLN6_AccountReverseLookup	vw_INFORLN6_AccountReverseLookup	'' / ''	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 False, Sync_Batch_Size 200. Text columns a template does not use are inserted as '' rather than left NULL.

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_INFORLN6_SalesPerson	insert + update	vw_INFORLN6_SalesPerson:	—	—	SF_ERP_Salesforce_Clone_LN_Tccom001
vw_INFORLN6_Account		vw_INFORLN6_Account:	—	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_LN_Tccom100, SF_ERP_Salesforce_Clone_LN_Tccom112, SF_ERP_Salesforce_Clone_LN_tccom130, SF_ERP_Salesforce_Clone_LN_tccom139, SF_ERP_Salesforce_Clone_LN_tcmcs143
vw_INFORLN6_Customer	insert + update	vw_INFORLN6_Customer:	vw_INFORLN6_Account:	—	SF_ERP_Salesforce_Clone_LN_Tccom100
vw_INFORLN6_SalesOrderHeader	insert + update	vw_INFORLN6_SalesOrderHeader:	vw_INFORLN6_Account:, vw_INFORLN6_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_LN_Tdsls400, CommercientFlags
vw_INFORLN6_SalesOrderLine	insert + update	vw_INFORLN6_SalesOrderLine:	vw_INFORLN6_SalesOrderHeader:	—	SF_ERP_Salesforce_Clone_LN_Tdsls401
vw_INFORLN6_InvoiceHeader	insert + update	vw_INFORLN6_InvoiceHeader:	vw_INFORLN6_Account:, vw_INFORLN6_Customer:	—	SF_ERP_Salesforce_Clone_LN_Cisli305, CommercientFlags
vw_INFORLN6_InvoiceLine	insert + update	vw_INFORLN6_InvoiceLine:	vw_INFORLN6_GetOpportunity:, vw_INFORLN6_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_LN_Cisli310
vw_INFORLN6_InvoicePayment	insert + update	vw_INFORLN6_InvoicePayment:	vw_INFORLN6_Account:, vw_INFORLN6_Customer:, vw_INFORLN6_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_LN_Cisli305, SF_ERP_Salesforce_Clone_LN_Cisli310
vw_INFORLN6_Address	insert + update	vw_INFORLN6_Address:	vw_INFORLN6_Account:, vw_INFORLN6_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_LN_tccom130, SF_ERP_Salesforce_Clone_LN_Tccom100
vw_INFORLN6_AccountReverseLookup	insert + update	vw_INFORLN6_AccountReverseLookup:	vw_INFORLN6_Account:, vw_INFORLN6_Customer:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_LN_Tccom100

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 2 to 21. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 2 — Sales Person Sync
• 4 — Account Sync
• 6 — Customer Sync
• 7 — SalesOrder Header Sync
• 9 — SalesOrder Line Sync
• 10 — Invoice Header Sync
• 11 — Invoice Line Sync
• 12 — Invoice Payment Sync
• 15 — Address Sync
• 21 — Account To Customer Reverse Lookup

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_INFORLN6_AccountReverseLookup reads vw_INFORLN6_Account:, vw_INFORLN6_Customer:
• vw_INFORLN6_Customer reads vw_INFORLN6_Account:
• vw_INFORLN6_Address reads vw_INFORLN6_Account:, vw_INFORLN6_Customer:
• vw_INFORLN6_InvoiceHeader reads vw_INFORLN6_Account:, vw_INFORLN6_Customer:
• vw_INFORLN6_InvoiceLine reads vw_INFORLN6_GetOpportunity:, vw_INFORLN6_InvoiceHeader:; no template in this set writes vw_INFORLN6_GetOpportunity:
• vw_INFORLN6_InvoicePayment reads vw_INFORLN6_Account:, vw_INFORLN6_Customer:, vw_INFORLN6_InvoiceHeader:
• vw_INFORLN6_SalesOrderHeader reads vw_INFORLN6_Account:, vw_INFORLN6_Customer:
• vw_INFORLN6_SalesOrderLine reads vw_INFORLN6_SalesOrderHeader:

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
Sales Person Sync	CommercientSF14__BAAN_SALESPERSON__c	12	t_ccal → t_ccal, t_cpcp → t_cpcp, t_cwoc → t_cwoc, t_emno → CommercientSF14__t_emno__c, t_namb → CommercientSF14__t_namb__c
Account Sync	Account	20	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, ShippingStreet → ShippingStreet, ShippingCity → ShippingCity, ShippingState → ShippingState, ShippingCountry → ShippingCountry
Customer Sync	CommercientSF14__BAAN_CUSTOMER__c	34	t_cadr → t_cadr, t_iscn → t_iscn, t_inrl → CommercientSF14__t_inrl__c, t_bptx → CommercientSF14__t_bptx__c, t_prst → CommercientSF14__t_prst__c
SalesOrder Header Sync	CommercientSF14__BAAN_SALESORDERHEADER__c	59	Account → Account, Customer → CommercientSF14__Customer__c, t_akcd → t_akcd, t_creg → t_creg, t_bptx → CommercientSF14__t_bptx__c
SalesOrder Line Sync	CommercientSF14__BAAN_SALESORDERDETAIL__c	57	Sales_Order_Header → CommercientSF14__Sales_Order_Header__c, t_oamt → CommercientSF14__t_oamt__c, t_damt → CommercientSF14__t_damt__c, t_qbbo → CommercientSF14__t_qbbo__c, t_cvbs → t_cvbs
Invoice Header Sync	CommercientSF14__BAAN_INVOICEHEADER__c	58	t_aaai → CommercientSF14__t_aaai__c, t_amth_1 → CommercientSF14__t_amth_1__c, t_amth_2 → CommercientSF14__t_amth_2__c, t_amth_3 → CommercientSF14__t_amth_3__c, t_amti → CommercientSF14__t_amti__c
Invoice Line Sync	CommercientSF14__BAAN_INVOICEDETAIL__c	44	t_amth_1 → CommercientSF14__t_amth_1__c, t_amth_2 → CommercientSF14__t_amth_2__c, t_amth_3 → CommercientSF14__t_amth_3__c, t_amti → CommercientSF14__t_amti__c, t_bpct → t_bpct
Invoice Payment Sync	CommercientSF14__BAAN_InvoicePayment__c	41	ExternalKey1 → CommercientSF14__ExternalKey1__c, t_amth_1 → CommercientSF14__t_amth_1__c, t_amti → CommercientSF14__t_amti__c, t_amth_2 → CommercientSF14__t_amth_2__c, t_amth_3 → CommercientSF14__t_amth_3__c
Address Sync	CommercientSF14__BAAN_CUSTOMERADDRESS__c	45	Account → Account, Customer → CommercientSF14__Customer__c, t_cadr → t_cadr, t_namc → t_namc, t_namd → CommercientSF14__t_namd__c
Account To Customer Reverse Lookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF14ustomer → CommercientSF14__Customer__c

6. Community templates

The catalogue carries 21 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: 21
• Default operations: insert on 21, update on 21, delete on 21
• Marked circular-sync: 0
• Licence groups they span: 11
• Destination objects: Account, BAAN_DivisionCode, BAAN_OpportunityHeader__c, BAAN_OpportunityLine__c, BAAN_Order_Shipment__c, CommercientSF14__BAAN_CUSTOMER__c, CommercientSF14__BAAN_CUSTOMERADDRESS__c, CommercientSF14__BAAN_INVOICEDETAIL__c, CommercientSF14__BAAN_INVOICEHEADER__c, CommercientSF14__BAAN_InvoicePayment__c, CommercientSF14__BAAN_PAYMENTTERM__c, CommercientSF14__BAAN_SALESORDERDETAIL__c, CommercientSF14__BAAN_SALESORDERHEADER__c, CommercientSF14__BAAN_SALESPERSON__c, ContentDocument, Opportunity, Quote_History__c and a custom object
• Object display names: Account Sync, Account To Customer Reverse Lookup, Address Sync, BAAN OpportunityHeader Sync, BAAN OpportunityLine Sync, BAAN_DivisionCode, BAAN_Order_Shipment, Customer Sync, Get Account, Get Opportunity, Invoice Header Sync, Invoice Line Sync, 8 more and a further template
• Template groups: Account, Customer Multi Ship Addresses, Invoice, Opportunity, Salesorder, CRM Opportunity and Line

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_INFORLN6_Account
• vw_INFORLN6_AccountReverseLookup
• vw_INFORLN6_Customer
• vw_INFORLN6_Address
• vw_INFORLN6_InvoiceHeader
• vw_INFORLN6_InvoiceLine
• vw_INFORLN6_InvoicePayment
• vw_INFORLN6_SalesOrderHeader
• vw_INFORLN6_SalesOrderLine
• vw_INFORLN6_SalesPerson

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 Infor LN 6 → 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.