Architectural design for sell from stock application software

• US 20070156500A1
• Filed: 12/30/2005
• Published: 07/05/2007
• Est. Priority Date: 12/30/2005
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Picht, Michael, Bach, Thomas, Mayer, Uwe, Steinbach, Jochen, Liebich, Gunther, Adelmann, Stefan, Hirth, Jochen, Nitschke, Thomas, Hetzer, Stephan, Bock, Daniel, Franke, Stefan, Moosmann, Gerd, Marschall, Peer, Kaetker, Stefan, Poth, Andreas, Kenntner, Joachim, Reinke, Ralf, Zwerger, Wilhelm, Ude, Cordula, Nowotny, Dietmar, Merkel, Wilfried, Sudbrack, Andrea, Herrmann, Holger, Kasteleiner, Katja, Freund, Jens, Latocha, Peter, Emde, Martin, Yu, Tao, Podhajsky, Georg, Wickel, Jochen, Heger, Achim, Heun, Rainer
• Application Number:
  US11/322,611
• Publication Number:
  US 20070156500A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/0611 Request for offers or quotes

Abstract

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing sell from stock software useful to process quotations, capture orders, process delivery and invoice. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include an Outbound Delivery process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Customer Quote Processing process component, a Sales Order Processing process component, and a Sales Contract Processing process component.

Claims

1. A computer program product comprising application software encoded on a tangible machine-readable information carrier, the application software being structured as process components interacting with each other through service interfaces, the software comprising:

a plurality of process components, each of the process components being a package of software implementing a respective and distinct business process, the plurality of process components including;

an Outbound Delivery process component that combines tasks concerning outbound delivery processes and enables communication with a vendor and a process component within the Invoice deployment unit;

a Site Logistics Processing process component that supports all preparation and execution tasks concerning internal inventory movement in a warehouse type environment;

a Confirmation and Inventory process component that combines tasks required to confirm inventory changes and may provide services to maintain current stock, handling unit content, logistics operating unit content, and allocation content;

a Customer Requirement Processing process component that combines tasks required for processing customer requirements including receiving customer requirements, preparing them, and passing them on as supply planning requirements;

a Supply and Demand Matching process component that combines tasks necessary to ensure that sufficient material receipt elements exist to cover material demand while taking available capacity into account;

a Logistics Execution Control process component that controls and monitors the supply chain execution activities necessary for the fulfillment of an order;

a Customer Quote Processing process component that can make a legally binding offer to a customer for a delivery of goods or services according to fixed terms;

a Sales Order Processing process component that handles customers'"'"' requests for delivery of goods or services at a certain time;

a Sales Contract Processing process component that handles sales agreements that contain special negotiated conditions; and

a plurality of service interface operations, each service interface operation being implemented for a respective process component, the operations comprising inbound and outbound operations, the outbound operation for a first process component being operable to send a message to a second process component of the plurality of process components, the second process component having an inbound operation for receiving the message, the passing of messages between an inbound and an outbound operation defining a message-based pair-wise interaction between the respective process components of the respective operations, the pair-wise interactions between pairs of the process components including interactions between;

the Sales Order Processing process component and the Product Valuation Accounting process component;

the Logistics Execution Control process component and the Outbound Delivery Processing process component;

the Outbound Delivery Processing process component and the Customer Invoice Processing process component;

the Sales Order Processing process component and the Customer Invoice Processing process component;

the Logistics Execution Control process component and the Site Logistics process component;

the Sales Order Processing process component and the Customer Requirement Processing process component; and

the Customer Quote Processing process component and the Customer Requirement Processing process component.

2. The product of claim 1, wherein

the plurality of process components further includes:

an Accounting process component that records all relevant business transactions;

a Due Item Processing process component that manages all payables, receivables from service and supply and corresponding sales including a withholding tax;

a Payment Processing process component that handles all incoming and outgoing payments as well as represent the main database for a liquidity status; and

a Customer Invoice Processing process component that charges a customer for the delivery of goods or services; and

wherein

