Project Partners Blog


Posts Tagged ‘oracle project billing’

Part 2 of 2
LEVERAGING ORACLE PROJECTS TO MANAGE PERFORMANCE BASED REVENUE

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

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.

USING ORACLE PROJECTS TO MEET THE OBJECTIVES OF CONTRACT MODIFICATIONS AS DEFINED
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.

 

 

 

 

MANAGING PERFORMANCE BASED REVENUE RECOGNITION

Accounting Standards Codification (ASC) 606

-CURRENT UPDATES-

This paper provides an update to one of our previous six-part blog series “Are you Ready for the New Revenue Recognition Standards?”

It outlined the May 28, 2014 announcement that the FASB and IASB jointly issued ASC 606, Revenue from Contracts with Customers.  The intention around this change was to standardize revenue recognition practices across industries as existing practices fall short when it comes down to how value is delivered to the client based on obligations explicitly or implicitly specified in contracts.

IN THIS LATEST SERIES, WE WILL RECAP AND HIGHLIGHT THE MOST CURRENT CHANGES SINCE THE DEADLINES FOR COMPLIANCE HAS PASSED.

On May 28, 2014, FASB and IASB jointly issued ASC 606, Revenue from Contracts with Customers.  Due to inconsistencies in revenue recognition among industries, and the disconnect between U. S. GAAP and IFRS reporting, the Boards collaborated to reduce or eliminate those inconsistencies and thereby improve comparability between domestic and international best practices.  The resulting standards will therefore significantly affect the revenue recognition practices of many companies.

Depending upon the business’ current model and revenue recognition practices, this standard could have a significant impact on the amount and timing of revenue recognition, which in turn will impact key performance measures and debt covenant ratios, and may even change the way the company looks at capital investment and compensation.  The new standards are poised to change budgets, contract negotiations and current business practices.

Industry-Neutral Revenue Recognition

The core principle in the converged standard requires that an entity recognize revenue to depict the transfer of promised goods or services to a customer in an amount that reflects the consideration in exchange for those goods and services.  To accomplish this goal, a five-step process has been outlined in the new standard.  Every contract with a customer should be analyzed using these five steps to afford accurate reporting.

Step 1 – Identify the Contract with the Customer – A contract is defined as an agreement between two or more parties that creates enforceable rights and obligations.  The guidance applies to all contracts that meet specific criteria as defined within the standard.

Step 2 – Identify the Performance Obligations in the Contract – Performance obligations are promises to deliver certain goods and services to a customer.

Step 3 – Determine the Transaction Price – The transaction price is the amount an entity is expected to receive in exchange for transferring goods and services to a customer.

Step 4 – Allocate the Transaction Price – The relative standalone transaction price of each good or service being transferred to a customer, including discounts and other variable amounts of consideration.

Step 5 – Recognize Revenue as Performance Obligations are Satisfied – This step happens when the goods or services are transferred to the customer.  The customer will have taken control of the goods or services at this time.  The amount of revenue that is recognized is the amount allocated to satisfy a performance obligation.

HOW CAN WE HELP YOU SUCCESSFULLY NAVIGATE THROUGH THESE CHANGES?

Project Partners will demonstrate how project-centric companies, using Oracle Projects and/or Oracle Project Contracts, can comply to the new standards with minimum disruption to existing business practices.  View 5-Step recap below.

ASC 606:  REVENUE FROM CONTRACTS WITH CUSTOMERS

PART 1

The core principle in the converged standard requires that an entity recognize revenue to depict the transfer of promised goods or services to a customer in an amount that reflects the consideration in exchange for those goods and services.  To accomplish this goal, a five-step process has been outlined in the new standard.  Every contract with a customer should be analyzed using these five steps to afford accurate reporting.

STEP 1   IDENTIFY THE CONTRACT WITH A CUSTOMER

The new revenue guidance defines a contract as an agreement between two or more parties that creates enforceable rights and obligations.  Essentially, all parties to the contract have to approve the agreement, are committed to fulfilling their obligations, and have Identifiable rights.  The contract must have commercial substance and collectability is probable.

STEP 2   IDENTIFY THE PERFORMANCE OBLIGATIONS IN THE CONTRACT

