ARXCUDCI - Customer Account Numbering Is Skipping Next Sequence Value For Potential Duplicate Address
(Doc ID 1403113.1)
Last updated on SEPTEMBER 21, 2018
Applies to:Oracle Receivables - Version 18.104.22.168 and later
Information in this document applies to any platform.
In 22.214.171.124, automatic numbering for customer accounts is used and the sequence is set to no cache. However, when creating a new customer account with a new address that is a potential duplicate of existing addresses, the next value in the sequence is being skipped.
Query the customer accounts in HZ table and note the next account number was skipped.
The skipping only occurs when there is a potential duplicate and when users are creating a customer account address for a new customer account, not an existing customer account.
This can be reproduced every time.
The sequence is set as follows:
CREATE SEQUENCE AR.HZ_ACCOUNT_NUM_S
START WITH 6102935
Steps to reproduce:
-Responsibility: Receivables Manager
-Navigation: Customers > Standard
-Create a new customer account.
-Enter an address that is a potential duplicate of an existing address.
-Save the record. Note the warning that this address is a potential duplicate of existing accounts.
-Click Save New Account.
-Note the address form lists the account name and an account number: 6102937
-After that, the account number is the next available in the sequence.
-Close the Customer Addresses window and note that the actual customer account has skipped to next value in the sequence: 6102938.
-Run the following query and 6102937 doesn’t show in query of hz_cust_accounts table:
where account_number > 6102930 ;
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
|Still Have Questions?|