Abstract: Implementations of the present disclosure include receiving, by a parser, a view source file and an extension source file, the view source file defining a view on data stored in a database, the extension source file defining an extension to the view, parsing, by the parser, the view source file to provide a view abstract syntax tree (AST) and the extension source file to provide an extension AST, providing, by the parser, a merged AST based on the view AST and the extension AST, generating a mixed runtime data object using the merged AST, and providing the mixed runtime data object for consumption by at least one runtime component.

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.

Abstract: Methods, systems, and computer-readable storage media for include receiving, by a parser, a view source file and an extension source file, the view source file defining a view on data stored in a database, the extension source file defining an extension to the view, parsing, by the parser, the view source file to provide a view abstract syntax tree (AST) and the extension source file to provide an extension AST, providing, by the parser, a merged AST based on the view AST and the extension AST, generating a mixed runtime data object using the merged AST, and providing the mixed runtime data object for consumption by at least one runtime component.

Abstract: The present disclosure involves systems, software, and computer implemented methods for enabling data source extensions for individual customers of a cloud platform. One example method includes receiving an extension request, from a particular customer, to extend a data source used to populate an application output. A selection is received of at least one field to be included in a data source extension that extends the data source. Extensibility metadata is stored, in association with the particular customer, that defines the data source extension. The extensibility metadata identifies the data source, the particular customer, and the selected at least one field. A data request is received, from a client device of a user of the customer, for a field included in the data source extension. The data source extension is used to retrieve a field value for the field and the field value is provided in response to the data request.

Abstract: The present disclosure involves systems, software, and computer implemented methods for enabling data source extensions for individual customers of a cloud platform. One example method includes receiving an extension request, from a particular customer, to extend a data source used to populate an application output. A selection is received of at least one field to be included in a data source extension that extends the data source. Extensibility metadata is stored, in association with the particular customer, that defines the data source extension. The extensibility metadata identifies the data source, the particular customer, and the selected at least one field. A data request is received, from a client device of a user of the customer, for a field included in the data source extension. The data source extension is used to retrieve a field value for the field and the field value is provided in response to the data request.

Abstract: In one aspect, there is provided a method. The method may include performing, by a sequencer, one or more validations of a plurality of extensions to a core service of a business system; controlling, by the sequencer, execution of a sequence including the plurality of extensions and the core service to enable an action to be performed at the business system; and performing, by the sequencer, one or more post-processing checks of the plurality of extensions. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Software solutions in a business software framework can expose their data via web services, which can readily provide access to all non-customized fields of objects included as part of the default installation of the software solution. However, customer-added extensions, such as for example custom fields and the like, added to customize the software solution for a specific business or business use can be difficult to add to web services by a typical business user who lacks technical abilities. Described herein are approaches to enabling addition of custom fields to web services via an intuitive interface that does not require technical understanding of the software solution, the business software framework, web services, etc.

Abstract: A multi-tenant environment can support field extensibility via extension tables. An in-memory, columnar database can store a core table being extended as well as the corresponding extension table. Transactional and analytical processing can be performed on the extension fields. A business-objects-based system can take advantage of the technologies to provide greater flexibility, security, and performance improvements.

Abstract: An extension naming approach for avoiding naming collisions in de-normalized view on a business object can include accessing a reference field bundle, which includes reference field(s) corresponding to a core business object defined in a core software platform of a software architecture, from a metadata repository. A user can define an extension to the business object based on the core business object, for example via a development environment. The reference field(s) can include a defined path from a node in a peripheral object to a corresponding node in the core business object. A unique and reproducible name for the extension field can be generated based on the reference field, and the extension field with the unique and reproducible name can be added to the business object and to a data model of the peripheral object.

Abstract: This disclosure provides various embodiments of software for identifying and utilizing a generic update module with recursive calls. In one aspect, the software receives packed update parameters for updating a data record in a database, unpacks the update parameters, and updates the data record in the database using the unpacked update parameters. In some implementations, the update parameters may comprise a packed long byte string. The software may update the data record by returning the unpacked update parameters to a business application for database execution.

