About Journal Import Validation
Journal Import validates all of your data before it creates journal entries in your General Ledger application. If you allow suspense posting for your set of books, Journal Import will assign lines with invalid accounts to that account. Journal Import rejects all other invalid lines, and they remain in the GL_INTERFACE table where you can correct them online in the Correct Journal Import Data form or in your feeder system. Journal Import also prints your error lines in the Journal Import Execution Report.
Batch Level
Validation
Journal Import validates the following attributes to ensure that a batch with the same name does not already exist for the same set of books and period in your General Ledger application:
Journal Import also checks to ensure that more than one journal entry with the same name does not exist for a batch.
Journal
Level Validation
Journal Import validates the following attributes to ensure that your journals contain the appropriate accounting data:
- Reversal period (GL_INTERFACE.REFERENCE8)
Journal Entry Line
Level Validation
Journal Import validates the following attributes to ensure that your journal entry lines contain the appropriate accounting data:
Account Validation
Journal Import validates your account code combinations in a number of ways. Journal Import will successfully import your accounting data if your code combinations meet the following validation requirements:
- You allow detail posting to segment combinations.
- You have enabled your code combinations for the accounting date you specify.
- Your code combinations do not include summary accounts.
Effective Date Validation
Journal Import validates each transaction's Accounting Date to be sure it is a valid business day. If the date is a valid business day, General Ledger uses it as the transaction's effective date. If the Accounting Date is not a valid business day, Journal Import uses your defined Effective Date Rules to determine how to handle the transaction. If the Effective Date Rule is:
- Fail: Journal Import will reject transactions when the Accounting Date is not a valid business day (no posting takes place). The Accounting Date is considered the effective date.
- Leave Alone: Journal import will accept all transactions regardless of the Accounting Date. The Accounting Date is considered the effective date.
- Roll Date: Journal Import will accept the transaction, but roll the Accounting Date back to the nearest valid business day (within the same period) to determine the transaction's effective date. If there is no prior valid business day within the same period, the Accounting Date is rolled forward to determine the effective date.
Additional Information: If you specify a reversing effective date, Journal Import will validate the date using the same process and rules noted above for accounting dates.
Note: Effective Date Rules are defined in the Journal Sources window. See: Defining Journal Sources.
Descriptive Flexfield Validation
Journal Import validates your descriptive flexfield segments in a number of ways depending on the particular descriptive flexfield. If your descriptive flexfield segments are null, then Journal Import does not validate the descriptive flexfield. Otherwise, Journal Import will successfully import your descriptive flexfield data if your descriptive flexfield segments meet the following validation requirements:
Journals - Journal Entry Line Descriptive Flexfield
- The descriptive flexfield global segments have valid values.
- The descriptive flexfield context is a valid value.
- The descriptive flexfield context dependent segments have valid values.
Journals - Captured Information Descriptive Flexfield
- The descriptive flexfield global segments have valid values.
- The descriptive flexfield context dependent segments have valid values.
Value Added Tax Descriptive Flexfield
- The descriptive flexfield context is set to Yes or No.
- The descriptive flexfield context dependent segments have valid values.
USSGL Transaction Code
If you use Public Sector General Ledger, Journal Import validates the USSGL Transaction Code to ensure that it has been defined in the Public Sector Transaction Codes window.
