My Oracle Support Banner

Application with journals getting failed while Importing / Exporting application in Oracle Financial Consolidation and Close Cloud. (Doc ID 2310235.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Financial Consolidation and Close Cloud Service - Version 16.05 to 17.09.49 [Release 16.0 to 17.0]
Information in this document applies to any platform.

Symptoms

Relational data/Journals:- The Import file (/Relational data/ Journals.xml) was not found for the artifact - Journals

Changes

1. If a user created journals with scenario "forecast" and the corresponding id is stored in the journal table.
2. Now, user modifies the metadata and removes the forecast member or renames it.
3. Now when we try exporting the journal the old id pointing to forecast will not get the member and will fail..

Cause

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
Symptoms
Changes
Cause
Solution

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