Sap Se

Sap Ag

Dirk Endesfelder

Markus Helmut Kahn

Ralf Handl

Michael Hladik

Christoph Meinel

Markus Fenn

Hermann Haaf

Matthias Schwan

Lothar Muessler

Dorothea Mayer

Frank Andreas Raebiger

Roland Kolata

Markus Roeckelein

Manfred Wanninger

Silvia Harmsen

Markus Riepp

Mathias Vahle

Martin Erdelmeier

Ekkehard Lange

Andreas S Borchardt

Joerg Bartelt

Rainer Richter

Sarah Von Glan

Markus Kahn

Holger Wuest

Karola Ludes

Techniques and solutions are provided for a table schema that facilitates data denormalization, and which can allow for improved database system performance. Rather than accessing multiple tables, database operations can access a single table, which can reduce the number and complexity of database operations. The table schema includes an attribute subset indicator field. Different values of the attribute subset indicator field can be associated with different contexts, such as different tables or views, which in turn can represent different entity types. A given value of the attribute subset indicator field allows data to be accessed at a coarse granularity, while more-fine grained results can be obtained by providing a value for one or more attribute fields of the table. Different subsets of attributes are retrievable for a given value of the attribute subset indicator field.

Table schema providing improved database system performance

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a financial instrument impairment attribute values analytical result business object.

Consistent interface for financial instrument impairment attribute values analytical result

In a banking application system including numerous banking applications, a data management framework allows for the generalized storage and subsequent access of result data. Through the application of the framework to the raw processing data generated by one of the banking applications, the result data is stored in a general storage location. Through this framework, the data is then readily accessible by all other banking applications. This framework includes a header field, characteristics data and key figure data. This removes proprietary restrictions on the data itself and thus makes it available to the other applications, increasing cross-system efficiency by allowing other applications to access and subsequently use the result data.

Framework for integrated storage of banking application data

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a financial instrument position accounting period total analytical result, a financial instrument position accounting valuation analytical result, a financial instrument position accrual analytical result, a financial instrument position fair value analytical result, and/or a financial instrument position period average volume analytical result business object.

Managing consistent interfaces for financial instrument business objects across heterogeneous systems

Growing community of inventors

Heldelberg, Germany

Dirk Endesfelder