BACKGROUND

In some instances, an application (e.g., Advanced Business Application Programming (ABAP) application) may manage a plurality of database objects of a database system. As such, consumers are unable to reliably access the database objects without using the application. For example, database-level access to the database objects may be frustrated by mutable application-managed implementation details, the lack of a well-defined access interface, application-based lifecycle management of the database objects, or reliance on session variables which are set during access via the application. In some other examples, database-level access may be prohibited as a security detail. Further, some consumers may be unable to utilize the application to access the database objects due to interoperability issues (e.g., a consumer may utilize an access protocol or application platform incompatible with the application).

