RFQ, RFI and Auction Numbering Generation

ID# 414531.1
Currently Sourcing. does not provide separate numbering scheme for difference sourcing documents.
They all share the same sequential numbering scheme.
The numbering is based on an internal sequence (oracle sequence) pon_auction_headers_all_s.
This Sequence is setup when the Sourcing product is installed.
For multi round and amended negotiation, the original auction header id is used with the round number/amendment number
to derive the auction/document number.
ID# 464875.1
Use this query to see the sequence generator used for assigning an AUCTION_HEADER_ID (and
DOCUMENT_NUMBER) to sourcing documents.
SQL> select * from dba_sequences
where sequence_name = 'PON_AUCTION_HEADERS_ALL_S';
Notice that the cache_size is set to 1000. This causes the sequence to increase by 1000 each time
a new session is used for creating auctions.

A) To reduce the increment, reduce the cache_size value in dba_sequences for sequence_name
PON_AUCTION_HEADERS_ALL_S to a number less than 1000.
OR
B) Consider the following and commit the change to the database to eliminate the cached values and
just increment the counter by 1 each time.
SQL> ALTER SEQUENCE PON.PON_AUCTION_HEADERS_ALL_S INCREMENT BY 1 NOCACHE;