To let people submit time cards, the department on the person's employment record has to be an expenditure organization. Here's how you classify a department as an expenditure organization.
Required Required Step 19 Define usage cost rate overrides. See: Usage Cost Rate Overrides. See: Compensation Rules. Required Required Step 21 Define employee cost rates. See: Employee Cost Rates. Required Required Step 22 Define labor cost multipliers. See: Labor Cost Multipliers. Optional Optional Step 23 Implement labor costing extension advanced implementation step.
See: Labor Costing Extensions. Optional Optional Step 24 Implement labor transaction extension advanced implementation step. See: Labor Transaction Extensions. Optional Optional Step 25 Implement overtime processing advanced implementation step. See: Overview of Implementing Overtime. Optional Optional Step 27 Define burden cost codes. See: Burden Cost Codes.
Optional Optional Step 28 Define burden structures. See: Burden Schedules. ATTENTION: If you have a multiple organization installation, you must repeat this step for each operating unit if the new operating unit is associated with a new business group. See: Billing Cycles.
See: Billing Cycle Extension. See: Payment Terms. See: Agreement Types. See: Bill Rate Schedules. See: Invoice Formats. See: Credit Types. See: Event Types. See: Labor Billing Extensions. See: Billing Extensions. See: Revenue-Based Cost Accrual. You can define additional transaction sources to import transactions from third-party applications. For example, you can define the transaction source Payroll to identify expenditure items imported from an external payroll application.
You control the transaction import processing by the options that you select for each transaction source. Predefined transaction sources exist for the following Oracle Fusion applications:. Specify import and accounting options in the transaction document to define how cost transactions are imported and processed. Specify document import options to control how the application imports transactions that are associated with documents. Here is a list of import options for each document.
Import raw cost amounts from transactions listed in a document. Import burdened cost amounts from transactions listed in a document. Allow multiple transactions from a document to have the same original transaction reference value. Override the primary human resources assignment organization of the persons associated with the transactions in a document. Revalidate cost transactions that you import from a document.
Specify that the imported cost requires expenditure batch approval. Accounting options that you define for documents impact how the application accounts transactions for that document. Here is a list of the accounting options for each document. Select this option to specify that cost transactions must be accounted in the source application.
That is, you must account for raw, burden, or burdened costs externally. If the raw cost, burden, or burdened cost is accounted in the source, then the respective general ledger accounts are required to import the transactions successfully.
Select this option to create raw cost accounting journal entries on transactions. This option is applicable only when the cost is not accounted in the source application. Select this option to create adjustment accounting journals entries on transactions. You must select the Create raw cost accounting journal entries and Create adjustment accounting journal entries options if you plan to cross-charge or capitalize costs. Select this option to import accounted costs even when the project period is closed.
Transactions accounted in Payables, Cost Management, or third-party applications that are accounted in the source system can skip import costs validations if the project period status is closed or close pending. However, you must account the applicable burden cost and accrued revenue in the next open period.
You can have a document with the same name in multiple sources but you can't share documents across sources. For example, a corporation with multiple time capture systems can associate a time card document with Oracle Fusion Project Financial Management and a non-Oracle application as sources. The rules on how these transactions are treated differ based on how they're processed in the source applications. You can create documents and document entries only for third-party transaction sources.
You can delete third-party transaction sources, documents, and document entries only if no cost transactions exist for them. However, you can't delete the predefined transaction sources, documents, or document entries. You decide whether to allow transaction adjustments and reversals for each document entry that you create during implementation. However, you can't define document entries to allow adjustments and reversals for transactions that are generated by the application, such as allocation transactions, capital interest expenditure transactions, or summarized burden transactions.
You can't cancel an adjustment performed on an expenditure item for which funds are already reserved against a control budget. You can't change the source, document, or document entry after exporting a transaction to Project Costing.
Use Project Process Configurator to define formulas for billing, costing methods, and complicated revenue and invoice amounts. To use the Project Process Configurator, you must have the following privileges and roles:.
Use Project Process Configurator to group asset lines using additional grouping criteria. This grouping is useful while assigning assets to projects. For example, you can create a configurator to specify that the application must group asset line costs using project attributes, such as inventory item or funding source, or a user-defined descriptive flex-field.
You can also combine attributes to create specifications for more complex grouping scenarios, such as expenditure category and expenditure organization. In the Configurator section, move the grouping sources that you want to use to group asset lines from the Available Grouping Sources list to the Selected Grouping Sources list.
If you want to manage an existing configurator, use the Search Results section to view and update its details, or to delete it. Keep the following considerations in mind while creating the asset line grouping Configurator:. You can create multiple configurators for asset line grouping, but only one of them can be active. When you create a new asset line grouping method or update an existing one, the application groups all subsequent asset lines created using the active grouping method.
You can update grouping methods at any time, and all new asset lines will use the active criteria. When you create asset line grouping criteria using the Project Process Configurator, the application applies the new criteria on top of the default grouping criteria.
For example, if you create a configurator that groups asset lines by Expenditure Organization and Expenditure Type, the application groups asset lines by the following sources.
Here's how you can associate project types with an asset line grouping method created using the Project Process Configurator. On the Manage Project Types page, click the project type that you want to update. By default, Projects groups project burden costs using built-in criteria, such as task, organization, and funding source.
Use Project Process Configurator to specify that the application must group a transaction's project burden cost by that transaction's transaction number. On the Create Project Process Configurator page, enter a name for your configurator.
Here are a few considerations that you must keep in mind while using Project Process Configurator for project burden cost grouping configuration. You can't have more than one active burden cost grouping configurator at any time. When you create a burden cost grouping configurator or activate an existing one, the application groups all burden costs created thereafter based on the grouping method in the configurator.
Even when you adjust costs in an existing project, the application ignores the originally used grouping method and follows the specifications in the configurator. Here are the default criteria that Oracle Project Management uses to group project burden costs.
These criteria are implicit and can't be changed or removed. Use the Manage Project Process Configurator task to create additional project burden cost grouping criteria. Previous Next JavaScript must be enabled to correctly display this content.
Define Capital Projects Configure options used to capitalize project costs and place assets in service. Define Borrowed and Lent Accounting Configure borrowed and lent accounting to distribute project costs across organizations. How Time and Labor Works with Project Costing The integration between Time and Labor and Project Costing allows project managers and accountants to manage time cards for employees and contingent workers. Based on the setup, a time card displays: All projects in the business unit.
Only those projects in which the user is a team member. Using Time and Labor Employees and contingent workers report project-related time in the Time work area. Using Project Costing Project accountants use the Import Costs process to validate and import approved time cards into Project Costing. Business unit Transaction source information Expenditure type and organization Expenditure item date Person Worked hours Batch name Original transaction reference The project must be enabled for multiple language support and the project name must appear in the user session language.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.
0コメント