Professional Documents
Culture Documents
1 of 7
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
Type: HOWTO
Status: PUBLISHED
Priority: 3
In this Document
Goal
Fix
1. Enable Sequential Numbering Profile Option
2. Setup System Options
a. Set Document Number Generation System Option to When Completed
b. Disable Changes to Printed Transactions and Transaction Deletion
3. Define a Transaction Type
4. Define a Batch Source
5. Define a Document Sequence
6. Define a Document Category
7. Assign a Document Sequence to the Document Category
8. Test your Setup
9. Representation in AR Tables
10. Other Gapless Sequence Configurations
11. References
12. Troubleshooting Document Sequences
Still Have Questions?
References
Applies to:
Oracle Receivables - Version 11.5.0 to 12 [Release 11.5.0 to 12.0]
Information in this document applies to any platform.
Form:FNDSNDSQ.FMB - Define Document Sequences
Form:FNDSNDCT.FMB - Define Document Categories
Form:FNDSNASQ.FMB - Assign Document Sequences
Form:ARXTWMAI.FMB - Transactions
Executable:RAXTRX - Autoinvoice Import Program
Executable:ARXREC - Recurring Invoice Program
Goal
Oracle Receivables (AR): AutoInvoice Information Center Note 197212.1
Oracle Receivables (AR): Transactions Workbench Information Center Note 197212.1
This document covers setup specific to gapless document sequences. For a more general discussion on document sequences in Receivables, please review Note
1086565.1, How To Setup Document Sequences In Receivables.
In some countries, it is a legal requirement that transactions are numbered in a gapless sequence for audit purposes.
Gapless document sequences ensure that there are no gaps or missing numbers in your document sequence. By using this feature in tandem with the Copy Document
Number to Transaction Number setting in your transaction source definition, you can generate gapless transaction numbers.
This document provides steps on how to setup Gapless document sequencing within Receivables.
Fix
1. Enable Sequential Numbering Profile Option
The profile option Sequential Numbering must be enabled in order to use the document sequence feature.To ensure gapless numbering, it is recommended that this is
set at the Application Level as Always Used.
Note: By setting this profile to Always used, you will also need to complete the setup of document sequence for your Receipt Methods and Receivable Activities.
Responsibility: System Administrator
Navigation: Profile > System
Query on:
Application = Receivables
Responsibility = Receivables Manager
Profile = Sequential Numbering
4/10/2013 12:54 PM
Document Display
2 of 7
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
4/10/2013 12:54 PM
Document Display
3 of 7
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
4/10/2013 12:54 PM
Document Display
4 of 7
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
A document sequence is defined specifically for a particular application. In this case, GAPLESS_INV1 can only be used within the Receivables application. We specified
the Type =Gapless, and provided the Initial Value = 1000. The first time this document sequence is used, the value will be 1000 and will increment by 1 for each
subsequent use.
Note: Although you are allowed to enter any number for Initial value, you are advised to keep the number low, and not to exceed 10 digits. Otherwise you will
encounter unexpected errors when creating invoices because some pieces of code are unable to handle document sequence values exceeding 10 digits.
Note: For all new records created in the following areas, a row will exist in this form with the following data:
Entity
Application Code
Name
Description
Table Name
Transaction
Types
Receivables
same
value as
Code
RA_CUSTOMER_TRX_ALL
Receipt
Methods
Receivables
same
value as
Code
4/10/2013 12:54 PM
Document Display
5 of 7
Receivable
Activities
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
Receivables
same
value as
code
AR_RECEIVABLES_TRX_ALL
The field Method, designates the manner in which invoices using this category will be created:
Automatic - transactions are created via a concurrent process, such as an external program or something like AutoInvoice which creates transactions without
manual data entry.
Manual - transactions are manually created using a form in an application, such as the Transaction workbench.
Null - transactions can be created either Automatically or Manually.
For our example, the transaction type GAPLESS INVOICE can be used for both manual and automatic processes. Hence, we set the Method = Null. Another way to
implement this is by creating 2 records with the information shown above where all fields are identical except for Method, one row will have Method = Automatic and
the other Method = Manual.
In the Assignment tab, we associate this category to the sequence GAPLESS_INV1 we created earlier.
Ensure that you provide a Start Date that comes prior to any transaction date you will use with this transaction type.
8. Test your Setup
Responsibility: Receivables Manager
Navigation: Transactions > Transactions
Create an invoice using the transaction type GAPLESS INVOICE and take note of the behavior.
4/10/2013 12:54 PM
Document Display
6 of 7
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
Prior to completing the invoice, the fields: Number = 2 and Document Num = null . Since our batch source is enabled to use Automatic Transaction Numbering, the
value 2, is generated by incrementing the Last Number value in the Batch Source GAPLESS BATCH SOURCE.
After completing the invoice, the fields: Number and Document Num now contain 1000. This value is from the sequence GAPLESS_INV1. This shows that during
completion, the document sequence returned the the value 1000, and this value becomes the Document Num as well as replaces the Transaction Number.
9. Representation in AR Tables
If you are interested in seeing what the data looks like in the back-end:
4/10/2013 12:54 PM
Document Display
7 of 7
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_ad...
The original transaction number prior to replacement with document number is stored in the field OLD_TRX_NUMBER.
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support
Receivables Community.
To provide feedback on this note, click on the Rate this document link.
References
NOTE:1086565.1 - How To Setup Document Sequences In Receivables
NOTE:1087122.1 - Troubleshooting Document Sequences in Receivables
4/10/2013 12:54 PM