Home

Order Chapters run in dependency order. Each one needs only what the chapters before it set up.

Direction Each chapter has an ERP → Salesforce page and a Salesforce → ERP page. Each page names the side that receives the call.

Search Press / to search headings and body text. A quoted phrase narrows the match.

Chapters

Territory and the catalogue come first, then the vendor. The distributor is onboarded after that, and its lifecycle and Ship To build on the Sold To.

• Territory

  ---

  The Region, Zone, and Territory tree behind TER-KA-BLR-01.

  • ERP → Salesforce: the upsert by territory code, and the geography create
  • Salesforce → ERP: the 201, the empty 204, and the geography results

• Product

  ---

  The Tea category, Assam Leaf 500g, and the gift-pack bundle.

  • ERP → Salesforce: the category upsert, the product upsert, and the bundle lines
  • Salesforce → ERP: the 201, the empty 204, and the bundle create

• Price

  ---

  The INR price of TEA-500, and the next batch that closes it.

  • ERP → Salesforce: the upsert by sku batch key, and the Composite that end-dates the open price
  • Salesforce → ERP: the 201, the empty 204, and the Composite result

• FOC

  ---

  The branded umbrella Sharma Distributors can issue free of cost.

  • ERP → Salesforce: the upsert of FOC_Master__c by FOC code
  • Salesforce → ERP: the 201 that stores the id, and the 204 that counts as success

• Vendor

  ---

  Speedy Service on TER-KA-BLR-01, code VN-00001.

  • ERP → Salesforce: the Account upsert by vendor code, and the deactivate
  • Salesforce → ERP: the record type query, the 201, and the empty 204

• Distributor onboarding

  ---

  The sample distributor, how the two systems connect, and the order of calls.

  • Salesforce → ERP: the onboarding POST, the callback, every mapping, and every error
  • ERP → Salesforce: the Sold To PATCH and the Bill To create
  • Failures and retry: what stays saved when a later call fails

• Account lifecycle

  ---

  Updates, a new Bill To, freeze, unfreeze, deactivate, and activate.

  • ERP → Salesforce: the PATCH and POST bodies ERP sends after onboarding
  • Salesforce → ERP: the 204, the 201, and the callback for a new Bill To

• Ship To

  ---

  A delivery address under DIST001, created by either system.

  • Salesforce → ERP: the finished Ship To Salesforce posts after the code exists
  • ERP → Salesforce: the Ship To ERP creates, and the Ship_To__c body it posts