Abstract: A computer-implemented system may include an application platform comprising a platform model of a plurality of business objects, each of the business objects comprising a model of data and associated logic, and a public solution model comprising a subset of the platform model. The system may also include a business application, wherein a data model and access logic of the business application are defined based on the public solution model, and wherein the application platform is to provide services to the business application based on the data model, the access logic and the platform model.

Abstract: A system includes a data structure comprising a business object metadata model describing a generic business object model, executable program code of a transactional service to create a second data structure comprising a specific business object model based on the business object metadata model, and a persistent storage to store the second data structure comprising the specific business object model. Some aspects include creation of an electronic data structure comprising a business object metadata model describing a generic business object model, execution, using a processor, of program code of a transactional service to create a second electronic data structure comprising a specific business object model based on the business object metadata model, and storage of the second electronic data structure comprising the specific business object model in a persistent storage.

Abstract: Methods and systems to include transformation nodes in a business system are provided. A transformation node may provide controlled redundancy of data within the business object hierarchy. Transformation nodes may store data from core nodes without persistency, and permit different data presentation modes than for the core nodes. When a service call is placed to a transformation node, the transformation node may call corresponding services from associated core nodes.

Abstract: Methods and apparatus, including computer program products, provided default values for business objects. In one exemplary embodiment, there is provided a method for providing default values for attributes of business objects. The method may comprise receiving, at a first service provider, a call to instantiate a first business object. The method may then obtain a static default value of an attribute associated with the first business object. A second service provider may be called to determine a dynamic default value for the attribute based on the static default value. The first service provider may then be provided with the dynamic default value for use when instantiating the first business object.

Abstract: Systems, methods, computer program code, and means are provided for processing retrieve requests received in a business software system. Pursuant to some embodiments, a retrieve request is processed by identifying that the requested node is a retrieve transformation node, determining that the node relates to one of a currently selected business object and a secondary business object, and retrieving the node data from one of a persistence buffer and a secondary buffer based on the determining.

Abstract: A system for extending a business object used in a user interface. The system includes a service layer comprising the business object. The system also includes a models framework comprising a meta model including business data of the business object, wherein the meta model is extended for use in the user interface. The system further includes a processing engine for generating the user interface, wherein the processing engine provides a platform for extending the meta model for use in the user interface.

Abstract: A request originating at a frontend server for data encapsulated in a plurality of business objects is received. The plurality of business objects are stored in a business object layer at the backend server remote from the frontend server. In addition, the request originates from a user interface layer is received at a controller layer. A controller object is instantiated in the controller layer at the backend server. Nodes of the controller object are mapped to nodes in the plurality of business objects so that the controller object encapsulates the request data. Thereafter, transmission of data response to the request encapsulated by the controller object to the frontend server is initiated. Related apparatus, systems, techniques and articles are also described.

Abstract: A method and system provide a business scenario. The method includes executing a first deployment unit on a first application platform. The method includes replacing an original second deployment with an upgraded second deployment unit on an upgraded second application platform. The method includes executing the upgraded second deployment unit. The method including transmitting messages related to the business scenario over a communications link between the first deployment unit and the upgraded second deployment unit. The method includes storing master data related to the business scenario in a data storage.

Abstract: A tool for classifying and installing patches on terminals. Specifically, when a patch is designed, it may be automatically installed on a terminal if it does not have a direct impact on the terminal and is not in an area which relevant to the terminal user.

Abstract: A software tool for automatically executing relevant testing in an Application Platform. When an object in an Application Platform is changed, testing may be executed for the changed object as well as any related objects.

Abstract: Methods and apparatus, including computer program products, provided default values for business objects. In one exemplary embodiment, there is provided a method for providing default values for attributes of business objects. The method may comprise receiving, at a first service provider, a call to instantiate a first business object. The method may then obtain a static default value of an attribute associated with the first business object. A second service provider may be called to determine a dynamic default value for the attribute based on the static default value. The first service provider may then be provided with the dynamic default value for use when instantiating the first business object.

Abstract: A system for managing user interface events in user interface of a client system. The system includes a service layer including a business object. The system also includes an intermediate object layer comprising an intermediate object associated with the business object, wherein the intermediate object handles user interface messages raised by the business object and retrieves data from the business object for user interface. The system further includes a service manager that provides the retrieved data from the intermediate object for display on the user interface.

Abstract: A system for extending a business object used in a user interface. The system includes a service layer comprising the business object. The system also includes a models framework comprising a meta model including business data of the business object, wherein the meta model is extended for use in the user interface. The system further includes a processing engine for generating the user interface, wherein the processing engine provides a platform for extending the meta model for use in the user interface.

Abstract: Business object templates which include a plurality of hierarchically arranged entities and characterize services associated with the entities can be used to generate new business objects. These new business objects are generated based on projections of the business object template. In some variations, the business objects include a subset of the entities defined by the business object template. In other variations, the business objects include all of the entities defined by the business object template but with only certain entities being activated.

Abstract: Methods and systems to include transformation nodes in a business system are provided. A transformation node may provide controlled redundancy of data within the business object hierarchy. Transformation nodes may store data from core nodes without persistency, and permit different data presentation modes than for the core nodes. When a service call is placed to a transformation node, the transformation node may call corresponding services from associated core nodes.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having foundation layer functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: A system and method for temporarily saving entries to the fields of a business object is disclosed. A draft manager may receive a first field entry of a set of field entries from a first user for an active instance of a business object. The draft manager may store a first temporary save draft of the active instance. The draft manager may assign the first temporary save draft to the first user. The draft manager may discard the first temporary save draft if the active instance is saved by, for example, a second user.