Project Partners Blog

Posts Tagged ‘Oracle E-Business Suite Applications Release 12.2’

Part 2 of 2

As stated previously, the core principle in the new Standard requires that an entity recognize revenue to depict the transfer of goods or services to a customer in an amount that reflects the consideration given in exchange for those goods or services.

Impact to Balance Sheet and Income Statement

When a contract is signed, an asset and a liability are created for the total amount of goods and services promised to the customer.

Upon fulfillment of an identifiable performance obligation (commonly referred to as a “deliverable”), the liability is reduced, and revenue is recognized when that performance obligation is satisfied and accepted by the customer.

When payment is received for the goods and services provided, the asset is reduced.

This new methodology differs from the previous generally accepted practice of recognizing revenue when the customer is billed, and a receivable is created.  No longer will a company track unbilled revenue streams.  Oracle Projects provides the ability to configure your projects to meet the requirements of Step 5 of the new ASC 606 guideline with standard functionality.

Step 5 of the Standard requires a two-step approach.   Using Oracle Projects, work is performed, and delivery is recorded.  Then, a process to Generate Draft Revenue for the projects is run to complete the recognition process.

The following is an example of how your company can leverage Oracle Projects to meet ASC 606 compliance.

Service Contracts based on selling hours (T&E)

  • Work Based Revenue Recognition
    • Standard Oracle functionality of Time & Expense Billing
    • Set up project and billing information

  • Identify the Performance Obligations and set up as Budget Lines for the contracted number of hours

  • Delivery Team Charges Time & Expenses to the Project

  1. Revenue based on hours charged
  2. Acceptance of work performed implicit when customer signs timecard
  3. Invoicing takes place when the timecard is approved. This process can precede the actual recognition of revenue as the performance obligation is not yet complete.
  4. As each phase of the project is finished, revenue is recognized.

Run the Generate Draft Revenue Process for your projects to recognize revenue

Perform Work and Record Delivery

  • T&M Service Contracts based on specific Deliverables
  • Fixed Price Service Contracts based on Milestones
    • Mark Deliverable as Complete. Mark Billing Action as Complete

Run the Generate Draft Revenue Process for your projects to recognize revenue:

T&M/Fixed Price Service Contracts

  • A Fixed Price Service Contract requires the use of Billing Events generated from deliverables to generate revenue.
  • Invoicing can be generated per the terms of the contract; however, revenue cannot be recognized until the performance obligation has been met.

Unit Price Based Contracts

Oracle Planning and Control offers the ability to utilize a structure called Schedule of Values (“SOV”).  The SOV allocates value for various parts of the work from a contractual agreement.  The SOV schedule is also used as the basis for monitoring progress, tracking deliverables, and submitting and reviewing payment certificates for billing the client.  The user can either enter a contract in Oracle Project Contracts, or directly enter one.  Once a project is created, it can be updated from Oracle Project Contracts or directly entered in Oracle Planning and Control.

  • Enter Progress and record quantity completed for each SOV Task
  • In this case, a task has been set up for each performance obligation under the contract. As the task is completed and accepted, revenue can be taken

  • Billing Events are generated from Schedule Of Values progress and are used to generate revenue

Recent Enhancements to Support ASC 606

Oracle has been supporting organizations implementing these changes in their business to accommodate the new Standard.  To aid in the implementation and management of project revenue according to the new accounting standards, new consolidated patch sets to Oracle Projects have been released.

For companies using Oracle EBS Projects Suite Release 12.1.3 and above and Release 12.2.7 and above, Oracle has issued a patch set specific to each release to support management of project revenue according to ASC 606.

Below you will find screen shots of some of the new standard functionality available with these changes, recently published by Oracle.  As you can see, Oracle Projects addresses set up, tracking and revenue recognition via the use of a new Structure for Performance Obligations.

The new processes allow for the user to enable the use of Performance Obligation, create said obligations, publish and track progress against the performance obligation and generate revenue in accordance with the new standards.

As you can see Oracle Projects provides the ability to configure your projects to meet the requirements of the new ASC 606 guideline with standard functionality.

Oracle Licensing Requirements

  • Project Costing and Billing are required for all features discussed in this paper
  • Project Planning and Control (formerly known as Project Management) must be implemented to leverage Deliverable functionality
  • Schedule of Values functions are available in Oracle Project Planning and Control release 12.2.5
  • Application of Patch sets as described in this paper to take advantage of the ability to record and track Performance Obligations


Contract modifications, commonly referred to as change orders or amendments, occur when the price or scope of a contract is changed.  Depending on the circumstances, these changes are accounted for either as a modification to an existing contract, or as a separate contract.  Proper accounting treatment for modifications differs based upon this determination.

