Map

In the Map screen in train stop 4, you can map run types to applications. There can be many-to-many mappings between the run types and applications. For example, if IPO-DF requires a forecast for two different measures (for example, total gross sales units and total net sales units), which may or may not be at the same forecast intersection, there will be two run types and both must be mapped to IPO-DF. Also, if two different applications (for example, IPO-DF and IPO-IO) require a forecast for the same measure and at the same forecast intersection, then both the applications will be mapped to the same run type.

You can select more than one run type at a time to be mapped to an application except when the applications are IPO-DF and RI/RMS, as shown below.

You can assign an external application key to the run types in this screen. An external application run type key value can only be assigned to a run type when the selected application is IPO-DF. Two run types that have the exact same forecast intersection, forecast measure, and data source, but different forecast methods (Sales & Promo vs. Life Cycle) can have the same external application run type key.

Basically, for each external application run type key, there can be at most one Sales & Promo run type and at most one Life Cycle run type, and those two run types must have the same forecast intersection, forecast measure, and data source.

To create a new mapping, click on the + (plus) icon above the table in Map screen. Select an application and one or more run types (based on what the application allows) and click Save. To delete a mapping, select a row and click the X icon above the table.

Figure 11-34 Map Run Types to IPO-DF as a Single-Select Option

Figure 11-35 Map Run Types to IPO-IO as a Multi-Select Option