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

Chart of account values parent and child to use separate value sets.

Summary:

Client has a requirement where their parent node values or node names are descriptive and need to use separate value sets than child value set.

Content (required):

There is a requirement with client to load parent node values in descriptive nature like about 100 chars. Child values are 6 chars always. Sharing same value set is not desirable option given the difference in size. is it feasible to use different value set for parent and child value set ? Such hierarchy needs to be published to cube as well. We have FCCS and downstream systems who will read data from cube and published hierarchy.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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