Abstract: A system may include presentation, to a user, of a consuming business entity including a reference field of a business object, reception of an instruction from the user to add an extension field to the consuming business entity based on the reference field of the business object, determination of a second consuming business entity including the reference field of the business object, and presentation of the second consuming business entity to the user.

Abstract: Software solutions in a business software framework can expose their data via web services, which can readily provide access to all non-customized fields of objects included as part of the default installation of the software solution. However, customer-added extensions, such as for example custom fields and the like, added to customize the software solution for a specific business or business use can be difficult to add to web services by a typical business user who lacks technical abilities. Described herein are approaches to enabling addition of custom fields to web services via an intuitive interface that does not require technical understanding of the software solution, the business software framework, web services, etc.

Abstract: A multi-tenant environment can support field extensibility via extension tables. An in-memory, columnar database can store a core table being extended as well as the corresponding extension table. Transactional and analytical processing can be performed on the extension fields. A business-objects-based system can take advantage of the technologies to provide greater flexibility, security, and performance improvements.

Abstract: In one aspect, there is provided a method. The method may include performing, by a sequencer, one or more validations of a plurality of extensions to a core service of a business system; controlling, by the sequencer, execution of a sequence including the plurality of extensions and the core service to enable an action to be performed at the business system; and performing, by the sequencer, one or more post-processing checks of the plurality of extensions. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: An extension naming approach for avoiding naming collisions in de-normalized view on a business object can include accessing a reference field bundle, which includes reference field(s) corresponding to a core business object defined in a core software platform of a software architecture, from a metadata repository. A user can define an extension to the business object based on the core business object, for example via a development environment. The reference field(s) can include a defined path from a node in a peripheral object to a corresponding node in the core business object. A unique and reproducible name for the extension field can be generated based on the reference field, and the extension field with the unique and reproducible name can be added to the business object and to a data model of the peripheral object.

Abstract: This disclosure provides various embodiments of software for identifying and utilizing a generic database query. In one aspect, the software identifies a generic query such that the generic query is independent of a particular database layout, and accesses a database table having a first layout using the generic query. In some implementations, the software may comprise a business application associated with a database, where the generic query is embedded in the business application without knowledge of the associated database's table layout. In other implementations, the generic query may be embedded in the software before the database table is created.

Abstract: This disclosure provides various embodiments of software for identifying and utilizing a generic update module with recursive calls. In one aspect, the software receives packed update parameters for updating a data record in a database, unpacks the update parameters, and updates the data record in the database using the unpacked update parameters. In some implementations, the update parameters may comprise a packed long byte string. The software may update the data record by returning the unpacked update parameters to a business application for database execution.

Abstract: This disclosure provides various embodiments of software for identifying and utilizing a generic update module with recursive calls. In one aspect, the software receives packed update parameters for updating a data record in a database, unpacks the update parameters, and updates the data record in the database using the unpacked update parameters. In some implementations, the update parameters may comprise a packed long byte string. The software may update the data record by returning the unpacked update parameters to a business application for database execution.

Abstract: A system may include presentation, to a user, of a consuming business entity including a reference field of a business object, reception of an instruction from the user to add an extension field to the consuming business entity based on the reference field of the business object, determination of a second consuming business entity including the reference field of the business object, and presentation of the second consuming business entity to the user.

Abstract: Systems and methods are disclosed for managing a lock on an object dependent upon a nested LUW. The disclosed systems and methods may include registering a lock manager with an LUW manager responsible for managing a nested LUW on a buffer. The nested LUW may comprise an inner LUW and an outer LUW. The systems and method may further include locking an object affected by the inner LUW of the nested LUW. The LUW manager may transmit to the lock manager any events pertaining to the inner LUW. The lock manager may be operative to determine, based on the events pertaining to the LUW received from the LUW manager, whether the lock should be retained or released such that the status of the lock is consistent with the state of the nested LUW.