Download Oracle.1z0-511.TestKing.2018-06-13.40q.vcex

Note:*Distribute Usage and Miscellaneous Costs The process computes the costs and determines the default GL account to which to post the cost for expenditure items with the following expenditure type classes:Usages Burden Transactions Miscellaneous Transactions Inventory and WIP transactions not already costed or accounted

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 codes To 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. References:

You can split an item into two items so that you can process the two resulting split items differently. For example, you may have an item for 10 hours, of which you want 6 hours to be billable and 4 hours to be non-billable. You would split the item of 10 hours into two items of 6 hours and 4 hours, marking the 6 hours to be billable and 4 hours to be non-billable. The resulting split items are charged to the same project and task as the original item. References:

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 ResourcesReferences:

Note:*Project Asset Type This field identifies whether an asset represents an Estimated or complete, As-Built capital asset, or a Retirement Adjustment asset. *We have a Capital Projects, every month end we want generate asset lines and send to FA as CIP asset lines against the project asset. Once project is completed then all the Asset lines will capitalize in FA . When we want to generate asset lines, we have to give the Date in Service and Project asset Type as "Built". after generating the asset line we can't change the Date in service in oracle projects If we have given the Project Asset type as " Estimated" then i can't generate asset lines. *Project Asset Type When you copy an asset, Oracle Projects copies the asset with the same project asset type. For estimated assets, you can optionally copy the asset as an as-built asset.

The Automatic Invoice Approve/Release Extension allows you to release invoices automatically as part of the Generate Draft Invoice process. Incorrect:Not E:Generating Revenue Accounting Events After you generate and release the revenue, you run the concurrent program PRC: Generate Revenue Accounting Events. The concurrent program determines default unearned revenue and unbilled receivables accounts using AutoAccounting and generates accounting events for Oracle Subledger Accounting.Note: If you set the profile option PA: Interface Unreleased Revenue to GL to yes, then Oracle Projects automatically releases any unreleased revenue when you run the concurrent program PRC: Generate Revenue Accounting Events.References:

One Customer, Multiple Agreements Use multiple agreements when you have one customer, but a requirement to create a separate invoice for each top task. You can use this method to accrue revenue cost-to-cost or impose hard or soft revenue limits by task, as well as automatically create separate invoices by task. To create separate invoices by task, you must use a different agreement to fund each task. If you use more than one agreement for a single task, the agreements are used according to the precedence described earlier for projects. References:

Revenue Once revenue is created, Oracle Projects runs AutoAccounting to determine the appropriate default accounts. AutoAccounting selects all of the AutoAccounting parameters for each item or event, determines the account coding, validates the account coding against the general ledger, and updates each revenue distribution line with the appropriate default account. Account Debit Credit Unbilled Receivables and/or Unearned Revenue200.00 Revenue200.00

C:Consolidated Invoicing allows you to consolidate multiple project invoices into one single invoice.References:

Structure Integration Setup 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.References: