Update Customer Account sequence starting point WITHOUT using Document Sequencing

Summary:

Our client has no use case for using document sequencing in AR, except for the Customer Account number sequence. Is there a way for Oracle to update the sequence (next number…) in the back-end tables somewhere? This way we would NOT need to enable document sequencing for an entire subledger that otherwise has no need for this configuration.

Content (please ensure you mask any confidential information):

In an earlier development phase, we did have document sequencing enabled and were able to use the task Manage Document Sequences for the BILLING_ACCOUNT_NUMBER to successfully change the next number for manually creating customers in the UI. Document sequencing caused a lot of issues - that we are looking to avoid if it is not necessary. Ultimately, document sequencing is not necessary at all for this customer - except for this one customer account numbering sequence.