Estimating compensation
AssigneeOracle International Corporation
InventorsGanesh Naganathan, Pamela Walker-Cleary, Rohan R. Shetty, Jayakrishnan Radhakrishnan
Life of this patent
Estimating the term…
Abstract
A salesperson may estimate his compensation in different hypothetical scenarios by inputting hypothetical sales data into a compensation estimation system. The compensation estimation system may compute the sales person's hypothetical compensation based on both actual sales data and the hypothetical sales data, thereby producing a “what if” outlook for the sales person. Significantly, the hypothetical sales data can be entered into and modified within the compensation estimation system without modifying or corrupting the actual sales data.
Claims24
A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:
- receiving, via a graphical user interface (GUI), a first user input that includes one or more sales entry attributes for at least one non-materialized sale associated with an individual salesperson;
- generating a first set of non-materialized sales entries based on the one or more sales entry attributes;
- storing the first set of one or more non-materialized sales entries in a first data object;
- detecting addition of a set of one or more materialized sales entries, associated with the individual salesperson, to a second data object different than the first data object;
- wherein the second data object maintains transactional sales data as stages of a sales cycle are completed;
- wherein at least one of the set of materialized sales entries is entered into the second data object by an application rather than directly entered by any user;
- responsive to detecting the addition of the set of one or more materialized sales entries:
- continually updating and storing an earned compensation value, for the individual salesperson, corresponding to the set of materialized sales entries stored in the second data object;
- responsive to a second user input initiating an estimation process to generate an estimated compensation value:
- determining the estimated compensation value, for the individual salesperson, based on (a) the first set of non-materialized sales entries stored in the first data object and (b) the previously determined earned compensation value without accessing the set of materialized sales entries stored in the second data object;
- and
- concurrently presenting, at the GUI, the estimated compensation value and the earned compensation value.
A method, comprising:
- receiving, via a graphical user interface (GUI), a first user input that includes one or more sales entry attributes for at least one non-materialized sale associated with an individual salesperson;
- generating a first set of non-materialized sales entries based on the one or more sales entry attributes;
- storing the first set of one or more non-materialized sales entries in a first data object;
- detecting addition of a set of one or more materialized sales entries, associated with the individual salesperson, to a second data object different than the first data object;
- wherein the second data object maintains transactional sales data as stages of a sales cycle are completed;
- wherein at least one of the set of materialized sales entries is entered into the second data object by an application rather than directly entered by any user;
- responsive to detecting the addition of the set of one or more materialized sales entries:
- continually updating and storing an earned compensation value, for the individual salesperson, corresponding to the set of materialized sales entries stored in the second data object;
- responsive to a second user input initiating an estimation process to generate an estimated compensation value:
- determining the estimated compensation value, for the individual salesperson, based on (a) the first set of non-materialized sales entries stored in the first data object and (b) the previously determined earned compensation value without accessing the set of materialized sales entries stored in the second data object;
- and
- concurrently presenting, at the GUI, the estimated compensation value and the earned compensation value.
A system, comprising:
- at least one device including a hardware processor;
- and
- the system being configured to perform operations comprising:
- receiving, via a graphical user interface (GUI), a first user input that includes one or more sales entry attributes for at least one non-materialized sale associated with an individual salesperson;
- generating a first set of non-materialized sales entries based on the one or more sales entry attributes;
- storing the first set of one or more non-materialized sales entries in a first data object;
- detecting addition of a set of one or more materialized sales entries, associated with the individual salesperson, to a second data object different than the first data object;
- wherein the second data object maintains transactional sales data as stages of a sales cycle are completed;
- wherein at least one of the set of materialized sales entries is entered into the second data object by an application rather than directly entered by any user;
- responsive to detecting the addition of the set of one or more materialized sales entries:
- continually updating and storing an earned compensation value, for the individual salesperson, corresponding to the set of materialized sales entries stored in the second data object;
- responsive to a second user input initiating an estimation process to generate an estimated compensation value:
- determining the estimated compensation value, for the individual salesperson, based on (a) the first set of non-materialized sales entries stored in the first data object and (b) the previously determined earned compensation value without accessing the set of materialized sales entries stored in the second data object;
- and
- concurrently presenting, at the GUI, the estimated compensation value and the earned compensation value.
Dependencies are inferred from the claim text.