Abstract: A core data services (CDS) explain agent receives a CDS explain request to generate an explanation with respect to a CDS data model. A CDS explain process is orchestrated for the CDS data model using a CDS explain handler of the CDS explain agent. A validator of the CDS explain agent and advanced business application programming (ABAP) dictionary metadata is used to validate if a CDS entity exists and if the CDS entity can be explained. Using a prompt assembler of the CDS explain agent, a large language model (LLM) prompt is assembled by combining multiple prompt snippets that satisfy the explanation with respect to a CDS data model. Using a CDS explain request processor of the CDS explain agent, the LLM prompt is transmitted to an LLM. Using a post-processor of the CDS explain agent, relevant information of a response from the LLM is extracted.

Abstract: According to some embodiments, systems and methods are provided including a memory storing program code; and one or more processing units to execute the program code to cause the system to: receive an aspect definition in a first format, the aspect definition including at least one aspect field; transform the aspect definition into aspect definition metadata, the aspect definition metadata is in a second format; store the aspect definition metadata; receive a view definition including a binding of the aspect definition and at least one view field; transform the view definition into view definition metadata, the view definition metadata is in the second format; and include the aspect definition metadata into a view, wherein activation of a view including an aspect links at the least one aspect field of the aspect definition to a corresponding at least one view attribute of the view definition. Numerous other aspects are provided.

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).