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: 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 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: 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 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: According to some embodiments, input may be received from a designer via a runtime authoring tool associated with a business service provider user interface page. The designer input defining at least one in-port to receive data from components and at least one out-port to provide data to components. A mashup component may then be embedded within the business user interface page in accordance with the input received from the designer. Moreover, a display of the user interface page to a client may be facilitated, including the embedded mashup component. Further, according to some embodiments the mashup component consumes business context data and combines and displays data received from a plurality of external data sources.

Abstract: According to some embodiments, a business user interface page associated with a business service provider may be established. The user interface page may have, for example, at least one in-port to receive data from components and at least one out-port to provide data to components. A mashup component may be embedded within the business user interface page, and may also have at least one out-port to provide data to components. A display of the user interface page to a client may then be facilitated, including the embedded mashup component, wherein the mashup component combines and displays data received from a plurality of external data sources.

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