Use this subtask to map accounts to a line in the CLIN Mapping subtask.
|
|
Note: You can enter data for a given project/CLIN in only one subtask, Accounts or PLC Mapping. If you manually upload data into both subtasks for a project/CLIN, the data in the PLC Mapping subtask is used and the data in the Accounts subtask is ignored. |
You can specify summary and/or detail level account ranges to a project/line item (CLIN). You can map accounts to each project/CLIN. If you map accounts to a project/CLIN, you cannot map PLCs. If no accounts or PLCs are mapped to a project/line item (CLIN), all PLCs and accounts charged to the project are mapped to the CLIN line.
Assume the following project structure:
|
Project Number |
Project Function |
Line Item (CLIN) |
|
C001 |
Top Level Rollup |
|
|
C001.01 |
Revenue and Billing Level |
|
|
C001.01.01 |
Task 1 Engineering Labor |
0001AA |
|
C001.01.02 |
Task 2 Support Labor |
0002AB |
|
C001.01.03 |
Task 3 Other Direct Costs |
0001AA |
If you have this setup and the Project Account Group (PAG) structure matches the transaction projects, there is no need to map accounts. However, there may be times when the project structure is more complex, or an error in setup is discovered after charges have been applied to the project. In that case, you may need account mappings.
Assume that the engineering labor PAG linked with C001.01.01 has some support labor. According to this project structure, labor should not be charged to this project and needs to be included in CLIN 0002AB. In such a case, you could use account mapping to ensure the file is built correctly. The following charges occurred:
|
Project |
Account |
Amount |
|
C001.01.01 |
ENG-01 |
50,000 |
|
C001.01.01 |
ENG-35 |
15,000 |
|
C001.01.01 |
SUP-10 |
10,000 |
|
C001.01.02 |
SUP-10 |
25,000 |
|
C001.01.03 |
DIR-15 |
60,000 |
The mapping could look like this:
|
Project |
CLIN |
Starting Account |
Ending Account |
|
C001.01.01 |
0001AA |
ENG |
ENZ |
|
C001.01.01 |
0002AB |
SUP |
SUZ |
In this example, you need to map billed amounts to C001.01.01/002AB and C001.01.01/0001AA because errors were made regarding the accounts charged to that project. You could map the other two projects, C001.01.02 and C001.01.03, in the CLIN Mapping subtask. They do not need to be mapped in the Accounts subtask because all costs charged to those projects belong to one CLIN.
|
|
Note: If you use this subtask to map one account to a project, you must map all accounts or they will not be included in the file. The exception is units, if you selected the Combine Units by Transaction CLIN radio button on the main screen. |
|
|
Note: You cannot map the same account or have overlapping accounts ranges for the same project. |
Enter, or use Lookup to select, the starting account number. You can enter summary or detail accounts.
Enter, or use Lookup to select, the ending account number. You can enter summary or detail accounts.
Changes to this screen update the PROJ_WAWF_ACCT table.
* A red asterisk denotes a required field.
