An Orastudy Site | Oracle ERP 专业站点

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

The setting of Document Number Generation Level in the System Options form allows you to specify when Receivables should generate a document number for your transactions. This should be set to When completed so that the sequence is only invoked when the transaction is finalized.

To prevent the removal of transactions which have already been assigned gapless document sequence numbers, uncheck the check boxes for Allow Change to Printed Transactions and Allow Transaction Deletion.

Responsibility: Receivables Manager
Navigation: Setup > System > System Options

Define a transaction type which you will use to create invoices. A document category (discussed in step 5) is automatically created for each transaction type you create.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Transaction Type

There is no way to enforce gapless numbering directly on transaction number and the only way to do this is to create a gapless document sequence and then have it replace the transaction number by enabling Copy Document number to Transaction number.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

Take note of the following settings:

• Automatic Transaction Numbering – this check box has nothing to do with document sequencing. This feature simplifies the data entry process by assigning a system generated transaction number to the invoices that are created using this batch source. The number is unique but is not guaranteed to be gapless. When you check this, you are required to enter a value in Last Number.
  
• Last Number – this field contains the starting sequence number from which a counter will be created to determine the next value to assign to subsequent invoices created using this Batch Source.
  
• Copy Document Number to Transaction Number – this check box is impacted by the document sequence setup. By checking this, you are instructing Receivables to generate a document sequence for your invoice and use that to replace the current transaction number whether it was automatically generated or manually inputted.
  

Create a database sequence that will be used to generate a document sequence for your transactions.

Responsibility: System Administrator
Navigation: Application > Sequential Numbering > Define

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.

This step is no longer necessary in release 11.5, because document categories are automatically created for you when you define a new transaction type (or receipt method or receivable activity).

In this step, you create a relationship between the document category and the document sequence created earlier through an assignment.

Responsibility: System Administrator
Navigation: Application > Sequential Numbering > Assign

This form has 2 tabs, in the Document tab, create a new record as shown:



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.

Responsibility: Receivables Manager
Navigation: Transactions > Transactions

Create an invoice using the transaction type GAPLESS INVOICE and take note of the behavior.

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.

If you are interested in seeing what the data looks like in the back-end:

The original transaction number prior to replacement with document number is stored in the field OLD_TRX_NUMBER.

Using the number series to help identify the transaction type:
You can repeat this process for as many transaction types as you need to be Gapless. You can define the Initial value of the sequences so that you can identify a transaction’s type from it’s transaction number. For example: Invoices have transaction numbers in the 100000 series, Credit Memos have transaction numbers in the 200000 series and Debit Memos have transaction numbers in the 300000 series.

In doing such an implementation, care must be taken to ensure that the document sequence values never overlap, otherwise you will no longer be able to identify the transaction types from just the transaction number, further the transaction numbers will no longer be unique.

Using the same document sequence across operating units:
If you have the business requirement of sharing a document sequence across operating units, this can be done by assigning the same Gapless document sequence to different document categories. However, please remember the following restrictions:

You can associate several transaction types to a particular document sequence for as long as all these transaction types belong to operating units that use the same ledger, you cannot assign a document sequence defined in ledger 1 to a document category in ledger 2.

Impact of Gapless numbering on Consolidated Billing Invoices
In release 11.5, the Consolidated Billing Invoices (CBI) feature is used to group individual invoices for a particular customer. The numbering of a consolidated bill is not covered by the Gapless transaction numbering feature, as this is simply an artificial grouping of distinct invoices, hence your CBI number may have gaps. True gapless numbering is only implemented on individual invoices.