Maria Theresa Barnes-Leon

Bio: Maria Theresa Barnes-Leon is an academic researcher. The author has contributed to research in topics: Data type & Service (systems architecture). The author has an hindex of 7, co-authored 12 publications receiving 3606 citations.

Common common object

Abstract: Enterprise management information in a first format (500) for use by a first computerized system is transformed into an intermediate format (514) to readily make the stored enterprise management information available for use in a second computerized system that utilizes a second format (520). The transformation includes a plurality of common data type elements (502, 504, 506, 508, 510, 512) that are adapted to be shared across a plurality of data objects in the intermediate format.

Custom common object

Abstract: Enterprise management system includes a product data structure (160), a related product line element (162), a list of price type element (164), a list of related inventory location element (166), a list of related product (168), a list of related business unit element (170), and a product custom data element (172). The system converts some or all the enterprise information that is in the source format into the target format by using an intermediate format of the enterprise information. The intermediate format includes a plurality of custom data type elements that are adapted for capturing unique customer information that are relevant to the customer's business systems. The intermediate form is then used to convert the enterprise information into the target format.

Universal application network architecture

Abstract: A method and system for providing an integration environment in which integration processes can be developed independent of integration servers and applications. The integration environment provides an application service interface for each application that is independent of the integration servers. An integration process that is developed to use the application service interface is compatible with any integration server that supports the applications that the integration process accesses. The integration environment provides a common service interface for each type of application. The common service interface is independent of the application that is providing the service and is also independent of the integration server. Thus, an integration process developed to use the common service interface is compatible with any application of the appropriate type and any integration server.

Inventory transaction common object

Abstract: Stored inventory transaction information in a first format for use by a first computerized system is transformed to readily make the stored inventory transaction information available for use in a second computerized system that utilizes a second format in a cost-efficient and time-efficient manner.

Service request common object

Abstract: Service request information in a first format for use by a first computerized system is synchronized with the service request information in a second computerized system that utilizes a second format by using an service request common object data model.

Consistent set of interfaces derived from a business object model

Abstract: Methods and systems consistent with the present invention provide a data processing system having a business object model reflecting the data used during a business transaction. Consistent interfaces are generated from the business object model. These interfaces are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.

Common common object

Abstract: Enterprise management information in a first format (500) for use by a first computerized system is transformed into an intermediate format (514) to readily make the stored enterprise management information available for use in a second computerized system that utilizes a second format (520). The transformation includes a plurality of common data type elements (502, 504, 506, 508, 510, 512) that are adapted to be shared across a plurality of data objects in the intermediate format.

Product common object

Abstract: Stored product management information in a first format for use by a first computerized system is transformed to readily make the stored product management information available for use in a second computerized system that utilizes a second format in a cost-efficient and time-efficient manner.

Custom entities and fields in a multi-tenant database system

Abstract: Systems and methods for hosting variable schema data such as dynamic tables and columns in a fixed physical database schema. Standard objects, such as tables are provided for use by multiple tenants or organizations in a multi-tenant database system. Each organization may add or define custom fields for inclusion in a standard object. Custom fields for multiple tenants are stored in a single field within the object data structure, and this single field may contain different data types for each tenant. Indexing columns are also provided, wherein a tenant may designate a field for indexing. Data values for designated fields are copied to an index column, and each index column may include multiple data types. Each organization may also define custom objects including custom fields and indexing columns. Custom objects for multiple tenants are stored in a single custom object data structure. The primary key values for the single custom object table are globally unique, but also include an object-specific identifier which may be re-used among different entities.

System, method and computer program product for publicly providing web content of a tenant using a multi-tenant on-demand database service

Abstract: In accordance with embodiments, there are provided mechanisms and methods for publicly providing web content of a tenant using a multi-tenant on-demand database service. These mechanisms and methods for publicly providing web content of a tenant using a multi-tenant on-demand database service can allow the web content to be published by a tenant using the multi-tenant on-demand database service for use by non-tenants of the multi-tenant on-demand database service.