Resellers, distributors and agents as one party record with their territories, tiers, agreements and the sell-through data that measures them.
Today a distributor is a customer in the ERP, a partner account in the CRM and a row in the rebate spreadsheet, and the rebate is paid on the spreadsheet's numbers.
With Lima the channel partners are read where they live, matched on partner id and legal entity (golden customer), assembled field by field and published as one golden record per real distributors, with every source key underneath. Orders, sell-through reports, accruals and payments for the partner, by programme are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
A channel partner is a role on a golden customer, so orders, credit and rebates meet on one record.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Programme | programme → tier → partner |
| Territory | region → country → partner |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | tier is in the programme's list valid-to is after valid-from |
| Row | an exclusive territory has exactly one partner a partner with a rebate agreement reports sell-through |
| Business | rebate accruals equal the programme's rules applied to sell-in and sell-through attainment by region equals the sum of its partners no partner holds two conflicting exclusivities |
| Transactions in the bed | Read from |
|---|---|
| Sell-in orders | ERP sales orders |
| Sell-through and inventory | partner reports |
| Rebate accruals and payments | finance |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens orders, sell-through reports, accruals and payments for the partner, by programme.
Rebate terms visible to channel management and finance; territories to sales; the partner sees its own record on the portal. The twelve layers apply on every door; see security.
POST /api/v1/golden/partner/lookup
{
"customer": "C-00842"
}200 OK
{
"partner_id": "PT-0331",
"tier": "gold",
"territories": [
"US-West"
],
"programmes": 2,
"attainment_ytd": 0.87
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Partner account read from Account (IsPartner) · PartnerNetworkConnection.
Open the Salesforce page →Partner as customer read from KNA1 · KNVV.
Open the SAP S/4HANA page →Partner read from ZPM_PARTNER_PROFILES (REST: partners).
Open the Oracle Fusion Cloud page →Partner read from CONFORMED.CHANNEL_PARTNER.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A high-tech vendor paid rebates on partner-reported numbers reconciled by hand. With sell-in from the ERP and sell-through reports on one partner record, accruals became a rule, and the quarter-end dispute list shrank from 40 partners to 3.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.
High-tech and semiconductor, Consumer goods, Industrial manufacturing. The industry pages show the domains each starts with.
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.