Choose Handling of User Related Data

Explanation

Data associated with the user IDs are handled in a special way during the creation of a company template.  This data can be extracted from:

• A selected company template. This is also the default option and the template marked as the default template will be automatically suggested.
• The source company.

The reason why a template is suggested as source for the user data is that a template should be as neutral as possible and should, in most cases, only contain users' identities that makes sense in any environment and for any company. It is also not very convenient to create a company template, which is supposed to be used in a component release, that contains user IDs that are not neutral. User (ID-related) data is often associated with the installation and setup of IFS Applications but can also differ between companies.

By default, the default template is suggested as the source for this type of data. For example, let us say that the standard template with identity STD is marked as the default template. As long as this template is used as the source, we can be more or less assured that all created templates have user identity related data that makes sense, is neutral, and can be used without problems when creating a new company.

It is possible, however, to select a source company as the source for the user ID related data, meaning that user ID related data from the selected company will be extracted. In this case, note that:

• If this template is exported and then imported in another database, then it might be impossible to create the users defined in the template unless the users have been added as Foundation1 and Oracle users, according to Foundation1 administration guidelines.
• The same applies if the template is exported and then defined in one or more components as standard templates, which are supposed to be automatically defined during the installation phase.

The following data is regarded as user-related data:

• User groups,  Logical Unit UserGroupFinance in Accounting Rules
• Users per Company, Logical Unit UserFinance in Accounting Rules
• User per User Group, Logical Unit UserGroupMemberFinance in Accounting Rules
• User Groups per Period, Logical Unit UserGroupPeriod in Accounting Rules
• Authority Classes, Logical Unit AuthorizeClassFinance in General Ledger
• Users per Authority Class, Logical Unit  GenLedUser in General Ledger
• Authority Combinations, Logical Unit AuthorizeCombFinance in General Ledger
• Invoice Authorizers, Logical Unit InvoiceAuthorizer in Invoice
• Credit Analyst, Logical Unit CreditAnalyst in Payment
• Credit Analyst User, Logical Unit CreditAnalystUser in Payment
• Write Off Codes, Logical Unit WriteOffCode in Payment
• Write Off Limit per User, Logical Unit WriteOffCodeLimit in Payment  

Prerequisites

If the source for user-related data is a company template, then company templates must exist.  

System Effects

This activity defines whether user-related data is taken from the source company or from a company template. 

Window

Create Company Template Assistant

Related Window Descriptions

Create Company Template Assistant

Procedure

• If the suggested source company template (the one selected as the default company template) is OK, then nothing has to be done.
• If you want to use a template other than the suggested one, place the cursor in the Template ID field in the Source for User Related Data area and click List to choose from available templates.
• If if you want to use the current company as source, click Source Company in the Source for User Related Data area.