FUNPRDSTSB: AGIS Sweep Program Changes CREATED_BY To The Person Running The Sweep Process (Doc ID 1638656.1)

Last updated on MARCH 28, 2014

Applies to:

Oracle General Ledger - Version 12.1.1 to 12.1.3 [Release 12.1]
Oracle Financials Common Modules - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Executable:FUNPRDSTSB - Manual Intercompany Transactions Sweep

Symptoms

FUNPRDSTSB Manual Intercompany Transactions Sweep

If an AGIS batch is created containing one transaction and submitted for approval (status = RECEIVED) but it is not actioned before the AGIS period close, the transaction is swept to the next accounting period successfully. The batch number and all attributes (relevant here: CREATED_BY) remain unchanged. Only the GL_DATE changes.

If however an AGIS batch is created containing two (or more) transactions and submitted for approval and only one transaction is actioned (1 transaction having status = APPROVED and one transaction having status = RECEIVED) before the AGIS period close, the following happens: the transaction that was not actioned is swept to the next accounting period successfully, however a new batch is created for the transaction and the person ID for the person that submitted the sweep program is inserted into the CREATED_BY field. When the transaction is submitted for approval, the approval notification states that the transaction was generated by the person that submitted the sweep and not the person that originally created the transaction.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a batch containing at least two transactions
2. Submit for approval while only one transaction is actioned (Approved) and one is Received
3. The transaction not actioned is swept to the next period
4. Note the ID for person that performed the sweep is inserted into the CREATED_BY field
5. When the transaction is submitted for approval, the approval notification states that the transaction was generated by the person that submitted the sweep and not the person that originally created the transaction.


Changes

One transaction out of two is swept only.

Cause

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 hundreds of Community platforms