See how Advanced Orders for Telesales separates master business data from execution specifications, assortment listings, and transactional order records.
Required Editions
Advanced Orders for Telesales uses a modular, layered data architecture to define market scoping, product authorization listings, packaging units, and order execution rules.
Market Scoping and Reference Objects
| Object | Managed By | Purpose |
|---|---|---|
| Internal Organization Unit | Admin | Defines the business unit (InternalOrgUnit) that scopes orders, products, accounts, and users. |
| Account Internal Org Unit | Admin | Links customer accounts to an IOU to enforce market-level account scoping. |
| Product Internal Org Unit | Admin | Links products to an IOU and marks eligibility for Product Discovery API qualification (IsQualified). |
| Internal Org Unit User | Admin | Links sales reps to an IOU, establishing default market assignments, working hours, and work days. |
| Product Catalog Qualification | Admin | Binds product catalogs to an IOU, defining active qualification and eligibility date ranges. |
Order Specification and Rule Objects
| Object | Managed By | Purpose |
|---|---|---|
| Order Specification | Admin | Defines reusable order templates (OrderSpec), enforcing valid dates, DSD document types, allowed orderer types, and lead-time delivery rules. |
| Order Product Specification | Admin | Defines line-item rules (OrderItemSpec), including inventory movement types, closed listing rules, and quantity suggestion methods. |
| Order Spec Order Product Spec | Admin | Junction object (OrderSpecOrderItemSpec) defining which item specifications are permitted for a specific order specification. |
| Order Product Spec Rule | Admin | Attaches specific operational or price-impact rules to an order product specification. |
Assortment and Unit of Measure Objects
| Object | Managed By | Purpose |
|---|---|---|
| Assortment | Admin | Master list of authorized products or SKUs (Assortment and AssortmentProduct). |
| Store Assortment | Admin | Links product assortments to customer accounts, enabling automatic inheritance across parent/child account hierarchies. |
| Location Assortment | Admin | Links product assortments to physical warehouse stock points (Location) for Direct Store Delivery (DSD) workflows. |
| Associated Location | Admin | Connects customer retail accounts to their supplying warehouse locations (AssociatedLocation). |
| Product Unit of Measure | Admin | Defines ordering packaging levels (cases, pallets) per product and IOU, setting default ordering units and display sequences. |
Transactional Order Objects
| Object | Managed By | Purpose |
|---|---|---|
| Order | Telesales Rep | Represents the header transaction record (Order), tracking accounts, delivery dates, partner roles, and lifecycle phase (Draft to Activated). |
| Order Item | Telesales Rep | Represents individual line items (OrderItem), storing ordered quantities, selected UOMs, net prices, and pricing waterfall subtotals. |
Party, Role, and Account Hierarchy Objects
These objects define how customer accounts are classified and related to partner accounts (bill-to, ship-to, payer, and wholesaler/broker fulfillment), and how account hierarchies drive assortment inheritance.
| Object | Managed By | Purpose |
|---|---|---|
| Account Role | Admin | Sets an account's ordering classification through Allowed Orderer Type (Direct or Indirect) and other transaction defaults. Validated against the order specification's allowed orderer types when an order is saved. |
| Account Account Relation (AAR) | Admin | Defines relationships between a customer account and its partner accounts. At order save, these relationships automatically populate the order's Bill Recipient, Delivery Recipient (ship-to), Payer, and Fulfillment (wholesaler) accounts. The framework considers the relationship marked as primary and matching the order's IOU, and falls back to the customer's own account if no relationship is found. |
| Party Role Relation | Admin | Defines the role relationship type (such as Bill, Delivery Recipient, Payer, or Wholesaler) used by Account Account Relation records to classify how each partner account interacts for billing, delivery, payment, and distribution. |
Object Relationships and Data Flow
Here's the relationship flow from system configuration to runtime order execution:
- Market Setup: InternalOrgUnit records are created and bound to accounts, products, users, and catalogs to establish data visibility boundaries.
- Assortment and UoM Binding: Authorized products are grouped into Assortment records and assigned to account or account hierarchy node (StoreAssortment) or warehouse locations (LocationAssortment). ProductUnitOfMeasure records establish valid ordering packaging.
- Template Association: OrderSpec records are linked to permitted OrderItemSpec templates via OrderSpecOrderItemSpec, defining valid transaction rules.
- Runtime Execution: At runtime, launching New Order from an account evaluates IOU scoping and template rules, auto-populates pre-qualified assortment products, calculates UOM packaging pricing via AdvSalesTxnContext, and releases the Order record in Activated status for ERP replication.
For the full field-level reference for each object, see the Advanced Orders for Telesales object reference.