Domain catalogue Products on Salesforce

Material and product on Salesforce

One record per item: the global identity, the descriptions, the classification, and the plant-level data that planning and purchasing need.

SOURCES, READ IN PLACESalesforceCRMASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN MATERIAL AND PRODUCTMaterial and productone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
The objects the domain reads in place on Salesforce, the assembly steps, and who reads the result. Writes go through REST upserts on an external id.
2
objects read in place from Salesforce
catalogue
6
attribute groups assembled
catalogue
6 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The Salesforce objects behind the golden record

Objects are read through the Salesforce APIs (REST, Bulk, Change Data Capture); the rows stay in Salesforce.

ObjectRead fromFields the domain usesFreshness
ProductProduct2Id · Name · ProductCode · StockKeepingUnit · Family · IsActivelive; Change Data Capture where enabled
Price book entriesPricebookEntryProduct2Id · Pricebook2Id · UnitPrice · CurrencyIsoCodelive; Change Data Capture where enabled
The keys

How material and product records match, in this system's fields

GTINmanufacturer part number and manufacturerengineering drawing numberdescription tokens and attributes (fuzzy)legacy numbers kept in the crosswalk

The first object above carries the strong keys; the standardised attributes come from the same rows. Attribute-based matching compares the physical attributes (dimensions, material, rating) so two descriptions of the same resistor match even when the words differ.

What is written back

Through the interfaces Salesforce supports

Writes are upserts through the REST API on the external id; every call returns the record id or the error, and Lima logs both.

InterfaceUsed forResult
upsert Product2 on External_Id__c; PricebookEntry insertsgolden values approved for write-back: identity; classification; physicalthe id or error Salesforce returns, stored beside the change

Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.

Access and prerequisites

What is in place before the first build

Salesforce profiles and sharing rules are mapped to Lima policies once; a user sees here what they see in Salesforce.

Register the objects2 objects from the connector catalogue; each shows its rows at once.
Nearby

This domain on other systems, and other domains on Salesforce

Material and product on

Other domains on Salesforce

Terms on this page

Manufacturer part numberThe maker's own identifier for an item; a strong match key across plants.
Plant dataThe values that differ per plant: lead time, lot size, MRP controller, safety stock.
Read in placeThe rows stay in Salesforce; Lima sends the filter and the columns and Salesforce returns the matching rows.
Questions

Does this domain copy data out of Salesforce?

The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.

What does the Salesforce team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Salesforce.

Can we start with reads only?

Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.