Sales agreement data model components in the technical design
Key Takeaway
Planned terms live in Sales Agreement, Sales Agreement Product, and Sales Agreement Product Schedule, while actuals come from orders and contracts. Record a return as an order product with a negative quantity, and don't add record types to Sales Agreement Product.
A sales agreement in Agentforce Manufacturing is a long-term agreement between a buyer and a seller that sets the price and volume of products. Its data model stores the planned terms at three levels: the agreement, each product or category, and each schedule period. Orders and contracts supply the actual values that users compare with the plan. A technical design should name these objects and show how they connect to products, pricing, orders, and forecasting. It should also cover the constraints that limit how you can extend them.
The objects in the data model
The Agentforce Manufacturing data model is available in Enterprise, Unlimited, and Developer Editions. The model is built on industry-wide best practices, and you can adapt and extend it to fit a company's needs. Its sales agreements area covers managing sales agreements, plus managing orders and contracts to derive sales agreement actuals.
| Object | What it stores |
|---|---|
| Sales Agreement | The top-level object: a long-term agreement between a buyer and a seller to negotiate the price and volume of products |
| Sales Agreement Product | Quantity, revenue, and pricing of a product or product category across the full duration of the agreement |
| Sales Agreement Product Schedule | The same kinds of information for one schedule of the agreement |
| Order | A customer's order for a product or service |
| Order Product | The quantity and pricing of a product in an order |
| Contract | The business terms between a manufacturer and its customer |
The sales agreements data model also includes Account, Contact, Product, Price Book, and Price Book Entry.
A Sales Agreement Product can represent either a single product or a product category. An agreement can have its Product Level set to Category. You can add the same product to a sales agreement more than once, as long as each instance has a unique display name.
Picture the planned terms as a grid. Each row is a Sales Agreement Product. Each column is a schedule period, such as a month or a year. Each cell is a Sales Agreement Product Schedule record, so each product line is split into one record for each schedule period.
Users view and edit these revenue and quantity metrics on the "Agreement Terms" tab. They can filter by product, product category, or time period.
A valve manufacturer signs a one-year agreement with a distributor and chooses monthly schedules. The agreement covers three products: a ball valve, a gate valve, and a seal kit. The design has one Sales Agreement record and three Sales Agreement Product records. Under them sit 36 Sales Agreement Product Schedule records, one for each product in each of the 12 months. Each schedule record holds the quantity, revenue, and pricing for one product in one month.
Schedule names are generated from each schedule's start date, for example Aug '23 for a monthly schedule or 2023 for a yearly one. You can rename a schedule by editing the Name field on its Sales Agreement Product Schedule record.