Abstract: A current use context can be extracted based on concrete data related to a currently displayed user interface feature in a business software architecture user interface environment. Relevant related business objects and transactional data for concrete instances of a process or scenario relevant to the current use context can be identified and a specific business object instance can be determined from a plurality of business object instances related to a specific current instance of the process or scenario relevant to the current use context. At least one target user interface feature associated with the process or scenario can be pre-populated with at least one parameter specific to a current data entry state of the specific current instance of the process or scenario and displayed via a user interface.

Abstract: A business scenario landscape map can show a scenario-centric view of a business scenario landscape that includes business scenarios accessible to members of an organization and supported by a business software architecture. In the scenario-centric view, first user interface elements can be arranged to show a linear representation of business process features of a selected business scenario and a visual depiction of relationships between the selected business scenario and other business scenarios.

Abstract: A definition of a new user interface feature of a business software architecture supporting a business configuration used by an organization can be received and a rule in a scenario model of a business scenario can be accordingly modified to associate the new user interface feature with business process feature(s) of the business scenario. A selection of a business process feature received as a user interaction with first user interface elements arranged in a linear order in a navigation pane of a user interface to represent at least some of the plurality of business process features of the business process can result in the concurrent display via the user interface of a work frame comprising the new user interface feature.

Abstract: A single meta-model can include metadata defining a business scenario landscape that includes business scenarios accessible to members of an organization that are supported by a business software architecture. The metadata can include business process definitions and relationships between business processes. A user interface can present first, second, and/or third visualization layers based on the metadata. The first visualization layer can include first user interface elements forming a business scenario landscape map showing business scenarios and at least one relationship between the business scenarios. The second visualization layer can include second user interface elements displayed in a navigation pane concurrently with a work pane.

Abstract: Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature.

Abstract: A single meta-model can include metadata defining a business scenario landscape that includes business scenarios accessible to members of an organization that are supported by a business software architecture. The metadata can include business process definitions and relationships between business processes. A user interface can present first, second, and/or third visualization layers based on the metadata. The first visualization layer can include first user interface elements forming a business scenario landscape map showing business scenarios and at least one relationship between the business scenarios. The second visualization layer can include second user interface elements displayed in a navigation pane concurrently with a work pane.

Abstract: A graphical display can concurrently include a plurality of organizational roles within an organization and a plurality of business process features of at least one business process within a business configuration of a scenario landscape of the organization. After receiving input that includes an assignment of a linkage between one of the plurality of organizational roles and one of the plurality of business process features via the graphical display from an authorized administrator-level user at the organization, a meta-model that includes metadata that defines a global set of linkages between business process features and organizational roles for the business configuration of the scenario landscape of the organization can be updated based on the received input.

Abstract: A selection by a user of a first business process feature defining a starting point and a second business process feature defining an end point of a requested key performance indicator calculation can be received and a set of business objects related to a plurality of business process features that impact calculation of the requested key performance indicator can be determined based on the start point and the end point and on a meta-model of each of the related business process features. An algorithm for making the requested key performance indicator calculation can be generated based on metadata from retrieved from the meta-models, and transaction data can be retrieved from instances of business objects matching limiting criteria. A value for the requested key performance indicator calculation can be calculated based on the algorithm and the retrieved transaction data.

Abstract: A current use context can be extracted based on concrete data related to a currently displayed user interface feature in a business software architecture user interface environment. Relevant related business objects and transactional data for concrete instances of a process or scenario relevant to the current use context can be identified and a specific business object instance can be determined from a plurality of business object instances related to a specific current instance of the process or scenario relevant to the current use context. At least one target user interface feature associated with the process or scenario can be pre-populated with at least one parameter specific to a current data entry state of the specific current instance of the process or scenario and displayed via a user interface.

Abstract: A seed element can be determined by identifying a business object type underlying a current use context of a currently active application environment experienced by a user of a business software architecture. At runtime, a data context can be populated by applying a set of data derivation rules stored in a meta-model to compare the seed element to a plurality of business object instances retained in memory. Status and responsibility rules stored in the meta-model can be evaluated based on the data context to build a set of up-to-date process or scenario instance information. A process navigation user interface configuration presentable on a computer display device can display up-to-date instance information relating to the current use context for a business process or scenario instance related to the current use context.

Abstract: External transactional data relating to a completion status of an external business process feature of a specific business scenario instance supported by a business software architecture can be received and persisted at a repository. The business scenario can include business process features that include the external business process feature, which can be unsupported by a core software platform of the architecture. Navigation and work panes can be concurrently displayed to include first user interface elements arranged in a linear progression to represent the business process features in the linear sequence and second user interface elements corresponding to functionality related to a currently selected one of the plurality of business process features, respectively.

Abstract: A current transactional context of a user of a business software architecture can be detected, optionally in response to a guidance request received from the user. At least one matching business process feature related to the current transactional context can be determined by comparing the current transactional context with process metadata in a process repository, and the matching business process feature can be compared to scenario metadata defining a set of business process features that are part of each of a plurality of business scenarios within the business configuration to identify at least one matching business scenario containing the matching business process feature. In a user interface, the at least one matching business process feature and the identified matching business scenario that contains the at least one matching business process feature can be highlighted.

Abstract: A business scenario landscape map can show a scenario-centric view of a business scenario landscape that includes business scenarios accessible to members of an organization and supported by a business software architecture. In the scenario-centric view, first user interface elements can be arranged to show a linear representation of business process features of a selected business scenario and a visual depiction of relationships between the selected business scenario and other business scenarios.

Abstract: A single meta-model can include metadata defining a business scenario landscape that includes business scenarios accessible to members of an organization that are supported by a business software architecture. The metadata can include business process definitions and relationships between business processes. A user interface can present first, second, and/or third visualization layers based on the metadata. The first visualization layer can include first user interface elements forming a business scenario landscape map showing business scenarios and at least one relationship between the business scenarios. The second visualization layer can include second user interface elements displayed in a navigation pane concurrently with a work pane.

Abstract: Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature.

Abstract: A definition of a new user interface feature of a business software architecture supporting a business configuration used by an organization can be received and a rule in a scenario model of a business scenario can be accordingly modified to associate the new user interface feature with business process feature(s) of the business scenario. A selection of a business process feature received as a user interaction with first user interface elements arranged in a linear order in a navigation pane of a user interface to represent at least some of the plurality of business process features of the business process can result in the concurrent display via the user interface of a work frame comprising the new user interface feature.

Abstract: A user interface can concurrently display a work frame including business configuration user interface elements relating to a selected business process feature of a business scenario and a navigation frame including first user interface elements arranged within the navigation frame to represent at least some of a plurality of business process features of the business scenario. The business scenario can be part of a business configuration of a business software architecture used by an organization. A user input relating to a change to the business configuration can be received via the business configuration user interface elements, and a business configuration model storing the business configuration can be updated to reflect the received change.