Object oriented technology framework for order processing

• US 5,987,423 A
• Filed: 03/28/1997
• Issued: 11/16/1999
• Est. Priority Date: 03/28/1997
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Berg, Alf Christian, Bohrer, Kathryn Ann, Brane, Thomas Karl Athos, Dahl, Tore Magnus, Michaelson, Tor, Nilsson, Anders Magnus, Odegaard, Helge, Pernbeck, Torbjorn Harald Osten, Arnold, Vincent Davis
• Primary Examiner(s): Trammell, James P.
• Assistant Examiner(s): Nguyen, Cuong H.
• Application Number:
  US08/828,934
• Time in Patent Office: 963 Days
• Field of Search: 705/14, 705/39, 705/8, 705/35, 705/30, 705/36, 707/103, 707/1, 707/3, 707/100, 707/203, 395/683, 395/682, 395/500, 395/673, 395/701-703, 395/705, 395/710, 395/677, 395/685, 395/200.33, 345/326, 345/335, 345/334, 345/340, 345/348, 345/356
• US Class Current: 705/14.23
• 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
• CPC Class Codes: G06Q 30/0222 During e-commerce, i.e. online transactions
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

An object oriented programming (OOP) framework includes an Order Management (OM) mechanism that tracks sales orders received and matches them to warehouse inventory, a Sales Order (SA) mechanism that processes sales orders, and a Purchase Order (PU) mechanism that processes purchase orders. The OM mechanism comprises a category of OOP classes that provide the primary interface between the framework classes and underlying business objects that provide accounting functions and warehouse management interfaces, and the SA and PU mechanisms comprise respective categories of OOP classes that keep track of sales orders received and purchase orders issued.

Claims

1. A computer data processing system comprising:

a central processing unit;

a user interface; and

a main memory having an operating system that supports an object oriented programming environment containing a framework that provides an extensible order management system for a Company that is specified by a data object, the framework including a Sales Order mechanism comprising a Sales Order category of cooperating objects that identify one or more sales orders and a Purchase Order category of cooperating objects that identify one or more purchase orders.

2. A computer data processing system as defined in claim 1, wherein:

each Sales Order object references object classes that identify products that are the subject of the sales order and identifies pricing and discounts applicable to the products; and

each Purchase Order object references object classes that identify products that are the subject of the purchase order and identify pricing and discounts applicable to the products.

3. A computer system as defined in claim 2, wherein the Sales Order mechanism further includes a Sales Contract Analysis Manager class object that selects Sales Contract class objects that specify contracts between the Company and customers for customer purchase of products and analyzes the selected Sales Contracts.

4. A computer system as defined in claim 3, wherein the Sales Order mechanism further includes a Sales Price and Discount Requestor class object that determines Sales Contract product pricing and discounts.

5. A computer system as defined in claim 2, wherein the Purchase Order mechanism further includes a Purchase Price and Discount Requestor class object that:

(a) analyzes Purchase Order class objects specifying agreements by the Company for the purchase of Products from Logistic Supplier class objects that identify suppliers of the Products; and

(b) determines pricing and discounts of Purchase Orders for Products.

6. A computer system as defined in claim 5, wherein the Purchase Order mechanism further includes a Supply Contract Retriever class object that maintains cooperating objects relating to a Supply Contract class object that specifies a supply contract between the Company and a Logistics Supplier entity that obligates the Company for the purchase of Products from the Logistics Supplier.

7. A computer system as defined in claim 6, wherein the Purchase Order mechanism further includes a Supply Contract Analysis Manager class object that performs analysis on Supply Contracts concerning unfulfilled terms of the contracts.

8. A computer system as defined in claim 5, wherein:

the Sales Order mechanism further includes a Sales Order Planned Detail class object specifying that a Sales Order for a Product will be filled by first generating a Back to Back Request Detail class object for the Product, such that the Back to Back Request Detail species either a Purchase Order for the Product, or a Stock Movement class object identifying the Product in current inventory, or a Unit of Work class object specifying a group of inventory components from which the Product will be assembled; and

the Purchase Order mechanism includes a Back to Back Order Manager class object that responds to the generated Back to Back Request Detail object by creating a Back to Back Order Detail class object that contains data identifying the back to back order.

9. A computer system as defined in claim 8, wherein the Back to Back Order Manager class object references a Logistics Supplier class object that specifies attributes of the Back to Back Request Detail class object.

10. A program product data storage device, tangibly embodying a program of machine-readable instructions executable by a computer system having an operating system that supports an object oriented programming environment, the program product comprising:

a recordable media;

a framework recorded on the recordable media, the framework having

(a) an Order Management mechanism comprising an Order abstract base class specifying data structures that identify orders received by a company from customer business partners for products,