There are three steps to determine the proper treatment for a contract modification.

Determine Whether the Change Qualifies as a Contract Modification – A contract modification is any change to an enforceable rights and obligations of the parties to the original contract.  The Standards defines this as a change in scope and/or price of the original contract.  It does not need to be written, it can also be oral or implied through customary business practices.  Once an entity determines that a change is indeed a contract modification, it determines whether to account for it as a change to the original contract or as a separate contract.

Determine Whether the Modification is a Separate Contract – To determine that a modification is a separate contract, these two criteria must be met.

  1. The scope of the contract has increased with the addition of distinct goods or services, and
  2. The price of the contract increased by an amount comparable to the entities standalone selling price of the additional goods or services. (Selling price less ordinary selling costs)

Determine the Proper Accounting Treatment for Contract Modifications – If a contract modification is considered a separate contract, no changes to the existing revenue on the original contract are required.  The new contract is recognized as the performance obligations in the new, separate contract are met.  However, if the contract modification is not considered separate, then the modification is combined with the original contract.  There are two methods defined in the Standard for proper revenue recognition of a combined contract modification.

  • Prospective Treatment

If the remaining goods/services are distinct from those of the original contract and do not meet the criteria for a separate contract, the entity treats the original contract as terminated and accounts for both the original contract and modifications together as a newly created contract (ASC 606-10-25-13).

Revenue already recognized on the original contract is not adjusted.  All remaining transactions are accounted for on a prospective basis.

  • Cumulative Catch-up Adjustment

If the remaining goods/services are not distinct, the entity combines the increase or decrease of goods or services with the original contract’s promised goods/services to create a single performance obligation that is partially completed at the date of the modification.  The entity must adjust previously recognized revenue to reflect the changes of the modification to the transaction price.

IN ASC 606

Begin by increasing the amount of the Agreement on the project, then adding an additional funding line for the increased contract amount to the project tasks.

If the contract modification is Prospective, the Date Allocated should reflect the date from which revenue recognition will occur.

Create a Revenue Event using the new Date Allocated and run revenue generation processes.  The new revenue amount will begin as of the new date as indicated.















If the contract modification is cumulative, the Additional funding should be entered with the original Allocated Date.  When a new Revenue Event is created, use an event date that is retroactive to the original date.


The new revenue will “catch-up” in the currently open accounting period upon generation.





 Project Partners Blog Author: Donna Dignam | Principal Functional Consultant 

In April 2015, FASB (Financial Accounting Standards Board) issued ASU (Accounting Standards Update) 2015-05 to assist entities to determine when a customer in a cloud computing arrangement “CCA” (i.e. hosting arrangement) included a software license.

If a CCA includes a license to internal use software, the software license is accounted for by the customer as an intangible asset.  Basically, the intangible asset is recognized for the software license, and the payments or said license made over time are recognized as a liability.  If no software license is included in the contract, the company should account for the arrangement as a service contract, and the fees associated with the hosting service of the arrangement are expensed as incurred.

The Update did not give any guidance regarding the implementation costs for activities performed in a cloud computing arrangement as a service contract.  Since the FASB guidance in this area was not explicit, the Board decided to issue an Update to specifically address the resulting diversity in practice.

Who Is Affected by ASU 2018-154?

These Amendments on the accounting for implementation, setup and other upfront costs (commonly referred to as implementation costs) apply to entities that are a customer in a hosting arrangement that is a service contract.  Oracle Cloud computing arrangements where a license is sold to the customer along with a hosting arrangement with Oracle Cloud would be one such customer.

Main Provisions of ASU 20184

The Update’s intent is to align the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal use software and hosting arrangements that include an internal-use software license.  The current accounting for the service element of a hosting arrangement is not affected.

It is up to the company to determine which implementation costs to capitalize as an asset related to the service contract and which to expense.  Costs to develop or obtain internal use software that could not be capitalized under Subtopic 350-40, such as training costs and certain data conversion cost, also cannot be capitalized for a hosting arrangement that is a service contract.  The company in a hosting arrangement that is a service contract determines which project stage an implementation activity relates to.  Project stages include preliminary project stage, application development stage or post implementation stage.  Costs incurred for the application development stage are capitalized, while those costs related to the preliminary project stage or the post implementation stage are expensed as the activities are performed.

In addition, the company is required to amortize the capitalized implementation costs over the terms of the hosting arrangement.  The term of the hosting arrangement includes the noncancellable period of the arrangement plus periods covered by:

  1. Option to Extend – customer must be reasonable expected to exercise this option
  2. Option to Terminate the Arrangement – where the customer is reasonably expected NOT to exercise this option
  3. Option to Extend or Not to Terminate – where the vendor has control of exercising the option.

