BSP 8 Member Not Found in Database Errors Running Financial Element Load Rule After Running BSP Cash Flow for Current Position
Last updated on SEPTEMBER 28, 2016
Applies to:Oracle Financial Services Balance Sheet Planning - Version 8.0.1 and later
Information in this document applies to any platform.
Oracle Financial Services Balance Sheet Planning (BSP)
On BSP 126.96.36.199.1, when loading current position, the following errors are received for rejected financial elements during the last step that loads data into Essbase. The errors are not logged in the fusion apps log but they do appear when loading data into Essbase loading the "impCBCC1.rul" load rule in EAS.
\\ Member C183 Not Found In Database
\\ Member C193 Not Found In Database
\\ Member C198 Not Found In Database
\\ Member C213 Not Found In Database
\\ Member C225 Not Found In Database
\\ Member C235 Not Found In Database
\\ Member C245 Not Found In Database
The following message appeared in the Essbase application log which is why we ran the import manually in EAS with the load rule noted above.
>>> DATAERRORLIMIT reached . Rejected records will no longer be logged
The issue can be reproduced at will with the following steps:
1. Run a cash flow current position for an entity/chart of account combination that has data that would generate one of the following financial element id's (C183, C193, C198, C213, C225, C235, C245).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms