GL ENCUMBRANCE

ORACLE GENERAL LEDGER ENCUMBRANCE
------------------------------

FREQUENTLY ASKED QUESTIONS
--------------------------

1..Can you post a Manual Encumbrance journal to any period including a never
opened period?

This is the intended functionality of the encumbrance journal process.
For encumbrances, no attention is paid to the period status -- this only
effects actual journals. The only thing we look at is the encumbrance year.
If the encumbrance year is open, then you can create journals and reverse
journals to any period within that year.

Enhancement request 856002 has been logged to have this feature changed.
The best thing you can do to get this enhancement on the schedule is to vote
for it at your local OAUG (Oracle Applications Users Group).

Oracle receives hundreds of enhancement requests each year. The ones that make
the top 10 at OAUG's are generally implemented or at least considered.



2. Why do you find the period that you need to enter is not listed on the list
of values when entering the From Period and To Period parameters on the
Year-End Carry Forward form?

The status of the last period of your fiscal year must be Closed, and the
status of the first period of your next fiscal year must be Open or Future
Enterable.

General Ledger automatically defaults the From/To Period pair when the
last period of the fiscal year for which you are carrying forward balances
are Closed or Permanently Closed (From Period), and the period following
the closed period is Open or Future Enterable (To Period).

The period that follows the closed period must also be one of the following:

- An open encumbrance year if you are using the Encumbrances Only, or the
Encumbrances and Encumbered Budget rule.

- An open budget year if you are using the Encumbrances and Encumbered
Budget rule or the Funds available rule.

You can choose a period pair from a later fiscal year if all of the same
conditions are met.

3. Can we drilldown from GL to PO encumbrances?

Currently we cannot drill down from GL for PO ENCUMBRANCES .The issue is
categorized as an enhancement request 2139511.