This step requires an entity to identify all the distinct performance obligations in a contract or arrangement.  A performance obligation (commonly referred to as deliverables) is a promise to transfer goods or services to a customer.  A good or service is distinct when the customer can benefit from said good or service on its own or with resources the customer already has, and the good or service can be transferred to the customer independent of other performance obligations in the contract.  Goods and services that are not distinct should be combined with other goods or services until the whole group is distinct.

To be distinct, a good or service must meet two criteria:

  1. It must be capable of being distinct, and
  2. It must be separately identifiable.

STEP 3   DETERMINE THE TRANSACTION PRICE

The Transaction Price is the amount of consideration an entity expects to receive for the transfer of goods or services to the customer.  The amount can be fixed, variable or a combination of both.  Transaction Price is allocated to the identified performance obligations in the contract.  These amounts are what are recognized as revenue when the performance obligation is fulfilled.

STEP 4   ALLOCATE THE TRANSACTION PRICE

Allocation of the Transaction Price comes into play when a contract contains more than one performance obligation.  The seller should allocate the total amount of the selling price to each performance obligation based on its relative Standalone Selling Price (“SSP”).  The Standard permits any method of allocation of the SSP, just as-long-as that estimation is an accurate representation of what price would be charged in separate transactions.

STEP 5   DELIVER SERVICES AND RECORD OUTCOME

The last step in the new revenue recognition standard is to recognize revenue when or as the performance obligations in the contract are completed.  A performance obligation is completed when or as control of the good or service is transferred to a customer.  The Standard defines control as “the ability to direct the use of and obtain substantially all of the remaining benefits from the asset.” (ASC 606-10-20).

The Standard allows for revenue recognition based upon two methods for measuring progress, Output and Input.

Outputs are the result of inputs and processes   of a business and are goods or services finished and transferred to the customer.  The output method measures results achieved.  Surveys, appraisals, milestones reached, and units produced or delivered are all examples of output methods.  Value to the customer is the objective measure of an entity’s performance.

Examples of an output method would include the number of feet of pipe used for a specific distribution project, or the number of electrical poles used from a transmission plant, to a final destination.

The input method is a more indirect measure of satisfying a performance obligation.  Inputs are measured by determining the amount of effort put into completing the contract.  The input method is implemented by estimating the inputs required to satisfy a performance obligation, and then comparing the effort expended to date against that estimate.

Examples of input methods would be cost-to-cost, labor hours, or material quantities.

The Board decided that, at least conceptually, an output measure is the best depiction of the entity’s performance because it directly measures the value transferred to the customer.  Although the Boards did not state that the output method is the preferred method, they felt that in most cases it is the most appropriate method that is consistent with recognizing revenue as value is transferred to the customer.  A drawback to this method is that there may not always be a directly observable output to reliably measure progress.

 

CLICK HERE for a more in-depth discussion of this topic and read full posts to the ASC 606 Series on our website.

CONTINUE TO NEXT POST 2 OF 2…

“Let’s take another in-depth look at how to use Oracle to comply with the newest revenue recognition rules”  

 

www.projectp.com | Phone: +1.650.712.6200

 

 

 

Through this three (3) part educational web-series, Project Partners will arm you with critical steps and insight into a Project Financials cost-effective solution. This unique solution offering will assist administratively burdened organizations like yours to effectively manage Project Financials around Capital spend through all phases of the Capital Lifecycle (Concept Definition, Funding Approvals, Execution, Reporting, and Managing Project Costs).

WHY CAPITAL PROJECTS? – WEBINAR REGISTRATION INFORMATION

CLICK TO REGISTER HERE for our FINAL PART (3) of the three (3) part series as we explore how Project Partners has addressed the pain associated with AFE’s and the manual efforts.  We will showcase how we’ve developed an easy to use Authorization for Expenditure solution that extends the functionality of Oracle EBS Projects applications and walk you through the solution focused around project costing to your specific business requirements, robust functionality, and use of authorizations for expenditures to further efficiency gains and extensive return on investments.

MISSED PART 2?  Don’t Worry…CLICK HERE to get a downloadable recording so you will be up-to-speed!   

Have Questions?
Simply reach out to us and our experts will immediately assist, provide additional information, and ensure you have associated playbacks. We look forward to your attendance, and will set up a call to fully understand your needs, and offer next steps around a Project Financials cost-effective solution that best fits your organization.

P: #1.650.712.6203 Email: cfryc@projectp.com

