My Oracle Support Banner

How Does Journal Import Derive DEFAULT_EFFECTIVE_DATE for Journal Batches in R12 (Doc ID 1679020.1)

Last updated on JULY 12, 2019

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.
Executable:GLLEZL - Journal Import

Goal

How Is DEFAULT_EFFECTIVE_DATE Derived For Imported Journal Batches In R12?

What is the logic with which DEFAULT_EFFECTIVE_DATE is derived?
In R12 the DEFAULT_EFFECTIVE_DATE at batch level (GL_JE_BATCHES) is different compared to R11i for the same set of input transactions.

For Example:
1. Created two invoices using effective date as 16-May-14 and 17-May-14 and transferred to GL .
2. DEFAULT_EFFECTIVE_DATE is 16-May-14 whereas individual journal header effective dates are 16-May-14 and 17-May-14.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.