Previous | Next | Contents | Index | Navigation | Glossary | Library |
For example, in the situation illustrated above, the second weekly PA period, P11-01-96, includes the ending date of a GL period. Based on the PA period ending date (11/03), transactions falling into PA Period P11-01-96 would post to the GL period ending November 30. Some of the transactions may actually have occurred in October; so these items would be inaccurately accounted for in GL.
In addition, there would be no easy way to reconcile Oracle Projects with GL, because at the October GL closing, Oracle Projects would be mid-period. Adjustments would be necessary to reconcile the two systems.
Alternatively, you can split PA periods that would otherwise overlap the end of a GL period into partial weeks. In the example above, period P11-01-96 has been be split into two periods, one beginning 10/28 and ending 10/31 (P10-05-96), and the other beginning 11/01 and ending 11/03. However, this method is very vulnerable to error, since every user entering and processing transactions (including time sheets) during a split week must enter and process transactions in the correct partial-week period.
The recommended way to resolve this conflict is to use 5-4-4 GL periods to match weekly PA periods, or some other matching scheme if PA periods are other than weekly. At calendar year-end, GL journal entries must be made in any case, to compensate for overlapping periods.
Note: After a transaction is posted to a PA period from any operating unit, the Oracle General Ledger Accounting Calendar window will not allow changes to the period date range.
Status | Description | Entry Allowed | Interface Transactions | Reopen Period |
---|---|---|---|---|
Never Opened | New periods that are in the future, and in which you do not want to allow entry. | NO | NO | n/a |
Future | Future periods in which you allow entry but not interfacing transactions. | YES | NO | n/a |
Open | Current periods. | YES | YES | n/a |
Pending Close | Use for correcting unprocessed items. You can set a period to this status without checking for unprocessed items. | NO | YES | n/a |
Closed | You cannot close a period if unprocessed items exist. A closed period can be reopened at any time. | NO | NO | YES |
Permanently Closed | You cannot permanently close a period if unprocessed items exist. Once a period is permanently closed, you cannot reopen it. | NO | NO | NO |
Table 1 - 80. (Page 1 of 1) |
At least one PA period must be specified as Open or Future in order for Oracle Projects processes to process transactions. The PA Period with a status of Open or Future that includes a project transaction date is the PA Period for the transaction. However, if the transaction date falls in a period that is not Open or Future, Oracle Projects will find the next Open or Future PA Period and use it as the PA Period for the transaction. Oracle Projects will reject the transaction if it cannot find a PA Period for the transaction.
Previous | Next | Contents | Index | Navigation | Glossary | Library |