My Oracle Support Banner

Document Sequencing Number Are Not Gapless When One Sequence Used by Many Transaction Sources (Doc ID 2222703.1)

Last updated on JUNE 15, 2018

Applies to:

Oracle Fusion Receivables Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Symptoms

In Accounts Receivable, document sequence numbers are gapless for the transaction type but not gapless for the transaction source.

EXPECTED BEHAVIOR
-----------------------
Expect document sequence numbers to be gapless by the transaction source not just gapless by transaction type.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
navigation : home: receivables - accounts receivable - transactions - create transactions

Create invoice #1:

        Transaction source: Source 1
        Invoice number: 20007
        Document number: 20007
        Transaction type: TRXTYPE1

Create invoice #2:

        Transaction source: Source 1
        Invoice number:20008
        Document number:20008
        Transaction type: TRXTYPE1

Create invoice #3:

        Transaction source: Source 2
        Invoice number:109000
        Document number:20009
        Transaction type: TRXTYPE1

Create invoice #4:

        Transaction source: Source 1
        Invoice number:20010
        Document number:20010 ---> problem: using 20010 instead of 20009
       Transaction type: TRXTYPE1



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.