The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Oct. 28, 2014
Filed:
Dec. 17, 2010
Marcel Hermanns, Heidelberg, DE;
Jens Weiler, Weingarten, DE;
Michael Brombach, Leimen, DE;
Monika Kaiser, Bad Schoenborn, DE;
Jan Teichmann, Neustadt/Weinstrasse, DE;
Thomas Gauweiler, Speyer, DE;
Daniel Hutzel, Karlsruhe, DE;
Marcel Hermanns, Heidelberg, DE;
Jens Weiler, Weingarten, DE;
Michael Brombach, Leimen, DE;
Monika Kaiser, Bad Schoenborn, DE;
Jan Teichmann, Neustadt/Weinstrasse, DE;
Thomas Gauweiler, Speyer, DE;
Daniel Hutzel, Karlsruhe, DE;
SAP AG, Walldorf, DE;
Abstract
Embodiments of the invention relate to computing, and in particular, to a systems and methods for a querying a database. Certain embodiments implement a model-driven database query ('the SADL query') facilitating a design-time tool that allows a developer to create the query based upon existing Business Objects (BOs) and their associations. This SADL query leverages mapping between business-layer entities and database-layer entities, such mapping being derived from association metadata already extant in the business model used to create the Business Objects. In certain embodiments, query views may be based upon associations present within the business layer, rather than upon database-level entities (such as joins or restriction rules) that are typically relied upon in conventional query creation. Embodiments of the present invention may thus align query creation more closely with the structure of the business layer, and may also render query design agnostic relative to the identity of the underlying database.