Data transaction acceleration using multiple data structure types

1. A method of accelerating execution of a batch of transactions using two different data structures, the method comprising:

storing, by a computer system, one or more financial ledgers in a relational database system;

prepopulating, by a computer system, a multidimensional data cube using data from the one or more financial ledgers in the relational database system, wherein the multidimensional data cube comprises aggregated balances used by the batch of transactions;

receiving, by the computer system, the batch of transactions;

executing, by the computer system, the batch of transactions using data in the multidimensional data cube, wherein:

the multidimensional data cube is queried for the aggregated balances; and

the batch of transactions are executed using the queried aggregated balances of the multidimensional data cube to generate result values for each account affected by the batch of transactions;

generating, by the computer system, one or more accounting journal entries that update each account in the one or more ledgers affected by the batch of transactions using the result values from the multidimensional data cube;

posting, by the computer system, the one or more accounting journal entries to the one or more financial ledgers in the relational database system;

repopulating, by the computer system, the multidimensional data cube with changes resulting from the one or more accounting journal entries being posted to the one or more financial ledgers in the relational database system; and

updating, by the computer system, the aggregated balances of the multidimensional data cube.

2. The method of claim 1 further comprising:

receiving a point-of-view comprising information about the batch of transactions;

preparing a plurality of sequential interfaces, wherein each interface is configured to receive a portion of the batch of transactions;

determining that a first portion of the batch of transactions is defined by the point-of-view;

preventing a first interface in the plurality of sequential interfaces from being presented;

presenting the remaining interfaces in the plurality of sequential interfaces; and

receiving the remaining portions of the batch of transactions from the remaining interfaces in the plurality of sequential interfaces.

3. The method of claim 1 , wherein the batch of transactions comprises a transfer formula.

4. The method of claim 1 , wherein the batch of transactions comprises a allocation scenario.

5. The method of claim 1 , further comprising receiving a run-time-prompt variable definition that specifies a portion of the batch of transactions that should be received at run time.

6. The method of claim 5 , further comprising:

receiving, prior to executing the batch of transactions, a value for the run-time-prompt variable; and

using the value of the run-time prompt variable to execute the batch of transactions.

7. The method of claim 1 , further comprising:

generating a transaction scenario in the multidimensional data cube, wherein the transaction scenario is stored in a dedicated dimension in the multidimensional data cube; and

clearing data from the transaction scenario from the multidimensional data cube prior to posting the one or more journal entries.

8. The method of claim 7 , further comprising:

generating the one or more accounting journal entries by importing data from the transaction scenario using a general ledger interface of the relational database.

9. A non-transitory, computer-readable storage medium comprising a set of instructions which, when executed by one or more processors, causes the one or more processors to perform operations including:

storing one or more financial ledgers in a relational database system;

prepopulating a multidimensional data cube using data from the one or more financial ledgers in the relational database system, wherein the multidimensional data cube comprises aggregated balances used by a batch of transactions;

receiving the batch of transactions;

executing the batch of transactions using data in the multidimensional data cube, wherein:

the multidimensional data cube is queried for the aggregated balances; and

the batch of transactions are executed using the queried aggregated balances of the multidimensional data cube to generate result values for each account affected by the batch of transactions;

generating one or more accounting journal entries that update each account in the one or more ledgers affected by the batch of transactions using the result values from the multidimensional data cube;

posting the one or more accounting journal entries to the one or more financial ledgers in the relational database system;

repopulating the multidimensional data cube with changes resulting from the one or more accounting journal entries being posted to the one or more financial ledgers in the relational database system; and

updating the aggregated balances of the multidimensional data cube.

10. The storage medium of claim 9 , wherein the set of instructions cause the one or more processors to perform further operations including:

receiving a point-of-view comprising information about the batch of transactions;

preparing a plurality of sequential interfaces, wherein each interface is configured to receive a portion of the batch of transactions;

determining that a first portion of the batch of transactions is defined by the point-of-view;

preventing a first interface in the plurality of sequential interfaces from being presented;

presenting the remaining interfaces in the plurality of sequential interfaces; and

receiving the remaining portions of the batch of transactions from the remaining interfaces in the plurality of sequential interfaces.

11. The storage medium of claim 9 , wherein the batch of transactions comprises a transfer formula.

12. The storage medium of claim 9 , wherein the batch of transactions comprises a allocation scenario.

13. The storage medium of claim 9 , wherein the set of instructions cause the one or more processors to perform further operations including:

receiving a run-time-prompt variable definition that specifies a portion of the batch of transactions that should be received at run time.

14. The storage medium of claim 13 , wherein the set of instructions cause the one or more processors to perform further operations including:

receiving, prior to executing the batch of transactions, a value for the run-time-prompt variable; and

using the value of the run-time prompt variable to execute the batch of transactions.

15. The storage medium of claim 9 , wherein the set of instructions cause the one or more processors to perform further operations including:

generating a transaction scenario in the multidimensional data cube, wherein the transaction scenario is stored in a dedicated dimension in the multidimensional data cube; and

clearing data from the transaction scenario from the multidimensional data cube prior to posting the one or more journal entries.

16. A system comprising:

one or more processors; and

a non-transitory memory comprising a set of instructions which, when executed by the one or more processors, cause the one or more processors to perform operations including:

storing one or more financial ledgers in a relational database system;

prepopulating a multidimensional data cube using data from the one or more financial ledgers in the relational database system, wherein the multidimensional data cube comprises aggregated balances used by a batch of transactions;

receiving the batch of transactions;

executing the batch of transactions using data in the multidimensional data cube, wherein:

the multidimensional data cube is queried for the aggregated balances; and

the batch of transactions are executed using the queried aggregated balances of the multidimensional data cube to generate result values for each account affected by the batch of transactions;

generating one or more accounting journal entries that update each account in the one or more ledgers affected by the batch of transactions using the result values from the multidimensional data cube;

posting the one or more accounting journal entries to the one or more financial ledgers in the relational database system;

repopulating the multidimensional data cube with changes resulting from the one or more accounting journal entries being posted to the one or more financial ledgers in the relational database system; and

updating the aggregated balances of the multidimensional data cube.

17. The system of claim 16 , wherein the set of instructions cause the one or more processors to perform further operations including:

receiving a point-of-view comprising information about the batch of transactions;

preparing a plurality of sequential interfaces, wherein each interface is configured to receive a portion of the batch of transactions;

determining that a first portion of the batch of transactions is defined by the point-of-view;

preventing a first interface in the plurality of sequential interfaces from being presented;

presenting the remaining interfaces in the plurality of sequential interfaces; and

receiving the remaining portions of the batch of transactions from the remaining interfaces in the plurality of sequential interfaces.

18. The system of claim 16 , wherein the batch of transactions comprises a transfer formula.

19. The system of claim 16 , wherein the set of instructions cause the one or more processors to perform further operations including:

receiving a run-time-prompt variable definition that specifies a portion of the batch of transactions that should be received at run time.

20. The system of claim 16 , wherein the set of instructions cause the one or more processors to perform further operations including:

generating a transaction scenario in the multidimensional data cube, wherein the transaction scenario is stored in a dedicated dimension in the multidimensional data cube; and

clearing data from the transaction scenario from the multidimensional data cube prior to posting the one or more journal entries.