GL_INTERFACE Is not Deleted When Rollback Journal Entries Is Run with Different NLS Language against Create Journal Entries
(Doc ID 2428757.1)
Last updated on AUGUST 25, 2020
Applies to:
Oracle Assets - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]Information in this document applies to any platform.
Symptoms
GL_INTERFACE is not deleted when Rollback Journal Entries is run with different NLS language against Create Journal Entries.
Example:
- Run Create Journal Entries with Japanese.
Parameter :
Run Journal Import : No - Run Rollback Journal Entries with English.
The Assets data is done a rollback however GL_INTERFACE is not deleted.
NOTE:
These GL_INTERFACE cannot import to GL with Journal Import due to the following error because these GL_INTERFACE does not have the relationship about FA data.
Log of Journal Import:
Error in: gllcfa
Function return status: 0
Function Err Message: sqlerror trapped at sqlerr
Function warning number: -1
*****************************************************
sqlcaid: sqlabc: 0 sqlcode: -20000 sqlerrml: 70
sqlerrmc:
ORA-20000: fa_journals_pkg.update_gl_info failed
ORA-06512: at "APPS.F
sqlerrp: sqlerrd: 0 0 0 0 0 538976343
sqlwarn: W W sqltext:
*****************************************************SHRD0044: Process logging off database and exiting ...
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
Starting fa_journals_pkg.update_gl_info at: 28/06/2018 13:57:55
ORA-06550: line 18, column 17:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 12, column 10:
PL/SQL: SQL Statement ignored
ORA-06550: line 48, column 20:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 48, column 13:
PL/SQL: SQL Statement ignored
Error: function fa_journals_pkg.summary_update returned failure
Error: function fa_journals_pkg.update_gl_info returned failure
Failed in fa_journals_pkg.update_gl_info at: 28/06/2018 13:57:55
Getting Debug information
fa_journals_pkg.update_gl_info: -------------------------------------------------------------------------------- has the value of
fa_journals_pkg.update_gl_info: X_book_type_code has the value of <Book Name>
fa_journals_pkg.update_gl_info: X_period_counter has the value of 24170
fa_journals_pkg.update_gl_info: X_cje_id has the value of 9016
fa_journals_pkg.update_gl_info: X_je_batch_id has the value of 62505
fa_journals_pkg.update_gl_info: X_je_header_id has the value of 55891
fa_journals_pkg.update_gl_info: X_group_id has the value of 529
fa_journals_pkg.update_gl_info: X_set_of_books_id has the value of 7003
fa_journals_pkg.update_gl_info: X_je_category has the value of Depreciation
fa_journals_pkg.update_gl_info: X_batch_type has the value of DEPRECIATION ****
fa_journals_pkg.update_gl_info: fetching has the value of info from fa_journal_entries
fa_journals_pkg.update_gl_info: updating fa_journal_entries has the value of setting source type and cjeid
fa_journals_pkg.update_gl_info: l_je_info_rec.posting_level has the value of D ****
fa_journals_pkg.check_setups: preparing has the value of bonus check statement
fa_journals_pkg.check_setups: executing has the value of bonus check statement
fa_journals_pkg.check_setups: preparing has the value of group check statement
fa_journals_pkg.check_setups: executing has the value of group check statement
fa_journals_pkg.check_setups: X_je_info_rec.bonus_used has the value of TRUE
fa_journals_pkg.check_setups: X_je_info_rec.reval_used has the value of TRUE
fa_journals_pkg.check_setups: X_je_info_rec.group_used has the value of FALSE
fa_journals_pkg.check_setups: X_je_info_rec.batch_size has the value of 1000
fa_journals_pkg.check_setups: X_je_info_rec.posting_level has the value of S
fa_journals_pkg.update_gl_info: mrc_sob_type_code has the value of P
fa_journals_pkg.summary_update: Start Time for summary update has the value of 28/06/2018 13:57:55
fa_journals_pkg.summary_update: preparing has the value of statement for deprn temp table tie back
fa_journals_pkg.summary_update: executing has the value of statment for deprn temp table tie back
Changes
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 |