Impairment guidance, as if the costs were long-lived assets, and abandonment are to be applied based upon the existing guidance in SubTopics 350-40 and 360-10, respectively.

Income Statement presentation by the entity should be the same line item as the fees associated with the hosting service of the arrangement.  Similarly, classification of payments for capitalized implementation costs in the Statement of Cash Flows are done in the same manner as payments made for fees associated with the hosting arrangement.  In the Statement of Financial Position, capitalized implementation costs are presented in the same line item that a prepayment for fees associated to the hosting arrangement would be presented.

How is This Different and Why is it an Improvement?

Currently, GAAP does not specifically address accounting for implementation costs associated with a HASC.  Therefore, the Update improves current GAAP as it clarifies accounting and aligns the accounting for implementation costs for hosting arrangements, regardless of whether a license is conveyed.

For consulting firms, the new standards present an improved selling point as costs that were previously required to be expensed can now be capitalized.  For capital intensive industries, where cloud applications are being considered and dismissed due to financial considerations around increased expenses (and resulting decreased profitability metrics) due to cloud implementation, the new standard allows a way to capitalize the costs associated to both the license and the implementation and development costs around getting that application stood up.

When Does This New Update Take Affect?

For public entities, the amendments are effective for fiscal years beginning after December 15, 2019 and interim periods within those fiscal years. For all other entities, annual reporting periods beginning after December 15, 2020, and interim periods within annual periods beginning after December 15, 2021 are required.  Early adoption is permitted at any time.

The amendments in this Update should be applied either retrospectively or prospectively to all implementation costs incurred after the date of adoption.

Have Questions?
Simply reach out to us and our experts will immediately assist, provide additional information,
and answer any of your questions.

P: #1.650.712.6203  |   Email:


Author: Wendy Lamar | Managing Principal Consultant | Project Partners
Oracle E-Business Suite R12 Project Certified Implementation Specialist

By Wendy Lamar

Pay when paid functionality has been added to Oracle E-Business Suite as part of integration with procurement. The pay when paid functionality improves cash flow management by preventing payment to subcontractors until the customer invoice has been collected. Further, the supplier workbench provides the Project Manager improved visibility to the vendor invoice information, as well as enabling the management of invoice holds directly from the workbench. Read the rest of this entry »

By Neeraj Garg

Oracle E-Business Suite Project Costing

Labor Costing Enhancements: Labor transactions in Oracle Projects can now be costed via several new methods:

  1. Costing using HR Rates (includes support for multiple rates and rate by criteria). This feature now enables support for the Davis-Bacon Act.
  2. Support in Oracle Time and Labopr for additional data to be captured to support rate by Criteria.
  3. Total Time reporting. This feature allows the standard/actual cost for Exempt employees to be automatically pro-rated over all hours charged to projects by the employee. Prior to this enhancement, exempt employee costs could be over-counted if they charged more than the standard working hours.
  4. Labor costing using Payroll actuals. This feature supports using actual payroll costs to drive project labor costs. Support is included for Oracle Payroll or a third party payroll system.
  5. When using Payroll actuals for labor costing, you can choose to accrue labor cost using standard rates prior to payroll run. This allows you to continue billing all project costs using the accrued standard cost and then post adjustment entries to invoices based on the actual payroll run. When combined with the “Adjusted transactions on standard invoice” feature in Oracle Project Billing, this makes the accrual adjustment feature seamless to the end client.
  6. Expenditure Batch Reversal: In order to support the payroll feature of reversing a payroll run, Oracle Project Costing now supports reversing the costing for an expenditure batch and reverting the costed transactions to an uncosted state.

Integration to Oracle Complex Maintenance,Repair, and Overhaul (cMRO):  Support for unplanned and non-routine  maintenance has been added to the integration to Oracle cMRO in addition to existing support for Regular maintenance. Such maintenance visits/activities can now be associated to new or existing projects/tasks.

Enhanced Cost Collection by Cost Code: A new classification –Cost Code – is now available on a project/task. A Cost Code can be a multi-segmented attribute and can be setup to represent a hierarchy of values.  These cost codes are predefined during implementation and can be associated to a project. Each task can then be assigned one or more values for the cost code. Once this is done, all actuals must now include valid cost code values in addition to project and task. This allows for more granularity in setup and collection of actual costs and easy comparison of similar types of costs across projects and tasks for metrics like productivity that are key in the Engineering and Construction industry.