the pair-wise interactions between pairs of the process components further include interactions between;

the Payment Processing process component and the Accounting process component;

the Due Item Processing process component and the Accounting process component;

the Customer Invoice Processing process component and the Accounting process component;

the Sales Order Processing process component and the Accounting process component;

the Payment Processing process component and the Due Item Processing process component;

the Site Logistics Processing process component and the Accounting process component;

the Due Item Processing process component and the Payment Processing process component;

the Customer Invoice Processing process component and the Due Item Processing process component.

3. The product of claim 2, wherein:

each of the plurality of process components is assigned to exactly one deployment unit among multiple deployment units, and each deployment unit is deployable on a separate computer hardware platform independent of every other deployment unit; and

all interaction between a process component in one deployment unit and any other process component in any other deployment unit takes place through the respective service interfaces of the two process components.

4. The product of claim 3, wherein the deployment units comprise:

a Financial Accounting deployment unit that includes the Accounting process component;

a Logistics Execution deployment unit that includes the Outbound Delivery process 5 component, the Site Logistics Processing process component, and the Confirmation and Inventory process component;

a Supply Chain Control deployment unit that includes the Customer Requirement Processing process component, the Supply and Demand Matching process component, and the Logistics Execution Control process component;

a Due Item Management deployment unit that includes the Due Item Processing process component;

a Payment deployment unit that includes the Payment Processing process component;

a Customer Invoice deployment unit that includes the Customer Invoice Processing process component; and

a Customer Relationship Management deployment unit that includes the Customer Quote Processing process component, the Sales Order Processing process component, and the Sales Contract Processing process component.

5. The product of claim 1, wherein:

each of the process components includes one or more business objects; and

none of the business objects of any one of the process components interacts directly with any of the business objects included in any of the other process components.

6. The product of claim 5, wherein the business objects comprise a business process object.

7. The product of claim 5, wherein:

none of the business objects included in any one of the process components is included in any of the other process components.

8. The product of claim 1, further comprising:

a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, an inbound process agent being operable to receive a message from an inbound operation, an outbound process agent being operable to cause an outbound operation to send a message, each process agent being associated with exactly one process component.

9. The product of claim 8, wherein:

the inbound process agents comprise a first inbound process agent operable to start the execution of step requested in a first inbound message by creating or updating one or more business object instances.

10. The product of claim 8, wherein:

the outbound process agents comprise a first asynchronous outbound process agent that is called after a business object that is associated with the first outbound process agent changes.

11. The product of claim 1, wherein the operations comprise synchronous and asynchronous operations.

12. A system, comprising:

a computer system comprising one or more hardware platforms for executing a computer software application;

a plurality of process components, each of the process components being a package of software implementing a respective and distinct business process, the plurality of process components including;

an Outbound Delivery process component that combines tasks concerning outbound delivery processes and enables communication with a vendor and a process component within the Invoice deployment unit;

a Site Logistics Processing process component that supports all preparation and execution tasks concerning internal inventory movement in a warehouse type environment;

a Confirmation and Inventory process component that combines tasks required to confirm inventory changes and may provide services to maintain current stock, handling unit content, logistics operating unit content, and allocation content;

a Customer Requirement Processing process component that combines tasks required for processing customer requirements including receiving customer requirements, preparing them, and passing them on as supply planning requirements;

a Supply and Demand Matching process component that combines tasks necessary to ensure that sufficient material receipt elements exist to cover material demand while taking available capacity into account;

a Logistics Execution Control process component that controls and monitors the supply chain execution activities necessary for the fulfillment of an order;

a Customer Quote Processing process component that can make a legally binding offer to a customer for a delivery of goods or services according to fixed terms;

a Sales Order Processing process component that handles customers'"'"' requests for delivery of goods or services at a certain time;

a Sales Contract Processing process component that handles sales agreements that contain special negotiated conditions; and

