Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
'Calculate Movement' rule doesn't calculate correct movement , if data loaded to View: YTD_Input , i — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

'Calculate Movement' rule doesn't calculate correct movement , if data loaded to View: YTD_Input , i

Received Response
45
Views
5
Comments
edited Dec 24, 2020 1:39AM in Financial Consolidation and Close 5 comments

Summary

Nov-CB = 0 and DEC-CB is also 0 , which is being loaded to 'YTD_Input' using data management. However, FCCS is calculating wrong closing balance (-39984.) instead of 0.

Content

1. 'Calculate Movement' rule doesn't calculate correct movement , if data loaded to View: YTD_Input , is same in current month and prior month.
2. Nov-CB = 0 and DEC-CB is also 0 , which is being loaded to 'YTD_Inout' using data management. However, FCCS is calculating wrong closing balance (-39984.) instead of 0

3. As per our investigation, Dec-2020 update : "When you load data in YTD_Input, if the current period value is the same as the prior period value, the system no longer stores a zero (0) Periodic value.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!