(b) a Sales Order mechanism comprising a Sales Order category of data structures containing object classes that identify one or more sales orders received from customers of the company, each sales order referencing object classes such that the referenced objects identify products that are the subject of the sales order and identify pricing and discounts applicable to the products, and are abstracted from the Order class, and

(c) a Purchase Order mechanism comprising a Purchase Order category of data structures containing object classes that identify one or more purchase orders issued by the company, each purchase order referencing object classes such that the referenced objects identify products that are the subject of the purchase order and identify pricing and discounts applicable to the products, and are abstracted from the Order class.

40. A program product as defined in claim 10, wherein:

the Order Management mechanism further includes and a Contract abstract base class specifying data structures that identify contracts between the company and business partners for supply or purchase of products;

the Sales Order mechanism further includes a SA Sales Contract category of data structures that specify Sales Contract class objects that identify contracts between the Company and customers for customer purchase of products; and

the Purchase Order mechanism further includes a PU Supply Contract category of data structures that specify a Supply Contract class of objects that identify agreements between the company and a logistic supplier for purchase of supplies from the logistic supplier.

11. An object oriented extensible order management system framework for use in a computer system having an operating system that supports an object oriented programming environment and includes a memory in which object classes can be stored, the framework including a Sales Order mechanism comprising a Sales Order category of cooperating objects that identify one or more sales orders and a Purchase Order category of cooperating objects that identify one or more purchase orders.

12. A framework as defined in claim 11, wherein:

each Sales Order object references object classes that identify products that are the subject of the sales order and identifies pricing and discounts applicable to the products; and

each Purchase Order object references object classes that identify products that are the subject of the purchase order and identify pricing and discounts applicable to the products.

13. A framework as defined in claim 12, wherein the Sales Order mechanism further includes a Sales Contract Analysis Manager class object that selects Sales Contract class objects that specify contracts between the Company and customers for customer purchase of products and analyzes the selected Sales Contracts.

14. A framework as defined in claim 13, wherein the Sales Order mechanism further includes a Sales Contract Analysis Manager class object that selects Sales Contract class objects that specify contracts between the Company and customers for customer purchase of products and analyzes the selected Sales Contracts.

15. A framework as defined in claim 14, wherein the Sales Order mechanism further includes a Sales Price and Discount Requestor class object that determines Sales Contract product pricing and discounts.

16. A framework as defined in claim 12, wherein the Purchase Order mechanism further includes a Purchase Price and Discount Requestor class object that:

(a) analyzes Purchase Order class objects specifying agreements by the Company for the purchase of Products from Logistic Supplier class objects that identify suppliers of the Products; and

(b) determines pricing and discounts of Purchase Orders for Products.

17. A framework as defined in claim 16, wherein the Purchase Order mechanism further includes a Supply Contract Retriever class object that maintains data structures relating to a Supply Contract class object that specifies a supply contract between the Company and a Logistics Supplier entity.

18. A framework as defined in claim 17, wherein the Purchase Order mechanism further includes a Supply Contract Analysis Manager class object that performs analysis on Supply Contracts concerning unfulfilled terms of the contracts.

19. A framework as defined in claim 12, wherein:

the Sales Order mechanism further includes a Sales Order Planned Detail class object specifying that a Sales Order for a Product will be filled by first generating a Back to Back Request Detail class object for the Product, such that the Back to Back Request Detail species either a Purchase Order for the Product, or a Stock Movement class object identifying the Product in current inventory, or a Unit of Work class object specifying a group of inventory components from which the Product will be assembled; and

the Purchase Order mechanism includes a Back to Back Order Manager class Object that responds to the generated Back to Back Request Detail object by creating a Back to Back Order Detail class object that contains data identifying the back to back order.

20. A framework as defined in claim 19, wherein the Back to Back Order Manager class object references a Logistics Supplier class object that specifies attributes of the Back to Back Request Detail class object.

21. A program product data storage device, tangibly embodying a program of machine-readable instructions executable by a computer system having an operating system that supports an object oriented programming environment, the program product comprising:

a recordable media; and

a framework recorded on the recordable media, the framework including a Sales Order mechanism comprising a Sales Order category of cooperating objects that identify one or more sales orders and a Purchase Order category of cooperating objects that identify one or more purchase orders.

22. A program product as defined in claim 21, wherein:

each Sales Order object references object classes that identify products that are the subject of the sales order and identifies pricing and discounts applicable to the products; and

each Purchase Order object references object classes that identify products that are the subject of the purchase order and identify pricing and discounts applicable to the products.

