Sap Se

Sap Ag

Torsten Buecheler

Knut Heusermann

Matthias Becker

Guang Yang

Olga Kreindlina

Oliver Berger

Christian Hohmann

Martin Haerterich

Dietmar Henkes

Sophie Kraut

Marcus Echter

Albert Neumueller

Xenia Rieger

Walter Zimmermann

Thomas Vogt

Stefan J Moeller

Steffen Witt

Mukesh Kumar

Berthold Wocher

Markus Wolf

Ingo Pfitzner

Mohit V Gadkari

Santhosh N

Thorsten Bender

Esther Landes

Thomas Witzel

Sascha Zimmermann

Stephan Naundorf

Karthik Narayanan Mohan

Kritesh Vasing

Marcel Steinleitner

Stefan Mazur

Carsten Scheuch

Disclosed is a mechanism to process business object IDs in inbound and outbound processing. The mechanism takes into account a mapping table, matching capabilities, number ranges, inbound error and conflict handling, inbound processing, outbound processing, initial load, and data migration.

Processing of business object identifiers in master data integration scenarios involving non-local identifiers

According to one general aspect, a method may include replicating, to a software-as-a-service application, a plurality of pieces of master data from a physically remote master database. The method may also include converting the plurality of pieces of master data into one or more pieces of local data of the software-as-a-service application. The method may include changing one or more of either the pieces of master data or the pieces of local data. The method may further include synchronizing the changed pieces of either master data or local data between the remote master database and the software-as-a-service application.

Integration scenario for master data with software-as-a-service system

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 an entitlement product business object.

Consistent interface for entitlement product

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 an opportunity business object.

Consistent interface for opportunity

Test data for a software services (e.g., a Web service) can be automatically generated from a user-provided specification. The user-provided specification may identify mandatory data elements along with data elements to be tested. Test categories may be defined to specify the type of test to be performed. A value provider may serve as a source of data values for the generated test data.

Generation of test data for web service-based test automation and semi-automated test data categorization

Growing community of inventors

Speyer, Germany

Torsten Buecheler