Through this three (3) part educational web-series, Project Partners will arm you with critical steps and insight into a Project Financials cost-effective solution. This unique solution offering will assist administratively burdened organizations like yours to effectively manage Project Financials around Capital spend through all phases of the Capital Lifecycle (Concept Definition, Funding Approvals, Execution, Reporting, and Managing Project Costs).

WHY CAPITAL PROJECTS? – WEBINAR REGISTRATION

CLICK TO REGISTER HERE for PART 2 of the three (3) part series as we explore the WHY and HOW to leverage EBS Project Financials for Capital Projects. We’ll walk you through the solution focused around project costing to your specific business requirements, robust functionality, and use of authorizations for expenditures to further efficiency gains and extensive return on investments.

MISSED PART 1?  Don’t Worry…CLICK HERE to get a downloadable recording so you will be up-to-speed!   

Have Questions?
Simply reach out to us and our experts will immediately assist, provide additional information, and ensure you have associated playbacks. We look forward to your attendance, and will set up a call to fully understand your needs, and offer next steps around a Project Financials cost-effective solution that best fits your organization.

P: #1.650.712.6203 Email: cfryc@projectp.com

Project Partners, and our customer, Atkins North America, were pleased to present several sessions at Collaborate 15 in Las Vegas earlier this month. Now you can easily access the white papers and even view on-demand web casts of those sessions here.

We presented the following sessions at Collaborate 15. There is no charge to view any of this content, all it requires is a quick registration and approval. 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.

Technology 

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 11.2.0.2 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 John Sasali and Kimberly McDonald Baker

We know that many, many users of Oracle Project Billing use Billing Extensions to tailor their invoicing capabilities.  You can learn more about the expanded functionality provided by Extensions in Oracle E-Business Suite Projects by visiting our resource library, where you will find two whitepapers and a presentation.

Therefore, we want to make sure everyone who uses Extensions knows that Oracle patch 13345785:R12.PJ_PF.B causes issues with Billing Extensions.  Oracle describes this patch as PERIODIC RELEASE 6 FOR 12.1.3 ON RELEASE DATE 01-FEB-2013.

This patch for Oracle E-Business Suite Release 12.1.3 causes numerous issues if you use a billing extension that creates automatic class events and you are billing expenditures on the same invoice. If your invoice is only expenditures or only events, however, you should not have any problems. 

Error messages vary but you will find the following in the log.

ORACLE error during DRAFT INVOICE GENERATION (cursor=31 code=-1458: ORA-01458: invalid length inside variable character string
          )
PAI_ORACLE_ERROR

or

ORACLE error during DRAFT INVOICE GENERATION (cursor=32 code=-1722: ORA-01722: invalid number)

Oracle has this listed as as bug 16313327.

 

By Kimberly McDonald Baker

We want to be sure you don’t miss a new case study article featured in the November 2012 issue of Profit Magazine, titled “Unifying Financial and Project Management” In this article you will learn about Colonial Pipeline Company’s integrated Oracle E-Business Suite and Primavera systems, and a few of the benefits that Colonial is receiving.

With the new, integrated Oracle system, Colonial will have all project related financial records and information in one centralized repository. Project managers and the leadership team will be able to view individual projects or overall capital spend easily. With the new system, Colonial expects time spent on monthly status reporting to decrease by 75 percent, from 8,000 to 2,000 project management hours annually.

“This is a paradigm shift of work for our project managers from doing data manipulation to actually being a project manager,” says Phillip Chandler, Financial Controls Administrator at Colonial Pipeline Company. “This allows them to support our customers both internally and externally in a more effective manner.”

Chandler says Project Partners has helped Colonial implement best practices into its processes, making the company more efficient. “The Project Partners team is sensitive to the specific needs of Colonial. At the same time, they are able to present solutions from an outside perspective that we also need to grow as a business,” says Chandler. “Project Partners has provided the expertise and professionalism that we needed for developing and implementing our project.”

You can read the full article here.

By Randy Egger
President, Project Partners LLC
Former chief architect of Oracle E-Business Suite Projects applications

Over 20 years ago, Finance and IT organizations (under the direction of the Chief Financial Officer), were in control of systems and desperately wanted to instill some financial controls and measures into the Delivery organizations that ran projects. The battle was always that the Project Managers (PMs) didn’t want to be controlled by departments they felt had no understanding of the world of project management, they wanted complete flexibility to best deliver their projects, and they were not concerned with the CFO’s desire for visibility into projects. Most PMs managed projects using personal systems based on Microsoft® Excel or Microsoft Access. The more sophisticated project managers used Microsoft Project, and the most advanced firms used Primavera, Cascade, Mantix, Artemis, and Cobra. BUT, the project systems used by PMs seldom could reflect accurate cost data which then made it difficult to really know the financial health of the project. Therefore, many PMs simply managed to effort and schedule.

