Last updated on MARCH 08, 2017
Applies to:Oracle Receivables - Version 12.0.6 and later
Information in this document applies to any platform.
For Brazil,the sequence number generated was fetched from data base sequence owned by AR.
This sequence call is made during the Autoinvoice run. So when any validation fails for a specific invoice, the sequence number genereated for that invoice becomes useless. Thus, forming a gap in invoice numbers.
Code has been modified to use database sequence owned by JL.
This JL sequence will be called though AR code hook which is available once all validations are complete for an invoice. Thus, ensuring no gaps are formed.
For newly created batch sources, the sequence will be automatically created. For existing batch sources, customer have to run the script: jl8982308.sql
The sequence will be of the form:
'JL_BR_TRX_NUM_'||to_char(p_batch_source_id)'_' ||p_org_id || '_S' where p_batch_source_id is the batch source id of the imported transaction batch source used for AutoInvoices, and p_org_id is the org_id attached to the responsibility.
There is no provision to see the next value of the newly created sequence from Applications. If customer wants to verify the next value of this sequence, he can execute the following query:
The last number in the batch form should reflect the proper number.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms