A document sequence uniquely numbers documents generated by an Oracle Applications product. Using Oracle Applications, you initiate a transaction by entering data through a form and generating a document, for example, an invoice. A document sequence generates an audit trail that identifies the application that created the transaction, for example, Oracle Receivables, and the original document that was generated, for example, invoice number 1234.
Document sequences can provide proof of completeness. For example, document sequences can be used to account for every transaction, even transactions that fail.
Document sequences can also provide an audit trail. For example, a document sequence can provide an audit trail from the general ledger into the subsidiary ledger, and to the document that originally affected the account balance.
Document sequences generate audit data, so even if documents are deleted, their audit records remain.
To define a sequence, you select a sequence name and an application to “own” the sequence.
A sequence can number documents stored in database tables belonging to its owning application.
Audit records for a sequence are stored in the application’s audit table, titled Application Short Name_DOC_SEQUENCE_AUDIT. For example, the audit table for a sequence owned by Oracle Payables is AP_DOC_SEQUENCE_AUDIT.
Example of document sequence on some Oracle Apps forms:
Payables Invoice:
Voucher Number is generated by Oracle automatically using document sequence.
Payment:
Document Num is generated by Oracle using another sequence.
Configuration steps
Oracle Apps 11i
Step 1: Create a new sequence
Responsibility: General Ledger SuperUser
Navigation: Setup > Financials > Sequences > Define
Create a new record for a new sequence.
Step 2: Assign the new sequence to a document type
Navigation: Setup > Financials > Sequences > Assign
Document tab
Select the Application,Category and Set of Books to which the new sequence will be attached.
Assignment tab
Now add the sequence to this document type. If a sequence is already added to this application, category and set of books and it is not end dated, then the previous sequence needs to be end dated before the new sequence can be added.
Oracle Apps r12
Document Sequences
Responsibility: System Administrator
Navigation: Application > Sequential Numbering > Define
Query for Name = Journal Sequence
You can see the sequence name Journal sequence is created.
Check Categories
Navigation: Application > Sequential Numbering > Categories
Query for application = General Ledger
The categories defined under this application are displayed.
Now we shall check the categories to which the sequence, Journal sequence, is added.
Sequence Assignments
Navigation: Application > Sequential Numbering > Assign
Query for Sequence = Journal sequence (This field is in the Assignment tab)
Document tab
Assignment tab
As you can see the sequence, Journal sequence, is added only to Adjustment category.
Cheers!
Related articles
- Procure To Pay (P2P) Process flow (oraclemaniac.com)
- Open or Close Periods in Oracle Apps (oraclemaniac.com)
- Audit trail reporting (oraclemaniac.com)
- How to add a Descriptive Flexfield (DFF) in a custom Oracle Apps form (oraclemaniac.com)
- Create and register a custom Descriptive Flexfield (DFF) (oraclemaniac.com)
- How to enable General Ledger Journal approval (oraclemaniac.com)
- Transaction to Receipt flow in Oracle Receivables (oraclemaniac.com)
- Points to keep in mind while developing Oracle Apps forms (oraclemaniac.com)
- Oracle iExpenses flow (oraclemaniac.com)
- Oracle tables that store patch information (oraclemaniac.com)
