Sap Ag

Sap Se

Georg Dopf

Andreas Reccius

Stefan Gauger

Danny Pannicke

Michael Conrad

Gunther Liebich

Joachim Kenntner

Dirk Henrich

Rolf Schumann

Kai-Michael Roesner

Markus Klein

Peter Schwarz

Michael Hohendorf

Juergen Alfred Seyfried

Thomas Schachner

Martin Schorr

Joachim Welte

Michael Sylvester

Karsten Bruening

Christiane Cramer

Gerald Paetzold

Jochen Steinbach

Michael Seubert

Thomas Schneider

Werner Gnan

Ralf Dentzer

Daniel Bock

Thilo Kraehmer

Michael Meyringer

Andreas Poth

Georg Podhajsky

Robert Doerner

Thomas Hoffmann

Thomas Nitschke

Andre Wagner

Stefan Adelmann

Andreas Brossler

Klaus Reinelt

Udo Laub

Dieter Krisch

Peter Von Zimmermann

Rudolf Winkel

Stefan Walz

Axel Kuehl

Ralf Dinkel

Robert Reiner

Benjamin Klehr

Stefan Franke

Olaf Duevel

Volker Faisst

Juergen Kind

Giovanni Deledda

Otfried Geisau

Ralf Klein

Martin Gaub

Torsten Bachmann

Andreas Leukert-Knapp

Radim Sykora

Werner Liebold

Klaus Schlappner

Andrea Roesinger

Edwin Himmelsbach

Stefan Hirschenberger

Peter Himmighoefer

Joachim Liebler

Tanjana Preiser-Funke

Yongbin He

Ruediger Raubeck

Sabine Montnacher

Arno Eifel

Frank Reinemuth

Artur Berlinger

Rainer Soltek

Martin Von Der Emder

Ralf Schliehe-Diecks

Robert Bieber

Franz-Joachim Hoeckenreiner

Harald Roedel

Kerstin Bernet

Ralf Krenzke

Sergey Alekseev

Anil Joshi Jetti

Christian Saalfrank

Sunsil S Parvatikar

Frank Zeisberger

Financial reporting methods and systems integrate profitability and accounting data. A universal journal entry allows user definition of relevant characteristics for a market segment. The entry appends the structure of a financial document to provide linkage to market segment characteristics. When creating the financial document including profit and loss (P&L) and balance account line items, a market segment is defined with determined characteristics stored in the line item on the basis of business process dependent rules. For example in posting information on a sales order item, sales order data may be read, and customer, product, and/or other sales order information input. Additional data can be derived on the basis of the determined master data, depending upon user needs. Embodiments allow enriched reporting (e.g., flexible market segment reporting) at the line item level, affording intuitive access to defined characteristics, e.g., drill-down into details of P&L and balance account information.

Financial reporting system integrating market segment attributes and accounting data

A system stores financial accounting data in a Base ledger, together with overlying extension ledger(s). An engine receives both generic financial data, and financial data utilized for specific purposes. Utilizing a mapping table the engine stores in an underlying Base ledger, the generic financial data (e.g., a fixed asset acquisition). The engine stores in overlying extension ledgers, specific financial data (e.g., a linear asset depreciation and/or an declining balance method of asset depreciation) derived from that generic data. This reduces memory footprint by persisting the generic data in one location only. The stored data may be read utilizing dataviews combining data from Base and extension ledgers. A recursive algorithm may evaluate chain(s) of ledgers. Embodiments may be particularly suited to store in the Base ledger generic financial data common to multiple accounting principles (e.g., GAAP, IFRS), and store in extension ledger(s) the associated financial data specific to those accounting schemes.

Extension ledger

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.

Consistent set of interfaces derived from a business object model

Methods and system consistent with the present invention facilitate the management of financial information. Such methods and systems may receive transaction data, store the transaction data as a line item in a day ledger, receive a request for a report, the request indicating a financial figure, such as an average daily balance, to be generated over a specified time interval, and generate, substantially in real-time or during run-time per the request, a report with the financial figure over the specified time interval using data from the day ledger.

Systems and methods for managing and reporting financial information

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having accounting functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Providing accounting software application as enterprise services

A computer network architecture for making procurement-related information that has been generated on a transaction level available to data warehousing techniques is described. The network includes a transaction processing layer with at least one accounting component with a general ledger data base for centrally storing information contained in accounted-related data sets, a data warehousing layer and an additional data sourcing layer. A duplicator receives the data sets that will be or have been stored in the general ledger data base and delivers duplicates of those data sets that fulfil a predefined criteria in a procurement context. A source data base stores the duplicated data sets on a data line level. An extractor of the data sourcing layer interfaces with the data warehousing layer and selectively moves data contained in data lines or sets of data lines from the source data base to the data warehousing layer.

Provision of data for data warehousing applications

Systems and methods are provided for generating an accounting document. In one implementation, a computer-implemented method is provided. A message is received that includes operational data. An accounting notification is generated that includes the operational data using a first business object. The accounting notification is processed and the accounting document is generated using a second business object. The accounting document includes a number of posting lines corresponding to the operational data. The accounting document is processed and a set of third business objects is assigned to each posting line. The set of third business objects includes at least one general ledger account business object and a plurality of sub-ledger account business objects. One or more data processing tasks are delegated to the one of the third business objects that are assigned to the given posting line.

Systems and methods for generating an accounting document

A database is created for accounting purposes, which can be used to prepare financial statements according to various statutory accounting principles. According to one method, document data records are saved from posting documents to a document database. The document data records include a document header and a data part. The data part includes entries for at least two items each of which comprises a posting amount and an account assigned thereto. Calculation of totals from one or more posting amounts of the document data records are saved for the accounts assigned thereto. The totals are saved to totals entries of a totals table.

Systems and methods for creating a database for accounting purposes

A computer network architecture for making procurement-related information that has been generated on a transaction level available to data warehousing techniques is described. The network includes a transaction processing layer with at least one accounting component with a general ledger data base for centrally storing information contained in accounted-related data sets, a data warehousing layer and an additional data sourcing layer. A duplicator receives the data sets that will be or have been stored in the general ledger data base and delivers duplicates of those data sets that fulfill a predefined criteria in a procurement context. A source data base stores the duplicated data sets on a data line level. An extractor of the data sourcing layer interfaces with the data warehousing layer and selectively moves data contained in data lines or sets of data lines from the source data base to the data warehousing layer.

A data model for a supply chain is provided whereby individual working steps in a production process are defined as activities, and organized groups of such activities are defined as orders. Activities are allocated to no more than one resource and contain information concerning the start and finish time for the activity, any resource on which the activity is currently scheduled, and a list of alternative resources, if any. Activities are linked to each other via auxiliary objects, which contain information concerning the minimum and maximum time between activities. Orders may contain input and/or output interface nodes, representing the materials consumed and produced by the offer. Each output interface node representing a quantity of material created from one order is linked via an auxiliary object to respective input interface node or nodes from other orders that are scheduled to receive that material. Order anchors are defined whereby a planning algorithm can easily reference an order by its order number in a database table. Planning object anchors allow the planning algorithm to access all the orders for a given material, and resource anchors permit access to all activities scheduled for that resource.

Cross application time sheet for communicating with one or more enterprise management applications during time data entry

Growing community of inventors

Schwetzingen, Germany

Georg Dopf