Abstract: Extensible data management system and methods for enabling participants (providers and customers) in a software-as-a-service (SaaS) environment to define audit configurations for generating an audit trail tailored to a customers' business needs. A participant in the SaaS environment may define an extension to the data management system, wherein the extension is associated with a node representing the participant in a hierarchical data structure. The position of the participants in the hierarchical data structure ensures audit configurations created by one customer do not affect the functionality of other customers in the SaaS environment.

Abstract: An enterprise information system consists of two fundamental components—the data and the business logic. Relational databases can provide a stable, clear and robust implementation of transactions with ACID properties and a declarative query language (SQL) for managing data and are at the core of modern enterprise computing. But modern programming languages like Java—a compiled language, and Javascript—a scriptable language, provide a much better environment for implementing complex business logic. Object Relational Mapping (ORM) tools provide a bridge between the relational environment and the object environment, so that data can be persisted in a relational data model and business logic can be encoded using objects. An extension to the standard ORM is provided to allow an application written in an object oriented language to deal with the information it manipulates in terms of objects, rather than in terms of database-specific concepts such as rows, columns and tables.

Abstract: A fulfillment management system includes a database operable to store product availability information associated with at least one product. The fulfillment management system also includes one or more processors collectively operable to receive at least one component available-to-promise (ATP) request. Each component ATP request corresponds to a particular ATP request line-item for a desired product. The one or more processors are also operable to retrieve at least a portion of the product availability information associated with the desired product from the database for each component ATP request, determine an ATP response for each component ATP request using the retrieved product availability information, generate a component quotation for each component ATP request according to the corresponding ATP response, and communicate the component quotation for consolidation with other component quotations.

Abstract: A fulfillment management system includes a database operable to store product availability information associated with at least one product. The fulfillment management system also includes one or more processors collectively operable to receive at least one component available-to-promise (ATP) request. Each component ATP request corresponds to a particular ATP request line-item for a desired product. The one or more processors are also operable to retrieve at least a portion of the product availability information associated with the desired product from the database for each component ATP request, determine an ATP response for each component ATP request using the retrieved product availability information, generate a component quotation for each component ATP request according to the corresponding ATP response, and communicate the component quotation for consolidation with other component quotations.