Sap Ag

Sap Se

Herbert Hackmann

Kai Dehmann

Axel Herbst

Peter Surma

Jan Nolte-Boemelburg

Frank Rust

Legacy computing system archive files may have unique data structures designed for long-term data retention purposes and not particularly suited for data mining, querying, and other data collection functions needed to prepare certain types of reports. A report specific template may be created to facilitate the extract of specific legacy system data necessary to complete report that is stored in legacy system archive files. Once the data objects containing information relevant to the report have been identified, a hierarchical list of tables and fields of each table associated with each identified data object may be obtained from an external data source for further selection. Copies of the selected table and/or field data may then be extracted, compared, and merged with other data, such as other field and table data, obtained from other sources.

Standardized framework for reporting archived legacy system data

In general, the subject matter described in this specification can be embodied in methods, systems, and program products for mapping an object type to a document type. A computer system stores configuration templates that each identify a mapping of an object type to a markup language document type. The computer system displays a graphical user interface that permits a user of the computing system to select a configuration template. The computer system displays a list of the at least some attributes and, for each of the attributes, the associated markup language attribute or element that is identified by the selected configuration template. The computer system receives second user input that changes an association of one of the attributes so that the attribute is instead associated with a different markup language attribute or element. The computer system stores an updated mapping of the object type to the markup language document type.

Mapping an object type to a document type

In general, the subject matter described in this specification can be embodied in methods, systems, and program products for importing objects. A computer system processes structured electronic documents that define objects to be imported into a database in multiple phases. In a first phase, the computer system analyzes the structured electronic documents to determine whether the objects to be imported are related to one or more other objects that have yet to be stored in the database. If so, the computer system generates contextual information that defines the relationships between the objects. In a second phase, the computer system establishes relationships in the database between related objects using the contextual information.

Phased importing of objects

A computer-implemented method of configuring a database system for a global attribute search may include receiving a first user-actuated input in a distributed computing system that comprises multiple executable software applications. The software applications may process data objects in the system, and the data objects may have attributes and corresponding attribute values that are stored in two or more attribute repositories of an attribute system. The first user-actuated input may identify a user-selected attribute having an attribute name. The computer-implemented method may receive a second user-actuated input that identifies a user-determined alias name. The computer-implemented method may store in the attribute system an association between the user-determined alias name and the user-selected attribute name, such that during execution of a global search of attributes in the two or more attribute repositories, the attribute system may provide the user-selected attribute name in response to query input comprising the user-determined alias name.

Searching multiple repositories in a digital information system

A computer-implemented method of configuring a computing system may include receiving first user-actuated input selecting an existing service provider that processes data objects having a first data object type. The existing service provider may include at least a first class and a second class. Second user-actuated input may be received that identifies the first class and provides a replacement class to use in creating a new service provider to process data objects having a second data object type. An association may be stored in a service provider system between the second data object type, the existing service provider, the first class and the replacement class. During runtime, the service provider system may create the new service provider to process data objects having the second data object type by inheriting the second class from the existing service provider and incorporating the replacement class in place of the first class.

Growing community of inventors

Wiesloch, Germany

Herbert Hackmann