Automatic user defaults

• US 20070226210A1
• Filed: 03/24/2006
• Published: 09/27/2007
• Est. Priority Date: 03/24/2006
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Walter, Wolfgang
• Application Number:
  US11/388,468
• Publication Number:
  US 20070226210A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing

Abstract

A method and system for maintaining and supplying user defaults during transactions. Upon initiation of a transaction, a determination is made if any mandatory values are not maintained or if an explicit request is received. Values supplied in the window are verified to determine that they satisfy requirements of the expected values. If the verification fails, the transaction is prevented from continuing. Otherwise, the supplied values are maintained in persistent storage. Those values are then made available elsewhere in the transaction without requiring reentry.

Claims

1. A method comprising:

determining if a mandatory value is maintained in a persistent store when a transaction begins;

generating a window to accept the mandatory value only if not retained in the persistent store or an explicit request is received;

verifying that a value provided satisfies a requirement for the mandatory value;

preventing the continuation of the transaction if the requirement is not met;

maintaining the value in the persistent store if the requirement is met; and

making the value available at another point in the transaction.

2. The method of claim 1 further comprising:

using the value in a second transaction type different from the transaction.

3. The method of claim 1 wherein verifying comprises:

confirming the value is semantically correct.

4. The method of claim 1 wherein checking comprises:

comparing the value with at least a subset of valid values until a match is found.

5. The method of claim 4 wherein verifying further comprises:

rejecting the value unless a match is found.

6. The method of claim 1 wherein making the value available comprises:

permitting user access to the value in the database at any point during the transaction.

7. The method of claim 6 wherein permitting comprises:

automatically populating a field of a user interface display that corresponds to the value.

8. The method of claim 1 wherein preventing comprises:

maintaining the pop up as a focal window until the value is provided or the transaction is canceled.

9. The method of claim 1 further comprising:

displaying a pop up window to accept a changed value in response to a triggering event; and

replacing the value maintained in the database with the changed value.

10. A system comprising:

a persistent storage unit;

a user default module to ensure a value for at least one value is maintained in the persistent storage unit, the user default module having a pop up generation module and verification module; and

application to conduct a transaction using the value.

11. The system of claim 10 further comprising:

a graphical user interface (GUI) responsive to the pop up module to display modifiable fields corresponding to the at least one value.

12. The system of claim 10 wherein the user default module comprises:

a listener to invoke the pop up generation module responsive to an external event.

13. The system of claim 10 wherein the verification module comprises:

a comparator to compare at least a subset valid values with a value provided from the persistent storage.

14. The system of claim 10 further comprising:

a database table in the persistent storage to be populated with data provided to the user default module and to be indexed by a user identifier.

15. A machine-accessible medium containing instructions that when executed cause a machine to:

determine if a mandatory value is maintained in a persistent store when a transaction begins;

generate a window to accept the mandatory value if not retained in the persistent store;

verify that a value provided satisfies a requirement for the mandatory value;

prevent the continuation of the transaction if the requirement is not met;

maintain the value in the persistent store if the requirement is met; and

make the value available at another point in the transaction.

16. The machine accessible median of claim 15, further comprising instructions causing the machine to:

use the value in a second transaction type different from the transaction.

17. The machine accessible median of claim 15, wherein the instructions causing the machine to verify cause the machine to:

confirm the value with at least a subset of valid values until a match is found.

18. The machine accessible median of claim 17, wherein the instructions causing the machine to check further cause the machine to:

reject the value unless a match is found.

19. The machine accessible median of claim 15, wherein the instructions causing the machine to make the value available cause the machine to:

permit user access to the value in the database at any point during the transaction.

20. The machine accessible median of claim 19, wherein the instructions causing the machine to permit user access cause the machine to:

automatically populate a field of a user interface display that corresponds to the value.

21. The machine accessible median of claim 15, further comprising instructions causing the machine to:

display a pop up window to accept a change value in response to a triggering event; and

replace the value maintained in the database with the change value.