Abstract: An enterprise database server may store enterprise information. An application layer server, coupled to the enterprise database server, may use an application programming language (e.g., ABAP) to access the enterprise information. The application layer server may execute a plurality of domain runtimes, each associated with a domain service (e.g., transactional, SQL, analytical, search, etc.). The application layer server may also access, by a first domain runtime, a first data service entity in an infrastructure for data modelling (e.g., CDS) that enables data models to be defined and consumed on the enterprise database server. Similarly, the application layer server may access, by a second domain runtime, a second data service entity in the infrastructure for data modelling. According to some embodiments, the first data service entity includes a first provider contract and the second data service entity includes a second provider contract (different than the first provider contract).

Abstract: An enterprise database server may store enterprise information. An application layer server, coupled to the enterprise database server, may use an application programming language (e.g., ABAP) to access the enterprise information. The application layer server may execute a plurality of domain runtimes, each associated with a domain service (e.g., transactional, SQL, analytical, search, etc.). The application layer server may also access, by a first domain runtime, a first data service entity in an infrastructure for data modelling (e.g., CDS) that enables data models to be defined and consumed on the enterprise database server. Similarly, the application layer server may access, by a second domain runtime, a second data service entity in the infrastructure for data modelling. According to some embodiments, the first data service entity includes a first provider contract and the second data service entity includes a second provider contract (different than the first provider contract).

Abstract: The present disclosure involves systems, software, and computer implemented methods for ensuring seamless lifecycle stability for extensions to standard software products. One example method includes determining a requested change to a software feature of a software object. The software feature has been designated as an extensible software feature and is associated with a lifecycle stability contract that identifies aspects of the extensible software feature that are designated to remain stable across different releases of the software object. The lifecycle stability contract is used to perform a compatibility check for the requested change to determine whether the requested change complies with the lifecycle stability contract. The requested change is permitted in response to determining that the requested change complies with the lifecycle stability contract and the requested change is denied in response to determining that the requested change violates the lifecycle stability contract.