Accelerated system and method for providing data correction

1. A computer-implemented method for processing data change requests in a software production environment using an integrated platform that includes at least one processor, a database, a memory, and an interface, the method comprising the following steps:

receiving, by the integrated platform, one or more requests for one or more data changes to data stored in the database, the one or more requests being received from a requestor using the interface;

receiving, by the integrated platform, information associated with the requestor and an approver;

determining, by the processor, an identity of the requestor and an identity of an approver based on the information;

in response to the requestor and the approver having the same identity, automatically denying the one or more requests;

in response to the requestor and the approver not having the same identity:

executing, by the processor, the request(s) in the database in a rollback mode, wherein each of the individual data changes in the request(s) are combined, in the order they were received, into an integrated change execution package that is executed as an atomic transaction comprising all of the changes, except that if the requestor changes data within a parent document that includes data in a related child document, the change execution package processes the data change in the child document as a false execution before processing the data change in the parent document;

generating, by the processor, a snapshot of the executed request(s), wherein the snapshot includes values of the data before and after execution of the request(s) and any errors in the SQL statement(s) corresponding to the individual data changes in the integrated change execution package;

transmitting, on the interface, the snapshot to the approver; and

in response to an approval of the snapshot on the interface from the approver, executing, by the processor, the request(s) in the database in a commit mode.

2. The computer-implemented method of claim 1 , further comprising:

generating authentication data regarding the requestor and approver;

storing the authentication data and the snapshot in an audit log.

3. The computer-implemented method of claim 2 , further comprising:

creating an ANSI standard SQL statement for each of the data changes.

4. The computer-implemented method of claim 3 , wherein

the data changes correspond to one or more data values,

the data is of a type comprising a float, a string, an integer, binary data, a date field, and a date and time field, and

a different ANSI standard SQL statement is created for each type.

5. The computer-implemented method of claim 1 , further comprising:

performing error checking by applying one or more rules to the requests; and

storing a result of the error checking in an audit log.

6. The computer-implemented method of claim 1 , wherein the data values correspond to mortgage information.

7. The computer-implemented method of claim 1 , wherein the data is located in more than one related document and the snapshot includes a pre-execution and post-execution view of the requested data changes.

8. The computer-implemented method of claim 1 , wherein the one or more requests are one or more ANSI standard SQL statements received from the requestor.

9. A system for processing data change requests in a software production environment, the system comprising:

an integrated platform comprising one or more hardware processors, a database, a memory, and an interface, the memory storing instructions for execution by the one or more hardware processors, wherein the one or more hardware processors are configured by the instructions to:

receive, by the integrated platform, one or more requests for one or more data changes to data stored in the database, the one or more requests being received from a requestor using the interface;

receive, by the integrated platform, information associated with the requestor and an approver;

determine, by the processor, an identity of the requestor and an identity of an approver based on the information;

in response to the requestor and the approver having the same identity, automatically deny the one or more requests;

in response to the requestor and the approver not having the same identity:

execute, by the processor, the request(s) in the database in a rollback mode, wherein each of the individual data changes in the request(s) are combined, in the order they were received, into an integrated change execution package that is executed as an atomic transaction comprising all of the changes, except that if the requestor changes data within a parent document that includes data in a related child document, the change execution package processes the data change in the child document as a false execution before processing the data change in the parent document;

generate, by the processor, a snapshot of the executed request(s), wherein the snapshot includes values of the data before and after execution of the request(s) and any errors in the SQL statement(s) corresponding to the individual data changes in the integrated change execution package;

transmit, on the interface, the snapshot to the approver; and

in response to an approval of the snapshot on the interface from the approver, execute, by the processor, the request(s) in the database in a commit mode.

10. The system of claim 9 , wherein the one or more hardware processors are further configured to:

generate authentication data regarding the requestor and approver;

store the authentication data and the snapshot in an audit log.

11. The system of claim 10 , wherein the one or more hardware processors are further configured to create an ANSI standard SQL statement for each of the data changes.

12. The system of claim 11 , wherein

the data changes correspond to one or more data values,

the data is of a type comprising a float, a string, an integer, binary data, a date field and a date and time field, and

a different ANSI standard SQL statement is created for each type.

13. The system of claim 9 , wherein the one or more hardware processors are further configured to:

perform error checking by applying one or more rules to the requests; and

store a result of the error checking in an audit log.

14. The system of claim 9 , wherein the data values correspond to mortgage information.

15. The system of claim 9 , wherein the data is located in more than one related document and the snapshot includes a pre-execution and post-execution view of the requested data changes.

16. The system of claim 9 , wherein the one or more requests are one or more ANSI standard SQL statements received from the requestor.

17. A non-transitory computer-readable storage medium including program instructions for performing, when executed by an integrated platform that includes a processor, a database, a memory, and an interface, a method for processing data change requests in a software production environment, the method comprising:

receiving, by the integrated platform, one or more requests for one or more data changes to data stored in the database, the one or more requests being received from a requestor using the interface;

receiving, by the integrated platform, information associated with the requestor and an approver;

determining, by the processor, an identity of the requestor and an identity of an approver based on the information;

in response to the requestor and the approver having the same identity, automatically denying the one or more requests;

in response to the requestor and the approver not having the same identity:

executing, by the processor, the request(s) in the database in a rollback mode, wherein each of the individual data changes in the request(s) are combined, in the order they were received, into an integrated change execution package that is executed as an atomic transaction comprising all of the changes, except that if the requestor changes data within a parent document that includes data in a related child document, the change execution package processes the data change in the child document as a false execution before processing the data change in the parent document;

generating, by the processor, a snapshot of the executed request(s), wherein the snapshot includes values of the data before and after execution of the request(s) and any errors in the SQL statement(s) corresponding to the individual data changes in the integrated change execution package;

transmitting, on the interface, the snapshot to the approver; and

in response to an approval of the snapshot on the interface from the approver, executing, by the processor, the request(s) in the database in a commit mode.

18. The computer-readable medium of claim 17 , further comprising:

generating authentication data regarding the requestor and approver;

storing the authentication data and the snapshot in an audit log.

19. The computer-readable medium of claim 18 , further comprising:

creating an ANSI standard SQL statement for each of the data changes.

20. The computer-readable medium of claim 19 , wherein

the data changes correspond to one or more data values,

the data is of a type comprising a float, a string, an integer, binary data, a date field, and a date and time field, and

a different ANSI standard SQL statement is created for each type.

21. The computer-readable medium of claim 17 , further comprising:

performing error checking by applying one or more rules to the requests; and

storing a result of the error checking in an audit log.

22. The computer-readable medium of claim 17 , wherein the data values correspond to mortgage information.

23. The computer-readable medium of claim 17 , wherein the data is located in more than one related document and the snapshot includes a pre-execution and post-execution view of the requested data changes.

24. The computer-readable medium of claim 17 , wherein the one or more requests are one or more ANSI standard SQL statements received from the requestor.