Download Oracle E-Business Suite R12 Project Essentials.1z0-511.Pass4Success.2026-01-23.62q.tqb

Note:* Enable Budgetary Controls and Encumbrance AccountingTo use budgetary controls, you must implement budgetary control and encumbrance accounting for the ledger in Oracle General Ledger and enable encumbrance accounting in Oracle Payables or Oracle Purchasing. Encumbrance accounting automatically creates encumbrances for requisitions, purchase orders, and invoices.* PSA: Budgetary Control Report TemplateThis profile option can be set at the site, application, responsibility, and user levels. You must select Budgetary Control Results Template as the value for this profile option to enable users to view funds check results from Oracle Purchasing and Oracle Payables after a funds check.

* Defining Retention TermsRetention Terms determine how amounts are withheld from project invoices and how the withheld amounts are billed to the project customer. Retention terms include:Withholding TermsWithholding Terms by Expenditure CategoryWithholding Terms by Event Revenue CategoryBilling Terms* Witholding TermsThese terms apply to all sources of project invoice amounts for the specified project or top task. For each term, you can define a withholding percentage or amount. Optionally, a threshold amount can be defined to determine the maximum amount to be withheld per term.

Note:* You can set up two types of project structures in Oracle Projects:/ Workplan structures consist of tasks that help project managers and team members plan, track, and deliver projects on time./ Financial structures consist of tasks that help project managers and financial administrators track billing, costs, budgets, and other financial information for individual projects.* If you enable both a workplan structure and a financial structure for your project or project template, you can decide whether or not they are integrated, and if so, to what degree. You do this by choosing one of the following options on the Structures setup page:/ Shared Structures: Enables you to generate a financial structure with a task hierarchy that is fully shared by the workplan structure task hierarchy. Workplan and financial structures are fully shared by default./ Partially Shared Structures: Enables you to generate a financial structure that is partially shared by the workplan structure hierarchy./ Non-Shared: Task-Based Mapping: Enables you to map individual workplan structure tasks to individual financial structure tasks./ Non-Shared: No Mapping: Choose this if you do not want to integrate your project workplan and financial structures in any way.

InvoiceWhen you run the program to interface invoices to Oracle Receivables, Oracle Projects runs AutoAccounting to determine the appropriate default accounts. If the invoice fails AutoAccounting, then the program marks the draft invoice with an error. See: Overview of AutoAccounting, Oracle Projects Implementation Guide.The following table shows entries Oracle Projects creates when the Interface Invoices to Oracle Receivables process is run:Account Debit CreditReceivables 200.00Unbilled Receivables and/or Unearned Revenue 200.00Oracle Project Billing User Guide

Note:* You define project classifications to group your projects according to categories you define. A project classification includes a class category and a class code. The category is a broad subject within which you can classify projects. The code is a specific value of the category.* (see step 3 below) Defining class categories and class codesTo define class categories and class codes:1. Navigate to the Class Categories and Codes window.2. Enter a unique Class Category name and a Description.3. Specify whether the class category is mandatory for every project you define.Enable if all projects must have a code assigned to this class category. Do not enable if this class category is optional. If you do not enable this option, you cannot use this class category in your AutoAccounting rules.4. Specify whether you want to use the class category in your AutoAccounting rules.Suggestion: For each project, you can use only one code with one class category for use with AutoAccounting rules. If an AutoAccounting category already exists within a particular date range, assign an end date to the existing AutoAccounting category and then create a new one.5. Specify whether you want to allow entry of only one class code with this class category for a project.Note: Defining multiple class codes for one category for a project may affect reporting by class category; defining multiple class codes may cause your numbers to be included more than once.6. Enter the Name, Description, and Effective Dates for each class code.7. Save your work.

The following activities take place as part of the expenditures process flow for labor costs:1. Run the process PRC: Distribute Labor Costs. This process calculates the raw and burden cost components for labor cost expenditure items. It also uses AutoAccounting to determine the default debit account for each expenditure item.2. Run the process PRC: Generate Cost Accounting Events. This process uses AutoAccounting to determine the default credit account for each expenditure item. It also generates accounting events for distributed transactions. You can optionally select Labor Cost as the process category to limit the process to labor costs.3. Run the process PRC: Create Accounting. This process creates subledger journal entries for eligible accounting events. You can run the process in either draft or final mode. You can optionally select Labor Cost as the process category to limit the process to labor cost accounting events. Optionally, the process can post journal entries in Oracle General Ledger.If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting.4. Run the process PRC: Transfer Journal Entries to GL. When you run the process PRC: Create Accounting, if you select No for the parameter Transfer to GL, then you run the process PRC: Transfer Journal Entries to GL to transfer the final subledger journal entries from Oracle Subledger Accounting to Oracle General Ledger. You can optionally select Labor Cost as the process category to limit the process to labor cost accounting events. Optionally, the process can post journal entries in Oracle General Ledger.5. Run Journal Import in Oracle General Ledger. (optional) This process brings the final accounting entries from Oracle Subledger Accounting into Oracle General Ledger.

Note:* Compute Forecast Labor RevenueThis process calculates the potential revenue of labor expenditure items based on established bill rates and markups. The expenditure items that the process selects are billable labor expenditure items charged to contract projects that have not yet been processed by the Generate Draft Revenue process. The items do not have to be approved to be processed for forecast revenue.

Changes to these calendars impact the schedules of the person resources, requirements, and assignments differently. Oracle Project Resource Management provides the following administrative processes to help manage these changes and to maintain consistent schedule information throughout the application:PRC: Generate Calendar Schedule for a Single CalendarPRC: Generate Calendar Schedules for a Range of CalendarsPRC: Rebuild Timeline for a Single ResourcePRC: Rebuild Timeline for a Range of Resources