MFCS Financial System Integration Setup Of Clearing Accounts (Stage)
(Doc ID 2883794.1)
Last updated on DECEMBER 19, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Goal
With V19, the Financial System integration configuration requires the creation of Clearing Accounts for stock ledger transactions that do not map to the Financial System. At month end, if there are still transactions not mapped to the Financial System, and there are no Clearing Accounts configured, the Month End process will fail. Need to document the new process for managing this in the Cloud.
Client is using Cost Accounting method, and currently only have "C" records in their fif_gl_cross_ref table for mapping to GL. Since we have noticed that several of the Code_Detail table records, for example, Code Type = GLRT, contain an additional field for "Used" or not, we are concerned that we will need to mark the "R" transactions codes to "N". They are all currently set to "Y" in the "Used" field. We need Oracle's help with understanding how the Code Detail settings may impact mapping transactions to the fif_gl_cross_ref. For example, if GLRT settings are all "Y" in Used Column for transaction codes 01C and O1R, will the mapping in fifgldn1 expect to see both a "C" record and a "R" record in fif_gl_cross_ref?
Client located a new Code Detail Type record = GLTP, which allows them to set Clearing Accounts to "N". If Client chooses not to use the Clearing Account via the Code Detail table in the GLTP code type, what impacts do they expect?
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 |