CRMPro → Salesforce — JD Edwards: what the shipped templates set up

CRMPro → Salesforce — JD Edwards: 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/jd-edwards.md, and that skill’s ERP table is what points at it. What follows is only what the shipped JD Edwards → 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 User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	User	—
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, CommercientSF17__F03012__c, CommercientSF17_F0005__c	SF_ERP_Salesforce_Clone_F0101, SF_ERP_Salesforce_Clone_F03012, SF_ERP_Salesforce_Clone_F0116, SF_ERP_Salesforce_Clone_F0115, SF_ERP_Salesforce_Clone_F0005
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.	CommercientSF17_F4006__c, CommercientSF17__F0101__c, CommercientSF17__F0115__c	SF_ERP_Salesforce_Clone_F4006, SF_ERP_Salesforce_Clone_F0101, SF_ERP_Salesforce_Clone_F03012, SF_ERP_Salesforce_Clone_F0115
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.	CommercientSF17_F03B13__c, CommercientSF17_F03B14__c	SF_ERP_Salesforce_Clone_F03B13, SF_ERP_Salesforce_Clone_F03012, CommercientFlags, SF_ERP_Salesforce_Clone_F03B14
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.	CommercientSF17__F4201__c, CommercientSF17__F4211__c	SF_ERP_Salesforce_Clone_F4201, SF_ERP_Salesforce_Clone_F03012, CommercientFlags, SF_ERP_Salesforce_Clone_F4211

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 USERS	User	—	0	vw_JDEdwards_User	1=0	'' / ''	1
JDEdward SalesPerson	CommercientSF17_F0005__c	ExternalKey__c	1	vw_JDEdwards_SalesPerson	vw_JDEdwards_SalesPerson	'' / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_JDEdwards_Account	vw_JDEdwards_Account	'' / ''	1
JDEdwards Customer	CommercientSF17__F03012__c	CommercientSF17__ExternalKey__c	3	vw_JDEdwards_Customer	vw_JDEdwards_Customer	CommercientSF17__ / __c	1
AccountCustomerLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_JDEdwards_CustomerToAccountLookup	vw_JDEdwards_CustomerToAccountLookup	'' / ''	1
JDEdwards SalesOrder	CommercientSF17__F4201__c	CommercientSF17__ExternalKey__c	6	vw_JDEdwards_Sales_Order_Header	vw_JDEdwards_Sales_Order_Header	CommercientSF17__ / __c	1
JDEdwards SalesOrderLine	CommercientSF17__F4211__c	CommercientSF17__ExternalKey__c	7	vw_JDEdwards_Sales_Order_Detail_Line	vw_JDEdwards_Sales_Order_Detail_Line	CommercientSF17__ / __c	1
JDEdwards Invoice Header	CommercientSF17_F03B13__c	ExternalKey__c	8	vw_JDEdwards_InvoiceHeader	vw_JDEdwards_InvoiceHeader	'' / __c	1
JDEdwards Invoice Details	CommercientSF17_F03B14__c	ExternalKey__c	9	vw_JDEdwards_InvoiceDetail	vw_JDEdwards_InvoiceDetail	'' / __c	1
JDEdwards Order Address	CommercientSF17_F4006__c	ExternalKey__c	17	vw_JDEdwards_Order_Address	vw_JDEdwards_Order_Address	'' / __c	1
JDEdwards SalesOrder History	CommercientSF17__F4201__c	CommercientSF17__ExternalKey__c	18	vw_JDEdwards_Sales_Order_Header	vw_JDEdwards_Sales_Order_Header_History	CommercientSF17__ / __c	1
JDEdwards SalesOrderLine History	CommercientSF17__F4211__c	CommercientSF17__ExternalKey__c	19	vw_JDEdwards_Sales_Order_Detail_Line	vw_JDEdwards_Sales_Order_Detail_Line_History	CommercientSF17__ / __c	1
JDEdwards Address_Book_Master	CommercientSF17__F0101__c	CommercientSF17__ExternalKey__c	20	vw_JDEdwards_Address_Book_Master	vw_JDEdwards_Address_Book_Master	CommercientSF17__ / __c	1
JDEdwards Address_Book_Phone_Number	CommercientSF17__F0115__c	CommercientSF17__ExternalKey__c	21	vw_JDEdwards_Address_Book_Phone_Number	vw_JDEdwards_Address_Book_Phone_Number	CommercientSF17__ / __c	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. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on GET USERS, Account — those rows read records back from Salesforce as well as pushing. On JDEdwards SalesOrder History, JDEdwards SalesOrderLine History the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_JDEdwards_Sales_Order_Header_History against vw_JDEdwards_Sales_Order_Header; vw_JDEdwards_Sales_Order_Detail_Line_History against vw_JDEdwards_Sales_Order_Detail_Line), 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_JDEdwards_SalesPerson	insert + update	vw_JDEdwards_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_F0005
vw_JDEdwards_Account	insert + update	vw_JDEdwards_Account:	vw_JDEdwards_PaymentTerms:	—	SF_ERP_Salesforce_Clone_F0101, SF_ERP_Salesforce_Clone_F03012, SF_ERP_Salesforce_Clone_F0116, SF_ERP_Salesforce_Clone_F0115
vw_JDEdwards_Customer	insert + update	vw_JDEdwards_Customer:	vw_JDEdwards_Account:	ExternalKey	SF_ERP_Salesforce_Clone_F03012, SF_ERP_Salesforce_Clone_F0101
vw_JDEdwards_CustomerToAccountLookup	insert + update	vw_JDEdwards_CustomerToAccountLookup:	vw_JDEdwards_Customer:	—	SF_ERP_Salesforce_Clone_F0101, SF_ERP_Salesforce_Clone_F03012
vw_JDEdwards_Sales_Order_Header	insert + update	vw_JDEdwards_Sales_Order_Header:	vw_JDEdwards_Account:, vw_JDEdwards_Customer:, vw_JDEdwards_PaymentTerms:	ExternalKey	SF_ERP_Salesforce_Clone_F4201, SF_ERP_Salesforce_Clone_F03012, CommercientFlags
vw_JDEdwards_Sales_Order_Detail_Line	insert + update	vw_JDEdwards_Sales_Order_Detail_Line:	vw_JDEdwards_Sales_Order_Header:	ExternalKey	SF_ERP_Salesforce_Clone_F4211
vw_JDEdwards_InvoiceHeader	insert + update	vw_JDEdwards_InvoiceHeader:	vw_JDEdwards_Account:, vw_JDEdwards_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_F03B13, SF_ERP_Salesforce_Clone_F03012, CommercientFlags
vw_JDEdwards_InvoiceDetail	insert + update	vw_JDEdwards_InvoiceDetail:	vw_JDEdwards_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_F03B14
vw_JDEdwards_Order_Address	insert + update	vw_JDEdwards_Order_Address:	vw_JDEdwards_Sales_Order_Header:	ExternalKey	SF_ERP_Salesforce_Clone_F4006
vw_JDEdwards_Sales_Order_Header	insert-only	vw_JDEdwards_Sales_Order_Header:	vw_JDEdwards_Account:, vw_JDEdwards_Customer:, vw_JDEdwards_PaymentTerms:	ExternalKey	SF_ERP_Salesforce_Clone_F4201, SF_ERP_Salesforce_Clone_F03012, CommercientFlags
vw_JDEdwards_Sales_Order_Detail_Line	insert + update	vw_JDEdwards_Sales_Order_Detail_Line:	vw_JDEdwards_Sales_Order_Header:	ExternalKey	SF_ERP_Salesforce_Clone_F4211
vw_JDEdwards_Address_Book_Master	insert + update	vw_JDEdwards_Address_Book_Master:	vw_JDEdwards_Account:, vw_JDEdwards_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_F0101, SF_ERP_Salesforce_Clone_F03012
vw_JDEdwards_Address_Book_Phone_Number	insert + update	vw_JDEdwards_Address_Book_Phone_Number:	vw_JDEdwards_Account:, vw_JDEdwards_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_F0115, SF_ERP_Salesforce_Clone_F03012

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

