| User Data (ttams1100s000) |  |
| Use this session to define the system data, defaults settings, authorizations, and templates applicable for the ERP LN user. The data is necessary for the user to start up a Tools application successfully. In this session you can also define the Tools user's address data. For example, the e-mail address, telephone number, fax number, and so on. If you have defined the data for the Tools user, click Close to return to the overview session. Use the commands on the Specific menu to create the user file in Tools. Note A textgroup authorization template must be defined for a normal user, otherwise the user is unable to read or write text in Tools. Related topics To create an ERP LN user To create the database user To define authorizations
Fields | Description
User | Specifies a user code to identify the user as a ERP LN user. The Tools user code is normally similar to the user code defined in the System Login field. However, you can define more than one Tools user for one system logon. When a user starts the bshell, by default the system starts with the Tools user code that is equal to the system logon code. You can start the bshell with a different Tools user code by setting the environment variable User. Example
System logon | ERP LN user
dave | dave
dave | dave_01
dave | dave_02
john | john
john | john_01
If the user with the system logon dave starts the bshell, by default he will be user dave in Tools. The user dave can fill the environment variable User with dave_01 or dave_02, to start as another Tools User. If the user with the system logon dave sets the environment variable USER to john or john_01 and tries to start the bshell, the message Not authorized to run as user john appears. In the same way, UNIX user john can only start the bshell as Tools User john or john_01, but not as dave, dave_01 or dave_02.
Name | Specifies the name of the Tools user.
Infor SSO User | Only if the Overrule System User parameter is checked in session Single Sign On (SSO) Parameters (ttams0100m000), this field appears. Fill in the name of the user as it is known in SSO Service. The Infor SSO User field can be left empty. In that case the value of the System Login field will be used during the Convert to Runtime. The Infor SSO User must be unique, for example an Infor SSO User can only be defined for one ERP LN user. During the convert to runtime this field is dumped into the `u<user>` file with the tag `sso_user`. Also a `$BSE/lib/user/sso/s<SSO_USER>` file is created which contains the Application User name. The format is `baanuser:<baan user name>`. This file will be used by the Bshell to make the mapping from SSO user to Application User. To prevent that an end user can tamper with the configuration to get more credentials, an extra file `$BSE/lib/sso.permissions` is introduced for BLogin. This file contains the permissions for SSO users to impersonate a certain OS user. The file is to be maintained by the system admin and must only be writable on OS level by the system administrator. It must be considered as having the same security status as for example the OS password file. If this file does not exist, BLogin will refuse to handle SSO requests.
Use Generic System User | In case the Overrule System User parameter is checked in session SSO Parameters (ttams0100m000), the Use Generic System User and System Login fields are enabled. If this field is checked the default OS-user identity that is used in SSO mode to run the binaries will be displayed. Any user can impersonate the Generic System User. After conversion this data is placed into the `sso_config` file as `generic_user:<Generic User>`.
System Login | Specifies the System Login code of the user. The user code entered in the User field is used as the default. Before installing Tools, a number of system logons have to be created by the system manager by using a system administration program. Tools checks if the logon code specified in this field exists in the password file. If not, a warning appears. Important! You can only specify system login codes that are in lower case. Note that the System Login field will be disabled when the Use Generic System User field is checked. This is the case when SSO is activated. The value of the displayed Generic System User field will than be used during Convert to Runtime.
User Type | Select the user type for the ERP LN user.
Package Combination | Define the user's package combination of the Tools software.
Package Combination | The description of the package combination.
Company | Specifies the default company that contains data that the ERP LN user will work with. Access to a company is only possible if the package combination of the Tools user and company are the same. There are exceptions to this rule. The company's package combination can only differ from the user's package combination under the following restrictions: Both package combinations must include the same library authorizations. The package VRCs in both package combinations can only be different if both package VRCs are derived from each other, or both package VRCs are derived from the same package VRC, and no changes in data definitions or domains have been made in the derived package VRCs. Note If the user is a normal user, the company authorization for the entered company is automatically generated. Related topics Section "Working with the company data" of the online manual Companies - overview.
Company | The name of the company.
Logistical Company | Specifies the logistic company that contains data that the ERP LN user will work with. This field will only be visible if the parameter for dynamic Logistic - Financial Company switching (ttaad0101s000) has been enabled. Related topics Section "Working with the company data" of the online manual Companies - overview.
Financial Company | Specifies the financial company that contains data that the ERP LN user will work with. This field will only be visible if the parameter for dynamic Logistic - Financial Company switching (ttaad0101s000) has been enabled. Related topics Section "Working with the company data" of the online manual Companies - overview.
Language | The code of the Software Language in which the user starts up the application.
Data Language | The code of the Data Language of the user. For more information, refer to Multilanguage Application Data.
Menu browser | If this check box is selected, the Menu browser is included in the user's WorkTop at startup.
Process Browser | If this check box is selected, the Infor ERP Process Browser (DEM) is included in the user's WorkTop at startup.
Infor ERP Workflow | If this check box is selected, the Infor ERP Workflow is included in the user's WorkTop at startup.
Startup Menu | The package code of the user's startup menu.
Startup Menu | The module code of the user's startup menu.
Startup Menu | The code of the user's startup menu.
Startup Menu | The description of the user's startup menu.
Remember the user's settings |
Message Mode | Specifies the user's Possible values. At runtime, users can change the message mode in the Options (ttams1100s100) session, which they can access by clicking Options... on the Tools menu of any overview session.
Standard Toolbar | Specifies where the users standard toolbar appears on a session's form. Users can maintain this field in the Options (ttams1100s100) session, which they can access by clicking Options... on the Tools menu of any overview session.
Application Toolbar (Icons) | Specifies where the user's application toolbar (icon buttons) appears on a session's form. Users can maintain this field in the Options (ttams1100s100) session, which they can access by clicking Options... on the Tools menu of any overview session.
Application Toolbar (Text) | Specifies where the user's application toolbar (text buttons) appears on a session's form. Users can maintain this field in the Options (ttams1100s100) session, which they can access by clicking Options... on the Tools menu of any overview session.
User Data | Specifies the Tools user's user data template. Note You create the templates in the User Data Template (ttams1110m000) session.
Default Text Groups | Specifies the Tools user's default text group template. Note You create the template in the Default Text Groups Template (ttams1121m000) session.
Default Text Fields | Specifies the ERP LN user's default text field template. Note You create the template in the Default Text Groups by Text Field Template (ttams1120m000) session.
Development Parameters | Specifies the Tools user's development parameters template. You create the template in the Development Parameters Template (ttams1150m000) session.
Device Preferences | Specifies the Tools user's device preference template.
Role | Specifies a role of the ERP LN user in an organization. Note You can link the Tools user to more than one role. Example A manager must have the same authorizations as his staff in the organization, in addition to his own authorizations.
Role | The description of the role.
Auth for all Package VRCs | If this check box is selected, the developer has default authorization to change software components in all package VRCs. If a package VRC is defined in the Developer Authorization Template (ttams1151m000) session, the developer will no longer be authorized for all package VRCs, but only for the defined VRC. If this check box is cleared, the developer is only authorized for the package VRC that is defined in the Developer Authorization Template (ttams1151m000) session.
Developer Authorizations | Specifies the code of the template in which the authorizations for the developer are defined. Note You create the template in the Developer Authorization Template (ttams1151m000) session.
Text Group Authorizations | Specifies the code of the template in which the text group authorizations for the ERP LN user are defined. A textgroup authorization template must be defined for a normal user, otherwise the user is unable to read or write text in Tools. Note You create the template in the Text Group Authorization Template (ttams1122m000) session.
Email Type | Enter the address type of the user's e-mail address. Only SMTP is supported.
Email Address | Enter the e-mail address of the recipient. ERP LN checks the validity of the e-mail address based on the e-mail type.
Telephone Number | This field is not yet supported by ERP LN.
Fax Number | This field is not yet supported by ERP LN.
Telex Number | This field is not yet supported by ERP LN.
SITA Address | This field is not yet supported by ERP LN.
SMS Address | This field is not yet supported by ERP LN.
Default Address Type | Enter the default address type for the user. ERP LN uses the default when an application does not specify how a message should be sent to the user. If you use a default message type, you must also supply an address for that type. You can also leave this field empty, meaning this user has no default message type.