What if scenario planning—updating a base plan version

Patent metadata

Field	Value
Publication number	US-12468678-B2
Application number	US-202418594673-A
Country	US
Kind code	B2
Filing date	Mar 4, 2024
Priority date	Sep 22, 2023
Publication date	Nov 11, 2025
Grant date	Nov 11, 2025

Abstract

A system, method, and device for updating a base version of a hypercube are provided. The method includes (i) obtaining a request for a planning session with respect to a hypercube; and (ii) in response to obtaining the request: (a) determining that the planning session uses a base version of the hypercube, (b) receiving a value input to update a particular location in the hypercube, (c) storing the value for the particular location in the base version of the hypercube, and (d) propagating an update to the particular location of the base version of the hypercube to one or more scenario versions having a dependency on the base version.

First claim

What is claimed is:

1 . A system, comprising:
one or more processors configured to:
obtain a request for a planning session with respect to a hypercube; and
in response to obtaining the request,
determine that the planning session uses a base version of the hypercube;
receive a value input to update a particular location in the hypercube;
store the value for the particular location in the base version of the hypercube; and
propagate an update to the particular location of the base version of the hypercube to one or more scenario versions having a dependency on the base version, wherein the dependency of the one or more scenario versions on the base version is determined based at least in part on an override data structure that indicates a set of locations of the hypercube for which the one or more scenario versions have a value that overrides the base version; and

a memory coupled to the one or more processors and configured to provide the one or more processors with instructions.

2 . The system of claim 1 , wherein a scenario version has a dependency on the base version if a first location of the scenario version of the hypercube uses a value at a corresponding first location of the base version of the hypercube.

3 . The system of claim 1 , wherein storing the value comprises:
updating the base version of the hypercube for the particular location to be set to the value; and setting an indicator indicating that the particular location of the base version has changed.

4 . The system of claim 1 , wherein a first value at a first location of the hypercube is a static or input value.

5 . The system of claim 4 , wherein:
propagating the update for the first location of the base version comprises setting an indicator that the first value for the first location of the base version has been updated; and a service providing a first scenario version dependent on the base version determines to retrieve an updated value for the first location in connection with providing the first scenario version.

6 . The system of claim 5 , wherein:
the service providing the first scenario version provides the updated value for the first location of the first scenario version in response to determining that the first scenario version does not have a value at the first location that overrides the first value for the base version; and the service determines that the first scenario version does not have the value at the first location that overrides the first value for the base version based on a data structure indicating a set of overrides for the one or more scenario versions.

7 . The system of claim 5 , wherein:
in response to determining that the first scenario version comprises a second location having a formula that is dependent on the first value for first location of the base version, the service providing the first scenario version obtains an updated first value for the first location of the base version and recomputes the formula to return a value for the second location.

8 . The system of claim 1 , wherein a first value at a first location for the base version of the hypercube is a formula.

9 . The system of claim 8 , wherein propagating the update for the first location of the base version comprises setting an indicator that the first value for the first location of the base version has been updated.

10 . The system of claim 8 , wherein propagating the update for the first location of the base version comprises providing a scenario version an indication that a dependency on a previous value for the first location of the base version is no longer valid.

11 . The system of claim 10 , wherein a service providing the scenario version determines, based at least in part that the dependency is no longer valid, that a second value for a second location of the scenario version having the dependency on the previous value for the first location of the base version is to be recomputed.

12 . The system of claim 10 , wherein a service providing the scenario version determines that the dependency is no longer valid for reading processes having an associated timestamp that is after a time at which the update is set.

13 . The system of claim 1 , wherein in response to determining that the planning session corresponds to a request to use the base version, a set of values are obtained from the base version.

14 . The system of claim 1 , wherein in response to determining that the planning session corresponds to a request to use the scenario version, a set of values are obtained based at least in part on the base version and a scenario version.

15 . The system of claim 7 , wherein the value input to the particular location of the scenario version is not automatically propagated to the base version.

16 . The system of claim 7 , wherein the value input at the particular location of the scenario version is propagated to one or more other session versions that have a dependency to the scenario version associated with the planning session.

17 . The system of claim 1 , wherein the input value is automatically propagated to a scenario version having a dependency on the base version if the input value is a static value.

18 . The system of claim 1 , wherein in the event that the input value corresponds to a formula, the input value is propagated to a scenario version having a dependency on the base version when the scenario version recomputes the formula at the particular location.

19 . The system of claim 1 , wherein the override data structure indicates whether a value in the hypercube corresponds to a base version value for the base version or a first scenario version value according to a scenario version associated with the request for the planning session.

20 . A method, comprising:
obtaining a request for a planning session with respect to a hypercube; and in response to obtaining the request,
determining that the planning session uses a base version of the hypercube;
receiving a value input to update a particular location in the hypercube;
storing the value for the particular location in the base version of the hypercube; and
propagating an update to the particular location of the base version of the hypercube to one or more scenario versions having a dependency on the base version, wherein the dependency of the one or more scenario versions on the base version is determined based at least in part on an override data structure that indicates a set of locations of the hypercube for which the one or more scenario versions have a value that overrides the base version.

21 . A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
obtaining a request for a planning session with respect to a hypercube; and in response to obtaining the request,
determining that the planning session uses a base version of the hypercube;
receiving a value input to update a particular location in the hypercube;
storing the value for the particular location in the base version of the hypercube; and
propagating an update to the particular location of the base version of the hypercube to one or more scenario versions having a dependency on the base version, wherein the dependency of the one or more scenario versions on the base version is determined based at least in part on an override data structure that indicates a set of locations of the hypercube for which the one or more scenario versions have a value that overrides the ba

Assignees

• Workday Inc

Inventors

• Lee Darren
• Vemuri Srinivas
• Wang Francis
• Bornhoevd Christof
• Thompson Mark

Classifications

• G06F16/2264 Primary

  Multidimensional index structures · CPC title