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
Impact of end dating a Balancing Segment value which is used as default in all setups — 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

Impact of end dating a Balancing Segment value which is used as default in all setups

Received Response
21
Views
1
Comments
edited May 11, 2020 1:30PM in Financials – General 1 comment

Content

The company operations are being shifted from an existing legal entity that is setup in fusion to a new legal entity which needs to be newly setup. The Balancing Segment value (BSV1) that is assigned to the existing legal entity is used as default BSV in all setup code combinations including the retained earnings code combination and all subledger setups. This legal entity and BSV eventually needs to be end dated. The new legal entity to be setup will be assigned to new balancing segment value (BSV2). 

So the ask is to replace all default setup code combinations currently setup with BSV1 and update it to BSV2. Can you please let us know the impact of the same including replacing the BSV in Retained Earnings account and all other setups too. Note that there are already existing transactions posted in the BSV1.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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