Abstract: A system includes a first non-transitory computer-readable storage medium and a second non-transitory computer-readable storage medium each having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform steps. The steps associated with the first non-transitory computer readable medium include generating a Service Adaptation Definition Language (SADL) definition for each of a plurality of business entity types, the SADL definition being based on an intermediate representation of each of the plurality of business entities, and publishing the SADL definition as a service of a SADL engine. The steps associated with the second non-transitory computer-readable storage include discovering the SADL definition and displaying, on a user interface, a representation of the SADL definition, the user interface configured to enable selection of two or more business entity types each associated with a different model layer framework.

Abstract: A system includes a first non-transitory computer-readable storage medium and a second non-transitory computer-readable storage medium each having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform steps. The steps associated with the first non-transitory computer readable medium include generating a Service Adaptation Definition Language (SADL) definition for each of a plurality of business entity types, the SADL definition being based on an intermediate representation of each of the plurality of business entities, and publishing the SADL definition as a service of a SADL engine. The steps associated with the second non-transitory computer-readable storage include discovering the SADL definition and displaying, on a user interface, a representation of the SADL definition, the user interface configured to enable selection of two or more business entity types each associated with a different model layer framework.

Abstract: A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system.

Abstract: Embodiments relate to computing, and in particular, to methods, apparatuses and systems for operating on a database. Certain embodiments implement a consumption services reference by an SADL design-time tool that allows users to create SADL use modes based on existing Business Objects (BOs), business object entities and associations. The consumption service can provide a design-time tool or user with indications of a particular BO entity's availability based on a particular consumption scenario within a given SADL mode. Indications of availability can be built into or referenced by the design-time tool to give users design-time feedback as to why a certain BO entity is not available. The indications of availability can be provided separately from a compiler or compiler functionality. The indications of availability can be also be reused by the compiler, thus reducing redundant checks and operations and decoupling the compiler and any design-time tool from the check logic.

Abstract: A back-end service adaptation system provides access to normalized data in a data repository for a consumer runtime environment sending a query request for denormalized data. The back-end service adaptation system can include a data access service layer, a parser layer, and a back-end service adaptation runtime layer. The consumer runtime can use a service adaptation definition language (SADL), and the parser and data access service can be configured to convert and translate the SADL request for the back-end service adaptation runtime layer.

Abstract: Systems and methods for providing application services through business object views. In one aspect, a definition of at least one business object (BO) is included in a metadata of an application platform. The definition includes descriptions of entities of the BO, and an identification of a service provider of the BO. The service provider instantiates the business object in response to an application service request. In a further aspect, a definition of a business object view (BOV) is included in the metadata of the application platform. The definition includes description of entities of the BOV, and an identification of the BO. The BO is a data source of the BOV. In one other aspect, a transformation describes a mapping of BOV entities to data source BO entities. A service corresponding to a core service of a BOV entity is called at the BO service provider based on the mapping.

Abstract: A back-end service adaptation system provides access to normalized data in a data repository for a consumer runtime environment sending a query request for denormalized data. The back-end service adaptation system can include a data access service layer, a parser layer, and a back-end service adaptation runtime layer. The consumer runtime can use a service adaptation definition language (SADL), and the parser and data access service can be configured to convert and translate the SADL request for the back-end service adaptation runtime layer.

Abstract: A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system.

Abstract: Systems and methods for providing application services through business object views. In one aspect, a definition of at least one business object (BO) is included in a metadata of an application platform. The definition includes descriptions of entities of the BO, and an identification of a service provider of the BO. The service provider instantiates the business object in response to an application service request. In a further aspect, a definition of a business object view (BOV) is included in the metadata of the application platform. The definition includes description of entities of the BOV, and an identification of the BO. The BO is a data source of the BOV. In one other aspect, a transformation describes a mapping of BOV entities to data source BO entities. A service corresponding to a core service of a BOV entity is called at the BO service provider based on the mapping.

Abstract: A method includes receiving compensation information of a particular employee of a first company from a database, receiving compensation information associated with a second company from a different database, and presenting in a graphical user interface (GUI) a graphical representation comparing the compensation information of the particular employee of the first company and the compensation information associated with the second company.

Abstract: A request originating at a frontend server for data encapsulated in a plurality of business objects is received. The plurality of business objects are stored in a business object layer at the backend server remote from the frontend server. In addition, the request originates from a user interface layer is received at a controller layer. A controller object is instantiated in the controller layer at the backend server. Nodes of the controller object are mapped to nodes in the plurality of business objects so that the controller object encapsulates the request data. Thereafter, transmission of data response to the request encapsulated by the controller object to the frontend server is initiated. Related apparatus, systems, techniques and articles are also described.

Abstract: A method includes receiving compensation information of a particular employee of a first company from a database, receiving compensation information associated with a second company from a different database, and presenting in a graphical user interface (GUI) a graphical representation comparing the compensation information of the particular employee of the first company and the compensation information associated with the second company.

Abstract: A method includes updating record content included in a database, extracting updated record content during a periodic time interval, producing an internal document that includes data representing the updated record content, producing a file that includes data corresponding to content of the internal document, and sending the file at the periodic time interval.