My Oracle Support Banner

12.1.3+ Deduction / Overpayment Moving Back To Open Status From Cancelled After Approval Patch 21201186:R12.OZF.B Details (Doc ID 2045335.1)

Last updated on MARCH 18, 2019

Applies to:

Oracle Trade Management - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
This document is continuation for the document “12.1.3+ CONSOLIDATED PATCH MAR 2013 Patch 16198653:R12.OZF.B” Doc ID 1538404.1

The information included in this document assumes that you have already installed Oracle E-Business Suite 12.1.3 Release Update Pack

* Oracle E-Business Suite 12.1.3 Release Update Pack (12.1.3), features and other information, refer to <>

Details

Features in this release:

Feature 1 - Introduced by <Patch 21201186> R12.OZF.B
==================================================

A deduction/overpayment is created, settled and moved to pending Approval state.

While the claim is in pending approval state the source receipt is opened and un-applied as a result the claim is moved to cancellation state. When the claim is rejected by approver the claim is moved back to open status

 Changes are included in the patch to restrict user changing the claim when the claim is in pending approval state other than the approver (reject/approve).

 

Feature 2 - Introduced by <Patch 20387353> R12.OZF.B
=================================================

Un-applying a receipt from Invoice was reopening the Deduction/Overpayment in Pending Approval status. After this patch, if user tries to un apply a receipt line which is having a Claim in Pending Approval status associated with it, un apply is restricted with the following error message:

"Associated claim could not be updated because it is in Pending Close or Pending Approval status."

 

Feature 3 - Introduced by <Patch 19861775> R12.OZF.B
==================================================

The claims/child claims are not getting cancelled if the parent is closed when once receipt is applied which closes the invoice.
After this patch, the split claims also will go to cancelled status regardless of the status of the parent claim.

To update the claim/split claim by applying subsequent receipt from AR,
Customer has to apply the AR <Patch 19127398> R12.AR.B.

 

Feature 4 - Introduced by <Patch 19705251> R12.OZF.B
=================================================
When a non invoice deduction is netted by receipt to receipt application, if the deduction is cancelled and there are split claims which are open, then the split claims is not going to cancelled status. After this patch, the split claims also will go to cancelled status regardless of the status of the parent claim.

 

Feature 5 - Introduced by <Patch 16801224> R12.OZF.B
==================================================

I. What are the contents of this patch?
Fix for Bug 16801224 - SPLIT CLAIM IS STILL OPEN AFTER RECEIPT APPLICATION
and it includes <patch 16572826> R12.OZF.B(CANCEL CLAIM IN PENDING APPROVAL
THROUGH UNAPPLYING RECEIPT NOT UPDATING REM AMT)

II. Who should apply this patch?
Customers at R12.1.3 level. Before applying this patch, make sure you have reviewed and executed the following Preinstall steps -
1) Before applying this patch, review MOS Note <Doc ID 1537630.1> (Data Fix For Duplicate Claim Settlement SLA Events related on patch 16321430) to check the existence of duplicate claim settlement SLA events. If duplicate events exist, follow steps in the note to cleanup duplicate data.

2) Run concurrent program "Update Time Structure", else year_id column in ozf_funds_utilized_all_b will not be populated after applying the patch.
Schedule this concurrent program to run at regular intervals whenever GL Periods are opened.

3) For improving performance of Net Accrual Engine, create following custom indexes by executing these scripts if custom indexes doesn't exist on these columns on your instance:

CREATE INDEX ONT.OE_ORDER_LINES_ALL_XX1 ON ONT.OE_ORDER_LINES_ALL
(ACTUAL_SHIPMENT_DATE);
CREATE INDEX ONT.OE_ORDER_LINES_ALL_XX2 ON ONT.OE_ORDER_LINES_ALL
(FULFILLMENT_DATE);
CREATE INDEX ONT.OE_ORDER_LINES_ALL_XX3 ON ONT.OE_ORDER_LINES_ALL
(ACTUAL_ARRIVAL_DATE);

[Note : XX1, XX2 and XX3 can be replaced with any alpha numeric values in the
above commands for creating indexes.]

Refer to Sections IV & V of MOS <> for Post Install Steps and Additional Notes.

III.What are the new features in this release?
Refer to Section III of MOS <Doc ID 1538404.1>.

IV. Critical bugs Fixed in this release:
Bug:16801224 - SPLIT CLAIM IS STILL OPEN AFTER RECEIPT APPLICATION.

 

Feature 6 - Introduced by <Patch 16572826> R12.OZF.B
==================================================

I. What are the contents of this patch?
a) Fix for Bug 16572826 - CANCEL CLAIM IN PENDING APPROVAL THROUGH UNAPPLYING RECEIPT NOT UPDATING REM AMT
b) 16198653:R12.OZF.B 12.1.3+ CONSOLIDATED PATCH - MAR 2013

II. Who should apply this patch?
Customers at R12.1.3 level. Before applying this patch, make sure you have reviewed and executed the following Preinstall steps -
1) Before applying this patch, review MOS Note Doc ID 1537630.1 (Data Fix For
Duplicate Claim Settlement SLA Events related on patch 16321430) to check the
existence of duplicate claim settlement SLA events. If duplicate events
exists, follow steps in the note to cleanup duplicate data.

2) Run concurrent program "Update Time Structure", else year_id column in
ozf_funds_utilized_all_b will not be populated after applying the patch.
Schedule this concurrent program to run at regular intervals whenever GL
periods are opened.

3) For improving performance of Net Accrual Engine, create following custom indexes by executing these scripts if custom indexes doesn't exist on these columns on your instance:
CREATE INDEX ONT.OE_ORDER_LINES_ALL_XX1 ON ONT.OE_ORDER_LINES_ALL
(ACTUAL_SHIPMENT_DATE);
CREATE INDEX ONT.OE_ORDER_LINES_ALL_XX2 ON ONT.OE_ORDER_LINES_ALL
(FULFILLMENT_DATE);
CREATE INDEX ONT.OE_ORDER_LINES_ALL_XX3 ON ONT.OE_ORDER_LINES_ALL
(ACTUAL_ARRIVAL_DATE);
[Note : XX1, XX2 and XX3 can be replaced with any alpha numeric values in the
above commands for creating indexes.]

Refer to Sections IV & V of MOS <Note:1538404.1> for Post Install Steps and Additional Notes.

III.What are the new features in this release?
Refer to Section III of MOS <Note:1538404.1>.

IV. Critical bugs Fixed in this release:
<Bug:16572826> - CANCEL CLAIM IN PENDING APPROVAL THROUGH UNAPPLYING RECEIPT NOT
UPDATING REM AMT.

 

Actions

 

Contacts

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

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


In this Document
Details
Actions
Contacts
References

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