Recompiling Burden Schedule Recalculates Existing Costs

February 22, 2006 on 7:12 pm | by Marian Crkon | In Feature of the Week | Enter Comments | Print Print | Email Email

You may experience this feature if you are using Project Burdening in Oracle Projects 11.5.10.

The Feature

If you updated and recompiled your burden rates in the provisional burden schedule version, or defined a new version with a retroactive start date, the system will automatically update existing transactions (typically timecards) to be re-costed. This might have a major impact on your project costing and reporting since the PA Date and GL Date for re-costed transactions will change to the current period from the period when the transactions were originally calculated.

The Workaround

While this is a great feature if used as intended, watch out if you are not familiar with it. If you do not intend to recalculate the existing burden costs with new burden rates, set the start date of the new burden schedule version to the beginning of the current period to avoid unintentional retroactive recalculation of the existing burden costs.

No Comments yet »

RSS feed for comments on this post. TrackBack URI

Leave a comment

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Powered by WordPress with Pool theme design by Borja Fernandez.
Entries and comments feeds. Valid XHTML and CSS. ^Top^