Professional Documents
Culture Documents
In This Document: Goal Solution References
In This Document: Goal Solution References
In this Document
Goal
Solution
References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process
and therefore has not been subject to an independent technical review.
APPLIES TO:
GOAL
When the AR/AP or GL period is already closed, the AGIS transaction can no longer be
transferred to subledgers/ GL in order to be processed for completion.
How to process further an AGIS batch when the Receivables /Payables period was already
closed?
There are situations when the AGIS batch is created in September for example, but it is
approved in October, when the Receivables /Payables period for Sep-14 was already closed.
As the AGIS Batch has 19-Sep-2014 as GL date, the transaction cannot be imported in AR
since AR period is Closed.
Therefore, there is a need to sweep this batch completely into the current open period, so that
it creates both AR and AP transactions in October period.
SOLUTION
There are several situations which might appear:
a. In this case, one can run 'Manual Intercompany Transactions Sweep' program in
order to move the open transactions to the next Open period.
For more details on what this program does, please review Note 1086201.1: Which
Transactions are Processed by FUNPRDSTSB 'Manual Intercompany Transactions
Sweep' ?
This is in order to avoid an issue which appears for swept transactions, because the AR
transfer program is checking the batch date, while the Sweep program changes only the
GL date of the batch. This is causing error "Receivables Period Is Not Open" although
the AR period is Open.
c. Alternatively, you can Recall the transaction and re-enter it in the new period.
2) The AGIS transaction was Approved as described in the Goal section above.
In this case, 'Manual Intercompany Transactions Sweep' program can not be run as it does
not sweep transactions in any of the statuses below:
Transferred to Receivables
Transfer to Initiator GL
Transfer to Recipient GL
Approved
For this, Enhancement Request was raised as Bug 18677885 : Ability to move approved
transactions into the next period.
Until the enhancement will be implemented, the supported solution for the Approved
transactions will be to Reverse the affected transactions, provided that you did not opt for
Online transfer of transactions to subledgers