Document sequence numbers are unique numbers that can be assigned to transactions you create in Receivables. Assigning unique numbers to transactions lets you account for every transaction you enter.
This essay is a discussion on how to implement document sequences in Receivables. Refer to the Defining Document Sequences chapter in the Oracle E-Business Suite Setup Guide for more detailed information on using and defining document sequences and an explanation of the feature.
Receivables gives you the ability to track any transaction from creation to when it is posted. In addition:
By assigning unique numbers to each transaction you can ensure that no transactions have been lost or not posted.
Document sequences generate audit data so even if documents are deleted, their audit record remains.
Document sequences provide an audit trail back from the General Ledger into the sub-ledger, and to the document that originally affected the account balance.
Automatic sequences let you create an audit trail of unique, sequential document numbers without data entry.
Manual sequences let you decide which document numbers you want to assign to transactions at the time of data entry, while always ensuring that your numbers are unique.
Unique, sequential document numbers can be assigned to imported, automatically generated, and manually entered transactions.
You can assign different sequences for every transaction type, receipt method, adjustment, and late charge activity you use.
You can choose to enter document numbers for every transaction or for selected categories of transactions. You can also assign these numbers either manually or automatically.
When you define a new receipt method, transaction type, or receivables activity, Receivables automatically creates a corresponding document category with the same name.
Document categories store the sequence numbers assigned to your transactions to ensure that they are unique within each document type (for example, receipts, transactions, and adjustments).
You can control whether the document number and transaction number are the same for manually entered or imported transactions assigned to a specific batch source. The transaction batch source option Copy Document Number to Transaction Number determines whether these attributes are the same when the transaction is completed or if they are assigned different values.
If the document sequence type for your application is set to Gapless, you can ensure that your transaction numbers are also gapless. Gapless numbering ensures that transaction numbers are sequential and that there are no missing numbers.
To generate gapless transaction numbers, check the Copy Document Number to Transaction Number check box when you define your transaction batch sources. When you complete transactions, Receivables always assigns the same value to both the document number and the transaction number. See: Transaction Batch Sources.