AR Adjustment

AR Period Close Error: When There are Pending Adjustments, Attempting to Close the Period Raises Error: AR_SU_PENDING_GL_TRANSFER (文档 ID 1197693.1) 转到底部转到底部

In this Document


Symptoms

Changes

Cause

Solution
  1. Bug Summary
  2. Fixed Files
  3. Recommended Patches
  4. Solution Steps
  Still Have Questions?

References


APPLIES TO:

Oracle Receivables - Version 12.0.6 and later
Information in this document applies to any platform.

SYMPTOMS

You are attempting to close the AR period and find an error AR_SU_PENDING_GL_TRANSFER.

You cannot close AR period due to one incomplete adjustment number showing on the subledger period close exception report.

This adjustment is awaiting approval. 

In 11i, a period can be closed with Incomplete Adjustment.  
However, in R12 the functionality has changed and you have to either Reject/Approve the Adjustment or change the GL Date.

The subledger period close exception report displays pending adjustments as incomplete.
Query adjustment through AR application and you will see that adjustment is in status 'awaiting approval'.

Note: If you are encountering a similar error due to Incomplete transactions, please review Note 1233033.1, Incomplete Transactions in Subledger Period Close Exception Report (XLAPEXRPT) are Preventing You From Closing AR Period

 

CHANGES

None

CAUSE

This issue was reported in Bug 12760514 NEED TO BE ABLE TO CLOSE THE PERIOD WITH INCOMPLETE ADJUSTMENTS

There are pending Adjustments that are either waiting to be Approved or Rejected. Receivables will not allow period to be closed if pending adjustments exists in the period.
Pending adjustments will have unaccounted events in SLA and period cannot be closed with unaccounted events.

SOLUTION

1. Bug Summary

  1. Description
    GL Period cannot be closed when there are pending/incomplete adjustments.

  2. Workaround
    You have to either Reject/Approve the Adjustment or change the GL Date to resolve all the adjustments prior to closing period.

    To remove adjustment from subledger period close exception report:
    1. Sign into AR responsibility and navigate to Control > Adjustments > Approve
    2. Query adjustment number and either approve or reject this adjustment.

    a) If adjustment is approved then run create accounting to process this adjustment. This adjustment will no longer show on the subledger period close exception report as incomplete.
    b) If adjustment is rejected then this adjustments will no longer show on the subledger period close exception report.  The subledger period close exception report does not display rejected adjustments.

    If the adjustment cannot be approved or rejected before period close then you have two options:
    1. Set the next period status to Open or Future and change the GL DATE of pending adjustments to next period.
    2. If the next period status cannot be changed to Open or Future then set the current period status to Pending Close. 
    Whenever the next period is opened, change the GL DATE of pending adjustments to next period and change the period status from Pending Close to Close.
    However, before changing the period status to Close Pending ensure that:
    a. There are no unposted items other than pending adjustments. 
        Run the Unposted Items Report and Subledger Period Close Exception Report.
    b. Run the Revenue Recognition Program to process 'Invoices with rules'.

  3. Resolution
    Modified the code to remove the restriction on closing periods due to Pending Adjustments.

2. Fixed Files

R12.AR.A: 
ad_apply_patch.xml 120.3.12000000.2
ARXLAEVB.pls 120.48.12000000.42

R12.AR.B: 
ARXLAEVB.pls 120.56.12010000.22

R12.AR.C: 
ARXLAEVB.pls 120.85.12020000.5

PROACTIVE TIP: 
Applying higher versions of the files listed above can help you avoid known issues. Use Note 1584999.1 to help identify other patches containing higher versions of these files.

 

3. Recommended Patches

R12.AR.A: No released patch available.
R12.AR.B: Patch 12760514
R12.AR.C: No released patch available.

4. Solution Steps

  1. Ensure that you have taken a backup of your system before applying the recommended patch.
  2. Apply the patch in a test environment.
  3. Confirm the file versions listed above, by navigating to the directory where the file is and using:
    strings -a |grep '$Header'
  4. Retest the issue.
  5. Migrate the solution as appropriate to other environments.
  6. If the patch for your release is unavailable for download or needs a password, or if you experience any issues applying this patch, please contact the E-Business Patching Community for assistance.

 

Still Have Questions?

 

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 icon at the top right corner of this note.

REFERENCES



请使用浏览器的分享功能分享到微信等