23. A program product as defined in claim 22, wherein the Sales Order mechanism further includes a Sales Contract Analysis Manager class object that selects Sales Contract class objects that specify contracts between the Company and customers for customer purchase of products and analyzes the selected Sales Contracts.

24. A program product as defined in claim 23, wherein the Sales Order mechanism further includes a Sales Contract Analysis Manager class object that selects Sales Contract class objects that specify contracts between the Company and customers for customer purchase of products and analyzes the selected Sales Contracts.

25. A program product as defined in claim 24, wherein the Sales Order mechanism further includes a Sales Price and Discount Requestor class object that determines Sales Contract product pricing and discounts.

26. A program product as defined in claim 23, wherein the Purchase Order mechanism further includes a Purchase Price and Discount Requestor class object that:

(a) analyzes Purchase Order class objects specifying agreements by the Company for the purchase of Products from Logistic Supplier class objects that identify suppliers of the Products; and

(b) determines pricing and discounts of Purchase Orders for Products.

27. A program product as defined in claim 26, wherein the Purchase Order mechanism further includes a Supply Contract Retriever class object that maintains data structures relating to a Supply Contract class object that specifies a supply contract between the Company and a Logistics Supplier entity.

28. A program product as defined in claim 27, wherein the Purchase Order mechanism further includes a Supply Contract Analysis Manager class object that performs analysis on Supply Contracts concerning unfulfilled terms of the contracts.

29. A program product as defined in claim 23, wherein:

the Sales Order mechanism further includes a Sales Order Planned Detail class object specifying that a Sales Order for a Product will be filled by first generating a Back to Back Request Detail class object for the Product, such that the Back to Back Request Detail species either a Purchase Order for the Product, or a Stock Movement class object identifying the Product in current inventory, or a Unit of Work class object specifying a group of inventory components from which the Product will be assembled; and

the Purchase Order mechanism includes a Back to Back Order Manager class object that responds to the generated Back to Back Request Detail object by creating a Back to Back Order Detail class object that contains data identifying the back to back order.

30. A program product as defined in claim 29, wherein the Back to Back Order Manager class object references a Logistics Supplier class object that specifies attributes of the Back to Back Request Detail class object.

31. A method of distributing a program product, the method comprising the steps of:

establishing a connection between a first computer system and a second computer system; and

transmitting the program product from the first computer system to the second computer system, wherein the program product comprises an object oriented framework including;

a Sales Order mechanism comprising a Sales Order category of cooperating objects that identify one or more sales orders, and

a Purchase Order category of cooperating objects that identify one or more purchase orders.

32. A method as defined in claim 31, wherein:

each Sales Order object references object classes that identify products that are the subject of the sales order and identifies pricing and discounts applicable to the products; and

each Purchase Order object references object classes that identify products that are the subject of the purchase order and identify pricing and discounts applicable to the products.

33. A method as defined in claim 32, wherein the Sales Order mechanism further includes a Sales Contract Analysis Manager class object that selects Sales Contract class objects that specify contracts between the Company and customers for customer purchase of products and analyzes the selected Sales Contracts.

34. A method as defined in claim 32, wherein the Sales Order mechanism further includes a Sales Price and Discount Requestor class object that determines Sales Contract product pricing and discounts.

35. A method as defined in claim 31, wherein the Purchase Order mechanism further includes a Purchase Price and Discount Requestor class object that:

(a) analyzes Purchase Order class objects specifying agreements by the Company for the purchase of Products from Logistic Supplier class objects that identify suppliers of the Products; and

(b) determines pricing and discounts of Purchase Orders for Products.

36. A method as defined in claim 35, wherein the Purchase Order mechanism further includes a Supply Contract Retriever class object that maintains data structures relating to a Supply Contract class object that specifies a supply contract between the Company and a Logistics Supplier entity.

37. A method as defined in claim 31, wherein the Purchase Order mechanism further includes a Supply Contract Analysis Manager class object that performs analysis on Supply Contracts concerning unfulfilled terms of the contracts.

38. A method as defined in claim 32, wherein:

the Sales Order mechanism further includes a Sales Order Planned Detail class object specifying that a Sales Order for a Product will be filled by first generating a Back to Back Request Detail class object for the Product, such that the Back to Back Request Detail species either a Purchase Order for the Product, or a Stock Movement class object identifying the Product in current inventory, or a Unit of Work class object specifying a group of inventory components from which the Product will be assembled; and

the Purchase Order mechanism includes a Back to Back Order Manager class object that responds to the generated Back to Back Request Detail object by creating a Back to Back Order Detail class object that contains data identifying the back to back order.

39. A method as defined in claim 38, wherein the Back to Back Order Manager class object references a Logistics Supplier class object that specifies attributes of the Back to Back Request Detail class object.