A project is undertaken for a customer where all labor costs are non-billable, and Non-Labor costs are billable if the accumulated costs incurred are greater than $10k. How can Oracle Projects be implemented to support this?
Identify the four different levels where transaction controls are defined.
You can configure transaction controls by the following:
(A) Expenditure Category
(C) Employee
(E) Expenditure Type
Non-Labor Resource
A company has multi-currency projects and tasks. What is the hierarchy in which the currency attributes are allocated to a transaction?
Note:
Setting up Multi-Currency Transactions
To set up your system to process multi-currency transactions, perform the following steps:
* Implementation Options
Use the Currency Implementation Options to control the default values for currency attributes at the operating unit level. Oracle Projects uses the currency attributes to calculate currency exchange rates. See: Currency Implementation Options.
* Currency
For each project for which you want to process multi-currency transactions, set up the Currency options in the project and task options window. This option enables you to enter default currency attributes for a project. See: Currency, Oracle Projects Fundamentals.
* Cross Charge
You can use the Cross Charge Options to specify whether the project can accept charges from other operating units. See: Cross Charge Setup, Oracle Projects Fundamentals.
* Task Currency and Cross Charge Options
* You can use the Task Currency and Cross Charge Options to override the costing currency conversion attributes and cross charge options in a lowest task. See: Currency, Oracle Projects Fundamentals and Cross Charge Setup, Oracle Projects Fundamentals.
* Transaction Entry and Transaction Import
During Transaction Entry and Transaction Import, you can override the project and task currency attributes. See: Entering Expenditures, Oracle Project Billing User Guide and Currency Conversion Attributes for Imported Transactions, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
An organization wants to consolidate work based billing across multiple projects (produce one invoice for a single customer based on multiple contract projects). Which two methods will help them accomplish this?
C: Consolidated Invoicing allows you to consolidate multiple project invoices into one single invoice.
Identify two ways to ensure that correct class category codes are recorded against relevant projects.
B: 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.
C: As part of a project template definition setup, you can choose which Quick Entry fields you want to define. Oracle Projects prompts you to enter information in these Quick Entry fields when you create a new project from a template. Choose Quick Entry fields for project information you want to enter (instead of accepting the template default) each time you create a project.
Order: Enter a number to indicate the sequence in which you want the Quick Entry fields to appear.
Field name: Choose the fields you want to appear in the Quick Entry window when you create a new project.
Specification: You enter a specification for the following field names:
Key Member: Select the project role type to use when creating the key member
Classification: Select the class category to use when creating the classification
Customer Name: Select the customer relationship to use when creating the project customer
Prompt: You can enter a field name that is different from the predefined field name to display when you use Quick Entry.
Required: Choose whether you want to require entry for the Quick Entry field.
