Adjustment Entries Into PP Does Not Populate GL Codes To Correct GL Code Column
(Doc ID 2831329.1)
Last updated on JANUARY 05, 2022
Applies to:
Oracle Financial Services Analytical Applications Reconciliation Framework - Version 8.0.0 and laterInformation in this document applies to any platform.
Symptoms
While executing the GL recon rules in 8.1, GL codes are not being populated to the right GL code column name, instead, they are being populated into V_GL_CODE by default.
Example : select * from fsi_gl_map_recon_targets where v_gl_map_id=#MAP_ID# and n_version_number=#VERSION_NO#;
| V_LOGIC_TABLE_NAME | V_GL_CODE_COL_NAME | V_GL_CODE_LOGIC_COL_NAME | V_BALANCE_LOGIC_COL_NAME |
| Stage Guarantees | V_CUST_ACC_INT_SOLD_GL_CODE | Accrued Interest Sold Amount | Gl Code Accrued Interest Sold Amount |
| Stage Letter of Credit Contracts | V_CUST_ACC_INT_SOLD_GL_CODE | Accrued Interest Sold Amount | Gl Code Accrued Interest Sold Amount |
| Stage Loan Contracts | V_CUST_ACC_INT_SOLD_GL_CODE | Accrued Interest Sold Amount | Gl Code Accrued Interest Sold Amount |
Now as per the above example the V_GL_CODE_COL_NAME is V_DESJ_ACC_INT_SOLD_GL_CODE, but when the adjustment entries are posted to the PP table it is inserting the GL code into the "V_GL_CODE" column instead of the "V_DESJ_ACC_INT_SOLD_GL_CODE".
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 |
| References |