# US 2019/0172068 A1 · Method and system for implementing a crm quote and order capture context service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0172068 A1 - Document ID: US20190172068A1 - Status: Published application - Kind: A1 - Application number: 16/266,337 - Filed: 2019-02-04 - Published: 2019-06-06 - Earliest claimed: 2012-08-30 - Assignees: Oracle International Corporation - Applicants: Oracle International Corporation - Inventors: Mark David LEWIS; Jianfeng TAI; David WANG; Ying WANG; Re LAI - Web page: https://patentgrep.com/patent/US20190172068A1 ## CPC - G06Q 30/0611: {Request for offers or quotes} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Disclosed is an improved approach for implementing enterprise software systems that addresses the above-described problems with existing systems. The present approach provides an effective and efficient way for defining schemas for services, and to define how to map the schema to particular transactional contexts. ## Claims ### Claim 1 A computer implemented method implemented with a processor, comprising: defining a canonical schema that pertains to declarative schema representations for an enterprise application, the canonical schema comprising a set of data objects in a database of general database transaction applicability mappable for a specific database transaction usage; implementing a user interface to map the canonical schema to a specific database transaction usage; mapping the canonical schema to the specific database transaction usage through a configuration of user interface portions in the user interface without software code being coded to configure the canonical schema, wherein mapping the canonical schema to the specific database transaction usage comprises: defining, for the specific database transaction usage, a subset of data objects within the set of data objects in the canonical schema; and defining, for the specific database transaction usage, how to query and update the subset of data objects in the database; and using the subset of the canonical schema as an input of the specific database transaction usage or an output of the specific database transaction usage by: identifying a group of declarative schema representations to map to the specific database transaction usage; identifying, for a declarative schema representation from among the group of declarative schema representations, the attributes that are required by the specific database transaction usage; determining whether an entity from the subset of data objects maps to a view object or a service; upon determination that the entity maps to the view object, performing, for the declarative schema representation from among the group of declarative schema representations, a single query to the view object specified in the mapping that dedupes search keys before executing the single query; and upon determination that the entity from the subset of data objects maps to a query service, executing, for the declarative schema representation from among the group of declarative schema representations, the query service conforming to a standard service interface defined by the input or the output of the specific database transaction usage specified in the mappings. ### Claim 2 (depends on 1) The method of claim 1, in which the canonical schema comprises a set of objects for the enterprise application. ### Claim 3 (depends on 1) The method of claim 1, in which the canonical schema is related to the specific database transaction usage by performing mapping or populating. ### Claim 4 (depends on 1) The method of claim 1, in which a user interface is provided to relate the canonical schema to the specific database transaction usage. ### Claim 5 (depends on 4) The method of claim 4, in which the user interface defines a layer of abstraction over the canonical schema. ### Claim 6 (depends on 1) The method of claim 1, wherein the method is applied to a quote and capture service. ### Claim 7 (depends on 6) The method of claim 6, in which a service schema is edited to include add, remove, or edit attributes, where the attributes are defined in another schema. ### Claim 8 (depends on 7) The method of claim 7, in which contextual data is used to process the service schema. ### Claim 9 (depends on 1) The method of claim 1, in which a logic engine operates upon the canonical schema without being specifically programmed to do so. ### Claim 10 A computer program product embodied in a non-transitory computer readable medium, the computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes the processor to execute a method comprising: defining a canonical schema that pertains to declarative schema representations for an enterprise application, the canonical schema comprising a set of data objects in a database of general database transaction applicability mappable for a specific database transaction usage; implementing a user interface to map the canonical schema to a specific database transaction usage; mapping the canonical schema to the specific database transaction usage through a configuration of user interface portions in the user interface without software code being coded to configure the canonical schema, wherein mapping the canonical schema to the specific database transaction usage comprises: defining, for the specific database transaction usage, a subset of data objects within the set of data objects in the canonical schema; and defining, for the specific database transaction usage, how to query and update the subset of data objects in the database; and using the subset of the canonical schema as an input of the specific database transaction usage or an output of the specific database transaction usage by: identifying a group of declarative schema representations to map to the specific database transaction usage; identifying, for a declarative schema representation from among the group of declarative schema representations, the attributes that are required by the specific database transaction usage; determining whether an entity from the subset of data objects maps to a view object or a service; upon determination that the entity maps to the view object, performing, for the declarative schema representation from among the group of declarative schema representations, a single query to the view object specified in the mapping that dedupes search keys before executing the single query; and upon determination that the entity from the subset of data objects maps to a query service, executing, for the declarative schema representation from among the group of declarative schema representations, the query service conforming to a standard service interface defined by the input or the output of the specific database transaction usage specified in the mappings. ### Claim 11 (depends on 10) The computer program product of claim 10, in which the canonical schema comprises a set of objects for the enterprise application. ### Claim 12 (depends on 10) The computer program product of claim 10, in which the canonical schema is related to the specific database transaction usage by performing mapping or populating. ### Claim 13 (depends on 10) The computer program product of claim 10, in which a user interface is provided to relate the canonical schema to the specific database transaction usage. ### Claim 14 (depends on 13) The computer program product of claim 13, in which the user interface defines a layer of abstraction over the canonical schema. ### Claim 15 (depends on 10) The computer program product of claim 10, wherein the method is applied to a capture service for a CRM application. ### Claim 16 (depends on 15) The computer program product of claim 15, in which a service schema is edited to include add, remove, or edit attributes, where the attributes are defined in another schema. ### Claim 17 (depends on 16) The computer program product of claim 16, in which contextual data is used to process the service schema. ### Claim 18 (depends on 10) The computer program product of claim 10, in which a logic engine operates upon the canonical schema without being specifically programmed to do so. ### Claim 19 A system, comprising: a processor; and a memory comprising a computer code executed using the processor, in which the computer code implements: defining a canonical schema that pertains to declarative schema representations for an enterprise application, the canonical schema comprising a set of data objects in a database of general database transaction applicability mappable for a specific database transaction usage; implementing a user interface to map the canonical schema to a specific database transaction usage; mapping the canonical schema to the specific database transaction usage through a configuration of user interface portions in the user interface without software code being coded to configure the canonical schema, wherein mapping the canonical schema to the specific database transaction usage comprises: defining, for the specific database transaction usage, a subset of data objects within the set of data objects in the canonical schema; and defining, for the specific database transaction usage, how to query and update the subset of data objects in the database; and using the subset of the canonical schema as an input of the specific database transaction usage or an output of the specific database transaction usage by: identifying a group of declarative schema representations to map to the specific database transaction usage; identifying, for a declarative schema representation from among the group of declarative schema representations, the attributes that are required by the specific database transaction usage; determining whether an entity from the subset of data objects maps to a view object or a service; upon determination that the entity maps to the view object, performing, for the declarative schema representation from among the group of declarative schema representations, a single query to the view object specified in the mapping that dedupes search keys before executing the single query; and upon determination that the entity from the subset of data objects maps to a query service, executing, for the declarative schema representation from among the group of declarative schema representations, the query service conforming to a standard service interface defined by the input or the output of the specific database transaction usage specified in the mappings. ### Claim 20 (depends on 19) The system of claim 19, in which the canonical schema comprises a set of objects for the enterprise application. ### Claim 21 (depends on 19) The system of claim 19, in which the canonical schema is related to the specific database transaction usage by performing mapping or populating. ### Claim 22 (depends on 19) The system of claim 19, in which a user interface is provided to relate the canonical schema to the specific database transaction usage. ### Claim 23 (depends on 22) The system of claim 22, in which the user interface defines a layer of abstraction over the canonical schema. ### Claim 24 (depends on 19) The system of claim 19, wherein the method is applied to a capture service for a CRM application. ### Claim 25 (depends on 24) The system of claim 24, in which a service schema is edited to include add, remove, or edit attributes, where the attributes are defined in another schema. ### Claim 26 (depends on 25) The system of claim 25, in which contextual data is used to process the service schema. ### Claim 27 (depends on 19) The system of claim 19, in which a logic engine operates upon the canonical schema without being specifically programmed to do so.