You are here:
Considerations for Program Based Business
Review these considerations before you start using Program Based Business.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
- The out-of-the-box Data Processing Engine templates for Program Based Business work only for manufacturing programs in Active status.
- The Forecast Formula section in a Program Based Business-specific forecast set has no significance and isn’t used in forecast calculations.
- When using Data Processing Engine definitions for generating manufacturing program component forecasts, keep the limits and limitations for Data Processing Engine in mind. For more details, see Data Processing Engine Limits.
- If you’re using an orchestration flow to generate forecasts, keep the limitations of Flows in mind. For more information, see Flows.
- When you run a Data Processing Engine definition, ensure that the parameters—Manufacturing Program Id, Program Component Template Item Name, and Program Variant Template Item Name—are correctly mapped to the template associated with the manufacturing program. Incorrect mappings can lead to errors in the generated manufacturing program component forecasts.
- Ensure that the CSV files that you upload for the manufacturing program and manufacturing program variants don't contain duplicate period IDs for the same set of dimension hierarchy records. For example, for a manufacturer FastCars, for Chennai location and AutoX product, you can’t have more than one record with the same period ID.
- Ensure that you set up field-level security on the Bulk Job ID and Target Object API Name fields on the Received Document object so that these fields aren’t visible to a standard user.
- Ensure that the period group type, and calculation and rollover frequencies, of the forecast set for manufacturing program, manufacturing program variant, and manufacturing program component forecasts are the same.
- Each product related material record must have a unique combination of product variant and product component.
- The Product Component Pricebook field on the Product Related Material object is optional. If you enter a pricebook in which the specified product doesn't exist, and the DPE is run, forecasts for that product component aren't shown in the forecast grid.
- To generate forecasts for all periods, ensure that the effective start date for the product related material record and the manufacturing program forecast set period start date are the same. If you specify an effective start date of February 1, 2022 in a product related material record, and the forecast set is configured to generate quarterly forecasts starting January 1, 2022, the forecast data for the first quarter of 2022 isn’t generated.
- If the manufacturing program start date, program variant forecast start dates, and period group start date are different, the generated forecast is based on the latest date. For example, if the manufacturing program start date is January 1, 2022 the program variant forecast periods start date is January 1, 2022, and the start period in the period group setup for the associated forecast set is February 1, 2022, then the forecast grid shows component forecasts from February 1, 2022.
- If the manufacturing program end date, period group end date, or periods specified in the uploaded manufacturing program variants forecasts are different, forecasts are generated up to the earliest date. For example, if the manufacturing program end date is December 31, 2024, the period group end date is November 30, 2024, and the end date of periods in the period group setup for the associated forecast set is December 31, 2023, the forecast grid shows component forecasts up to December 31, 2023.
- The Rollover Program Component Forecast Data Processing Engine (DPE) definition runs only at the start of each period so you won't see forecasts generated for newer periods if you change forecast settings during an ongoing period. For example, if you change the display duration for a forecast in the middle of a month, the Rollover DPE considers the update only when it runs at the start of the next month. To consider the forecast settings updates, such as changes to forecast dimensions, frequencies, or period group settings during an ongoing forecast period, make sure you run the Regenerate Program Component Forecast DPE definition after you update the settings.
- Considerations for Program Based Business When Processing Large Volumes of Data
Program Based Business uses Data Processing Engines to generate manufacturing program component forecasts. The data volumes in the manufacturing program forecast fact, manufacturing program variant forecast fact, and manufacturing program component forecast fact records play a crucial role in determining the time taken to generate these forecasts.
Did this article solve your issue?
Let us know so we can improve!
