Patent Grant
9852428
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present invention relates to enterprise software applications in general and, more particularly, to tools for configuring enterprise software applications and/or for defining data structures for enterprise software applications.
Many businesses (and other organizations) use software applications (and/or suites of such applications) to organize their business affairs, track business performance, and/or the like. Such applications (referred to herein as “enterprise applications”) are often quite complex, relying on numerous database tables to store and manage data for virtually every aspect of an organization's business. Merely by way of example, enterprise applications can include supply chain management (“SCM”) applications that manage raw materials, work-in-process and/or finished products, coordinate with suppliers, and/or the like; customer relations management (“CRM”) applications that are used to track, store and/or manage customer information; financial applications that track and/or analyze the financial performance of the organization; human resources applications that provide management of the human resources functions of the organization; and/or the like. In some cases, these enterprise applications are standalone applications; in other cases, a single enterprise application (and/or suite of applications) might provide some or all such functionality. One type of enterprise application is referred to enterprise resource planning (“ERP”) software. Examples of enterprise applications include, without limitation, JD Edwards Enterpriseone™, PeopleSoft Enterprise™ applications, and the Oracle eBusiness Suite™, all available from Oracle Corporation.
For a variety of reasons, a modern business (or other organization) may be organized into several business units. (A “business unit,” as that term is used herein, means any group within a business that is viewed as a discrete entity for one or more purposes, such as for operational/functional distinctions, for financial responsibility, for managerial reporting, for legal reporting, and/or the like.) In an aspect, especially from the perspective of an enterprise application, a business unit might perform a variety of business functions (which can be represented by functions within the enterprise application, such as a payroll function, an accounts payable function, a sales order function, etc.).
As enterprises have grown more accustomed to managing their affairs with enterprise applications, process efficiencies and greater internal controls have lead many large enterprises to establish shared service centers to support a number of internal clients. For example, the payroll function of a particular business unit might provide such services not only for that business unit, but for other units within the enterprise as well. Enterprise applications, however, generally have not been designed to be used by one business unit of an enterprise while servicing many others. In many cases, the enterprise application could not be deployed in a manner that would support such a configuration.
Moreover, even if the software could be deployed to support multiple internal clients from a single business unit, the setup of each business unit was independent. Enterprise applications failed to provide any expression of what parts of the business perform what functions on behalf whom. Thus, even where was possible to associate a user with a number of clients (e.g., other business units), the business unit for which the user worked was invisible in the assignment. This lack of structure also has made it difficult or impossible to implement or document administrative controls (such as service level agreements, SAS 70 internal control audits, and the like).
Hence, there is a need for more robust tools for identifying relationships between the various components of organizations, and/or for configuring enterprise applications to account for these relationships.
A set of embodiments provides tools for configuring enterprise applications. In an aspect of certain embodiments, an enterprise application can be configured to account for relationships between multiple business units within an enterprise, including without limitation relationships between the business functions provided by various business units. Merely by way of example, a first business unit might be a client of a second business unit with respect to a particular business function, such that the second business unit provides the business function for the first business unit. As but another example, a first business function in a first business unit might be related to a second business function in a second business unit, such that a transaction processed by the first business function subsequently should be processed by the second business function.
In one aspect, tools in accordance with various embodiments provide a framework for identifying and/or defining relationships between business units. In another aspect, the tools provide a user interface for a user to identify one or more business units and/or business functions and defines a relationship between them. Based on this definition, the tools of the invention may configure an enterprise application to account for this relationship. Merely by way of example, in one aspect, the tools provided by various embodiments might store, in a database used by the enterprise application, a set of data representing the relationship defined by the user. Advantageously, this configuration allows the enterprise application to determine how certain transactions should be processed. Merely by way of example, if a one business unit is a defined as a client of a second business unit with respect to a particular function, when the first business unit receives (or generates, etc.) a transaction that particular function, the transaction can be automatically provided to the second business unit for processing. As described in detail below, various embodiments provide other and/or additional functionality.
The tools provided by various embodiments, without limitation, methods, systems, and/or software products. Mainly by way of example, a method might comprise one or more procedures, any or all of which are executed by a computer system. Correspondingly, a computer system might be configured with instructions to perform one or more procedures in accordance with methods provided by various embodiments. Similarly, a computer program might comprise a set of instructions that are executable by a computer system (and/or a processor therein) to perform such operations. In many cases, such software programs are encoded on physical and/or tangible computer readable media (such as, merely by way of example, optical media, magnetic media, and/or the like). In a particular embodiment, the set of instructions might be incorporated within an enterprise application and/or might be provided as a separate computer program that can be used to configure the enterprise application.
For example, one set of embodiments provides computer programs (which may be stored on computer readable storage media). In one set of embodiments, a computer readable storage medium might have encoded thereon a computer program comprising a set of instructions executable by a computer system to perform one or more operations. The computer program might comprise a framework for defining a set of relationships between a plurality of business units. In an aspect, the framework might comprise a business unit definition that is used to define representations of a plurality of business units, a business function definition that is used to define one or more business functions, and/or a relationship definition tool that is used to define a relationship between one or more business units and one or more business functions.
The computer program, in some embodiments, further comprises a user interface to receive input from a user and/or display output to a user. Merely by way of example, the user interface might receive first input for selecting a first representation of a first business unit, second input for selecting a second representation of a second business unit, third input for selecting a business function, and/or fourth input for defining a relationship among the first business unit, the second business unit, and the business function. In addition, the computer program might also comprise a configuration engine for configuring an enterprise application to reflect the defined relationship among the first business unit, the second business unit and the business function.
Another set of embodiments provides methods, including without limitation methods for configuring an enterprise application. An exemplary method comprises providing a user interface for a user to define a relationship between a plurality of business units and/or receiving, e.g., via the user interface, an identification of a first business unit and/or a second business unit. The method might further comprise receiving, again perhaps via the user interface, a selection of a first business function of the first business unit and/or a definition of a business function agency relationship between the first business unit and the second business unit. In an aspect, the business function agency relationship pertains to the first business function. In some cases, the method further comprises storing, e.g., in a database, a set of data representing the business function agency relationship between the first business unit and the second business unit.
Another exemplary method for configuring an enterprise application comprises providing a framework for defining a set of relationships between a plurality of business units, the framework comprising a business unit definition that is used to define representations of a plurality of business units, a business function definition that is used to define one or more business functions, and a relationship definition that is used to define a relationship between one or more business units and one or more business functions. This framework, in some cases, is provided in a computer system.
The method, in an aspect, further comprises providing, e.g., from the computer system, a user interface for a user to define a relationship between a plurality of business units, and receiving, via the user interface, an identification of a first business unit and/or a second business unit, as well as a selection of a first business function of the first business unit and/or a definition of a business function agency relationship between the first business unit and the second business unit. In some cases, the method further includes receiving a definition of a control to be implemented with respect to the defined business function agency relationship.
The method might further comprise configuring an enterprise application to reflect the business function agency relationship between the first business unit, the second business unit, and the first business function. Configuring the enterprise application, in an aspect, may comprise storing, e.g., in a database, a set of data representing the business function agency relationship.
Another set of embodiments provides computer systems. An exemplary computer system might comprise a database for storing data used by an enterprise application, one or more processors in communication with the database, and/or one or more computer readable storage media in communication with the one or more processors. In an aspect, the one or more computer readable storage media have encoded thereon a computer program comprising a set of instructions that are executable by the one or more processors to perform one or more operations. Merely by way of example, the set of instructions may be executable to perform one or more methods provided by various embodiments.
A further understanding of the nature and advantages of various embodiments may be realized by reference to the remaining portions of the specification and the drawings wherein like reference numerals are used throughout the several drawings to refer to similar components. In some instances, a sublabel is associated with a reference numeral to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sublabel, it is intended to refer to all such multiple similar components.
While various aspects of certain embodiments have been summarized above, the following detailed description illustrates exemplary embodiments in further detail to enable one of skill in the art to practice the described embodiments. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the described embodiments. It will be apparent, however, to one skilled in the art that the other embodiments may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form. Several embodiments are described below, and while various features are ascribed to different embodiments, it should be appreciated that the features described with respect to one embodiment may be incorporated with another embodiments as well. By the same token, however, no single feature or features of any described embodiment should be considered essential to all embodiments, as other embodiments of the invention may lack such features.
In a general sense, certain embodiments provide tools that can be used, for example, within an enterprise application (and/or in conjunction with an enterprise application) to configure the enterprise application to properly account for relationships between various business units within an organization. (As used herein, an “organization,” also referred to as an “enterprise,” refers to any concern that is organized for a particular purpose. In many cases, an organization will be a for-profit or nonprofit corporation, or a collection of related corporations. An organization, of course, might comprise one or more unincorporated business forms as well.) In an aspect, the tools can be used to allow a user to input information about such relationships.
In another aspect, these tools can be used to apply this information in configuring, customizing, and/or implementing the enterprise application for use within the organization. In particular, some embodiments are used to configure the data structures used by the enterprise application to account for the organization's structural hierarchy. Merely by way of example, in a set of embodiments, the tools are designed to define a data structure used by the enterprise application (which might comprise generating and/or modifying a set of one or more database tables used by the enterprise application, and/or storing those tables on a storage medium) to facilitate and/or optimize the use of the enterprise application with the specific characteristics of the organization.
One set of embodiments provides a software program, referred to herein as a “configurator.”
In some cases, the configurator 105 might include the functionality of the configurator described in commonly-assigned, copending U.S. patent application Ser. No. 12/192,418, filed on Aug. 15, 2008 by Bhatia et al. and entitled “Enterprise Structure Configurator” (the “Bhatia Application”), already incorporated herein by reference. Merely by way of example, in addition the functionality described herein, the configurator 105 might be enabled to define the structural hierarchy of an enterprise, as described in the Bhatia Application.
In many cases, the enterprise application 110 uses a database 115 to store data generated, used and/or maintained by the enterprise application 110. The database 115 typically is a relational database comprising one or more database tables 120 configured to store the data (e.g., as records, etc.). The configuration of these tables 120 can have a significant impact on the performance, features and/or usability of the enterprise application. Accordingly, in an aspect, the configurator 105 is designed to define and/or configure these tables 120, based, in part, on information about the business units in the enterprise, the business functions performed by the business units, and/or their relationships to one another.
In an exemplary embodiment, the configurator 105 comprises a user interface component 125 that is designed to interact with a user 130 (e.g., via a computer operated by the user). It should be appreciated that the configurator 105 (and, by extension, the user interface component 125) might be implemented in a variety of ways. Merely by way of example, the configurator 105 might be implemented as a web-based application, and the user interface component 125, accordingly, might be configured to provide interaction via a set of web pages (e.g., pages served by a web server, which might be integrated with, and/or separate from the configurator 105). In other embodiments, the configurator 105 might be configured to operate in a client-server configuration, or as a standalone application on a user computer (perhaps with facilities for communicating with the enterprise application 110 and/or database 115). Hence, the user interface component 120 might be configured to generate display screens (e.g., using tools provided by the operating system of the computer on which the configurator runs 105) for interaction with the user 125. One skilled in the art should appreciate, based on this disclosure, that there are many mechanisms for presenting a user interface to a user, and any of such mechanisms may be used in accordance with different embodiments of the invention.
In some embodiments, the configurator 105 also comprises a configuration engine 135, which is configured to communicate with the enterprise application 110 and/or database 115 to configure the enterprise application, e.g., to account for the relationships defined by the user via the user interface component 120 (as described in further detail below, for example). Merely by way of example, the data configuration engine 135 might be configured to modify and/or generate (e.g., create) one or more of the tables 120 and/or to create records in such tables 120 to reflect relationships among business entities within an enterprise (i.e., to configure the enterprise application to recognize the relationships and operate in accordance with the relationships, as described in further detail below). As another example, the configuration engine 135 might be configured to set one or more configuration parameters within the enterprise application itself 110 to reflect the relationships.
In an aspect, the configuration engine 135 may be configured to receive, from the user interface component 125, input provided by the user 130, and/or to configure the enterprise application 110 based, at least in part, on this input. As an example, in some cases, the enterprise application might be designed to maintain a table 120 (or set of tables) in the database 115 for each business unit in an organization. If the user indicates (e.g., via the user interface component 125) that a first business unit provides a business function for a second business unit, the configuration engine 135 might create two tables 120 (or two sets of tables, if appropriate) in the database 115. As another example, the enterprise application 110 might rely on a set of records in a particular table 120 in the database to represent relationships between various entities in an organization, and the configuration engine 135 might be configured to create appropriate records to reflect the relationships between two more business units and/or business function, based (at least in part) on input from the user. (It should be noted that these examples are provided for illustration only and should not be considered limiting with respect to the functionality of the data structure generator 135.)
In some cases, the configuration engine 135 is equipped with any necessary communication facilities and/or protocols for communicating with the database 115 and/or the enterprise application. Merely by way of example, the configuration engine 135 might be configured to generate structured query language (“SQL”) commands and transmit those commands to the database (using, for example, the SQL.net transport protocol, Oracle Networking Services, etc.) for execution. As another example, the data structure generator 135 might be configured to access an application programming interface (“API”) for the enterprise application 110 and/or database 115 to provide commands to configure the enterprise application 110. Any of a variety of communication protocols, including without limitation protocols within the TCP/IP suite, might be used by the configurator 105 (and/or components thereof) to communicate with users, other system components, and/or the like.
As noted above, in accordance with certain embodiments, various business units and/or business functions in an enterprise have relationships that can be represented within an enterprise application. As noted above, the term “business unit” in this document means any group within a business that is viewed as a discrete entity for one or more purposes, such as for operational/functional distinctions, for financial responsibility, for managerial reporting, for legal reporting, and/or the like. As used herein, the term “business function” refers to any function performed by a business unit and/or a discrete operational area of a business unit. A business function generally will comprise a collection of one more (typically related) services and/or tasks that are performed by the business unit (and/or, more specifically, by the business function). For example, an accounts receivable function might perform invoicing/billing tasks, funds collection/bookkeeping tasks, and/or the like—such tasks can also be considered services, which can be utilized (as described in further detail below) by different business units.
While such tasks are typically performed within a specific business function, in a more general sense, the business unit of which the business function is a part performs the tasks. Hence, this disclosure refers to a business function as performing a task or service, and also refers to a business unit as performing a business function (i.e., performing one or more tasks within the business function), often on behalf of another business unit, or in conjunction with the performance of a related business function by a different business unit. Within an enterprise, multiple business units might perform the same business function, on behalf of themselves or other business units.
A business function (and, in some cases, more specifically, the tasks or services provided by the business function) are often performed on, or with respect to, one or more transactions. Merely by way of example, in many cases, a business function (or task thereof) will generate a transaction. In other cases, the business function (or task thereof) will operate on an existing transaction (e.g., a transaction received from another business function). Collectively, these operations are described herein as “processing” a transaction; processing a transaction generally comprises any of a variety of operations that are performed with respect to the transaction, and the nature of the processing generally will depend on the type of transaction, as well as the business function and/or task that processes the transaction.
The term “transaction” is used broadly herein to refer to any unit of work that is to be performed by, or within, an enterprise application, and, in a particular aspect, by or on behalf of a particular business unit and/or business function. A transaction, therefore, might involve one or more database transactions (e.g., in a database that stores data used by the enterprise application), a request for a service to be performed, the performance of such a service, the generation and/or modification of data, etc.
To illustrate these concepts,
The arrangement 200 comprises three business units: a Central Accounting business unit 205a, a US Operations business unit 205b, and a Europe Operations business unit 205c. In the illustrated embodiment, the Central Accounting business unit 205a performs three business functions, an Accounts Payable function 210a, an Accounts Receivable function 210b, and a Payroll Function 210c. The US Operations business unit 205b performs two business functions, a Supply Chain Management function 215a and a Human Resources function 215b. The Europe Operations function 205c does not perform any business functions on its own. (It should be noted that these examples are necessarily incomplete, for brevity and ease of description; in implementation, it is likely that each business unit would perform several business functions. Hence, the business units and functions illustrated by
In an aspect, two business units (or business functions) can be thought of as having a “business function agency relationship,” in which one business unit (or a business function performed by that business unit) essentially acts as an agent or service provider for another business unit and/or function. The exemplary arrangement 200 illustrates two such agency relationships, although others are possible as well.
The first type of agency relationship illustrated by
Another type of business function agency relationship is referred to herein as a “related business function” relationship. In this type of relationship, a business function in one business unit is related to a business function in another unit. For example, in some cases, after a first business function processes a transaction, a second business function (in the same or a different business unit) may be required to further process the transaction.
To illustrate a related business function relationship, consider the following example: In the arrangement 200 of
Tools in accordance with various embodiments allow such relationships (and others) to be captured by an implementer of an enterprise application, so that the enterprise application accounts for these relationships (for example, by routing transactions appropriately within the business application (e.g., to appropriate sub-applications, users, etc.)). In other words, the enterprise application can be configured to more closely model the actual business processes performed by the various business units within an enterprise.
In addition, one benefit of some embodiments is to enable the enterprise application, in some aspects, to implement process controls and/or metrics based on these relationships. Merely by way of example, once a relationship has been defined within an enterprise application, a service level agreement attached to the relationship can be defined within the application and/or measured by the application. For instance, in the example discussed above, if an enterprise application has defined a client relationship between US Operations business unit 205b and the Europe Operations business unit 205c (e.g., with respect to a Supply Chain Management business function 215a, as described above), a service level agreement can be defined (for example, that the US Operations business unit 205a will process supply chain transactions within 24 hours and provide monthly activity reports) within the enterprise application, and the performance of the US Operations business unit 205b can be measured against the agreed service levels. Other types of process controls, such as internal audits (e.g., SAS 70 audits and others) can be supported as well by the relationship definitions implemented by various embodiments of the invention.
One set of embodiments provides methods for configuring an enterprise application, including without limitation configuring an enterprise application to account for relationships between various business units and/or business functions.
In some embodiments, the method 300 comprises providing a software framework for defining a set of relationships between a plurality of business units and/or business functions (block 305). Merely by way of example, the framework might comprise a business unit definition, which can be used to define a plurality of business units, and/or a business function definition that can be used to define business functions, as well as a relationship definition that is used to define a relationship between two or more of the business units and/or business functions. In an aspect, this framework provides a structure in which relationships can be defined in such a way that they can be represented within an enterprise application. Merely by way of example, the framework might provide a mapping between user input about various business units, functions and/or relationships and various database structures and/or application configuration parameters that are used to represent those business units, functions and/or relationships.
The method 300 may also comprise providing a user interface (block 310) for a user to define a relationship between one or more business units and/or business functions. In some cases, a user interface component of a configurator program might provide the user interface, as described above. Merely by way of example, the user interface might be configured to receive input from a user and/or to display output for a user. In some (but not all) embodiments, the user interface is provided as a set of one or more web pages. Alternatively and/or additionally, a third party application might be used to provide the user interface. In some cases, a combination of these procedures may be used.
The method 300 further comprises receiving (e.g., via the user interface) identifications of one or more business units for which a relationship is to be defined (block 315a). Merely by way of example, the configurator might present a list of business units that have been defined for a particular enterprise, and allow a user to select two or more such business units. In some cases, identifying a business unit might comprise defining the business unit itself (block 315b). A business unit can be defined in a variety of ways, such as by identifying the name of the business unit, identifying other characteristics of the business unit (geographical location, business functions performed, etc.) and/or the like. In a particular aspect, defining a business unit might comprise defining the business unit's location within a structural hierarchy of the enterprise. Tools for defining a business unit in this fashion are described in detail in the Bhatia Application, already incorporated by reference, and such tools may be incorporated within some embodiments of the present invention.
The method 300 may further comprise providing for the user to select one or more business functions for which the relationship is to be defined, and/or receiving (e.g., via the user interface) such a selection (block 320a). In some cases, selecting a business function might comprise defining that business function (block 320b), e.g., via the user interface (and/or receiving input that defines the business function). The definition of a business function can comprise any of a variety of data, including without limitation, a name or label for the business function, an identification of a business unit that performs the business function, an identification of one or more transactions that are processed by the business function and/or the like.
At block 325, the method 300 comprises defining a business function agency relationship between the identified business units and/or selected business functions. More specifically, in some cases, the method 300 comprises receiving a definition of such a relationship (and/or input defining the relationship). Merely by way of example, the configurator might provide a user interface for the user to specify which type (of several possible types) of business function agency relationship exists between the identified business units and/or functions, as well as, in some cases, defining a type of transaction to which the relationship applies and/or information specific to the selected type of relationship (e.g., which business unit is the client and which is the provider, which business function is to perform additional processing for which other business function etc.). In some cases, these relationships can be defined at the time a business unit and/or business function is defined (e.g., at blocks 315b and/or 320b, described above).
As noted above, certain embodiments of the invention can support and/or facilitate the use of service level agreements and other controls. In some cases, this can include allowing a user to define (i.e., provide details) about specific controls to be implemented with respect to a particular business function agency relationship. Hence, the method 300, in an embodiment, includes receiving a definition of a control pertaining to the defined relationship (block 330). Merely by way of example, the user interface might provide a set of one or more fields to allow the user to specify the details about a control, such as a service level agreement. Such details can include, without limitation, time and/or other performance requirements (e.g., how quickly and/or in what manner a business function must be performed for a client business unit, etc.), reporting requirements (e.g., when reports about the control should be generated, perhaps automatically by the enterprise application, etc.), and/or the like. In another embodiment, the user interface might be configured to allow the user to submit a document that provides such details (in such cases, the configurator might be configured to parse the document to ascertain the details and/or simply to store the document and/or the details for future reference, e.g., by officials at the relevant business units).
Another possible type of control is a control on the nature of the business function agency relationship itself. For example, the configurator might allow a user to set a limitation on the number and/or type(s) of business units that can perform a business function on behalf of a client business unit. Based on the disclosure herein, one skilled in the art will appreciate that there are a variety of controls that can be implemented in this fashion, and that the details provided with vary by embodiment and/or by the nature of the control(s) implemented.
In some cases, a confirmation of the defined relationship may be displayed for the user (block 335), e.g., by displaying a list of the selected business units and/or functions and the type of relationship between them (optionally including any defined controls). Among other things, this can give the user an opportunity to review the relationship before committing it. At block 340, the enterprise application is configured (e.g., by a configuration engine, etc.) to reflect the defined business function agency relationship. As noted above, configuring the enterprise application can comprise a variety of procedures. Merely by way of example, in some cases, configuration parameters in the enterprise application may be set to reflect the defined relationship.
In other cases, the enterprise application might be configured to obtain such configuration information from a database. Hence, in some embodiments, a set of data representing the defined relationship may be stored in a database (block 345), which might reside on a computer readable storage medium (i.e., a hard disk drive, an array of drives, a storage area network, an optical drive, etc.). Merely by way of example, as noted above, a relationship may be represented by one or more records and/or tables in a database, and such records and/or tables may be written to a database (and/or if they already exist, modified as appropriate) to provide the necessary information for the enterprise to account for the defined relationship.
In some cases, the method 300 further includes processing a transaction, according the defined business function agency relationship (block 350). There are many ways in which a transaction can be processed in this manner.
Merely by way of example
At block 370, the enterprise application (and/or a component thereof) determines that a particular business unit provides the business function for the business unit from which the request originates (i.e., that the requesting business unit is a client of the particular business unit). In an aspect, this determination is made based on configuration data provided by a configurator (e.g., based on data stored in a database, on configuration parameters, etc.). Such data can be generated and/or provided, for example, using the method 300 described above. The enterprise application then provides for the appropriate business unit to perform the requested function (and/or, more specifically, for the business function within the business to perform the task or service for which it was requested). For example, the enterprise application might route the request to the appropriate business unit and/or business function, might automatically process the request with the appropriate business function, etc.
The method 380 further comprises determining that the transaction should be further processed by a second business function (as, for example, in the “employee setup” example described above with respect to
In conjunction with the methods 360, 380 illustrated by
The computer system 400 is shown comprising hardware elements that can be electronically coupled via a bus 405 (or may otherwise be in communication, as appropriate). The hardware elements can include one or more processors 410, including without limitation one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration chips, and/or the like); one or more input devices 415, which can include without limitation a mouse, a keyboard and/or the like; and one or more output devices 420, which can include without limitation a display device, a printer and/or the like.
The computer system 400 may further include (and/or be in communication with) one or more storage devices 425, which can comprise, without limitation, local and/or network accessible storage and/or can include, without limitation, a disk drive, a drive array, an optical storage device, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like. The computer system 400 might also include a communications subsystem 430; which can include without limitation a modem, a network card (wireless or wired), an infra-red communication device, and/or the like), a wireless communication device and/or chipset (such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, cellular communication facilities, etc.). The communications system 430 may permit data to be exchanged with a network (such as the network 610 described below), and/or any other devices described herein. In many embodiments, the computer system 400 will further comprise a working memory 435, which can include a RAM or ROM device, as described above.
The computer system 400 also can comprise software elements, shown as being currently located within the working memory 435, including an operating system 440 and/or other code, such as one or more application programs 445, which may comprise computer programs of the invention (such as a configurator program, an enterprise application, a database server and/or client, a web server and/or browser, etc.) and/or may be designed to implement methods of the invention, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as instructions executable by a computer (and/or a processor within a computer). A set of these instructions might be stored on a computer-readable storage medium, such as the storage device(s) 425 described above. In some cases, the storage medium might be incorporated within a computer system, such as the system 400. In other embodiments, the storage medium might be separate from a computer system (i.e., a removable medium, such as a compact disc, etc.), such that the storage medium can be used to program a generic computer with the instructions stored thereon. These instructions might take the form of executable code, which is executable by the computer system 400 and/or might take the form of installable code, which, upon installation on the computer system 400 (e.g., using any of a variety of generally available installation programs, compression/decompression utilities, etc.) then takes the form of executable code.
It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
In one aspect, the invention employs a computer system (such as the computer system 400) to perform methods of the invention. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer system 400 in response to processor 410 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 440 and/or other code, such as an application program 445) contained in the working memory 435. Such instructions may be read into the working memory 435 from another machine-readable medium, such as one or more of the storage device(s) 425. Merely by way of example, execution of the sequences of instructions contained in the working memory 435 causes the processor(s) 410 to perform one or more procedures of the methods described herein.
The terms “machine readable medium” and “computer readable medium,” as used herein, refer to any medium that participates in providing data that causes a machine (e.g., a computer) to operation in a specific fashion. In an embodiment implemented using the computer system 400, various machine-readable media might be involved in providing instructions to processor(s) 410 for execution. In many implementations, a machine-readable medium is a physical and/or tangible medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as the storage device(s) 425. Volatile media includes, without limitation dynamic memory, such as the working memory 435. Transmission media includes, without limitation, coaxial cables, copper wire and fiber optics, including the wires that comprise the bus 405, as well as the various components of the communication subsystem 430 (and/or the media by which the communications subsystem 430 provides communication with other devices). Hence, transmission media can also take the form of waves, including without limitation radio, acoustic and/or light waves, such as those generated during radio-wave and infra-red data communications.
Common forms of physical and/or tangible machine-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
Various forms of machine-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 410 for execution. Merely by way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. The remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium. These signals, which might be in the form of electromagnetic signals, acoustic signals, optical signals and/or the like, are all examples of carrier waves on which instructions can be encoded, in accordance with various embodiments of the invention.
The communications subsystem 430 (and/or components thereof) generally will receive the signals, and the bus 405 then might carry the signals (and/or the data, instructions, etc. carried by the signals) to the working memory 435, from which the processor(s) 405 retrieves and executes the instructions. The instructions received by the working memory 435 may optionally be stored on a storage device 425 either before or after execution by the processor(s) 410.
A set of embodiments comprises systems for configuring an enterprise application, such as by defining one or more data structures used by the enterprise application. Merely by way of example,
Certain embodiments of the invention operate in a networked environment, which can include a network 510. The network 510 can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, the network 510 can be a local area network (“LAN”), including without limitation an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network, including without limitation a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth™ protocol known in the art, and/or any other wireless protocol; and/or any combination of these and/or other networks.
Embodiments of the invention can include one or more server computers 515. Each of the server computers 515 may be configured with an operating system including without limitation any of those discussed above, as well as any commercially-available server operating systems. Each of the servers 515 may also be running one or more applications, which can be configured to provide services to one or more clients 505 and/or other servers 515.
Merely by way of example, one of the servers 515 may be a web server, which can be used, merely by way of example, to process requests for web pages or other electronic documents from user computers 505. The web server can also run a variety of server applications, including HTTP servers, FTP servers, CGI servers, database servers, Java servers, and the like. In some embodiments of the invention, the web server may be configured to serve web pages that can be operated within a web browser on one or more of the user computers 505 to perform methods of the invention.
The server computers 515, in some embodiments, might include one or more file and or/application servers, which can include one or more applications (such as an enterprise application, a configurator application, etc.) accessible by a client running on one or more of the user computers 505 and/or other servers 515. Merely by way of example, the server(s) 515 can be one or more general purpose computers capable of executing programs or scripts in response to the user computers 505 and/or other servers 515, including without limitation web applications (which might, in some cases, be configured to perform methods of the invention, to provide a user interface for a configurator application, etc.). Merely by way of example, a web application can be implemented as one or more scripts or programs written in any programming language, such as Java™, C, C#™ or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The application server(s) can also include database servers, including without limitation those commercially available from Oracle, Microsoft, Sybase™, IBM™ and the like, which can process requests from database clients running on a user computer 505 and/or another server 515. In some embodiments, an application server can create web pages dynamically for displaying information in accordance with embodiments of the invention, such as for displaying a user interface for a configurator application, receiving data via the user interface, etc. Data provided by an application server may be formatted as web pages (comprising HTML, Javascript, etc., for example) and/or may be forwarded to a user computer 505 via a web server (as described above, for example). Similarly, a web server might receive web page requests and/or input data from a user computer 505 and/or forward the web page requests and/or input data to an application server.
In accordance with further embodiments, one or more servers 515 can function as a file server and/or can include one or more of the files necessary to implement methods of the invention incorporated by an application running on a user computer 505 and/or another server 515. Alternatively, as those skilled in the art will appreciate, a file server can include all necessary files, allowing such an application to be invoked remotely by a user computer 505 and/or server 515. It should be noted that the functions described with respect to various servers herein (e.g., application server, database server, web server, file server, etc.) can be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters.
In certain embodiments, the system can include one or more databases 520. The location of the database(s) 520 is discretionary: merely by way of example, a database 520a might reside on a storage medium local to (and/or resident in) a server 515a (and/or a user computer 505). Alternatively, a database 520b can be remote from any or all of the computers 505, 515, so long as it can be in communication (e.g., via the network 510) with one or more of these. In a particular set of embodiments, a database 520 can reside in a storage-area network (“SAN”) familiar to those skilled in the art. (Likewise, any necessary files for performing the functions attributed to the computers 505, 515 can be stored locally on the respective computer and/or remotely, as appropriate.) In one set of embodiments, the database 520 is a relational database, such as an Oracle database, that is adapted to store, update, and retrieve data in response to SQL-formatted commands. The database might be controlled and/or maintained by a database server, as described above, for example. The database, in an aspect, might be configured to store one or more tables used by an enterprise application and/or generated/modified by a configurator program.
While the invention has been described with respect to exemplary embodiments, one skilled in the art will recognize that numerous modifications are possible. For example, the methods and processes described herein may be implemented using hardware components, software components, and/or any combination thereof. Further, while various methods and processes described herein may be described with respect to particular structural and/or functional components for ease of description, methods of the invention are not limited to any particular structural and/or functional architecture but instead can be implemented on any suitable hardware, firmware and/or software configuration. Similarly, while various functionality is ascribed to certain system components, unless the context dictates otherwise, this functionality can be distributed among various other system components in accordance with different embodiments of the invention.
Moreover, while the procedures comprised in the methods and processes described herein are described in a particular order for ease of description, unless the context dictates otherwise, various procedures may be reordered, added, and/or omitted in accordance with various embodiments of the invention. Moreover, the procedures described with respect to one method or process may be incorporated within other described methods or processes; likewise, system components described according to a particular structural architecture and/or with respect to one system may be organized in alternative structural architectures and/or incorporated within other described systems. Hence, while various embodiments are described with—or without—certain features for ease of description and to illustrate exemplary features, the various components and/or features described herein with respect to a particular embodiment can be substituted, added and/or subtracted from among other described embodiments, unless the context dictates otherwise. Consequently, although the invention has been described with respect to exemplary embodiments, it will be appreciated that the invention is intended to cover all modifications and equivalents within the scope of the following claims.
This application is a non-provisional application claiming the benefit, under 35 U.S.C. §119(e), of provisional U.S. Patent Application No. 60/956,901, titled “Business Unit Outsourcing Model” and filed Aug. 20, 2007 by Nigel King et al. This application may be related to provisional U.S. Patent Application No. 60/956,898, titled “Enterprise Structure Configurator” and filed Aug. 20, 2007 by Akash Bhatia et al. This application may also be related to U.S. patent application Ser. No. 12/192,418 titled “Enterprise Structure Configurator” and filed on Aug. 15, 2008 by Akash Bhatia et al. The entire disclosure of each of the above applications is incorporated herein by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6072493 | Driskell | Jun 2000 | A |
| 6343291 | Goldman | Jan 2002 | B1 |
| 6473794 | Guheen et al. | Oct 2002 | B1 |
| 6626959 | Moise et al. | Sep 2003 | B1 |
| 6629081 | Cornelius et al. | Sep 2003 | B1 |
| 6668253 | Thompson et al. | Dec 2003 | B1 |
| 6925468 | Bobbitt et al. | Aug 2005 | B1 |
| 6985901 | Sachse | Jan 2006 | B1 |
| 6985955 | Gullotta et al. | Jan 2006 | B2 |
| 7167855 | Koenig | Jan 2007 | B1 |
| 7562308 | Pradhan et al. | Jul 2009 | B2 |
| 7650633 | Whitson | Jan 2010 | B2 |
| 7657471 | Sankaran et al. | Feb 2010 | B1 |
| 7693844 | Bobbitt et al. | Apr 2010 | B1 |
| 7712127 | Thompson et al. | May 2010 | B1 |
| 7823189 | Patrick | Oct 2010 | B2 |
| 7870595 | Finney et al. | Jan 2011 | B2 |
| 20010034693 | Farhat et al. | Oct 2001 | A1 |
| 20010034704 | Farhat et al. | Oct 2001 | A1 |
| 20020026592 | Gavrila et al. | Feb 2002 | A1 |
| 20020046074 | Barton | Apr 2002 | A1 |
| 20020059404 | Schaaf et al. | May 2002 | A1 |
| 20020087344 | Billings et al. | Jul 2002 | A1 |
| 20020107792 | Anderson | Aug 2002 | A1 |
| 20020178119 | Griffin et al. | Nov 2002 | A1 |
| 20030028451 | Ananian | Feb 2003 | A1 |
| 20030055788 | Sakuma et al. | Mar 2003 | A1 |
| 20030078815 | Parsons | Apr 2003 | A1 |
| 20030097319 | Moldovan et al. | May 2003 | A1 |
| 20030158768 | Maeda | Aug 2003 | A1 |
| 20030182461 | Stelting et al. | Sep 2003 | A1 |
| 20040064351 | Mikurak | Apr 2004 | A1 |
| 20040098594 | Fleming et al. | May 2004 | A1 |
| 20040107131 | Wilkerson et al. | Jun 2004 | A1 |
| 20040162771 | Tamatsu et al. | Aug 2004 | A1 |
| 20040210528 | Guion et al. | Oct 2004 | A1 |
| 20050010429 | Zipple et al. | Jan 2005 | A1 |
| 20050108021 | Anderson et al. | May 2005 | A1 |
| 20050246215 | Rackham | Nov 2005 | A1 |
| 20060041505 | Enyart | Feb 2006 | A1 |
| 20060178918 | Mikurak | Aug 2006 | A1 |
| 20060190486 | Zhou et al. | Aug 2006 | A1 |
| 20060229896 | Rosen et al. | Oct 2006 | A1 |
| 20070027829 | Graf | Feb 2007 | A1 |
| 20070088730 | Mason et al. | Apr 2007 | A1 |
| 20070156500 | Merkel et al. | Jul 2007 | A1 |
| 20070174390 | Silvain et al. | Jul 2007 | A1 |
| 20070214497 | Montgomery et al. | Sep 2007 | A1 |
| 20070226090 | Stratton | Sep 2007 | A1 |
| 20080021716 | Buss et al. | Jan 2008 | A1 |
| 20080077530 | Banas et al. | Mar 2008 | A1 |
| 20080098485 | Chiou | Apr 2008 | A1 |
| 20080162249 | Leventhal | Jul 2008 | A1 |
| 20080205295 | Saba | Aug 2008 | A1 |
| 20090006113 | Robertson et al. | Jan 2009 | A1 |
| 20090024494 | Walz et al. | Jan 2009 | A1 |
| 20090063549 | Bhatia et al. | Mar 2009 | A1 |
| 20090183244 | Saraf et al. | Jul 2009 | A1 |
| 20090204416 | King et al. | Aug 2009 | A1 |
| 20090222297 | Cao et al. | Sep 2009 | A1 |
| 20090222366 | Cao et al. | Sep 2009 | A1 |
| 20100049573 | Kantorova et al. | Feb 2010 | A1 |
| 20100312747 | Stolte et al. | Dec 2010 | A1 |
| 20110099030 | Besch et al. | Apr 2011 | A1 |
| 20110288968 | King et al. | Nov 2011 | A1 |
| Entry |
|---|
| U.S. Appl. No. 12/784,033, dated May 22, 2012, Non-Final Office Action. |
| U.S. Appl. No. 12/192,418, dated May 24, 2011, Non-Final Office Action. |
| U.S. Appl. No. 12/195,070, dated Jun. 20, 2012, Advisory Action. |
| U.S. Appl. No. 12/195,070, dated Mar. 30, 2012, Final Office Action. |
| U.S. Appl. No. 12/195,070, dated Sep. 28, 2011, Non-Final Office Action. |
| U.S. Appl. No. 12/192,583, dated Mar. 1, 2011, Non-Final Office Action. |
| U.S. Appl. No. 12/192,583, dated Aug. 15, 2011, Final Office Action. |
| U.S. Appl. No. 12/192,418, Final Office Action dated Aug. 9, 2013, 32 pages. |
| U.S. Appl. No. 12/192,418, Non Final Office Action dated Feb. 1, 2013, 34 pages. |
| U.S. Appl. No. 12/195,070, Final Office Action Response dated May 30, 2012, 16 pages. |
| U.S. Appl. No. 12/784,033, Advisory Action dated Mar. 7, 2013, 2 pages. |
| U.S. Appl. No. 12/784,033, Final Office Action dated Dec. 21, 2012, 19 pages. |
| U.S. Appl. No. 12/784,033, Non Final Office Action dated Sep. 11, 2013, 22 pages. |
| U.S. Appl. No. 12/784,033, Restriction Requirement dated Jan. 19, 2012, 7 pages. |
| Conditional Formatting, www.Ozgrid.com,http://www.ozgrid.com/Excel/conditional-formatting.htm, Nov. 25, 2005, pp. 1-2. |
| MS Excel: Change how empty cells are displayed in a pivot table in Excel 2003/XP/2000/97, www.techonthenet.com, Mar. 16, 2006, pp. 1-4. |
| U.S. Appl. No. 12/192,418, Non-Final Office Action dated Mar. 13, 2014, 50 pages. |
| U.S. Appl. No. 12/784,033, Final Office Action dated Mar. 10, 2014, 23 pages. |
| Bauer, Arbor ships first Microsoft Office compatible OLAP server, Business Wire, Dec. 5, 1994, 2 pages. |
| Hawley, Change the color of cells in the pivot table, http://www.ozgrid.com/forum/showthread.php?t=48003, post date Mar. 16, 2006, join date Jan. 24, 2003, pp. 1-2. |
| U.S. Appl. No. 12/784,033, Office Action dated May 22, 2012, 19 pages. |
| U.S. Appl. No. 12/192,418, Office Action dated May 24, 2011, 16 pages. |
| U.S. Appl. No. 12/195,070, Advisory Action dated Jun. 20, 2012, 3 pages. |
| U.S. Appl. No. 12/195,070, Final Office Action dated Mar. 30, 2012, 22 pages. |
| U.S. Appl. No. 12/195,070, Office Action dated Sep. 28, 2011, 19 pages. |
| White, Ron, “How Computers Work,” 7th Edition, Oct. 2003, 65 pages, Que, Indianapolis, IN. |
| Non-Final Office Action for U.S. Appl. No. 12/192,418, dated May 24, 2011, 16 pages. |
| U.S. Appl. No. 12/192,418, Non-Final Office Action dated Dec. 18, 2014, 51 pages. |
| U.S. Appl. No. 12/195,070, Non-Final Office Action dated Apr. 2, 2015, 24 pages. |
| U.S. Appl. No. 12/784,033, Non-Final Office Action dated Mar. 25, 2015, 24 pages. |
| U.S. Appl. No. 12/195,070, Final Office Action dated Jun. 7, 2016, 28 pages. |
| U.S. Appl. No. 12/784,033, Non-Final Office Action dated Jun. 16, 2016, 31 pages. |
| U.S. Appl. No. 12/784,033, Final Office Action dated Sep. 17, 2015, all pages. |
| U.S. Appl. No. 12/784,033, Advisory Action dated Dec. 8, 2015, all pages. |
| U.S. Appl. No. 12/192,418,Final Office Action dated Jul. 13, 2015, 71 pages. |
| U.S. Appl. No. 12/192,418, Non-Final Office Action dated Aug. 11, 2016, 51 pages. |
| U.S. Appl. No. 12/195,070, Final Office Action dated May 7, 2016, 28 pages. |
| U.S. Appl. No. 12/192,418, Notice of Allowance dated Mar. 20, 2017, 28 pages. |
| U.S. Appl. No. 12/784,033, Final Office Action dated Feb. 21, 2017, 17 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20090204416 A1 | Aug 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60956901 | Aug 2007 | US | |
| 60956898 | Aug 2007 | US |
