Abstract: According to some embodiments, information about a delta change package may be received. The delta change package may be, for example, associated with a customer extension project to be applied to content from a business service provider. A description tag for the delta change package may be received from a user, and the delta change package may be associated with the description tag in a repository of the business service provider.

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: 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 system and method for creating extension fields for business objects are described. In various embodiments, a system includes modules to display business processes and business objects thereof in graphical user interface screens. In various embodiments, the system propagates created extension fields to other business objects via metadata derived from selections in the graphical user interface. In various embodiments, a method for propagating extension fields from one business object to another business object via a data flow between the two business objects is presented. In various embodiments, the method receives instructions from a graphical user interface for the propagation of an extension field and sends instructions to a backend module to propagate the extension field from the source business object to the other business object.

Abstract: Systems and methods are provided for handling instances of providers in a plurality of frameworks. An instance of a first provider is created and registered to store a first change to a buffer. An instance of a second provider is created and registered to store a second change to the buffer. The buffer is checked to determine whether data consistency is guaranteed to result from the first and second changes. If data consistency is guaranteed, the first and second changes are committed to a database.

Abstract: A system may include presentation of a user interface including fields associated with a business object, reception, via the user interface, of an instruction to add an extension field to the business object, reception, via the user interface, of an indication of a reference field of the business object, determination of a binding of the reference field to the business object, and binding of the extension field to the business object based on the determined binding of the reference field to the business object.

Abstract: To improve access to message content in a message exchange system, a context object is defined for the message as an abstraction of the message content. The context object can be assigned to many different message communication interfaces, thereby allowing context objects to be reused across various interfaces. The context object provides access both to a message payload, and parts of a message other than the payload, such as technical data. Accordingly, access to message content for various tasks and applicability to a number of different message interfaces is improved.

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, wherein the original data type associated with the core data of the business object.

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 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: Systems and methods are provided for handling instances of providers in a plurality of frameworks. An instance of a first provider is created and registered to store a first change to a buffer. An instance of a second provider is created and registered to store a second change to the buffer. The buffer is checked to determine whether data consistency is guaranteed to result from the first and second changes. If data consistency is guaranteed, the first and second changes are committed to a database.

Abstract: In an embodiment, an XML data type may be extended with enhancements without creating a new data type. Enhancements to a “base” data type may be made in parallel such that multiple enhanced data types reference the same base data type. The enhanced XML data types can co-exist in XML schema with the base data types and each other without being redundant or conflicting with each other.

Abstract: To improve access to message content in a message exchange system, a context object is defined for the message as an abstraction of the message content. The context object can be assigned to many different message communication interfaces, thereby allowing context objects to be reused across various interfaces. The context object provides access both to a message payload, and parts of a message other than the payload, such as technical data. Accordingly, access to message content for various tasks and applicability to a number of different message interfaces is improved.