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.
Attention: Your database administrator must grant access to an application's audit table for all ORACLE usernames associated with responsibilities that will use the sequence (responsibilities that access forms using the sequence).
You can set start and end dates for when the sequence is available. The start date defaults to the current date. By default, there is no end date, so the sequence definition does not expire.
You can choose whether a sequence numbers documents automatically, or accepts numbers manually entered by a user.
Automatic numbering assigns a unique number to each document as it is generated. Automatic numbering is sequential by date and time of creation.
Gapless numbering also automatically generates a unique number for each document, but ensures that the document was successfully generated before assigning the number. With Gapless numbering, no sequence numbers are lost due to incomplete or failed document creation.
Attention: We recommend that you choose this type only when gapless numbering is essential, as it may affect the performance of your system.
Manual numbering requires a user to assign a unique number to each document before it is generated. With manual numbering, numerical ordering and completeness is not enforced. Users can skip or omit numbers when entering the sequence value.
If you define a sequence to automatically number documents, you can:
Enter an initial value for your sequence. The default is "1".
Choose whether you want to display a message when a document is generated, telling the user the name of the sequence, and the sequence value (document number).
Two examples of sequence definitions, one with automatic numbering and the other with manual numbering, are represented in the table below.
| Field in Document Sequences form | EXAMPLE 1 Sequence with Automatic Numbering | EXAMPLE 2 Sequence with Manual Numbering |
|---|---|---|
| (Sequence) NAME | AUTOPAY | ADJUSTMENTS |
| (Owning) APPLICATION | ORACLE PAYABLES - Sequence can number documents stored in an Oracle Payables database table. | ORACLE RECEIVABLES - Sequence can number documents stored in an Oracle Receivables database table. |
| EFFECTIVE DATE - START | CURRENT DATE & TIME (Default value) | OCT-01-94 User defines sequence "Adjustments" not to be available until Oct 1, 1994. |
| EFFECTIVE DATE - END | Field left blank. Sequence does not expire. | DEC-31-94 User defines sequence "Adjustments" to no longer be available after Dec 31, 1994. |
| (Numbering) TYPE | AUTOMATIC - Unique numbers are automatically generated in sequence. GAPLESS No omissions or gaps in numbers are possible, due to a rollback if the document creation is unsuccessful. | MANUAL - User must enter a unique number before transaction can be completed, and document is generated. User may skip or omit numbers. |
| INITIAL VALUE | 1 (Default value) User could enter their own initial value, for example, 5700. | Not Available when numbering type is Manual. |
| MESSAGE | YES - When a document that is automatically numbered is created, a message displays the sequence name and the sequence value (document number). | Not Available when numbering type is Manual. |