Administration of planning file entries in planning systems with concurrent transactions

• US 7,822,792 B2
• Filed: 12/15/2006
• Issued: 10/26/2010
• Est. Priority Date: 12/15/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Wiethoff, Andreas, Reusch, Hans-Georg, Soehner, Volkmar A.
• Primary Examiner(s): Jalil; Neveen Abel
• Assistant Examiner(s): KINSAUL, DANIEL W
• Application Number:
  US11/640,159
• Publication Number:
  US 20080147666A1
• Time in Patent Office: 1,411 Days
• Field of Search: 707/8, 705/1, 705/7, 705/8, 718/102
• US Class Current: 707/826
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

After a transaction modifying a planning area in a planning system is initiated, it is determined whether there are any change objects in a consistent view of the transaction that are associated with the planning area. If there is a single change object associated with the planning area, then, the logical state of such change object is read. Alternatively, if there is more than one change object for the planning area, it is determined that the planning area must be replanned. Related apparatus, systems, methods, and articles are also described.

Claims

1. An article comprising a non-transitory machine-readable storage medium embodying instructions that when performed by one or more machines result in operations comprising:

initiating a first transaction modifying data in a first plurality of planning areas of a planning system, the planning system defining functions and processes that review requirements and defined parameters to suggest new operating, material, and capacity plans and modifications thereto;

generating a change object for each of the plurality of planning areas, each change object including a logical state identifying whether the associated planning area requires replanning, the change objects being generated before the first transaction is committed;

initiating a second transaction modifying a second plurality of planning areas of the planning system;

determining whether there are pre-existing change objects in a consistent view of the second transaction that are associated with each of the second plurality of planning areas, the consistent view providing that each session has a view on the underlying data given by a committed state of the underlying data at a time when a current transaction associated with the planning area has started;

reading a logical state from a single change object if there is only one pre-existing change object associated with those planning areas in the second plurality of planning areas in order to determine whether each such planning area must be replanned;

or

determining that planning areas must be replanned if there is more one than pre-existing change object associated with such planning areas; and

completing the second transaction.

2. An article as in claim 1, wherein the operations further comprise:

generating an updated change object identifying a logical state of the planning area.

3. An article as in claim 2, wherein the updated change object is generated before the initiated second transaction has been committed.

4. An article as in claim 2, wherein the operations further comprise:

deleting any change objects for the planning area created prior to the consistent view of the initiated second transaction.

5. An article as in claim 2, wherein the logical state of the generated updated change object comprises a flag, and wherein a first state of the flag indicates that the planning area does not require replanning, and a second state of the flag indicates that replanning is required for the planning area.

6. An article as in claim 1, wherein the operations further comprise:

determining that replanning is not necessary if the there is no change object visible for the planning area.

7. A computer-implemented method comprising:

initiating a first transaction modifying data in a first plurality of planning areas of a planning system, the planning system defining functions and processes that review requirements and defined parameters to suggest new operating, material, and capacity plans and modifications thereto;

generating a change object for each of the plurality of planning areas, each change object including a logical state identifying whether the associated planning area requires replanning, the change objects being generated before the first transaction is committed;

initiating a second transaction modifying a second plurality of planning areas of the planning system;

determining whether there are pre-existing change objects in a consistent view of the second transaction that are associated with each of the second plurality of planning areas, the consistent view providing that each session has a view on the underlying data given by a committed state of the underlying data at a time when a current transaction associated with the planning area has started;

reading a logical state from a single change object if there is only one pre-existing change object associated with those planning areas in the second plurality of planning areas in order to determine whether each such planning area must be replanned;

or

determining that planning areas must be replanned if there is more one than pre-existing change object associated with such planning areas; and

completing the second transaction.

8. A method as in claim 7, further comprising:

generating an updated change object identifying a logical state of the planning area.

9. A method as in claim 8, wherein the updated change object is generated before the initiated second transaction has been committed.

10. A method as in claim 8, further comprising:

deleting any change objects for the planning area created prior to the consistent view of the initiated second transaction.

11. A method as in claim 8, wherein the logical state of the generated updated change object comprises a flag, and wherein a first state of the flag indicates that the planning area does not require replanning, and a second state of the flag indicates that replanning is required for the planning area.

12. A method as in claim 7, further comprising:

determining that replanning is not necessary if the there is no change object visible for the planning area.

13. A computer system comprising:

a processor; and

memory coupled to the processor encoding one or more programs causing the processor to perform operations comprising;

initiating a first transaction modifying data in a first plurality of planning areas of a planning system, the planning system defining functions and processes that review requirements and defined parameters to suggest new operating, material, and capacity plans and modifications thereto;

generating a change object for each of the plurality of planning areas, each change object including a logical state identifying whether the associated planning area requires replanning, the change objects being generated before the first transaction is committed;

initiating a second transaction modifying a second plurality of planning areas of the planning system;

determining whether there are pre-existing change objects in a consistent view of the second transaction that are associated with each of the second plurality of planning areas, the consistent view providing that each session has a view on the underlying data given by a committed state of the underlying data at a time when a current transaction associated with the planning area has started;

reading a logical state from a single change object if there is only one pre-existing change object associated with those planning areas in the second plurality of planning areas in order to determine whether each such planning area must be replanned;

or

determining that planning areas must be replanned if there is more one than pre-existing change object associated with such planning areas; and

completing the second transaction.

14. A system as in claim 13, wherein the operations further comprise:

generating an updated change object identifying a logical state of the planning area.

15. A system as in claim 14, wherein the updated change object is generated before the initiated second transaction has been committed.

16. A system as in claim 14, wherein the operations further comprise:

deleting any change objects for the planning area created prior to the consistent view of the initiated second transaction.

17. A system as in claim 14, wherein the logical state of the generated updated change object comprises a flag, and wherein a first state of the flag indicates that the planning area does not require replanning, and a second state of the flag indicates that replanning is required for the planning area.

18. A system as in claim 13, wherein the operations further comprise:

determining that replanning is not necessary if the there is no change object visible for the planning area.