23 Understanding GL Date Warnings and Errors

This chapter contains the following topics:

• Section 23.1, "GL Date Warnings and Errors"

23.1 GL Date Warnings and Errors

When you enter, review, or revise a transaction, the system validates the general ledger date against the open periods for the JD Edwards EnterpriseOne General Accounting, JD Edwards EnterpriseOne Accounts Payable, or JD Edwards EnterpriseOne Accounts Receivable system. The open periods are the current and next accounting periods (even if the next accounting period is in the next fiscal year) and are based on dates that are stored in the Company Constants table (F0010). If you enter, review, or revise a transaction with a general ledger date that is not in the open periods, you will receive a warning or an error message.

In this example, the current period is 06 (June):

Figure 23-1 Example of GL date warnings and errors

Description of ''Figure 23-1 Example of GL date warnings and errors''

If you enter, review, or revise transactions in periods 06 and 07 (June and July), you will not receive a warning or an error message because these are open periods.

23.1.1 Warning and Error Messages

Messages appear depending on fiscal date patterns and General Accounting constants. This table describes the warning and error messages that you might receive when you enter a transaction outside of the two-period window:

Message	Explanation
PYEB - Prior Year-End Balance	Reason: You entered a GL date for the prior year. Result: The system generates an error message and does not accept the entry. Solution: For journal entries only, you can use document type ## to enter and post entries to a prior year (for example, to make audit adjustments).
PBCO - Post Before Cut Off	Reason: You entered a GL date that is prior to the current period. Result: The system generates either a warning or an error message, depending on the PBCO setting on the General Accounting Constants form. Solution: If the PBCO setting is not selected, the system generates an error message, and you must change the date of the transaction so that it is in the current period, or change the constant to allow PBCO entries. If the PBCO setting is selected, the system generates a warning and you can click OK to accept the entry.
PACO - Post After Cut Off	Reason: You entered a GL date that is after the two-period window. Result: The system generates either a warning or an error message, depending on how the fiscal date pattern is set up. Solution: If the fiscal date pattern is set up for the full year, the system generates a warning and you can click OK to accept the entry. If the fiscal date pattern is not set up for the full year, the system generates an error message. You must change the GL date of the transaction to be within the two-month window, or set up the fiscal date pattern for the entire year.
WACO - Way After Cut Off	Reason: You entered a GL date for a future year that is not the next accounting period. Result: The system generates either a warning or an error message, depending on how the fiscal date pattern is set up. Solution: If the fiscal date pattern is set up for the future year, the system generates a warning, and you can click OK to accept the entry. If the fiscal date pattern is not set up for the future year, the system generates an error message. You must change the GL date of the transaction. Note: If the GL date of the transaction is the last fiscal period of the year and you enter a transaction in the first fiscal period of the next year, the system does not generate a warning; the open periods are the current and next fiscal periods regardless of the year.