oracle apps Journal Import Validation Process

Posted by

The Oracle Apps Journal Import validates the accounting data received from other systems in the GL_INTERFACE Table. The list of  journal error lines will be published in the Journal Import Execution Report.

Batch Level Validation:

Journal Import validates the below attributes so that the  batch name available for processing should not already exist for the same Ledger Id  Period in the Oracle Apps  General Ledger application for the particular Period

  • Ledger Id
  • Period Name
  • Batch Name

Journal Level Validation:

Journal Import validates the below attributes so that the journals available for processing should have the required accounting data

  • Ledger Id
  • Period Name
  • Journal Source Name
  • Journal Category Name
  • Currency Code
  • Encumbrance type ID
  • Actual Flag
  • User Conversion Type
  • Budget Version Id
  • Accounting Date

Journal Entry Line Level Validation:

Journal Import validates the below attributes so that the journals available for processing should have the required accounting data

Account Validation ( Code Combination) : 

Code Combinations will be considered valid and journal import will be processed successfully if the below validations exists:

  • If detail posting to segment combinations are allowed
  • If code combinations are enabled for the specified accounting date
  • If  code combinations does not include summary accounts

Effective Date Validation: 

Journal Import validates if the Accounting Date is a valid business day and thus General Ledger considers it as the transaction’s effective date.  Below are the Effective Date Rule defined in oracle apps for General Ledger Accounting Date:

  • Fail:   Journal Import will Reject the transactions
  • Leave Alone: Journal Import will consider transactions regardless of the Accounting Date
  • Roll Date:  Journal Import will roll the Accounting Date  to the nearest valid business day

Descriptive Flexfield Validation:

Journal Import validates the descriptive flexfield segments depending on the particular descriptive flexfield.

  • Journals – Journal Entry Line Descriptive Flexfield
    • The descriptive flexfield global segments have valid values
  • Journals – Captured Information Descriptive Flexfield
    • The descriptive flexfield context dependent segments , descriptive flexfield context  and descriptive flexfield context dependent segments  have valid values
  • Value Added Tax Descriptive Flexfield
    • The descriptive flexfield context is set to Yes or No and descriptive flexfield context dependent segments have valid values

USSGL Transaction Code:

In case of  Public  Sector General Ledger, Journal Import validates the USSGL Transaction Code