Data mapping plan from source systems to the Agentforce Manufacturing data model
Key Takeaway
Map each source record to the object at the same level of detail. A deal header maps to Sales Agreement, and its product lines map to Sales Agreement Product, which holds values for the whole agreement. Per-period values, such as monthly quantity and revenue, map to Sales Agreement Product Schedule.
A data mapping plan matches the data in a customer's existing systems, such as an ERP, to the right objects and fields in the Agentforce Manufacturing data model. A sound plan also decides how data keeps arriving. For example, the plan sets how sales agreement actuals come in when orders live outside Salesforce.
What the data model covers
The Agentforce Manufacturing data model holds objects and fields for commercial, service, partner engagement, and inventory operations. The data model is built on industry-wide best practices. You can adapt and extend it to fit a company's unique needs. The data model is available in Enterprise, Unlimited, and Developer Editions.
The data model is organized into areas, including these:
- Sales Agreements
- Advanced Account Forecasting
- Account Manager Targets
- Partner Visit Management
- Product and Asset Information
- Program Based Business
- Warranty Claims
- Warranty Supplier Recovery
- Warranty Terms and Service Standards
- Inventory Information
- Fleets of Assets