AR_ADJUST_PUB.Reverse_Adjustment: APP-AR-11503: Invoice type adjustment must make the balance due zero (Doc ID 2060596.1)

Last updated on MARCH 07, 2017

Applies to:

Oracle Receivables - Version 11.5.10.2 and later
Information in this document applies to any platform.
Issue is also replicable in R12(12.1.3)

Symptoms

On : 11.5.10.2(also 12.1.3) versions, Transactions Related

The adjustment reversal created from the form is behaving different from the API- AR_ADJUST_PUB.Reverse_Adjustment

have a look at the given scenarios:


I. Create an Invoice with amount, say x$
II. Create an adjustment of amount, -x$ on this Invoice 

Case A: 
In this case, the user_id passed while using the API script has higher approval limits than x$
Use the API to reverse this adjustment - AR_ADJUST_PUB.Reverse_Adjustment
Amount=x$

Result A:

API script is successfully executed. Adjustment reversal of type 'INVOICE' is created and approved automatically for this Invoice.

Case B:

In this case, the user_id passed while using the API script has lower approval limits than x$
Use the API to reverse this adjustment - AR_ADJUST_PUB.Reverse_Adjustment
Amount=x$

Result B:

API script is successfully executed. Adjustment reversal of type 'INVOICE' is created, but is pending approval. 
When the approver having higher approval limits than x$ tries to approve it, he receives an error message:

APP-AR-11526: arp_process_adjustment.update_adjustment exception:
ORA-20001:APP-AR-11503: Invoice type adjustment must make the balance due zero.


Case C:

Do Not use API. Create a reversal adjustment of type 'INVOICE' from the form on this Invoice. 
Amount= x$

Result C:

This is not allowed. User receives an error message:
APP-AR-11503: Invoice type adjustment must make the balance due zero.

Case D:

Do Not use API. Create a reversal adjustment of type 'LINE' from the form on this Invoice. 
Amount= x$

Result D:

This is allowed, and the adjustment reversal is successfully created, invoice balance is changed as expected.

The UI and the API are supposed to be in sync, but the listed scenarios show that this is not the case. This makes the issue a "potential bug".

 

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