Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
Time fences let demand planning managers define rules that prevent users from manually editing time series values that are associated with a specified time span. They ensure that agreed-upon plans remain intact and unchanged during specified periods. Time fences are similar to time freezes, which are used to prevent the system from automatically editing certain existing time series values when you use rolling forecasts or when you manually rerun a forecast to update an existing time series. However, time fences only prevent manual updates.
For example, users might be prevented from editing specific time series values that fall within the current month. However, they can still edit values for the previous month or the next month. Every time fence uses the bucket size of the time series to establish a time span that starts in the current period and extends a fixed number of periods into the future.
Time fences are defined as logical expressions and apply to all time series cells where the expression is true. For example, you could create a time fence that lasts two months and applies to product ID K0001 in color Red for all time series that use Monthly time buckets.
Time fences are both flexible and easy to maintain. Managers create time fence rules based on the dimensions that are available in each plan. For example, a single product can be set up so that different time fences apply to each store or geographical location. Time fence rules can also apply based on each user's role. For example, a role-based time fence rule might allow managers to edit a forecast in a period that planners can't edit.
Time fence example
The following screenshot shows an example of a time series where two time fences apply. The time fences are represented by cells that show a lock symbol. This symbol indicates that the cells are locked. Therefore, the current user can't edit the values in them. However, the user can still edit the values in all unlocked cells. The following time fences apply here:
- Warehouse location name (Warehouse location) = Store 1 US; Time bucket = Monthly; Size = Current period + 2 Time buckets
- Product variant name (Product) = Car Audio Unit-200, Car Audio Unit-500, Car Audio 65-Silver; Time bucket = Monthly; Size = Current period + 4 time buckets
Manage time fences
To view, create, edit, or delete a time fence, follow these steps:
On the navigation pane, select Configuration > Time fences.
The Active time fence rules page shows a list of active time fences. For each time fence, you can review the name, conditions, role, and other settings.
Follow one or more of these steps as required:
- To create a new time fence, select New on the Action Pane.
- To edit an existing time fence, select the link in the Name column.
- To delete a time fence, select the row for it, and then, on the Action Pane, select Delete.
- To view and edit inactive time fences, select the Active time fence rules heading, and then select Inactive time fence rules in the dropdown list.
If you chose to edit a time fence in the previous step, a tabbed window appears. If you choose to create a new time freeze, then a wizard launches, which offers similar settings. On the Summary edit tab (or Get started wizard page), set the following fields:
- Name – Enter a name for the time fence.
- Description – Enter a short description of the time fence.
- Owner – Select the user account that owns the time fence record.
- Active – Select whether the time fence should be active. (This option is only shown on the Summary edit tab. In the wizard, you can set this field on the Review and finish page.)
On the Conditions edit tab (or Add conditions wizard page), define the conditions under which the time fence applies. Use the Add condition and Delete (trashcan) buttons to add or remove rows as required. The rows are combined by using an AND operator. Therefore, the time fence locks only cells where the condition in every row is true. For each row, set the following fields:
- Table – Select the data table that provides the cell value to compare.
- Column – For the selected table, select the column that provides the cell value to compare.
- Operator – Select the logic to apply to test the cell value against the row value. For example, select equals, greater than, or less than. There is also a Select all operator, which matches all values in the column; learn more in Using the select all operator.
- Value – Enter a comma-separated list of values to compare the cell value to. You can either select among available values in a dropdown list or enter custom values. If you specify more than one value, the values are combined by using an OR operator. Therefore, the condition in the row is true for every time series cell that matches any one of the specified values. The Value field is disabled when you use the Select all operator.
On the Time fence horizon edit tab or wizard page, define the time span that the time fence applies to. The time span always starts in the time bucket that includes the current date. It then extends a fixed number of time buckets into the future. Set the following fields:
- Time buckets – Specify the size of the time buckets that you want to use to define the time span. The time fence applies only to time series that also use this time bucket size. The system doesn't convert between time bucket sizes. For example, if you select Monthly here, your rule doesn't apply to time series that use Weekly time buckets (even though a month is about four weeks long).
- Current period + – Specify the total number of time buckets, after the current one, to include in the time fence. The time fence always applies to the current time bucket. Therefore, if you want to include only the current time bucket in the time fence, set this field to 0 (zero). To include only the current time bucket and the next one, set this field to 1.
The Example area shows the time fence that results from your settings on this page.
On the Role edit tab (or Select roles wizard page), select the user security roles that the time fence applies to.
On the Review and finish wizard page (which isn't shown when you edit an existing time fence), review the settings that you made in the previous steps and set the Active option as needed. If everything looks correct, select Review and Finish to create the time fence.
Using the select all operator
To improve efficiency and make queries easier to formulate, Demand planning provides a select all operator for creating rules for time fences, time freezes, and row level access. The Select all operator matches all values in a selected column and doesn't require a value to compare to.
The following table provides an example that shows how the select all operator can be used in a time fence rule. As a result of the rules, all products except Product A have a two-month time fence. Product A has a three-month time fence.
| Conditions | Ruling | ||||||
|---|---|---|---|---|---|---|---|
| Table | Column | Operator | Value | Time bucket | Time bucket size | Role | Status |
| Product | Product name | Select all | Not applicable | Monthly | 2 months | All | Active |
| Product | Product name | Equals | Product A | Monthly | 3 months | All | Active |
Overlapping time fences
In situations where time fences overlap, the more specific condition applies. Here are some examples:
- A time fence for all users prevents a specific cell from being edited, but the time fence for the manager user role allows the cell to be edited. In this case, a user who has the manager role is allowed to edit the cell.
- A time fence of four months is set for all products, but a time fence of two months is set for product 00001. In this case, the time fence for product 0001 is two months, but is four months for all other products that don't have more specific rules defined for them.