a plurality of service interface operations, each service interface operation being implemented for a respective process component, the operations comprising inbound and outbound operations, the outbound operation for a first process component being operable to send a message to a second process component of the plurality of process components, the second process component having an inbound operation for receiving the message, the passing of messages between an inbound and an outbound operation defining a message-based pair-wise interaction between the respective process components of the respective operations, the pair-wise interactions between pairs of the process components including interactions between;

the Sales Order Processing process component and the Product Valuation Accounting process component;

the Logistics Execution Control process component and the Outbound Delivery Processing process component;

the Outbound Delivery Processing process component and the Customer Invoice Processing process component;

the Sales Order Processing process component and the Customer Invoice Processing process component;

the Logistics Execution Control process component and the Site Logistics process component;

the Sales Order Processing process component and the Customer Requirement Processing process component; and

the Customer Quote Processing process component and the Customer Requirement Processing process component.

13. The system of claim 12, wherein:

each of the process components includes one or more business objects; and

none of the business objects of any one of the process components interacts directly with any of the business objects included in any of the other process components.

14. The system of claim 12, wherein:

none of the business objects included in any one of the process components is included in any of the other process components.

15. The system of claim 12, wherein:

a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, an inbound process agent being operable to receive a message from an inbound operation, an outbound process agent being operable to cause an outbound operation to send a message, each process agent being associated with exactly one process component.

16. The system of claim 12, the system comprising multiple hardware platforms, wherein:

the Outbound Delivery process component, the Site Logistics Processing process component, and the Confirmation and Inventory process component are deployed on a first hardware platform;

the Customer Requirement Processing process component, the Supply and Demand Matching process component, and the Logistics Execution Control process component are deployed on a second hardware platform;

the Customer Quote Processing process component, the Sales Order Processing process component, and the Sales Contract Processing process component are deployed on a third hardware platform.

17. The system of claim 16, wherein each of the first through the third hardware platforms are distinct and separate from each other.

18. A method for developing a computer software application, comprising:

obtaining in a computer system digital data representing an architectural design for a set of processes implementing an end-to-end application process, the design specifying a process component for each process in the set of processes, the design specifying further specifying a set of process component interactions, wherein

the specified process components include

an Outbound Delivery process component that combines tasks concerning outbound delivery processes and enables communication with a vendor and a process component within the Invoice deployment unit;

a Site Logistics Processing process component that supports all preparation and execution tasks concerning internal inventory movement in a warehouse type environment;

a Confirmation and Inventory process component that combines tasks required to confirm inventory changes and may provide services to maintain current stock, handling unit content, logistics operating unit content, and allocation content;

a Customer Requirement Processing process component that combines tasks required for processing customer requirements including receiving customer requirements, preparing them, and passing them on as supply planning requirements;

a Supply and Demand Matching process component that combines tasks necessary to ensure that sufficient material receipt elements exist to cover material demand while taking available capacity into account;

a Logistics Execution Control process component that controls and monitors the supply chain execution activities necessary for the fulfillment of an order;

a Customer Quote Processing process component that can make a legally binding offer to a customer for a delivery of goods or services according to fixed terms;

a Sales Order Processing process component that handles customers'"'"' requests for delivery of goods or services at a certain time;

a Sales Contract Processing process component that handles sales agreements that contain special negotiated conditions; and

wherein

the process component interactions include interactions between

the Sales Order Processing process component and the Product Valuation Accounting process component;

the Logistics Execution Control process component and the Outbound Delivery Processing process component;

the Outbound Delivery Processing process component and the Customer Invoice Processing process component;

the Sales Order Processing process component and the Customer Invoice Processing process component;

the Logistics Execution Control process component and the Site Logistics process component;

the Sales Order Processing process component and the Customer Requirement Processing process component; and

the Customer Quote Processing process component and the Customer Requirement Processing process component; and

using the design including the specified process components and the specified process component interactions to develop a computer software application to perform the set of processes.

19. The method of claim 18, wherein:

each process in the set of processes is a business process transforming a defined business input into a defined business outcome.

20. The method of claim 19, wherein:

obtaining digital data representing the architectural design further comprises editing the design before using the design.