• 0 — GET USERS
• 1 — JDEdward SalesPerson
• 2 — Account
• 3 — JDEdwards Customer
• 5 — AccountCustomerLookup
• 6 — JDEdwards SalesOrder
• 7 — JDEdwards SalesOrderLine
• 8 — JDEdwards Invoice Header
• 9 — JDEdwards Invoice Details
• 17 — JDEdwards Order Address
• 18 — JDEdwards SalesOrder History
• 19 — JDEdwards SalesOrderLine History
• 20 — JDEdwards Address_Book_Master
• 21 — JDEdwards Address_Book_Phone_Number

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_JDEdwards_Account reads vw_JDEdwards_PaymentTerms:; no template in this set writes vw_JDEdwards_PaymentTerms:
• vw_JDEdwards_CustomerToAccountLookup reads vw_JDEdwards_Customer:
• vw_JDEdwards_Customer reads vw_JDEdwards_Account:
• vw_JDEdwards_Order_Address reads vw_JDEdwards_Sales_Order_Header:
• vw_JDEdwards_Address_Book_Master reads vw_JDEdwards_Account:, vw_JDEdwards_Customer:
• vw_JDEdwards_Address_Book_Phone_Number reads vw_JDEdwards_Account:, vw_JDEdwards_Customer:
• vw_JDEdwards_InvoiceHeader reads vw_JDEdwards_Account:, vw_JDEdwards_Customer:
• vw_JDEdwards_InvoiceDetail reads vw_JDEdwards_InvoiceHeader:
• vw_JDEdwards_Sales_Order_Header reads vw_JDEdwards_Account:, vw_JDEdwards_Customer:, vw_JDEdwards_PaymentTerms:; no template in this set writes vw_JDEdwards_PaymentTerms:
• vw_JDEdwards_Sales_Order_Detail_Line reads vw_JDEdwards_Sales_Order_Header:
• vw_JDEdwards_Sales_Order_Header reads vw_JDEdwards_Account:, vw_JDEdwards_Customer:, vw_JDEdwards_PaymentTerms:; no template in this set writes vw_JDEdwards_PaymentTerms:
• vw_JDEdwards_Sales_Order_Detail_Line reads vw_JDEdwards_Sales_Order_Header:

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
JDEdward SalesPerson	CommercientSF17_F0005__c	13	DRSY → drsy__c, DRRT → drrt__c, DRKY → drky__c, DRDL01 → drdl01__c, DRDL02 → drdl02__c
Account	Account	16	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingPostalCode → BillingPostalCode, BillingCity → BillingCity
JDEdwards Customer	CommercientSF17__F03012__c	232	AIABC2 → AIABC2, AIABC3 → AIABC3, AIABC1 → AIABC1, AIAB2 → CommercientSF17__AIAB2__c, AIAN8 → CommercientSF17__AIAN8__c
AccountCustomerLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, JDEdwards_Customer_Master → JDEdwards_Customer_Master__c
JDEdwards SalesOrder	CommercientSF17__F4201__c	136	Account → Account, JDEdwards_Customer_Master → JDEdwards_Customer_Master, Payment_Terms_Code → Payment_Terms_Code, SHFUF1 → CommercientSF17__SHFUF1__c, SHCACT → SHCACT
JDEdwards SalesOrderLine	CommercientSF17__F4211__c	269	SDXPTY → CommercientSF17__SDXPTY__c, SDAN8 → CommercientSF17__SDAN8__c, SDCCIDLN → SDCCIDLN, SDCMCO → SDCMCO, SDLITM → CommercientSF17__SDLITM__c
JDEdwards Invoice Header	CommercientSF17_F03B13__c	99	RYPYID → rypyid__c, RYCKNU → rycknu__c, RYAN8 → ryan8__c, RYPYR → rypyr__c, RYDMTJ → rydmtj__c
JDEdwards Invoice Details	CommercientSF17_F03B14__c	200	LOOKUPTO_CommercientSF17_F03B13 → sf17f03b13__c, LOOKUPTO_CommercientSF17_F03B13 → sf17f03b13__c, RZPYID → RZPYID__c, RZPYID → rzpyid__c, RZRC5 → RZRC5
JDEdwards Order Address	CommercientSF17_F4006__c	23	LOOKUPTO_CommercientSF17__F4201 → sf17f4201__c, OADOCO → oadoco__c, OADCTO → oadcto__c, OAKCOO → oakcoo__c, OAANTY → oaanty__c
JDEdwards SalesOrder History	CommercientSF17__F4201__c	136	Account → Account, JDEdwards_Customer_Master → JDEdwards_Customer_Master, Payment_Terms_Code → Payment_Terms_Code, SHFUF1 → CommercientSF17__SHFUF1__c, SHCACT → SHCACT
JDEdwards SalesOrderLine History	CommercientSF17__F4211__c	269	SDXPTY → CommercientSF17__SDXPTY__c, SDAN8 → CommercientSF17__SDAN8__c, SDCCIDLN → SDCCIDLN, SDCMCO → SDCMCO, SDLITM → CommercientSF17__SDLITM__c
JDEdwards Address_Book_Master	CommercientSF17__F0101__c	98	ABEFTB → CommercientSF17__ABEFTB__c, ABPDI → CommercientSF17__ABPDI__c, ABURDT → CommercientSF17__ABURDT__c, ABUPMJ → CommercientSF17__ABUPMJ__c, ABUPMT1 → CommercientSF17__ABUPMT1__c
JDEdwards Address_Book_Phone_Number	CommercientSF17__F0115__c	19	WPAN8 → CommercientSF17__WPAN8__c, WPIDLN → CommercientSF17__WPIDLN__c, WPRCK7 → WPRCK7, WPCNLN → WPCNLN, WPPHTP → CommercientSF17__WPPHTP__c

