Astounding as it may seem, when Oracle launched Oracle Project Management (PJT), it surprised many people by actually stating in the associated manuals that some functionality had in fact disappeared, if users adopted the financial planning model that is available in PJT. Throughout the manuals there are statements to this effect.
What this actually means is that if an organisation wishes to use Budgetary Controls, where by project budgeted funds are checked when users attempt to raise a requisition, they can not use the PJT financial planning model (planning resource lists, etc.) or vice versa. The same applies to budgetary integration between Oracle Projects and General Ledger.
This is highly irritating to organisations that want both and has not helped the cause of PJT, delaying the adoption of this functionally rich application. Organisations have been forced to choose between the two and prioritise where the biggest benefit lies. This adversely affects sectors where budgetary control (aka Funds Checking) is important, such as Higher Education & Research. This is far from ideal and it has vexed the consultants at Projected for some time.