In the “old days” a job code equating to a project was part of the general ledger chart of accounts – and most PMs were not strongly concerned about financials. So, how could you let accountants manage financials and project managers manage projects? You needed a system that allows both worlds to obtain the information that they wanted in the format that they wanted. To meet this need, in the early 1990’s Oracle released its first Project Accounting (PA) system: a true project based sub-ledger.

When the initial implementations of PA started, it was the Finance group that was imposing controls onto the Project Managers. Finance wanted visibility into ongoing projects, hence Finance was making most of the decisions, which generated friction between the organizations. To meet the requirements driven by Finance, PMs needed to change the way they were managing projects and that introduced a large opportunity for Change Management.

Getting structure into a non-structured environment was the primary challenge. When companies have been doing things a certain way for decades, it is VERY hard to change that culture… so compromises are made in an attempt to balance the needs of both organizations. Some folks would create a Work Breakdown Structure (WBS) to map to a Cost Structure simply so that they could track and control costs. Other companies placed intelligence into both the Project number as well as the WBS … because that was the way it was always done in the past. Some would claim that it made controlling charges easier while others would claim that it made reporting easier. But, in both cases, Project/Task naming was mirroring the way a General Ledger chart of accounts is structured, and not the way a project manager manages a project.

As time progressed, operations and project-based delivery organizations matured and developed a better understanding of what is needed to facilitate harmony between Finance and Project based Operations. At the same time, Oracle developed a Project Management system that was closely linked to its Project Accounting application. When Oracle released its Oracle Project Management (PJT) application and companies began to implement it, it became clear that Oracle had taken one step closer to really bridging the Accounting world to the Project Management world. But that still was not enough. PMs wanted and needed an EASY tool to assist them with their Project Management needs. Then, Oracle made the smart decision to purchase Primavera.

For those companies that implemented Oracle Project Costing and Project Billing only, without a futuristic vision of having a truly integrated Project Management system in place, trying to implement any form of integration of Project Accounting to a Project Management system became a horrible mess. When that happens, the only real thing that can be done is to update the implementation of Project Costing and Project Billing with a clear understanding of how it would integrate with either Oracle Project Management or Primavera. If there are other major issues that also need to be addressed, then a complete reimplementation of these modules should be considered.

Any company that is upgrading to E-Business Suite Release 12, or implementing R12 for the first time, will have the opportunity to rethink or redefine how they will move to become a truly project centric organization. Whether you are implementing for the first time, updating your implementation or re-implementing, thinking through the business needs that address both Project Accounting and Project Management will be paramount for your future long term success.

This issue applies to more firms than one might initially expect. I have always stated that “every company is a project company … they just don’t know it yet.” As more and more organizations decide to operate their firm or certain divisions on a project basis to better understand costs and level of effort and to develop repeatable processes using a structured Project Management methodology they will look to Oracle’s Enterprise Project Portfolio Management solutions, which remain the most complete in the market. And they will benefit from the significant evolution of these applications that enable Finance and Project Management to work together in harmony.

Your firm made a large investment in Oracle Applications because management knows that using Oracle E-Business Suite Projects will help increase profitability and ensure that project objectives are met. But your project managers and administrators already have full time jobs, and they frequently remind IT and Line of Business Managers that they don’t have extra time to learn new software or hours every day to use project management programs. End-user adoption or acceptance of new software is often the biggest hurdle to bringing in new programs, no matter how great the functionality is.

But the fact remains: your firm needs to meet its business goals and has bought or is considering buying Oracle EBS Applications because of the improved business performance that results from a successful implementation.

So how can YOU help your firm maximize the return on its software investment?

Here’s a great start: You can have your project managers and administrators trained on Oracle EBS Projects in 82% less time and spending 40% less time on a daily basis, using a familiar Microsoft® Excel front-end, ensuring rapid end-user adoption, and putting your company on the fast track to the many benefits provided by Oracle.

View this webinar and see how our User Interface Applications free up your firm’s employees to make more strategic contributions and achieve business objectives.