Run-time control

Runtime Version, Project Model and Optimization Phase per Company (tgbrg0105m000)

To create and maintain the run-time project models for a combination of a company and a version, use the Runtime Version, Project Model and Optimization Phase per Company (tgbrg0105m000) session.

To define a runtime version, project model and optimization phase, complete the following steps:

In the Company field, click New group and select the company in which the project models are stored that you want to use at run-time.
In the Version field, select a version that provides the project models that can be assigned as the run-time project model.
In the Project Model field, select a project model that provides the business processes for the Process Browser.
Click Save

Field	Description
Key fields for the Runtime Version, Project Model and Optimization Phase per Company (tgbrg0105m000) session
Default for Companies Without Run-Time Project Models	Wenn dieses Kontrollkästchen markiert ist,, the run-time project models in this company are for use in all companies for which no run-time project models are defined. You can only select this check box if you click the New group button.
Optimization Phase	The optimization phase used at run-time. Combined with the run-time version and run-time project model, it determines the business processes available in the Process Browser.
Main Project Model	Wenn dieses Kontrollkästchen markiert ist,, this is the main default run-time project model in case more than one run-time project model is defined for a company.

Hinweis

Only one main run-time project model can be defined per company. If a run-time project model is for use in all companies, you only need to select the Default for Companies Without Run-Time Project Models check box, instead of inserting it in all companies.

To change to another project model linked to your current company, on the Zusatzoptionen menu, click Change Project Model. The project model that is started is displayed in a new Process Browser window. The original Process Browser Window also remains open; this way, you can use more than one project model simultaneously.

Multi-logistic company

Multiple runtime project models dependent on the same logistic company will be solved by storing one or more project models per company [DS Org. Modeling].

Because of the multiplicity of companies and project models per logistic company, the default runtime company and default project model for this company will have to be stored in the DMB user settings. To use different project models per company, an entry must be created to allow the user to switch to another project model. This project model will be opened in a new instance of the DMB.

When the user changes the runtime company, and the selected project model is different from the one currently displayed in the DMB window, another instance of the DMB tree will be started.

The runtime version, project model, and phase are stored per company instead of by user. Only the current modeling version is still stored by user.

Starting an end user desktop using the Dynamic Menu Browser (DMB)

When an end user interface is started, the DMB uses the defined organization model. This section describes what must be done, using the organization model, to create an end user interface:

Find the runtime project model, the runtime current version, and the current phase for the current company the user is in. This can be the Default Project Model from the Baan User DEM Settings, or the main Project Model from the Runtime Project Models by Company. When the Default Project Model is not found within the current company, a message is given and the main Project Model for the current company is used.
Find the employee linked to the Baan User and the current Baan User DEM Settings.
Check whether the employee is linked to the current project model and optimization phase; if not linked, a message is given and the process is aborted.
To find the roles linked to the employee, use the runtime current version.
Find the business processes the user is authorized for according to his roles. This check has to be done in the repository and within the current project model because the authorization can be restricted within the project model.