This chapter describes each standard report and listing in Oracle Projects.
This chapter covers the following topics:
Report parameters let you specify the information to include in your report or listing. Most reports provide report parameters, and some parameters (such as the Order By option) are required before you can submit the report.
Some parameters let you specify a range of values to include only information within that range. These parameters use the format <parameter>Low to <parameter name>High (or From/To). For example, if you enter a range of customer names from BMW Motors to Global Shipping, Receivables will include these two customers and any customers whose names alphabetically fall within that range in your report. Alternatively, if you leave these parameters blank, Receivables will include information for all customers. To limit information to only one customer, enter the same customer name for both the Low and High parameters.
Important: You do not need to enter values for the range of customer names and customer numbers if both of these parameters are available for a report. We recommmend that you specify either a range of customer names or customer numbers when both of these options are provided.
Below is a list of report parameters that are common to many Oracle Projects reports and listings.
Agreement Number: Enter the agreement number to include in the report. Leave this field blank to show all agreements.
Class Category. To limit the report to one class category, enter the category. Otherwise, leave this field blank
Cost Budget Type. To limit the report to one cost budget type, enter the cost budget type. Otherwise, leave this option blank.
Customer: Enter the customer name of the customer you want to include in the report. Leave this field blank to show all customers.
Effective Date. Enter an effective date to report all entities that are active as of the date you enter here. Leave blank to submit the report for all effective dates.
Employee Name: To report on only one employee, enter the employee name. Otherwise leave this option blank.
Expenditure Category. To report on only one expenditure category, enter the expenditure category. Otherwise leave blank.
Expenditure Type: To report on only one expenditure type, enter the expenditure type class. Otherwise leave blank.
Expenditure Type Class: To report on only one expenditure type class, enter the expenditure type class. Otherwise leave blank.
From/To Date. Enter the date range for which you want to submit the report.
Function Name. To limit the output of this report to only one AutoAccounting function, enter the function. Otherwise, leave this field blank.
Incurred By Organization. If you want to submit the report only for employees in a particular organization, enter the organization. Otherwise, leave this field blank.
Job Discipline: To limit the report to one job discipline, enter the job discipline. Otherwise, leave blank.
Job Level: To limit the report to one job level, enter the job level. Otherwise, leave blank.
Job: To limit the report to one job, enter the job. Otherwise, leave blank.
Lookup Set. To limit the output of this report to only one AutoAccounting lookup set, enter the lookup set. Otherwise, leave this field blank.
Organization. To limit the report to one organization, enter the organization. Otherwise, leave this field blank.
Organization Type. To limit thereport to one organization type, enter the organization type. Otherwise leave this field blank.
Project Manager. To limit the report to one project manager, enter the project manager. Otherwise leave this option blank.
Project Member. To submit the report for only one project member's projects, enter the project member's name. Otherwise, leave this field blank.
Project Number. To limit the report to one project, enter the project number. Otherwise, leave this option blank. [changed]
Project Organization. To report on only one organization, enter the organization. Otherwise leave this option blank.
Project Role Type. The report includes only projects where the person specified in the Project Member report parameter is defined with this project role type. If you did not enter a value for the Project Member report parameter, this option has no effect.
Project Type: To limit the report to one project type, enter the project type. Otherwise, leave this option blank.
Revenue Budget Type. To limit the report to one revenue budget type, enter the revenue budget type. Otherwise, leave this option blank.
Rule Name. To limit the output of this report to only one AutoAccounting rule name, enter the rule name. Otherwise, leave this field blank.
Start Organization. Enter the organization from which you want this report to start down the organization hierarchy. If you leave this option blank, Oracle Projects uses the Start Organization you defined in the Define Implementation Options window.
Task Number. To limit the report to one task, enter the task number. Otherwise, leave this option blank.
Top Task. The number of the project task from which you want this report to start down the work breakdown structure.
Report headings provide general information about the contents of your report, such as the report title, date and time the report was created, your ledger name, page number, and parameters that you specified when submitting the report.
Some column and row headings are provided with the report description and sample output. This section lists headings that are common to many Oracle Projects reports and listings.
Agreement Number: The number of each agreement in your report.
Agreement Type: The type of each agreement in your report.
Customer Name: The name of each customer in your report.
Customer Number: The identification number for each customer included in your report. Each customer has a unique ID number.
Employee Name: The name of each employee in your report.
Employee Number: The employee number of each employee in your report.
Page: The current page number of this report. For example, "Page 2 of 6" indicates that you are viewing the second page of a six page report.
Report Date: The date that you submitted this report.
Start Organization. The name of the organization from which this report starts, then continues down the organization hierarchy
Start/End Date: The beginning and ending dates of an entity.
Use Oracle Projects standard reports and listings to review your system setup, keep track of your projects, and reconcile Oracle Projects to your general ledger.
You can run a single report (see: Submitting Requests) or submit a streamline request to run a predefined group of reports and processes at one time (see: Submitting Streamline Processes) If you have access to multiple operating units, and want to run a report by operating unit, you can select the operating unit for which you want to run the report.
To submit a standard request from the Submit Request window:
Navigate to the Find Requests window.
Select the Submit a New Request button
Select either the Single Request or Request Set option and click the OK button
Enter the name of the request that you want to submit.
Enter the name of the operating unit for this request
Note: If the MO: Operating Unit profile option is defined and valid, then the operating unit field will be populated with the value set for the MO: Operating Unit profile option. Similarly, if the MO: Default Operating Unit profile option is defined and part of the operating units assigned to MO: Security Profile profile option, the operating unit field will be populated with that default operating unit.
If the request or request set has parameters, enter the parameters in the Parameters window. Choose OK to save the parameters.
Choose Submit to submit your request. You can review the status of your request in the Concurrent Requests Summary or in the Requests window.
To cancel a concurrent request:
In the Concurrent Requests Summary, query the concurrent request number for your request. Select your request. Choose Cancel Request. See also: Cancelling Requests, Oracle E-Business Suite User's Guide.
To monitor status of a concurrent request:
You can view the status of your request in the Requests window by choosing View My Requests from the Help Menu. See Also: Monitoring Requests, Oracle E-Business Suite User's Guide.
You can run Oracle Projects processes and some reports in debug mode. Debug mode provides more details in the log file for debugging purposes, and creates a trace file for performance analysis.
To run a process or report in debug mode:
Set the profile option PA: Debug Mode to yes, and submit the process or report.
Related Topics
Submitting Streamline Processes
Defining Request Sets, Oracle E-Business Suite User's Guide
Submitting a Request, Oracle E-Business Suite User's Guide
Submitting a Request Set, Oracle E-Business Suite User's Guide
These implementation listings help you audit your implementation of Oracle Projects, so you can verify your entry of implementation data and document your implementation decisions.
You submit each of the implementation listings from the Submit Request window. Include the prefix "IMP:" when you enter the report name. See: Submitting Requests.
The implementation listings include the following:
AutoAccounting Rule Definitions
AutoAccounting Segment Rule Pairings
Employee Assignments by Organization
Labor Cost Rates Listing By Organization
Non-Labor Resources by Organization
Project Customer Relationships
Use IMP: Agreement Types to review all agreement types and their associated terms and revenue limit defaults. See also: Defining Agreement Types, Oracle Projects Implementation Guide.
Use IMP: AutoAccounting Functions to review a complete list of the parameters and transactions associated with a particular AutoAccounting function.
For each function, this report displays all of the possible parameters that AutoAccounting rules use to derive key flexfield segment values. The report also shows you all of the transactions related to the AutoAccounting function and whether each transaction is enabled or disabled.
Use IMP: AutoAccounting Lookup Sets to obtain a list of all the AutoAccounting lookup sets.
For each AutoAccounting lookup set selected, this report prints each possible intermediate value and its corresponding segment value.
Use IMP: AutoAccounting Rule Definitions to review the definition of a particular AutoAccounting rule. See: Defining AutoAccounting Rules, Oracle Projects Implementation Guide.
For each AutoAccounting rule selected, this report displays the type of its intermediate source (either a Constant, Parameter, or SQL Statement) and the corresponding value for that source. If the intermediate value source is a SQL statement, this report displays the text of that statement.
This listing also includes the segment value source (either the Intermediate Value or a Segment Value Lookup Set) that maps an intermediate value to the final segment value. If the segment value source is a lookup set, this report displays the name of that lookup set.
Use IMP: AutoAccounting Segment Rule Pairings to review all pairings of AutoAccounting rules with key flexfield segments.
For each function selected, this report displays each of the function's transactions. It also lists the AutoAccounting rule and key flexfield segment pairings for each transaction. See: Assigning Rules to Transactions, Oracle Projects Implementation Guide.
This report also displays the function's transactions without paired segments and rules.
IMP: Class Categories and Codes lists class categories and their associated class codes. See: Project Classifications (Class Categories and Class Codes), Oracle Projects Implementation Guide.
For each class category selected, this report indicates whether a class category is a mandatory part of project setup, whether AutoAccounting uses the class category, and whether the "pick one code only" restriction is assigned to a class category.
Use IMP: Credit Types to obtain a list of all credit types. See: Credit Types, Oracle Projects Implementation Guide.
Use the employee assignments reports to review all employees including their associated organization and job assignments. See Defining People, Oracle Projects Implementation Guide.
IMP:Employee Assignment. If you want a listing for a particular organization, use this report and specify that organization in the report parameters. Leave organization parameters blank to see all employees.
IMP:Employee Assignments by Organization. This report starts with a particular organization and reports down the organization hierarchy listing employees and their jobs. You cannot print a listing for a single organization using this report unless the organization is on the lowest level of the hierarchy.
Enter values for organization, job, job level, and/or job discipline, to limit the output of this listing to include only the specific employees you want to review.
Effective Date. Date Oracle Projects uses to identify active employee assignments. The report lists only active employees.
Use IMP: Event Types to obtain a list of all the event types and their classifications. See: Event Types, Oracle Projects Implementation Guide.
Use IMP: Expenditure Cost Rates to review the non-labor expenditure cost rates. You can print a listing for one or all expenditure categories, one or all expenditure types, and/or for a specified effective date. If an effective date is specified for the report, the report will list only expenditure cost rates that are active as of the date you enter.
See: Defining Cost Rates for Expenditure Types, Oracle Projects Implementation Guide.
Use IMP: Expenditure Types to review expenditure types. You can print a listing for one or all expenditure categories and/or for a specified effective date. If an effective date is specified for the report, the report will list only expenditure types that are active as of the date you enter.
See: Expenditure Types, Oracle Projects Implementation Guide
Use IMP: Implementation Options to review all values you entered in the Define Implementation Options window. See: Implementation Options in Oracle Projects, Oracle Projects Implementation Guide.
Use the IMP: Invoice Formats Listing to review invoice formats. See: Invoice Formats, Oracle Projects Implementation Guide.
For each invoice format listed, this report displays the grouping, the invoice format type, and the fields and text objects that comprise each invoice format line.
Format Name. To limit the report to one format name, enter the format name. Otherwise, leave this field blank.
Grouping Name. To submit the report for only one grouping name, enter the grouping name. Otherwise, leave this field blank.
Use IMP: Job Listing to review jobs. See: Jobs, Oracle Projects Implementation Guide.
Use IMP: Labor Cost Multipliers to review all labor cost multipliers. See: Labor Cost Multipliers, Oracle Projects Implementation Guide.
Use the Labor Cost Rates listings to review all employees and their cost rates, job level, job discipline, or labor costing rule. See: Labor Costing Rules, Oracle Projects Implementation Guide, and Defining People, Oracle Projects Implementation Guide.
IMP: Labor Costs Rates Listing. For each employee listed, this report displays the employee's active organization and job assignments, the assigned labor costing rule, and the hourly cost rate.
IMP:Labor Cost Rates Listing By Organization. This report starts at a specified organization and reports down the organization hierarchy listing employees and their labor cost rates. You cannot print a listing for a single organization using this report unless the organization is on the lowest level of the hierarchy.
Top Organization. (Cost Rates Listing By Organization only) The organization from which you want the Labor report to start down the organization hierarchy.
Effective Date. This listing includes all labor cost rates that are effective as of the date you enter here. Leave blank to include all labor cost rates.
This listing also includes all employee organization and job assignments that are active as of the date you enter here.
Job Level. To submit the report for employees at only one job level, enter the job level. Otherwise leave this field blank.
Job Discipline. To submit the report for only on job discipline, enter the job discipline. Otherwise, leave this field blank.
Labor Costing Rule. To submit the report for only one labor costing rule, enter the labor costing rule.
Use the IMP: Labor Costing Rules Listing to review labor costing rules See: Labor Costing Rules, Oracle Projects Implementation Guide.
Labor Costing Rule. To limit the report to only one labor costing rule, enter the labor costing rule. Otherwise, leave this field blank.
Use IMP: Non-Labor Resources by Organization to review all non-labor resources associated with a particular organization, expenditure category, or expenditure type. See Defining People, Oracle Projects Implementation Guide.
For each organization listed, this report displays the organization's non-labor resources and their corresponding expenditure types and expenditure categories.
Use IMP: Organization Hierarchy to review relationships between organizations. See: Defining Organization Hierarchies.
This report displays each organization in the hierarchy and its corresponding organization type. By using an indented-outline format, this report depicts the hierarchical relationships between the listed organizations.
Top Organization: The organization at the top of the hierarchy covered by this report.
Hierarchy Type: The type of hierarchy for which the report is printed.
Related Topics
Use the IMP: Organization Listing to review organizations. Organizations are work units that Oracle Projects uses for employee assignments, project and task ownership, and cost and revenue allocation.
This report displays each defined organization, its organization type, whether it is Internal or External, and its location. See: Organizations.
Related Topics
Organization Hierarchy Listing
Use IMP: Project Contact Types to review all project contact types. See: Defining Contact Types, Oracle Projects Implementation Guide.
Use IMP: Project Customer Relationships to review all project customer relationships. See: Defining Project Customer Relationships, Oracle Projects Implementation Guide.
Use IMP: Project Roles to review project roles. See: Project Roles, Oracle Projects Implementation Guide.
For each project role listed, this report indicates whether individuals with that project role are permitted to query labor costs.
Use IMP: Project Statuses to review the list of all project statuses. See: Project Statuses, Oracle Projects Implementation Guide.
Use IMP: Project Types to review all project types. See: Project Types, Oracle Projects Implementation Guide.
For each project type listed, this report displays whether the project type is direct or indirect, and whether costs are burdened. It also displays the default service type, default labor and non-labor bill rate schedules, default invoice formats, and the distribution rules assigned to the project.
Use IMP: Projects Lookups to review all lookup codes, meanings, and descriptions associated with a particular lookup type.
For each lookup type listed, this report displays whether the lookup type and its codes are system-defined or user-definable. It then lists all the lookup codes for a lookup type and their corresponding meanings and active dates.
Lookup Type. To limit the output of this report to only one lookup type, enter the lookup type. Otherwise, leave this field blank.
Use IMP: Projects Periods to review all project accounting periods. See: Defining GL and PA Periods, Oracle Projects Implementation Guide.
For each project accounting period, this report displays its start and end dates, and its closing status.
Closing Status. To limit the report to periods with one closing status, enter the closing status (Closed, Future, Never Opened, or Open). Otherwise, leave this field blank.
Use IMP: Revenue Categories to review revenue categories. See: Revenue Categories, Oracle Projects Implementation Guide.
For each revenue category listed, this report prints all the associated expenditure types and their corresponding expenditure categories.
Revenue Category. To limit the report to only one revenue category, enter the revenue category. Otherwise, leave this field blank.
Use IMP: Service Types to review all the service types. See: Service Types, Oracle Projects Implementation Guide.
Use IMP: Standard Rate Schedules to review the rates or markup percentages for an organization's standard rate schedules or for all standard rate schedules. See: Rate Schedule Definition, Oracle Projects Implementation Guide.
Standard Rate Schedule. To limit the report to one standard rate schedule, enter it. If you specify an Organization, the standard rate you enter must belong to that organization. Leave blank to submit the report for all standard rate schedules.
Use IMP: Transaction Sources to review the transaction sources you defined to identify data imported into Oracle Projects using Transaction Import. See: Transaction Import.
Use IMP: Units Definition to review all units of measure. See: Units, Oracle Projects Implementation Guide.
Use the project entry reports to verify that your have set up your projects correctly.
You submit each of these reports from the Submit Request window. Include the prefix "AUD:" when you enter the report name. See: Submitting Requests.
Related Topics
Use the AUD: Project Configuration report to review the configuration details of a particular project and verify that you have entered the data correctly.
This report lists details of project setup including: multinational information, revenue and billing information, project customers, customer contacts, project members, class categories, employee bill rates overrides, and non-labor bill rate overrides.
Use the AUD: Task Detail report to review task details for a specific task, or for all tasks of a project. Like the Project Configuration report, this report provides a comprehensive view of how you have defined your tasks.
Explode Subtasks.
Yes. Display information about each subtask of the specified task.
No. Display information for only top-level tasks of the project you specify in the Project Number option.
Display Task Details. Enter Yes if you want this report to display for each lowest-level task selected, the task organization, customer, and service type details. Enter No to exclude task details.
Use the AUD: Work Breakdown report to review the complete task structure of a particular project. This report lists all tasks and subtasks in hierarchical format with their respective start and completion dates. This report lists all tasks in an indented outline format so that you can easily identify the hierarchical relationship between tasks.
Use the transaction entry reports to audit data entry of expenditures.
You submit each of these reports from the Submit Request window. Include the prefix "AUD:" when you enter the report name. See: Submitting Requests.
Related Topics
Pre-Approved Expenditures Entry Audit
Use the AUD: Expenditure Batch Status report to view the status of expenditure batches. With this report you can identify expenditure batches that are ready to be released. You can also ensure that none of your expenditure batches go unprocessed by retaining a status of Working or Submitted.
This report groups expenditure batches first by status, then by expenditure type class. It lists the name of the person who entered the expenditure batch, and it prints the Control and Running totals for the batch. This report also provides summaries for each expenditure batch, for each organization, and for the entire report.
(Required) Organization Name. The organization for which you are submitting the report.
Expenditure Ending Date. To submit this report only for expenditure batches with a particular expenditure ending date, enter the date. Leave blank to submit the report for all expenditure batches.
Display Released Batch? Enter No or leave this field blank if you do not want this report to include expenditure batches with a status of Released. Enter Yes if you want this report to include expenditure batches of any status.
Use the AUD: Expense Report Entry report to review all expense reports within a specified date range for either a particular employee, all employees within an organization, or all employees within all organizations. An employee can run this report after submitting an expense report to use as a hard copy record of submission. Or, the controller of an organization may want to audit all the expense reports submitted by the employees in a particular organization.
For each expense report selected, the report displays the total expenses submitted by an employee and the total billable expenses as a percentage of the total expenses.
In addition to the Submit Request window, you can submit this report from the Enter Expense Reports window.
Week Ending Date From/To. Enter the range of week ending dates you want included in the report. The report includes only those expense reports with week ending dates on and between the dates you enter.
The AUD: Missing Timecards report includes employees that:
have not entered a timecard in the expenditure week
have entered a timecard, but have not submitted it (timecard has a status of Working)
have a rejected timecard, but have not corrected it and resubmitted it (timecard has status of Rejected)
The expenditure date range is required. To limit the report, you can enter any other parameters.
From/To Expenditure Ending Date. This report includes only those timecards with expenditure dates on or between the expenditure dates you specify.
Use the AUD: Pre-Approved Expenditures Entry Audit report to review preapproved expenditures. After you have entered all the expenditures for an expenditure batch, submit this report and use it to verify that all of the data you have entered is correct before you submit your expenditure batch. This report provides a summary for each expenditure batch that displays the total amounts for each expenditure type in the expenditure batch.
The total currency amounts are shown in the transaction currency.
(Required) Entered By. The report includes only those expenditure batches entered by the person you specify.
(Required) Expenditure Ending Date. The report selects only expenditure batches with the expenditure date you specify.
(Required) Sort Expenditures By: Choose the criteria by which to order the report output: alphabetically by Employee Name or Organization, or numerically by Employee Number.
Expenditure Batch. To review expenditures for only one expenditure batch, enter an expenditure batch. Otherwise leave this field blank.
Date Entered. To include expenditures entered on one particular date, enter it. Otherwise leave this field blank.
Expenditure Type Class. To limit the output of this report to expenditure batches having a particular expenditure type class, enter an expenditure type class. Otherwise, leave this field blank.
Expenditure Batch Status. To limit the output of this report to expenditure batches having a particular status, enter the expenditure batch status. Otherwise, leave this field blank.
Expenditure Batch Sort By. Choose the criterion by which the report sorts expenditure batches.
Use the AUD: Timecard Entry report to review all timecards within a specified date range for either a particular employee, all employees within an organization, or all employees within all organizations. For example, an employee can run this report after submitting a timecard to use as a hard copy record of submission. Or, the controller of an organization may want to audit all the timecards submitted by the employees of a particular organization.
For each timecard selected, the report displays the total time worked by an employee and the total billable time reported in the timecard as a percentage of the total time.
You can submit this request from the Submit Request window or from the Timecards window.
Week Ending Date From/To. Enter the range of week ending dates you want included in the report. The report includes only those timecards with week ending dates on and between the dates you enter.
After processing a payroll run using the PRC: Process Payroll Actuals process, you run the exception report to determine any payroll amounts that could not be processed by the program. The report allows you to determine the specific exceptions that may require a correction before finalizing the processing of a payroll run
You submit the PRC: Generate Process Payroll Actuals Exception Report from the Submit Request window. See: Submitting Requests
To generate the exception report, select the following parameters:
Operating Unit: Select the operating unit associated to the payroll organization you processed. The list displays all operating units to which the user has access in their security profile.
Costed Payroll Set ID: Select the number of the processed costed payroll set. The list includes all processed payroll sets for the selected operating unit. The list of values displays costed payroll set attributes to help you select the correct set number.
Payroll
Pay Period Start Date
Pay Period Date
Expenditure Organization: Select an organization if you want to limit the reconciled payroll data in the report to a single organization.
Employee: Select an employee if you want to limit the reconciled payroll data in the report to a single employee.
These reports provide a detailed view of the cost, revenue, and invoice activities of your projects. Use them to review your project expenditures, revenues, invoices, and expenditure item adjustments.
You can also use these reports to compare a project's performance against performance data for other projects within the same organization or across organizations. By submitting and analyzing the reports in this section regularly, you can monitor the performance of your projects.
The reports in this section describe how well your projects perform in terms of their budgets versus actual cost and revenue amounts.
These reports provide you with many different views of actual and budgeted project costs and revenues. For example, Oracle Projects reports revenue, cost, and budget summaries at the project level, the task level, the Work Breakdown Structure, the project level by category, and the task level by category. In addition, these reports display budgeted and actual costs and revenues for a specified PA Period, a PA Period range, or as project-to-date amounts.
The reports in this section also provide you with information about the status of your agreements, capital projects with no activity over a period of time, and employee activity by organization.
You submit each of these reports from the Submit Request window. The report names include a prefix of either "MGT:" or "AUD:". See: Submitting Requests.
Related Topics
Capital Project Summary Report
Inactive Capital Projects Report
Project Expenditure Adjustment Activity
The MGT: Capital Project Summary Report shows capital project amounts by project for the following amount groupings:
Expensed Amount
CIP Amount
Interfaced CIP Amount
RWIP Amount
Interfaced RWIP Amount
Total Amount
Class Category. Optionally, select a class category to view only specific project expenditures.
Class Code. Optionally, select a class code to view only specific project expenditures. To select a class code, you must first select a class category.
The MGT: Expenditures Detail Report shows expenditures detail for one project. The report shows each expenditure item's revenue amount, burdened cost amount, and billing status. It includes totals for labor items, non-labor items, and the entire project.
The report also separates expenditure items into the categories of labor and non-labor. Because labor costs may be sensitive information, the report displays labor costs only if the employee submitting the report is a cross-project user or a project member having a project role that allows access to view labor costs. If the employee submitting the report does not have access to view labor costs, the report does not display labor costs.
This report shows amounts in the project currency.
The Sort Expenditures By parameter is required both reports. If you submit the detail report, you must also enter a project number. You can enter any other parameters to limit the report.
Sort Expenditure Items By. Choose the order in which you want to view the report:
Employee. Alphabetically by the employee who submitted the expenditures.
Expenditure Item Date. Ascending date order by the date on which the expenditure item was incurred.
Expenditure Type. Alphabetically by expenditure type.
Task. In alphanumeric order by task number.
Vendor. Alphabetically by supplier.
Suppress Labor Costs? To exclude labor costs from the report, enter Yes. Enter No to include labor costs and revenue.
From/To Expenditure Item Date. The report lists expenditure items dated on or after the From Expenditure Date, and on or before the To Expenditure Date. Both parameters are optional.
Display Comments. To display any comments the expenditure items may have, enter Yes. Enter No to omit comments.
Task Number. Enter the task number of the particular task for which you want to review expenditure details. The task you enter here must be a lowest-level task of the project you specified in the Project Number option. Leave this option blank to include expenditure details for all tasks.
Billable/Capitalizable Flag Yes/No: Enter Yes if you want the report to show only billable/capitalizable expenditures, or No if you want it to show only non-billable and non-capitalizable expenditures. Otherwise, leave this option blank.
Items On Hold Yes/No: Enter Yes if you want the report to show only items on hold, or No if you want it to show only items that are not on hold. Otherwise, leave this option blank.
The MGT: Expenditures Summary Report gives an overview of expenditures for one project or many projects belonging to a specified organization or project manager.
For each project listed, this report selects the total labor hours reported, the total billable hours as a portion of the total hours, the total burdened costs, and the total revenue of the project.
The report also separates expenditure items into the categories of labor and non-labor. Because labor costs may be sensitive information, the report displays labor costs only if the employee submitting the report is a cross-project user or a project member having a project role that allows access to view labor costs. If the employee submitting the report does not have access to view labor costs, the report does not display labor costs.
This report shows amounts in the project currency.
You can submit this report for a particular period of time by specifying the start and end dates of the desired date range in the report parameters. If you do not specify a date range, this report displays project-to-date expenditure totals.
Sort Expenditure Items By. Choose the order in which you want to view the report:
Employee. Alphabetically by the employee who submitted the expenditures.
Expenditure Item Date. Ascending date order by the date on which the expenditure item was incurred.
Expenditure Type. Alphabetically by expenditure type.
Task. In alphanumeric order by task number.
Vendor. Alphabetically by supplier.
From/To Expenditure Item Date. Enter start and/or end dates of the desired date range. If you do not specify a date range, the report displays project-to-date expenditure totals.
Suppress Labor Costs? To exclude labor costs from the report, enter Yes. Enter No to include labor costs and revenue.
Use the MGT: Inactive Capital Projects Report to find capital projects with no activity for a specific period of time. You can use this list to identify projects for which you need to suspend capitalized interest calculation.
The report lists the project name and number, the last non-Allowance for Funds Used During Construction (AFUDC) activity date, and the suspension start date for each inactive project.
From Project Number / To Project Number. Enter the range of project numbers that you want to include. You can leave either or both parameters blank. See: Entering a Project Number Range Parameter.
(Required) Number of Inactive Periods: Enter the minimum number of periods (months) that a capital project must be inactive to appear on the report. This parameter is required.
The MGT: Project Asset Details Report shows capital project amounts by project, event, and asset.
Event Period Name. Select an event period to show amounts for a specific event period.
Project Organization. Select a project organization if you want to include projects only for a particular product organization.
Class Category. Optionally, select a class category to view only specific project expenditures.
Class Code. Optionally, select a class code to view only specific project expenditures. To select a class code, you must first select a class category.
Show Asset Details. By default, this value is set to Yes. Select No if you want to suppress the display of asset details information.
Use the AUD: Project Expenditure Adjustment Activity report to review all the adjustments made to expenditure items of a particular project. You can make adjustments to expenditure items. See: Adjusting Expenditures, Oracle Project Costing User Guide and Adjustments to Supplier Invoices, Oracle Project Costing User Guide.
Your accounting department can submit this report regularly to audit the kinds of expenditure adjustments being made for a project. For example, they can use this report to identify any expenditure adjustments that are unauthorized or against company policy.
The Project Number parameter is required. You can enter other parameters to limit the report.
Project Number. Enter the number of the project for which you want to review expenditure adjustment activities.
Task Number. Enter the number of the lowest level task whose expenditures want to review. Leave this field blank to review expenditure adjustment activities for all tasks.
From/To Adjustment Date. The report includes expenditure adjustments made on and after the From Adjustment Date, and on and before the To Adjustment Date. Both fields are optional.
Use the MGT: Transfer Activity report to review the expenditure item transfers into and out of a particular project. You can use this report as an audit tool to control project costs by identifying incorrect or unauthorized transfers for a project. You can also use this report to verify any expenditure item transfers that you perform.
For each specified project, this report shows you the expenditure items transferring into or out of the project and the transfer history of each of these expenditure items. For each expenditure item listed, this report displays the item's cost amount, its quantity, and either the destination project and task numbers or the originating project and task numbers, depending on the expenditure item's transfer direction.
You must enter a Project Number. You can enter other parameters to limit the report.
Project Number. Enter the number of the project for which you want to run the report.
Use the Project Financial Reports to review revenue and costs for your projects.
Note: A project's status determines whether it should be included in project financial reports. See: Project Statuses, Oracle Projects Implementation Guide.
You submit each of these reports from the Submit Request window. Include the prefix "MGT:" when you enter the report name. See: Submitting Requests.
Related Topics
Revenue, Cost, Budgets by Resources (Project Level)
Task - Revenue, Cost, Budgets by Resources
Revenue, Cost, Budgets by Work Breakdown Structure
Use the MGT: Revenue, Cost, Budgets by Resources (Project Level) report to review project revenue and costs broken down by resources for a particular PA Period and for the project-to-date. This report also displays budgeted revenue and cost amounts broken down into the same resources, but only under the project-to-date column since budgets are independent of PA Periods.
This report always lists revenue amounts by revenue budget type, but the categorization of costs depends on how a project is budgeted. If the project is budgeted by budget item at the project level, then this report lists costs by the cost breakdown code specified in the project-level budget. For the cost breakdown level of Organization and Organization/Expenditure Category and Job, this report lists costs by expenditure category.
If budget amounts are not entered at the budget-item level, then this report cannot determine the revenue or expenditure categories in which the amounts belong. For these cases, it displays the budget amounts under the revenue or expenditure category titled Uncategorized.
For each project selected, this report displays the project's total unbilled receivables amount and its total unearned revenue amount.
If a budget is categorized at the task level, this report shows only summarized information for categorized costs for the whole project across all tasks.
Although the report parameters are each optional, you must enter a value for at least one of the following: Project Organization, Project Manager, or Project Number. Enter any additional parameters to limit the report. If you do not enter a Period Name, the report uses the current PA period.
Use the MGT: Task-Revenue, Cost, Budgets by Resources report to review a task's revenue and costs broken down by resources for a particular PA Period and for the project-to-date.
This report is the task-level counterpart to the Revenue, Cost, Budgets by Resources (Project Level) report. Like the Project Level report, this report lists revenue by revenue budget type and costs by the cost breakdown code specified for the budget items budget. The only difference in this case is that the budget items budget must exist at the task level instead of the project level.
If a task has direct budgeted amounts, but it does not have budgeting by budget item, then this report cannot determine the revenue or expenditure categories in which the budget amounts belong. For these tasks, it displays the budget amounts under the revenue or expenditure categories entitled Uncategorized.
Although you can submit this report to run for all tasks belonging to a specified organization or task manager, it provides summaries only by task.
Although the report parameters are all individually optional, you must enter a value for at least one of the following: Task Organization, Task Manager, or Project Number. Enter any additional parameters to limit the report.
Use the MGT: Revenue, Cost, Budgets by Work Breakdown Structure report to review the tasks in a project's work breakdown structure and their budgeted and actual revenue, burdened costs, and labor hours. This report displays information for projects that have baselined budgets only. This report always displays project-to-date totals.
By default, this report displays all of a project's top-level tasks and their subtasks in an indented outline format that depicts the task hierarchy of the project's work breakdown structure. However, you can enter values for the report parameters that limit the output to top-level tasks only, to a specific top-level task only, or to one top-level task and all of its subtasks.
For each task selected, this report displays the task's actual and budgeted amounts side by side for easy comparison. It also lists the task's completion date, if one exists.
The top-level tasks have corresponding actual costs shown even though Oracle Projects only allows expenditure charges to a lowest-level task. These figures are a sum of the task's subtask amounts. This report rolls-up the amounts of the lowest-level tasks to each level in the project's work breakdown structure, all the way up to the project level itself. The project-level aggregates display on the last line of the report.
The budget amounts also roll-up. However, budget definition is not restricted to one level in Oracle Projects. The budget amounts in this report, therefore, might not originate from the lowest-level tasks. For example, a report can show budget amounts for the top-level task 1.0, but not for 1.0's subtasks. These figures, then, are not rolled-up amounts of the lowest-level tasks.
For each project listed, this report shows the total amount invoiced, the project's accounts receivable, its unbilled receivables, and its unearned revenue.
Although the report parameters are each optional, you must enter a value for at least one of the following in order for this report to return output: Project Organization, Project Manager, or Project Number. Enter any additional parameters to limit the report.
Explode Subtasks.
Yes. Display all subtasks under each top level task.
No. Display only top level tasks with amounts that are rolled up from the subtasks.
Use the billing review reports to review invoice information and agreements with your customers.
You can submit each of these reports from the Submit Request window. Include the prefix "MGT:" when you enter the report name. See: Submitting Requests.
Related Topics
Use the MGT: Invoice Review report to review the draft invoices of a particular project. You can use this report to verify your draft invoices before approving and releasing them for interface to Oracle Receivables for final customer invoice generation.
The report does not include partially written-off amounts on invoices.
This report begins by listing header information regarding the project. It also displays project totals, including the withheld retention and billed retention amounts, the unbilled receivables amount to date, the the currency amount of expenditure items on hold, and the budgeted revenue.
For each draft invoice selected, this report displays invoice header information including the customer name, the percentage of the total invoice amount for which the customer is responsible, withheld amount, whether it is a retention invoice, and the invoice status. It also displays the AR Invoice Number that is created when you interface your draft invoice to Oracle Receivables.
If you regenerate a draft invoice to credit a previously released invoice and create a customer credit memo, this report displays the number of the original approved invoice in the Credit of Number field.
Below the invoice header information, this report displays all the invoice line items of the draft invoice. The invoice line descriptions appear on the final customer invoice when it is generated in Oracle Receivables. You can change the look and content of your invoice line descriptions by regenerating the draft invoice after first selecting new labor or non-labor invoice formats for your project.
This report finishes by listing a summary of the revenue-distributed expenditure items and billing events that have not yet been billed for this project.
In addition to submitting the MGT: Invoice Review report from the Submit Reports window, you can also submit this report from the Review Invoices, Adjust Invoices, and Release Invoices windows by selecting Print Invoice Review.
The following parameters are required.
Invoice Status. To limit the report to a particular invoice status, select the invoice status. You can select to generate the report for all invoices or limit the report to invoices by their release, approval, and Oracle Receivables transfer status.
Display Details. Select Yes to display all expenditure items for that invoice line. Select No to display only invoice lines.
Display Unbilled Items. Enter Yes to include any items that have not been billed or are on hold. Otherwise enter No.
You can enter other additional parameters listed below to further limit the report.
Project Number. Select a project number to limit invoices reported by the selected project.
From/To Project Number. Enter start and end project numbers to limit invoices reported by a range of projects.
Project Status. Use this to limit the report to invoices for projects with the selected status. Alternatively, leave the default setting of All except Closed to display invoices for open projects in any status.
Project Closed After. If you selected a project status of All or All except Closed, enter a date to limit the report to invoices for projects closed after this date.
Draft Invoice Number. Enter the invoice number to limit the report to the specified invoice.
Start Organization. Select an organization to limit the report to invoices for projects of the selected organization.
Project Member. Select a name to limit the report to invoices for projects that this works for.
Project Role Type. Select a project role. Then, enter the name of the project member in this role to limit the report to invoices for projects on which the named person plays this role.
Use the MGT: Unbilled Receivables Aging report to review, by project, eligible revenue items that have not yet been invoiced, or those items not included on a released draft invoice. This report lists the receivables in four age buckets. You can specify the number of days for each bucket when you submit the report.
The report does not include partially written-off amounts on invoices. However, it does include amounts on canceled invoices that have been written-off completely. Retention amounts shown are net of billed amounts.
You can submit this report for an organization, in which case it groups all projects owned by the organization by their project managers. The report then displays summaries for each project manager.
If you specify a project manager in the report parameters and do not specify an organization, the report groups all projects by project manager regardless of the project-owning organization. This format provides you with the real total of unbilled receivables for a particular project manager.
Events relieve the oldest unbilled receivable as the invoices in which the events are billed are released. Revenue events age from their Completion Date if you choose Expenditure Item Date as your preference in the Age Receivables From report parameter.
Note: This report is not intended to be used to reconcile Oracle Projects with Oracle General Ledger and Oracle Subledger Accounting.
The Age Receivables From and the Number of days in Bucket parameters are required. You can enter any of the other parameters to limit the report.
Effective Date. The report ages unbilled receivables backwards starting from the date you enter here until it reaches the start date, which is determined by the value you enter for the Age Receivables From parameter.
Project Organization. Select an organization to limit this report for the projects in the selected organization. In this case, the report groups projects for the organization by project manager and displays summaries for each project manager by buckets.
Project Number. Select a project number to limit the report to unbilled receivables for the selected project.
From/To Project Number. Enter project numbers that define the range of projects for which the report must display unbilled receivables.
Project Status. Select a project status to limit the report to projects with the selected status. Alternatively, leave the default setting of All except Closed to display unbilled receivables for open projects in any status.
Project Closed After. If you selected a project status of All or All except Closed, enter a date to limit the report to unbilled receivables for projects closed after this date.
Project Manager. If you specify a project manager and do not specify an organization, the report groups all projects by project manager regardless of the project-owning organization. This provides the real total of unbilled receivables for a particular project manager.
Age Receivables From. Select the end date for aging unbilled receivables for this report. This can be the PA date, GL date, or the expenditure item date. If you select expenditure item date as the start date for aging unbilled receivables, for revenue items this translates to the completion date of the revenue event.
Number of days in Bucket 1/2/3. Enter the number of days that you want in each bucket. For example, if you have entered 30/60/90 for the first, second, and third buckets respectively, the first bucket displays unbilled receivables that are less than 30 days old, the second bucket displays those between 30 and 60 days old, and the third displays those between 60 and 90 days old. The fourth bucket displays unbilled receivables that are beyond 90 days old. Billing events relieve the oldest unbilled receivable when you release the invoices created for billing them.
Use the MGT: Agreement Status by Customer report to review the status of your customer agreements. The report includes an agreement's revenue limit, expiration date, and the amounts allocated, accrued, and invoiced against it.
This report groups all the agreements by customer, then orders them by the value that you enter in the Sort By report parameter. It also includes summaries for each customer and for the entire report.
The Sort By parameter is required. You can enter any other parameters to limit the report.
Sort By. Choose the order within each customer in which you want to review the report:
Agreement Number. Ascending alphanumeric order by the agreement number.
Amount Not Allocated. Ascending numeric order, by the funding not allocated.
Expiration Date. Ascending date order by the expiration date of each agreement.
Revenue Backlog. Ascending numeric order by the revenue backlog (amount allocated minus the amount accrued) of each agreement).
Revenue Limit. Ascending numeric order by the revenue limit of each agreement.
These reports show how effectively your organization turns earned revenue into cash. These reports help you identify any bottlenecks in your revenue and invoice processing flow, and they alert you to problems your organization may have in collecting on invoices.
You submit each of these reports from the Submit Request window. The report names include a prefix, either "FLW:" or "MGT:" See: Submitting Requests.
Related Topics
Invoice Flow Detail and Invoice Flow Summary
Use the invoice flow reports to review flow information about project invoices through Oracle Projects.
FLW: Invoice Flow Detail. This report groups invoices by invoice status, allowing you to quickly identify where your draft invoices currently are in the invoice processing flow. You can specify a transfer status or a currency amount to report on a subset of invoices.
FLW: Invoice Flow Summary. You can use this report to identify by currency range how many invoices are in each stage of the invoice processing flow. After reviewing this report, if you want to see the specific draft invoices that comprise the invoice summaries, submit the Invoice Flow Detail report and specify the same date range.
You must specify a Start Organization or Project Member when you submit these reports. Enter any other parameters to limit the report.
Project Member. To submit the report for only one project member's draft invoices, enter the project member's name. Otherwise, leave this field blank.
Project Role. The report includes only draft invoices of projects where the person specified in the Project Member report parameter is defined with this project role. If you did not enter a value for the Project Member report parameter, this option has no effect.
Creation Date To/From. The report includes draft invoices created on or after the Creation Date From report parameter, and draft invoices created on or after the Creation Date To report parameter. Both fields are optional. Leave both blank to submit the report for draft invoices regardless of their creation dates.
Include Released Invoices. Enter Yes if you want the report to include draft invoices with a status of Released. Enter No to exclude released invoices from the report.
Include Amount Ranges. Only invoices with amounts in the amount range you specify will be reported. Select All to include draft invoices regardless of invoice amount.
Invoice Status. The report includes only invoices with the status you select.
Accepted. Invoices that have been interfaced to and tied back from Oracle Receivables.
All. All invoices regardless of invoice status.
Approved. Invoices that have been approved.
Rejected. Invoices that have been rejected by Oracle Receivables.
Rejected in Transfer. Invoices that have been rejected during the interface to Oracle Receivables.
Transferred. Invoices that have been successfully interfaced to, but not yet accepted by, Oracle Receivables.
Unapproved. Invoices that have not yet been approved.
Use the MGT: Potential Revenue Summary report to identify projects that cannot fully accrue revenue due to a hard funding limit encountered. This report shows you the total potential revenue, the total amount accrued, and the difference between these two values for a project's expenditure items incurred through the date you specify in the report parameters.
When the total available amount of an agreement's funding is insufficient to accrue revenue on all of a project's expenditure items, Oracle Projects accrues as much as possible against the potential revenue. This report alerts you to the amount of additional revenue you could accrue with more funding.
Note: This report is not run for projects with the Cost/Event distribution rule.
You must provide a value for at least one of the following parameters: Project Organization, Project Manager, or Project Number. Enter any other parameters to limit the report.
Accrue Thru Date. The report includes only expenditure items dated on or before the Accrue Thru Date you enter.
Include Closed Projects? Enter Yes if you want the report to include the potential revenue of all projects regardless of project status. Enter No if you want to report to exclude the potential revenue for expenditure items of projects with a Closed status.
Use the MGT: Project Billing Status report to review the billing status of your projects, and identify projects that have not yet been billed.
For each project listed, this report displays the days since the last billing date, the date of the last billing, the next scheduled billing date, the amount of any pending invoices, and the amount of unbilled receivables. The last page of the report defines the columns in this report.
You must specify a Start Organization or a Project Member when you submit this report. You can enter any other parameters to limit the report.
Project Role. The report includes only projects where the person specified in the Project Member report parameter is defined with this project role. If you did not enter a value for the Project Member report parameter, this option has no effect.
Days Since Last Billing. The report includes projects only when the number of elapsed days since the latest invoicing for the project is greater than or equal to the number you enter here. Leave this option blank to include all projects regardless of the last invoice date.
Only Report Never Billed. Enter Yes to include only projects that have never been invoiced. Enter No to include projects regardless of invoicing status.
Billing Method. To report on projects with one particular billing method, enter the billing method. Leave this option blank to include projects regardless of billing method.
Thru Next Bill Date. The report includes projects with next billing dates that are on or after the date you enter here. Leave this option blank to include projects regardless of their next billing dates.
Use the FLW: Revenue Flow Detail report to review the flow of draft revenue through Oracle Projects. This report shows all draft revenues generated within a specified PA Period Date range. The draft revenues are sorted by their transfer statuses, thereby allowing you to quickly identify where revenue currently is in the revenue processing flow. If a draft revenue is rejected by the process PRC: Generate Revenue Accounting Events, then this report displays the reason for the rejection. It also provides action hints to help you resolve any problems and continue the flow of revenue through the system.
The From PA Date parameter and the To PA Date parameter are required. You can enter any other parameters to limit the report.
From/To PA Date. Enter the PA Period date range for which you want to submit the report.
Revenue Transfer Status. To limit the report to one particular transfer status, enter the status. Otherwise, leave this field blank.
Include Accepted Revenue. To include in the report revenues with a transfer status of Accepted, enter Yes. Enter No to exclude Accepted revenues.
Use these reports to verify that your interface of information to another Oracle product was complete and accurate.
You submit each of these reports from the Submit Request window. Include the prefix "AUD:" when you enter the report name. See: Submitting Requests.
Related Topics
Interfaced CIP/RWIP Amounts by FA Period
Use the AUD: Cost Audit Report to review cost distribution lines that are successfully accounted in final mode in Oracle Subledger Accounting. This report includes labor costs, usage costs, miscellaneous costs, inventory costs, work in process costs, burden costs, total burdened costs, supplier cost adjustments, and expense report adjustments. The report shows the final subledger accounting for the distribution lines. This report displays items by the expense account number and includes information about the item and liability credit account.
Oracle Projects uses the post-accounting programs in Oracle Subledger Accounting to determine the accounts to show in the audit report. For additional information on maintaining post-accounting program assignments, see: Implementing Oracle Project Costing, Oracle Projects Implementation Guide.
Note: For historical (prior to Release 12) transactions that you have not migrated to Oracle Subledger Accounting, the audit report shows the accounts that Oracle Projects derived using AutoAccounting and interfaced to Oracle General Ledger.
Amounts on this report are shown in the functional currency.
All parameters for this report are optional. However, entering no parameters or specifying only the interface date range can result in poor performance. Specifying the GL account range or the GL period name rang (or any combination of these parameters) significantly improves the performance of this report.
From/To Account. Enter the range of GL account numbers for the cost distribution lines that you want to appear in the report.
From/To Period. Enter the names of the starting and ending GL periods within which you want the report to select cost distribution lines.
From/To Accounting Event Date. Enter a date range to limit the distribution lines that the report displays. The report displays the date that Oracle Projects successfully generated a cross charge accounting event.
Use the AUD: Cross Charge Audit Report to review cross charge distribution lines that are successfully accounted in final mode in Oracle Subledger Accounting. The report shows the final subledger accounting for the distribution lines. This report displays items by the debit account number and includes information about the item and the credit account.
Oracle Projects uses the post-accounting programs in Oracle Subledger Accounting to determine the accounts to show in the audit report. For additional information on maintaining post-accounting program assignments, see: Implementing Oracle Project Costing, Oracle Projects Implementation Guide.
Note: For historical (prior to Release 12) transactions that you have not migrated to Oracle Subledger Accounting, the audit report shows the accounts that Oracle Projects derived using AutoAccounting and interfaced to Oracle General Ledger. For these transactions, the report derives the audit report information from the cross charge distribution lines in Oracle Projects.
Amounts on this report are shown in the functional currency.
All parameters for this report are optional. However, entering no parameters or specifying only the interface date range can result in poor performance. Specifying the GL category, the GL account range, or the GL period name range (or any combination of these parameters) significantly improves the performance of this report.
GL Category. Select the GL category that you want to include in the report.
From/To GL Account. Enter the range of GL account numbers for distribution lines of cross-charged transactions that you want to appear in the report.
From/To GL Period. Enter the names of the starting and ending GL periods within which you want the report to select distribution lines of cross-charged transactions.
From/To Accounting Event Date. Enter a date range to limit the distribution lines that the report displays. The report displays the date that Oracle Projects successfully generated a cross charge accounting event.
Use the AUD: Revenue Audit Report to review a listing of the revenue distribution lines that are successfully accounted in final mode in Oracle Subledger Accounting. The report shows the final subledger accounting for the distribution lines. The revenue distribution lines are reported by revenue account and by project. The report also displays the project revenue unbilled receivable and unearned revenue amounts.
Oracle Projects uses the post-accounting programs in Oracle Subledger Accounting to determine the accounts to show in the audit report. For additional information on maintaining post-accounting program assignments, see: Implementing Oracle Project Billing, Oracle Projects Implementation Guide.
Note: For historical (prior to Release 12) transactions that you have not migrated to Oracle Subledger Accounting, the audit report shows the accounts that Oracle Projects derived using AutoAccounting and interfaced to Oracle General Ledger.
All parameters for this report are optional. However, entering no parameters or specifying only the interface date range can result in poor performance. Specifying the GL account range, or the GL period name range (or any combination of these parameters) significantly improves the performance of this report.
From/To GL Account. Enter the range of GL account numbers for the revenue distribution lines that you want to appear in the report.
From/To GL Period. Enter the names of the starting and ending GL periods within which you want the report to select revenue distribution lines.
From/To Accounting Event Date. Enter a date range to limit the revenue distribution lines that the report displays. The report displays the date that Oracle Projects successfully generated a revenue accounting event.
Use the AUD: Interfaced CIP/RWIP Amounts by FA Period Report to view a summary of assets and asset lines interfaced from Oracle Projects to Oracle Assets. You can optionally choose to sort the report by asset category or project number.
Note: You must run the process PRC: Tieback Asset Lines from Oracle Assets before you run the AUD: Interfaced CIP/RWIP Amounts By FA Period Report.
From/To FA Period. Select a fixed assets period or period range to include in the report.
From/To GL Account. Select a GL account or a range of GL accounts to include in the report.
Project Type. To limit the report to projects for a single project type, enter the project type.
Project Number. Select a project number to show amounts for a single project.
Project Organization. Select a project organization if you want to include projects only for a particular project organization.
Class Category. Optionally, select a class category to view only specific project expenditures.
Class Code. Optionally, select a class code to view only specific project expenditures. To select a class code, you must first select a class category.
Primary Sort by Asset Category? This parameter enables you to change the primary sort order for the report. By default, the report is sorted by project. If you want to first sort the report by asset category, select Yes. Otherwise, select No to maintain the default sort order.
Use the AUD: Revaluated Funding Audit report to view a summary or detailed listing of all the components used in the funding revaluation calculation.
Although the report parameters are mostly optional, you must enter a value for the Mode.
From/To Project: Enter the range of project numbers you want to run the audit report for.
Project Type: To limit the report to only one project type, enter the project type. Otherwise, leave this field blank.
Revaluation From Date: The report includes components from the revaluation run on or after the Revaluation From Date.
Revaluation To Date: The report includes components from the revaluation run on or before the Revaluation to Date. The default is the system date.
Mode: Enter the mode you want to run the report. The options are Detailed and Summary.
Use the AUD: Supplier Cost Audit Report to audit transactions between Oracle Projects, Oracle Purchasing, Oracle Payables, Oracle Subledger Accounting, and Oracle General Ledger. This report lists all supplier cost transactions in Oracle Projects for a selected operating unit.
Additional Information: This report shows the final debit account information and the GL period. It does not show the credit account or any GL batch names.
From Project Number/To Project Number: Optionally enter a range of project numbers for which you want to run the report.
Task: Optionally, enter the task for which you want to run the report.
From Award Number/To Award number: For Oracle Grants Accounting, optionally enter a range of awards for which you want to run the report.
Expenditure Organization: Optionally, select an expenditure organization for which you want to run the report.
Supplier Name: Optionally, select a supplier for which you want to run the report.
Invoice Number: Optionally, select an invoice number for which you want to run the report.
Purchase Order: Optionally, select a purchase order number for which you want to run the report.
Transaction Type: Select one of the following transaction type options:
All: Specify this option to include all transaction types. This is the default option.
Expense Reports: Specify this option to include invoices of type Expense Report. In addition, when the invoice source is Credit Card, select this option to include invoices with an invoice type of Standard, Mixed, and Credit Invoices.
Payments: Specify this option to include all payments and discounts.
Supplier Invoices: Specify this option to include all supplier invoice types, except expense reports.
Receipts: Specify this option to include all receipt accruals.
From GL Period / To GL Period: Optionally, enter the GL period range for which you want to run the report.
From GL Account / To GL Account: Optionally, select a range of GL accounts for which you want to run the report.
Adjustment Type: Specify one of the following adjustment type options:
All Transactions: Specify this option to include all adjustment types. This is the default option.
Project Adjustments: Specify this option to include adjustment transactions made in Oracle Projects.
Unmatched Reversing Expenditure Items that Require Adjustments: Specify this option to include unmatched reversing expenditure items that the process PRC: Interface Supplier Costs interfaced from Oracle Purchasing and Oracle Payables to Oracle Projects. For information about unmatched reversing expenditure items, see: Manually Adjusting Unmatched Reversing Expenditure Items, Oracle Project Costing User Guide.
Sort Order: This parameter controls how data and columns are sorted and displayed in the output report. You can select how you want your report to display from the following list of options:
Invoice: Select this option to display and total the report by invoice columns. This is the default option.
Purchase Order: Select this option to display and total the report by purchase order columns.
Use the AUD: Supplier Invoice Audit Report to review the cost distribution lines for supplier invoices.
Important: This report lists only historical (prior to Release 12) supplier cost adjustments that you made in Oracle Projects and interfaced from Oracle Projects to Oracle Payables. It does not provide information regarding supplier cost adjustments that you make in Oracle Projects and send directly from Oracle Projects to Oracle Subledger Accounting.
All parameters are optional.
From/To GL Date: Enter the date range within which you want to the report to select cost distribution lines of supplier invoices.
From/To Transfer Date: Enter the date range within which the cost distribution lines you want to include in the report were transferred.
From/To GL Account: Select a GL account or a range of GL accounts to include in the report.
Use the AUD: Expense Report Audit Report to review the cost distribution lines for expense reports.
Important: For adjustments, this report lists only historical (prior to Release 12) adjustments to expense report costs that you made in Oracle Projects and interfaced from Oracle Projects to Oracle Payables. It does not provide information regarding adjustments to expense report costs that you make in Oracle Projects and send directly from Oracle Projects to Oracle Subledger Accounting.
All parameters are optional.
From/To GL Date: Enter the date range within which you want to the report to select cost distribution lines of expense reports.
From/To Transfer Date: Enter the date range within which the cost distribution lines you want to include in the report were transferred.
From/To GL Account: Select a GL account or a range of GL accounts to include in the report.
The Project Subledger Audit Reports print cost distribution lines related to projects. The reports enable you to drill down from a GL account balance in the trial balance to the individual project-related transactions.
Amounts in these reports are shown in the functional currency.
You submit each of these reports from the Submit Request window. Include the prefix "AUD:" when you enter the report name. See: Submitting Requests.
Related Topics
Project Subledger Detail by Project
Project Subledger Detail by Expenditure Type
Oracle Projects Reports and Listings
Because the number of transactions that comprise a GL account balance is usually very large, it is preferable to print a summary report of the transactions and then print a detailed report to narrow down the range of transactions that need to be examined. The Project Subledger Summary report prints a summary of cost distribution lines by project.
The transaction sources are classified broadly as Manufacturing and Non-manufacturing. This is done to enable the user to see manufacturing costs separate from non-manufacturing costs. Manufacturing transactions include imported items using the following transaction sources:
Inventory
Inventory Misc.
Work in Process
The report prints subtotals for GL Account, Project Number, Manufacturing-Related, and Expenditure Type Class.
From/To GL Account. Select a GL account or a range of accounts.
From/To Project. Select a project or range of projects.
From/To GL Date. Enter the date range within which you want the report to select cost distribution lines of expense reports.
This report shows cost distribution lines for a single project by task.
From/To GL Account. Select a GL account or a range of accounts.
From/To GL Date. Enter the date range within which you want the report to select cost distribution lines of expense reports.
Project Number. Select a project.
From/To Task Number. Select a task or range of tasks.
This report shows project subledger detail across projects for one expenditure type.
From/To GL Account. Select a GL account or a range of accounts.
From/To GL Date. Enter the date range within which you want the report to select cost distribution lines of expense reports.
Expenditure Type. Select an expenditure type.
From/To Project. Select a project or range of projects.
Use the period close exception reports to identify transactions that have not been fully processed, and that would prevent you from closing a PA period or a GL period in Oracle Projects. These reports are commonly used when you are preparing to close a period. When the exceptions are corrected, the period can be closed.
You can submit each of these reports from the Submit Request window. Include the prefix "EXC:" when you enter the report name. See: Submitting Requests.
Related Topics
Defining GL and PA Periods, Oracle Projects Implementation Guide
The transaction exception details reports list all transactions that have not been fully processed. You can use this report to identify corrections that you need to make before you attempt to close a period in Oracle Projects. You can run the following two transaction exception details reports:
EXC: Transaction Exception Details by PA Period: The report is sorted by PA period. Within each PA period, the report is sorted by exception category (see the list of report parameters below) and exception reason. For each group of transactions under an exception reason, the report lists the total amount and total number of items.
EXC: Transaction Exception Details by GL Period: The report is sorted by GL period. Within each GL period, the report is sorted by exception category (see the list of report parameters below) and exception reason. For each group of transactions under an exception reason, the report lists the total amount and total number of items.
Costing and cross charge exceptions are shown in functional and transaction currencies. Revenue exceptions are shown in the project currency.
The table below shows the information that is listed for transactions in each exception category:
| Exception Category | Information Listed for Each Transaction |
|---|---|
| Accounts Payable Invoice Exceptions | invoice number, invoice date, supplier number, supplier, line number, posted (yes or no), project, task, expenditure type, and amount |
| Costing Exceptions | supplier or employee, project, task, expenditure type, expenditure item date, expenditure batch name, quantity, unit, functional amount, transaction currency, and transaction amount |
| Cross Charge Exceptions | receiver operating unit, project, task, employee, supplier, non-labor resource organization, expenditure organization, date, type |
| Project Manufacturing/Inventory Exceptions | organization, originating table, transaction identifier, project, and task |
| Receipt Accrual Exceptions | receipt number, date, supplier number, supplier name, PO number, line number, shipment number, distribution number, project, task expenditure type, and amount |
| Revenue Exceptions | project, draft revenue number, and project amount |
| Uncosted Transactions | project, task, expenditure batch, supplier or employee, expenditure type, expenditure item date or accrual date, currency, and amount |
From PA Period...To PA Period. This parameter is only for the EXC: Transaction Exception Details by PA Period report. Enter a range of PA periods for which you want the report to print exceptions. These parameters are required. You must specify valid PA periods.
From GL Period...To GL Period. This parameter is only for the EXC: Transaction Exception Details by GL Period report. Enter a range of GL periods for which you want the report to print exceptions. These parameters are required. You must specify valid GL periods.
Exception Category. If you want the report to print just one category of exceptions, you can select an exception category. If you leave this parameter blank, the report includes all categories. The categories are:
Accounts Payable Invoice Exceptions. Includes supplier invoices that have not been interfaced from Oracle Payables to Oracle Projects.
Costing Exceptions. Includes cost distribution lines for which Oracle Projects has not successfully generated an accounting event.
Cross Charge Exceptions. Includes cross charge distribution lines for which Oracle Projects has not successfully generated an accounting event.
Project Manufacturing/Inventory Exceptions. Includes costs that have not been interfaced from Oracle Project Manufacturing and Oracle Inventory to Oracle Projects.
Receipt Accrual Exceptions. Includes receipt accruals that have not been interfaced from Oracle Purchasing to Oracle Projects.
Revenue Exceptions. Includes revenue distribution lines for which Oracle Projects has not successfully generated an accounting event.
Uncosted Transactions. Includes expenditure items that have not been cost distributed in Oracle Projects.
Exception Reason. If you selected an exception category, you can also select an exception reason. The list of values displays exception reasons that are valid for the category you chose. If you leave this parameter blank, the report includes all exception reasons.
Show Transaction Exceptions Across Operating Units. This parameter is only for the EXC: Transaction Exception Details by GL Period report. Select Yes if you want the report to display transaction exceptions across operating units. This parameter is required.
The Transaction Exception Summary report lists a summary of transactions that have not been fully processed. This report also lists the action required to correct the exceptions. You can run the following two transaction exceptions details reports:
EXC: Transaction Exception Summary by PA Period: This report is sorted by PA period. Within each PA period, the report is sorted by exception category and exception reason. For each exception reason, the report lists the total amount, the total number of items, and a description of the corrective action required to process the transactions.
EXC: Transaction Exception Summary by GL Period: This report is sorted by GL period. Within each GL period, the report is sorted by exception category and exception reason. For each exception reason, the report lists the total amount, the total number of items, and a description of the corrective action required to process the transactions.
Costing and cross charge exceptions are shown in functional and transaction currencies. Revenue exceptions are shown in the project currency.
The following parameters are for the EXC: Transaction Exception Summary by PA Period report:
From PA Period...To PA Period. Enter a range of PA periods for which you want the report to print exceptions. These parameters are required. You must specify valid PA periods.
The following parameters are for the EXC: Transaction Exception Summary by GL Period report:
From GL Period...To GL Period. Enter a range of GL periods for which you want the report to print exceptions. These parameters are required. You must specify valid GL periods.
Show Transaction Exceptions Across Operating Units. Select Yes if you want the report to display transaction exceptions across operating units. This parameter is required.
When you change the PA Reporting Period, Oracle Projects displays a warning message if the change would affect the summary amounts reported on any projects. This report lists projects that will be affected by changing the reporting period.
The report lists projects by the following categories:
Projects that have been summarized beyond the reporting period parameter.
Projects that have not been summarized up to the reporting period parameter.
Projects that have never been summarized.
For example, suppose the PA Reporting Period is week 3-JUL-98, and you want to change the PA Reporting Period to week 2-JUL-98. When you make the change, the PA Periods window displays a warning message indicating that some projects would be affected by the change. This report enables you to see which projects would be affected.
The summarization period exception report is based on the view PA_ACCUM_PERIOD_EXCEPTIONS_V.
You can submit this report from the Submit Request window. Include the prefix "EXC:" when you enter the report name. See: Submitting Requests.
Reporting PA Period. Enter the PA Period you want to set as the new current reporting period.
Related Topics
Setting the PA Reporting Period, Oracle Projects Implementation Guide
Use the Delete PA Periods report to identify and delete PA periods which contain transactions that are not cost distributed or accounted, or which contain existing budget data in one or more projects for the selected period. A PA period may not be deleted if transactions are cost distributed or accounted and invoice or revenue transactions exist for the selected period.
The Period Deletion Output Listing generated by the PRC: Delete PA Period process provides the following information:
PA Periods that can be deleted or cannot be deleted for the selected period
Details of all the transactions for the selected period.
Existing budget detail information that will be affected by deleting a PA period.
A list of steps that need to be performed after a PA period is deleted, such as:
Generation of new or replacement PA periods before new transactions can be posted.
Generation of new or replacement PA periods and summarization of budgets, workplan data, and reporting data.
Generation of new or replacement PA periods and regeneration of schedules for resource assignments.
These reports are commonly used when you are preparing to delete a PA period.
You can submit these reports from the Submit Request window. See: Submitting Requests, page 10-5
The following parameters are required.
Delete From Period: Enter the start date for the period for which you want to identify the PA periods eligible or not eligible for deletion.
Delete To Period: Enter the end date for the period for which you want to identify the PA periods eligible or not eligible for deletion.
Report Mode: Select the mode you want to run the report in. The options are Review and Final.
Review: Select this mode to identify impacted transactions and corrective actions for the periods which are eligible or not eligible for deletion.
Final: Select this mode to delete periods if validations pass, and view the transaction data for the range of selected periods and further actions to be taken.
This report is generated when the program PRC: Delete PA Periods is run in Review mode. This report displays transaction, budget and schedule details for the selected PA period range. You can use this report to identify the PA periods that can be deleted before you attempt to delete a PA period in Oracle Projects.
This report is generated when the program PRC: Delete PA Periods is run in Final mode. The program deletes the PA periods that are eligible for deletion and generates a report listing all deleted PA periods.
Important: It is recommended that you run the program PRC: Delete PA Periods in Review mode before running it in Final mode to prevent unwanted period deletion
The reports, Period Deletion Output Listing - Review and Period Deletion Output Listing - Final display the following information.
Transactions preventing deletion of a PA period: This section displays details of the transactions that are cost distributed or accounted in projects for the selected period. A period cannot be deleted if transactions are listed under this section
Transactions distributed or accounted in projects: This section displays details of all the labor and non-labor transactions that are cost distributed or accounted in projects for the selected period.
Invoice or revenue transactions in projects: This section displays details of all the draft invoice or draft revenue transactions for the selected period.
Transactions not stopping deletion of a PA period: This section displays details of the transactions that are not cost distributed or accounted in projects for the selected period. A period can be deleted if transactions are listed under this section.
Transactions not yet distributed in projects: This section displays details of all the labor and non labor transactions that are not cost distributed in projects for the selected period
Transactions not yet interfaced to projects: This section displays details of all the labor and non labor transactions that are not yet interfaced to projects
The following table lists the source and their corresponding source IDs for the labor transactions that are not yet interfaced to projects:
| Source | Source ID |
|---|---|
| OTL Transaction | hxc_time_building_blocks.time_building_block_id hxc_time_building_blocks.object_version_number |
| Third Party Data | orig_transaction_reference |
The following table lists the source and their corresponding source IDs for the non-labor transactions that are not yet interfaced to projects:
| Source | Source ID |
|---|---|
| Oracle Payables | Invoice Number |
| Oracle Purchasing | Receipt Number |
| Oracle Inventory | orig_transaction_reference |
| Oracle Project Manufacturing | Transaction ID |
| Third Party Data | orig_transaction_reference |
Use this report to check for errors and to review errors that occur during the organization forecast calculation and generation processes. This report shows calculation errors for all forecast periods based on the date parameters you specify in your organization forecast implementation options.
The system automatically generates this report when you submit the PRC: Generate Organization Forecast process. This report is also generated automatically when you specify you want to generate the report for the PRC: Calculate Forecast Amounts (Initial) and PRC: Update Forecast Amounts processes.
You can manually generate this report at any time by submitting the PRC: List Organization Forecast Exceptions process. For information on how to submit a concurrent program request, see: Submitting Requests.
When the system generates this report for a forecast calculation or generation process, the system sets the report parameters based on the parameters you specify for the calculation or generation process. When you submit this report as a concurrent program, you can generate the report for:
a specific project
a specific assignment within a project
a specific organization
multiple organizations in a reporting organization hierarchy
To submit the process for multiple organizations in a reporting organization hierarchy, specify a start organization parameter. When you specify a start organization, the system runs the process for the start organization and all subordinate organizations in the hierarchy. For more information on organization hierarchies, see Defining Organization Hierarchies.