Self-Assessed Tax from Payables: Oracle E-Business Suite Projects Applications will now bring over any self-assessed tax on project related supplier invoices from Oracle Accounts Payable as a project expense.

Oracle E-Business Suite Project Billing

Standard Invoicing for Adjusted Transactions: Adjusted transactions can now be included on a net new invoice instead of going to a credit memo. This is controlled via an option at the project and task level for labor transactions only, or for all transactions.

Oracle E-Business Suite Project Management

Planning with HR Rates: If you use the HR Rates option for labor costing, these rates are also available in the planning screens (WorkPlans and Financial Plans) to determine planned cost for labor lines.

Forecasting Using Updated Rates: When generating a forecast, ETC amounts are now computed using updated rates (from the rate schedules) for all rate based resources.

Planning Without Resource Classes: You can now plan for projects, tasks and resources without assigning a resource class. This allows additional flexibility in determining the planning granularity

Planning by Cost Codes: You can now plan by cost code (assigned to project/task) and further at any level of the cost code you choose.


Online Patching: In addition to these features specific to Oracle E-Business Suite Projects, the biggest technology update is Online Patching.  Online Patching uses the Oracle Database 11g Release feature of “edition-based” redefinition to significantly reduce the downtime traditionally needed for patching and related maintenance activities.

The way this works is fairly elegant. An “edition” is a private environment in which you can redefine database objects. With online patching, patches are applied to a separate edition while users are working with the original edition. After applying patches, the system is cut over to make the patch edition the new production edition. After the initial upgrade to Release 12.2, all future patches and maintenance packs will be applied online, requiring only a brief cutover period to make the new functionality active.

If you have any questions about the new features in Oracle E-Business Suite Applications, Release 12.2, don’t hesitate to contact us via our online form, or call me at +1.650+712.6200.

By Neeraj Garg

This is the third of three articles discussing new enhancements in Oracle E-Business Suite Projects Applications Release 12.2. In this article we address the third of three key enhancements: Costing Using Payroll Actuals

Costing Using Payroll Actuals

This enhancement enables companies to use actual payroll costs from Oracle Payroll or a third-party payroll system to cost project labor transactions. These actual costs are distributed to the labor transactions on projects using new mapping rules that specify the expenditure type, cost type and distribution rules to be used for this purpose. Figure 1 shows an example of this mapping.

Payroll Actuals Figure 1

Figure 1


Drawing on this mapping and the amounts retrieved from the payroll system, the costing process will distribute payroll costs to various labor transactions, as illustrated in Figure 2.

Payroll Actuals Figure 2

Figure 2


The resulting distributed costs are shown in Figure 3.

Payroll Actuals Figure 3

Figure 3


Users also have the choice of accruing standard labor costs prior to a payroll run in order to report project costs and support billing. When payroll costs are distributed, the accrued costs are automatically reversed. In addition, a new process has been introduced in the solution to support payroll roll-backs needed for error correction. This process will reverse out an existing labor distribution to projects, making all the transactions re-eligible for costing. Then, when the new payroll run is completed, these transactions can be costed with the corrected payroll numbers. This process may also be used to correct errors in the setup of labor costing in Oracle Projects. For example, it can be used to reverse out a standard costing run and replace it with an actual costing run.

As with the Costing Using HR rates method described above, companies implementing this feature need consider the need for labor-cost information security, because actual labor costs may be exposed.


With this recent set of enhancements, Oracle E-Business Suite Projects has evolved into a more complete solution that can be used to address nearly any costing requirements that companies may have. Oracle users can more easily take advantage of various approaches to labor costing, using payroll data, HR rates and total time. These enhancements allow companies to manage and perform costing in ways that fit their specific needs, which in turn helps create a better understanding of project costs and, ultimately, profitability.

If you have questions about the new costing enhancements, the use of costing extensions, or any other issues pertaining to using Oracle Applications in an project-intensive environment, contact us! We are always very happy to help end-users make the best use of the applications that we at Project Partners originally invented.

By Neeraj Garg

Continuing from last week’s blog article, new enhancements in Oracle E-Business Suite Projects Applications Release 12.2 allow companies to address various project costing requirements without the use of extensions. There are three key enhancements:

  1. Total Time Costing
  2. Costing Using HR Rates, and
  3. Costing Using Payroll Actuals.


Total Time Costing

This enhancement addresses the need to cost labor transactions using effective rates, and especially to encompass exempt employees who do not get paid for overtime work. Like Standard Costing, this enhancement works with standard rates. However, it computes an effective rate for costing labor transactions based on total time charged for a period and the base hours for that period.

