Abstract: Transporting of flexibility changes of customer content between tenants in a multi-tenant computing system can be performed by exporting customer content from a first tenant of the multi-tenant computing system, transporting the customer content exported from the first tenant to a second tenant of the multi-tenant computing system, importing the customer content into a staging area in the second tenant to enable a user associated with second tenant to access the customer content via the staging area based on a content extraction trigger, and activating selected customer content from the staging area in a productive component of the second tenant. The content extraction trigger can characterize an extraction of at least some of the customer content from the staging area. Related methods, systems, and articles of manufacture are also disclosed.

Abstract: A design-time status schema model is defined at design-time and includes a core status schema group and an. a status schema model. The status schema model includes a core status schema group and an extended status schema group. The status schema model also includes a precondition included in one of the status schema groups. The precondition identifies how a status affects whether an action included in the other of the status schema groups is to be allowed to be performed at runtime by a data object node instance having the status. Based on a status schema instance, the status of a data object node instance is monitored to determine whether the action is allowed to be performed by the data object node instance. In response to a determination that the action is allowed, enabling the action to be executed.

Abstract: A system may include acquisition of metadata defining a first object model including extensible entities, the first object model comprising an instance of a metaobject, acquisition of metadata defining an extension object model, the extension object model to extend at least one of the extensible entities of the first object model, and merging of the object model and the extension object to create metadata defining an extended object model, the extended object model comprising an instance of the metaobject.

Abstract: A quick buffer validity check can optionally be performed when a potential invalidity of the content of a buffer is identified. The identifying of the potential invalidity condition can include determining that a most recent lifecycle management event timestamp is more recent than a most recent buffer validity check timestamp for the buffer. To determine whether the buffer contents need to be refreshed, a list of the last changed timestamps for the constituent elements of the buffer can be compared to a new list. If the new list and the old list are not identical, the buffer can be rebuilt.

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: An adaptable business object can include a generic, content-free, and meaning-free skeleton business object, which can be used to create a new business object without requiring that a user be proficient in a development environment such as a software development kit (SDK). Definitions of a first field to be added to a header of the adaptable business object and a second field to be added to an item node of the adaptable business object can be received via a field extensibility tool, and a terminology tool can adapt the adaptable business object by storing metadata relating to the terminology of the business object in a metadata repository such that screen and section titles for at least one user interface screen supported by the new business object can be presented at runtime using the stored metadata.

Abstract: A system, a method, and a computer program product for adapting field extensibilities of business objects to changes in business processes are disclosed. An upgrade information for a business object model is received. Data and metadata associated with at least one field extension of at least one business object in the business object model to be migrated to an upgraded business object model are determined based on the received upgrade information. The determined data and metadata are migrated to the upgraded business object model.

Abstract: An extension node can be defined in a second layer of a software architecture for a first business object existing in a first layer and originally having an association with a second business object that is also in the first layer. The extension node can be defined to have an association with the second business object existing in a second layer of the software architecture. The association of the second business object can be altered from the first business object to the extension node so that at run time, metadata defining one or more nodes of the first business object and the extension node can be read from a metadata repository and a run time version of the first business object can be constructed at run time in a run time business object load based on the metadata.

Abstract: A delta handler can allow calculation of difference between an already generated set of backend entities and a set of new entities necessary to support a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture. Improved stability and robustness can be provided via an approach in which a target list of activities relating to creating, changing, or deleting of entities in backend repositories necessary to support the affected primary object is created and a sequence for performance of the activities in the target list is determined in a manner that can allow handling of such activities in a unified manner rather than on a per object type basis. Related methods, systems, articles of manufacture, and the like are described.

Abstract: A system may include reception of a definition of an extension field to be added to a business object node, generation of metadata for a data type enhancement object associated with the extension field, and generation of an ABAP dictionary proxy object based on the data type enhancement object, wherein the ABAP dictionary proxy object describes the extension field in a sub-structure of a first field of the ABAP dictionary proxy object.

Abstract: Transporting of flexibility changes of customer content between tenants in a multi-tenant computing system can be performed by exporting customer content from a first tenant of the multi-tenant computing system, transporting the customer content exported from the first tenant to a second tenant of the multi-tenant computing system, importing the customer content into a staging area in the second tenant to enable a user associated with second tenant to access the customer content via the staging area based on a content extraction trigger, and activating selected customer content from the staging area in a productive component of the second tenant. The content extraction trigger can characterize an extraction of at least some of the customer content from the staging area. Related methods, systems, and articles of manufacture are also disclosed.

Abstract: A system may include generation of extension metadata defining a functional extension associated with a business object, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the functional extension, an extension service associated with the functional extension is provided if it is determined that the service request is associated with the functional extension, and a core service associated with core data of the business object is provided if it is determined that the service request is not associated with the functional extension.

Abstract: A computer implemented method for providing code list extensibility includes providing a first code data type representation. The first code data type representation corresponding to a first code data type and having a first code value representation for at least one code value. The at least one code value associated with a corresponding code value issuing entity. The method may also include providing a second code data type representation. The second code data type representation corresponding to the first code data type and having a second code value representation for the at least one code value. The second code value representation including a unique identifier associated with the code value issuing entity. The method also may include mapping the first code data type representation and the second code data type representation based at least in part on the unique identifier associated with the code value issuing entity.

Abstract: A program and corresponding method allow for the enablement of customizable extension fields into a form template, independent of the field type of the extension field. New extension fields corresponding to section headers of the form template can be created and added to a user interface. A new extension field can drive the form template and be added to all applicable section headers in the form template from the user interface.

Abstract: Transporting of flexibility changes of customer content between tenants in a multi-tenant computing system can be performed by exporting customer content from a first tenant of the multi-tenant computing system, transporting the customer content exported from the first tenant to a second tenant of the multi-tenant computing system, importing the customer content into a staging area in the second tenant to enable a user associated with second tenant to access the customer content via the staging area based on a content extraction trigger, and activating selected customer content from the staging area in a productive component of the second tenant. The content extraction trigger can characterize an extraction of at least some of the customer content from the staging area. Related methods, systems, and articles of manufacture are also disclosed.

Abstract: Some aspects include reception of an indication of an extension field added to a node of a business object object model, and modification of a schema of a search engine index based on the extension field and before receiving an instruction to add the extension field to a search view.

Abstract: According to some embodiments, a business service provider may define a stable user interface anchor entity associated with a business object data structure. A reference field may be associated with the stable user interface anchor, the reference field representing a path to a persistent node of the business object data structure. An end user adaptation to a user interface may then be applied in connection with the business object data structure, the adaptation referencing the stable user interface anchor entity.

Abstract: A system may include generation of extension metadata defining an extension field of a core node of a business object, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the extension field, an extension service associated with a dynamic data type is provided if it is determined that the service request is associated with the extension field, wherein the dynamic data type is associated with extension data of the extension field and core data of the business object, and a core service associated with an original data type is provided if it is determined that the service request is not associated with the extension field.

Abstract: A system may include generation of extension metadata defining an extension node associated with a core node of a business object and extension fields associated with the extension node, and generation of a runtime metadata buffer comprising enhanced metadata, the enhanced metadata based on core metadata of the business object and the extension metadata. In some aspects, a service request associated with the business object is received, it is determined whether the service request is associated with the extension node, an extension service associated with the extension node is provided if it is determined that the service request is associated with the extension node, and a core service associated with core data of the business object is provided if it is determined that the service request is not associated with the extension node.

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.