Use this subtask to enter combinations, using project/account wildcards, for charging by your projects. If you select the Accounts checkbox in the Limits group box in the Basic Info screen in the Project User Flow (Projects\Maintain\Project), the project/account combination must exist in the project/account wildcard before the transaction can be validated. If the combination does not exist, the transaction cannot be entered. If you do not select the Accounts checkbox, any account in the project account group can charge the project.
You can maintain this table using wildcards. Wildcards not only provide for a quicker initial setup, but also ease maintenance when new branches are added to existing projects or accounts. For example, if you enter a project of "1000" as "1000%," this means any lower levels of this project, such as "1000.001," that are added later to the system will be automatically included in this table.
In this screen, you can view the combinations to the level you desire or to receive a count on the combinations that have been created. New combinations will not be available for use until you save this screen.
This screen contains one block containing a table window and three subtasks that can be used in the following manner:
The Project Accts block contains a table window with fields where you can enter the project and the accounts that you want to validate. You can also review the number of projects and the number of accounts that will be included using the wildcard strings entered in the Project Wildcard String and Account Wildcard String fields.
Use the Sample Projects subtask to review the projects that will be included using the Project Wildcard String entered in the table window.
Use the Sample Accounts subtask to review the accounts that will be included using the Account Wildcard String entered in the table window.
The Wildcard Option subtask contains a table that explains the use of wildcards in this screen.
Use this screen after you have entered your projects and accounts and want to limit which accounts can charge a given project. You must use this screen any time a new project or account has been entered into the system that is not included in the wildcard strings.
How do I use the Wildcard feature?
Review the following examples for information in the use of wildcards. The wildcards are "%" and "_." Examples of their use are as follows:
% = All
%123 = Ends with 123
123% = Begins with 123
%123% = Contains 123
1_3 = Begins with 1 and ends with 3 and is 3 characters long
|
|
Note: The "%" wildcard denotes "any character, any length," while the "_" wildcard indicates "any single character." |
Use the table window in this block to enter the projects and accounts that you want to be valid for your project.
Enter a valid project for which you want to select accounts. You can enter wildcards in this field. See the "How do I use the Wildcard feature?" question in the FAQs section for more information on the use of wildcards.
Enter a valid account that you want to validate for this project. Wildcards can be used in this field. See the "How do I use the Wildcard feature?" question in the FAQs section for more information on the use of wildcards.
This non-editable field displays the number of projects that are included in a given project wildcard string after a value has been entered in this Project Wildcard String field.
This non-editable field displays the number of accounts that are included in a given account wildcard string. This field will be populated after an entry has been made in the Account Wildcard String field.
The system derives the number of possible combinations by multiplying the values in the Project Count field by the value in the Account Count field.
* A red asterisk denotes a required field.
Select this subtask link to open the Sample Projects subtask.
Select this subtask link to open the Sample Accounts subtask.
Select this subtask link to open the Wildcard Option subtask.
This screen updates the PROJ_ACCT_WILDCARD (Project Account Wildcard) table.