There are three new setup elements that are needed to enable Total Time Costing:

  1. Effective period (typically, this will be “weekly”)
  2. Base hours
  3. Enabling Total Time Accounting – new Costing Method for Labor Costing

With these three elements enabled, the effective rate used for costing labor transactions is now computed using the following three-step formula:

                 I.          Base Hours/Charged Hours * Derived Rate = Effective Rate
                II.          Effective Rate * Charged Hours = Raw Cost (Labor)
               III.          Labor Raw Cost * (1 + Burden Multiplier) = Total Burdened Cost (Labor)

In addition, if Total Time Costing is enabled and a new or adjusted transaction is introduced for a person for a previously costed period, the solution does not re-cost all transactions in that previous period. That is, it leaves them at the old rate rather than applying the new rate that was derived using the new total charged hours.

Overall, this enhancement allows users to accurately cost labor for exempt employees. It also allows organizations to meets federal contracting rules for exempt employees, as spelled out in the DCAA Contract Audit Manual, Section 9.

Costing Using HR Rates

This enhancement enables organizations that hold employee rate information in Oracle HR to directly use these rates for project labor costing. This feature is enabled by setting Rate Source in Oracle Projects to “HR” in the costing rule allocation. Rates are then retrieved from the Oracle HR rate matrix using “Rate by Criteria.”

There are many standard criteria available for setting up matrix rates in Oracle HR. Users can also add custom criteria to the rate matrix; these criteria can even call for rates at the project and task levels, if that degree of granularity is needed. Typically, the most commonly used criteria in a matrix are “job,” “location,” and “work type.” A new Project Timecard Template in Oracle Time and Labor has been seeded with these three attributes.

HR rates may also be enabled for use in planning when companies need to compute labor costs in budgets and forecasts.

This enhancement can also play a role in compliance. For example, many companies will benefit from the fact that it enables support for the Davis-Bacon Act in the U.S., which requires companies to pay minimum prevailing wage rates for construction work done at a given location. Also, because the HR rates used in calculations are the actual rates paid to employees, it is very important that labor-cost information security be carefully considered and implemented prior to enabling this enhancement.

In the next blog article we will discuss Costing using Payroll Actuals.

By Neeraj Garg


Oracle E-Business Suite Projects applications have provided Standard Costing for labor transactions for some time. However, other important approaches to costing have not been supported out of the box, such as costing using effective rates, HR rates or payroll actuals. To address these approaches, Oracle Projects provided three client extensions that could be used to replace Oracle’s standard capabilities.

Now, in Oracle Projects Release 12.2, Oracle has provided a number of enhancements that go beyond Standard Costing. These enhancements, which provide more options and greater flexibility, give companies new tools to help ensure that their costing approach fits their business, and gives them a clear view of the labor component of project costs.

The Traditional Approach

The Oracle Projects Standard Costing for labor transactions uses job or employee-based rates defined in Oracle Projects tables. However, this does not meet the specific needs of some companies and situations. For example, it does not support the following.

  • Costing using effective rates: This is typically used to address costing of labor transactions for exempt employees. Under the Standard Costing approach, all hours (including overtime hours) are costed at the standard rate. This may result in the overstatement of project costs, because exempt employees do not get paid extra for overtime work.
  • Costing using HR rates: Standard Costing in Oracle Projects requires users to set up rates by job or by employee with Oracle Projects Rate schedules. If a company is already using Oracle HR and holding employee rate information there, that information cannot be reused in Standard Costing. That is, companies cannot use HR rates directly to cost labor charges to a project.
  • Costing using actual payroll information: The distribution of actual payroll costs to project labor transactions is an industry standard in a variety of industries, such as construction, where companies typically work with small margins. Without this ability, variations between Standard Costing calculations and actual costs may be greater than the profits on projects.

Because such costing requirements could not be met with Standard Costing, Oracle Projects has traditionally provided three Client Extensions that companies could use to address a wider range of needs: These extensions are:

  1. Labor Costing Extension, which can be used to override or replace the costing algorithm provided by Oracle. It essentially allows users to implement any business logic they choose to cost labor transactions.
  2. Labor Overtime Extension, which can be used to determine overtime transactions, and then classify and cost them based on the appropriate overtime rules.
  3. Related Item Extension, which allows users to create separate “related” transactions for different labor-cost components in order to gain visibility for reporting or billing purposes.

Understanding the Enhancements

The new enhancements in Oracle Projects Release 12.2 allow companies to address various costing requirements without the use of these extensions. There are three key enhancements:

  1. Total Time Costing
  2. Costing Using HR Rates, and
  3. Costing Using Payroll Actuals.

These elements are discussed in subsequent blog articles.