Multitenant architecture for prior period adjustment processing

• US 10,545,952 B2
• Filed: 01/31/2017
• Issued: 01/28/2020
• Est. Priority Date: 01/31/2017
• Status: Active Grant

• Current Assignee: Xactly
• Original Assignee: Xactly
• Inventors: Rasmussen, Ron, Krishnamoorthy, Vasu, Gefter, Denis
• Primary Examiner(s): Vital, Pierre M
• Assistant Examiner(s): Sultana, Nargis
• Application Number:
  US15/421,008
• Publication Number:
  US 20180218025A1
• Time in Patent Office: 1,092 Days
• Field of Search: 707692
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A data processing method comprises receiving a request to perform a prior period adjustment (PPA) for a tenant in which data values applicable to a time period earlier than a current time period will be modified, in response to the request, identifying a working subset of data from tenant data in the production database and copying the working subset to a calculation database separate from the production database, performing the PPA, using the working subset in the calculation database, to result in creating and storing a plurality of result data, receiving, while performing the PPA, an additional request using the tenant data in the production database, performing the additional request using the tenant data in the production database while performing the PPA and updating the replay log, after completing the PPA and using the replay log, transferring the plurality of results to the production database.

Claims

1. A data processing method comprising:

using an application server computer of an application service provider (ASP), establishing computerized shared multi-tenant data storage in which tenant data that is associated with a plurality of different tenants of the ASP is stored together in a production database, wherein the application server computer maintains a replay log that tracks changes for each tenant;

receiving, by the application server computer, a first request to perform a prior period adjustment (PPA) for a first tenant in which data values applicable to a closed time period earlier than an open current time period will be modified, wherein the closed time period was previously processed;

in response to the first request, identifying a working subset of data from first tenant data in the production database and copying the working subset of data to a calculation database that is separate from the production database, wherein the working subset comprises a minimum amount of data needed to perform an accurate PPA according to a policy of the first tenant;

performing the PPA, using the working subset in the calculation database, by performing a plurality of same calculations in a same order as when the closed time period was previously processed to result in creating and storing a plurality of result data;

while performing the PPA;

receiving a second request that uses the first tenant data in the production database;

performing the second request using the first tenant data in the production database; and

updating the replay log based on the second request;

in response to a failure;

identifying a portion of the working subset related to the failure;

deleting the portion of the working subset related to the failure;

copying the portion of the working subset related to the failure from the production database to the calculation database;

after completing the PPA, transferring the plurality of result data to the production database using the replay log;

sending a notification to one or more entities impacted by a plurality of changes that were made to the first tenant data during transferring.

2. The method of claim 1, wherein the replay log comprises stored digital data representing a plurality of events, each event comprising a definition.

3. The method of claim 2, wherein an event of the plurality of events comprises a data deletion event.

4. The method of claim 3, further comprising:

performing the second request by modifying the first tenant data.

5. The method of claim 1, wherein the working subset of data comprises 4 periods of data that is read-only and cannot be written back to the production database.

6. The method of claim 1, wherein the notification identifies differences represented in the plurality of changes.

7. The method of claim 1, wherein the production database comprises two or more databases in different formats.

8. A computer system comprising:

a production database storing tenant data that is associated with a plurality of different tenants of an application service provider;

a calculation database separate from the production database;

one or more application server computers communicatively connected to the production database and the calculation database, the one or more application server computers comprising one or more processors and electronic digital memory storing one or more sequences of instructions which, when executed by the one or more processors, cause the one or more processors to perform;

establishing computerized shared multi-tenant data storage in the production database, wherein the application server computer maintains a replay log that tracks changes for each tenant;

receiving a first request to perform a prior period adjustment (PPA) for a first tenant in which data values applicable to a closed time period earlier than an open current time period will be modified, wherein the closed time period was previously processed;

in response to the first request, identifying a working subset of data from first tenant data in the production database and copying the working subset of data to a calculation database that is separate from the production database, wherein the working subset comprises a minimum amount of data needed to perform accurate PPA according to a policy of the first tenant;

performing the PPA, using the working subset in the calculation database, by performing a plurality of same calculations in a same order as when the closed time period was previously processed to result in creating and storing a plurality of result data;

while performing the PPA;

receiving a second request that uses the first tenant data in the production database;

performing the second request using the first tenant data in the production database; and

updating the replay log based on the second request;

in response to a failure;

identifying a portion of the working subset related to the failure;

deleting the portion of the working subset related to the failure;

copying the portion of the working subset related to the failure from the production database to the calculation database;

after completing the PPA, transferring the plurality of results to the production database using the replay log;

sending a notification to one or more entities impacted by a plurality of changes that were made to the first tenant data during transferring.

9. The system of claim 8, wherein the replay log comprises stored digital data representing a plurality of events, each event comprising a definition.

10. The system of claim 9, wherein an event of the plurality of events comprises a data deletion event.

11. The system of claim 10, the one or more sequences of instructions, when executed by the one or more processors, further causing the one or more processors to perform:

performing the second request by modifying the first tenant data.

12. The system of claim 8, wherein the working subset of data comprises 4 periods of data that is read-only and cannot be written back to the production database.

13. The system of claim 8, wherein the notification identifies differences represented in the plurality of changes.

14. The system of claim 8, wherein the production database comprises two or more databases in different formats.