Two PC Contracts Have the Same Accounting Serial Number
(Doc ID 2451948.1)
Last updated on NOVEMBER 26, 2019
Applies to:Oracle FLEXCUBE Universal Banking - Version 12.0.3 and later
Information in this document applies to any platform.
Bank reported that there are two PC contracts for which ac_entry_ref_no is same
Case is as below:
When the contract was initiated from one branch (Branch1), mark BOD process was running in another branch (Branch2) where the accounting serial number was generated. This accounting serial number is a combination of Julian date and sequence generated. Below is the sequence of events
- Date was changed (date in sttm_date updated to 27th Jul) first for branch (Branch2) and then sequence drop starts product-wise(IBII in this case). The moment first product sequence is dropped, update on sttm_dates will get committed where the rest of the sequences is still being dropped.
- In the meantime, if system try to fetch next sequence of the product IBII, Julian date will be picked for 27th Jul, sequence will be 0049 resulting in reference number <Ref1>. Once product sequences are dropped and next PC contract is booked and since IBII sequence is not available, new sequence will be created resulting in serial number <Ref2>. If more than 48 contracts are booked in branch 000 on same day, 49th contract will have serial number <Ref1>again.
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