How a DRG Request Numbering Creates When Multiple Request Items Exists and a New Request Added?
(Doc ID 2883678.1)
Last updated on JULY 20, 2022
Applies to:Hyperion Data Relationship Management - Version 184.108.40.206.000 and later
Information in this document applies to any platform.
How request ID gets generated when multiple request items exists and a new request added on top of it?
1. Last committed ID number in May was 108
2. Request 1 for June for had 5 new rollups
a. 109 assigned
b. 110 assigned
c. 111 assigned
d. 112 assigned
e. 113 assigned
3. Request 2 for June had 1 new rollup
a. 110 assigned
b. How did it get 110 if the next available NOT YET COMMITTED was 109? Why wouldn’t it also get 109?
4. Request 2 was approved and committed first so Request 1 went to error when committed because 110 was already taken
5. Other requests took subsequent numbers and were committed successfully
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