6. Community templates

The catalogue carries 79 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: 79
• Default operations: insert on 79, update on 79, delete on 79
• Marked circular-sync: 0
• Licence groups they span: 13
• Destination objects: Account, Product2, CommercientSF17__F4201__c, CommercientSF17__F4211__c, Pricebookentry, CommercientSF17_F03B13__c, CommercientSF17_F03B14__c, CommercientSF17__F0101__c, CommercientSF17_F0005__c, CommercientSF17_F4006__c, Contact, Opportunity, PricebookEntry, User, CommercientSF17__F0115__c, Custom_Pricing__c, JDEdwards_Invoice_Detail__c, JDEdwards_Invoice_Header__c and 10 custom objects
• Object display names: Account, AccountCustomerLookup, JDEdwards Customer, JDEdwards Invoice Header, JDEdwards SalesOrder, JDEdwards SalesOrderLine, Product, JDEdwards Invoice Details, JDEdwards Item Master, Product Reverse Lookup, Contact, Create Standard PriceBook, 26 more and 4 further templates
• Template groups: Account, Product, Salesorder, Invoice, Customer Multi Ship Addresses, CRM Opportunity and Line, Opportunity

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_JDEdwards_User
• vw_JDEdwards_Account
• vw_JDEdwards_CustomerToAccountLookup
• vw_JDEdwards_Customer
• vw_JDEdwards_Order_Address
• vw_JDEdwards_Address_Book_Master
• vw_JDEdwards_Address_Book_Phone_Number
• vw_JDEdwards_InvoiceHeader
• vw_JDEdwards_InvoiceDetail
• vw_JDEdwards_Sales_Order_Header
• vw_JDEdwards_Sales_Order_Detail_Line
• vw_JDEdwards_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 JD Edwards → 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.