Hi Roxiejeff1,
The help file in SL gives a pretty good description of what the PMA Integrity Check does. I have copied it below. You might run the process if you corrected some data directly in the tables and need to rebuild the project balances.
PMA Integrity Check (PA.BLD.00)
PMA Integrity Check (PA.BLD.00) rebuilds the project summary and rollup tables (PJACTROL, PJACTSUM, PJPTDROL, and PJPTDSUM) from the Project Transactions table (PJTRAN). The screen can also be used during the initial implementation of the Employee Utilization module to create historical data in the Employee Utilization Rollup table (PJUTLROL) from existing transactions. In addition, employee utilization history can be reconstructed following a change to utilization periods (e.g., periods are changed from monthly to weekly in Utilization Period Maintenance (UZ.PER.00)). A rebuild of all summary and rollup tables may also be necessary when changing fiscal periods and/or fiscal year-end. When these events occur, synchronizing summary and rollup records with transaction data can be time-consuming and costly. PMA Integrity Check (PA.BLD.00) accomplishes these tasks by zeroing out fields in records or, in some cases, deleting entire records, before rebuilding the tables. For this reason, the entire database must be backed up and all users must exit Microsoft Dynamics SL before proceeding.
Note: For detailed instructions on implementing the Employee Utilization module, see the “Setting up Employee Utilization” section of the Employee Utilization Help or user's guide.
Implementer’s Notes on Rebuilding PJUTLROL:
Before rebuilding the Employee Utilization Rollup table (PJUTLROL), the process performs the following checks:
· At the start of processing, the function deletes all PJUTLROL records and blanks out the utilization period from all PJTRAN records (PJTRAN.tr_id26 is set to b).
· System registration is examined to ensure that the Employee Utilization module (module code UZ) is registered.
· The process verifies that the Employee Utilization module has been activated (Activate Utilization Process is selected in Project Controller Setup (PA.SET.00)).
The process then reads only those PJTRAN records that have a fiscal period greater than or equal to the starting period. In order to qualify for further processing, the PJTRAN record must meet the following criteria:
· The PJTRAN record must contain a project ID (PJTRAN.project cannot be blank), which must exist in the Project Master table (PJPROJ) and have a Utilization Type assigned to it (PJPROJ.pm_id37 cannot be blank).
· The PJTRAN record must contain an employee ID (PJTRAN.employee cannot be blank).
· The account category of the transaction must have a transaction class of Labor, Revenue, or Adjustments (PJACCT.id5_sw must be L, R, or A).
The process determines the utilization period for qualifying transactions according to the following rules:
· If the transaction date falls within the date range of the fiscal period, the process uses the transaction date to determine the UZ period. This is accomplished by looking up the fiscal period of the transaction (PJTRAN.fiscalno) in the Project Fiscal Periods table (PJFISCAL) and comparing the transaction date of the transaction (PJTRAN.trans_date) to the starting and ending dates of the fiscal period (PJFISCAL.start_date and PJFISCAL.end_date, respectively). If PJTRAN.trans_date >= PJFISCAL.start_date and PJTRAN.trans_date <= PJFISCAL.end_date, the corresponding utilization period is retrieved from the Utilization Periods table (PJUTPER) and written to PJTRAN.tr_id26.
· If the transaction date falls outside the date range of the fiscal period, the following logic is applied:
– If the transaction date is before the first day of the fiscal period, the process uses the first day of the fiscal period to determine the UZ period.
– If the transaction date is after the last day of the fiscal period, the process uses the last day of the fiscal period to determine the UZ period.
For example, if fiscal periods are set up this way in Fiscal Period Maintenance (PA.FPM.00):
Fiscal Period
Start Date
End Date
01-2001
01/01/01
01/31/01
02-2001
02/01/01
02/28/01
03-2001
03/01/01
03/31/01
If utilization periods are set up this way in Utilization Period Maintenance (UZ.PER.00):
UZ Period
Start Date
End Date
2001-01
12/31/00
01/06/01
2001-02
01/07/01
01/13/01
2001-03
01/14/01
01/20/01
2001-04
01/21/01
01/27/01
2001-05
01/28/01
02/03/01
2001-06
02/04/01
02/10/01
2001-07
02/11/01
02/17/01
2001-08
02/18/01
02/24/01
2001-09
02/25/01
03/03/01
2001-10
03/04/01
03/10/01
2001-11
03/11/01
03/17/01
2001-12
03/18/01
03/24/01
2001-13
03/25/01
03/31/01
A transaction dated 1/15/01 and posted to fiscal period 02-2001 will be assigned utilization period 2001-05, while a transaction dated 3/15/01 and posted to fiscal period 02-2001 will be updated with utilization period 2001-09.
Once a qualifying PJTRAN record is updated with the correct utilization period, it updates PJUTLROL.