1. Focus on Reports Session 3 LD_Pay & Distribution Adj History To print:
Right click
Choose “Print”
Change option “Print What?” from “slides” to “note pages”
Click ok
This report shows which PTAEO’s payroll and LD adjustment transactions were charged via the Labor Distribution module.
LD_Pay & Distribution Adj History

2. Organizations Carrying Out Org (Owning Org) (Org that owns project)
Incurred by Org (Expending Org) (‘O’ in PTAEO)
This report contains a lot of organization values, so let’s first review the different organizations and what they mean.
The Incurred by Org is the “O” in the PTAEO.
The Carrying Out Org is the owning org of the “P” in the PTAEO.
The Employee Org is the owning org of the employee’s assignment.
NOTE: All of the tabs show all org values for your reference.
Employee Org (Org that owns the Assignment)

3. The report data can be selected one of four ways:
1. All transactions whose “O” in the PTAEO matches the org number selected.
3. All transactions where the project’s owning org matches the org number selected.
4. All transactions for the selected project’s owning org and GM period.
2. All transactions for a selected employee.
The four ways data can be selected to appear on the report are:
By Incurred by (expending) Org (Default Tab): shows all transactions where the “O” in the PTAEO matches the org number selected.
By Employee: shows all transactions where the project’s owning org matches the org number selected.
By Project Carrying Out (owning) Org: shows all transactions where the project’s carrying out (owning) org matches the org number selected.
Payroll Expenditures by Period: shows all transactions for a selected GM Period and Project Carrying Out Org. The report is sorted and formated the way as the FM_Expenditure Detail by project report.
Each tab shows the same columns (e.g. employee name, assignment, etc). However, their location on the page varies by tab based on the input criteria you select. Generally speaking, the pay period start and end dates are shown in the report header, the input parameter of org or employee is shown in the page items, and the other information is shown in columns.

4. The input parameters for the ‘By Incurred by Org’ tab are:
the incurred by org, or the “O” in the PTAEO, that you want to select transactions for, and
the pay period between the start and end dates you want to appear on the report.
Note: Any transaction with a Pay Period whose Start Date is less than or equal to the start date parameter and whose End Date is Greater than or equal to the end date parameter will be selected to appear on the report. You may select a range to see more than one pay period.

5. This particular report was run by incurred by organization, and we see that in the page times. We also see the incurred by organization in the page header along with the payroll period begin and end dates.
The report shows the employee name and assignment number, the PTATEO, the pay period start and end date associated with the transactions, the transaction type and status, and an amount. In addition, it also shows the other associated org values and information that allows you to tie the transactions back to the FM_Expenditure Detail by project report where you can find the transaction that posted in the GM module.
NOTE: Both payroll and LD adjustments contain the pay period start and end dates to which it applies. The report selects all transactions, both Pay and Adjustments that were entered between the pay period start and end dates and INCURRED BY ORG you specify on the parameter screen. Transactions are sorted in chronological order by employee and assignment. In the transactions outlined in red, we see both a transaction type of pay, and two adjustments for the same pay period. The adjustments were made to credit the payroll charge to the original PTAEO, and move it to another PTAEO. NOTE: Both sides of the adjustment appear on this report because both have the same incurred by org, if they had different incurred by orgs, then you would only see one side (the reversing part) of the adjusting entry.
INTERFACE STATUS: On this report, the interface status is a page item on the report. If there is not associated value (it’s blank), it means there are no errors in the interface between LD and GM. Be sure to check the drop down box to make sure there are no errors.
NOTE: If the GM reference columns are blank, it means that the transaction has not yet posted in GM.

6. In our previous example, we saw two adjustments for pay period 25-Jun-2004 to 24-Jul-2004 that were transferred to GM.
Both of the adjustments were made to projects with a carrying out org of ‘40916’, and both were posted to GM in August.
By selecting the “Payroll Expenditures by Project” tab, we can see the GM transactions that posted for project carrying out org ‘40916’ in the ‘Aug-04’ project accounting period.

7. Here we see two page items, one for project at the top of the page, and one for project on the lower part of the page. Both projects show the associated adjusting entries.

8. The tab by Employee shows only those transactions associated with one or more employees, and for the pay periods within the start and end dates specified.

9. The Employee and the Employee’s Assignment Org are shown in the page items.
NOTE: If an employee has assignments owned by multiple organizations, you may wish to pull this page item down as a column to see all transactions for the employee.

10. Questions Regarding this report, are there any: Questions???
Frustrations????
Suggestions???