What's happening in your Oracle eBusiness Suite World?

Tuesday Nov 26, 2013

The purpose of this blog is to raise awareness of GDF patch availability for R12.2.x customers and customers preparing to upgrade to R12.2.x.

Development have been actively working on generating the Generic Data Fix (GDF) patches for R12.2 customers and when they are made available they will be delivered with a .C suffix:

i.e.

R12.0.x Customers would apply Patch 17714320:R12.AP.A

R12.1.x Customers would apply Patch 17714320:R12.AP.B

R12.2.x Customers would apply Patch 17714320:R12.AP.C

At present, around 60 GDF patches are available for R12.2.x, so if the Master GDF script (Doc ID 1360390.1) detects corruption and recommends a GDF patch that is not yet released for R12.2.x, then please understand that work is currently in progress to get the remaining Payables GDF patches released for R12.2.x as soon as possible. Until that time, customers on R12.2 can use the following workaround:

IMPORTANT: THESE INSTRUCTIONS ARE FOR EBS PAYABLES (AP) ONLY. IT DOES NOT APPLY TO EBTAX (ZX), PAYMENTS (IBY) OR ANY OTHER PRODUCT. FOR THOSE PRODUCTS, IF THE GDF IS NOT AVAILABLE PLEASE OPEN A NEW SR REQUESTING DEVELOPMENT TO CREATE THE REQUIRED GDF.

Review the output of the report to determine ig a GDF patch is required.

Determine in My Oracle Support if the GDF patch is already released for R12.2 (Check for .C version). If so, then that is the recommended patch to be applied and no further research is needed. Proceed to apply the .C version of the GDF patch.

However, if the required 'GDF'.C patch is NOT available then do both of the following steps:

a) Review My Oracle Support Doc ID 1597490.1 - R12.2.x Payables Generic Data Fixes - which advises customers to install GDF infrastructure patch 17637775:R12.AP.C. This only needs to be done once per installation even if multiple GDF patches are required.

b) Download the R12.1 version of the recommended GDF patch (i.e. Patch 17445464:R12.AP.B) and run the scripts from the patch as indicated in the README manually. Do not try to apply the patch as the system will prevent this due to incompatible release.

For Payables in particular, these are strongly advised to prevent known data integrity issues from resurfacing. The Generic Data Fix (GDF) patches that are available to fix issues detected by the Master GDF (Doc ID 1360390.1)will only fix existing data but the root causes for these data integrity issues cannot be eliminated until the code is upgraded by applying the specific Root Cause Analysis (RCA) patch or the latest RPC.

Wednesday Nov 21, 2012

The Payables MGD is a vital diagnostic that all R12/12.1 customers need to run regularly to
check the data integrity of their Payables system. This script does not make any changes to your
system, so it’s risk free and it produces a HTML formatted output showing which
data corruption issues have been detected and provides the Doc ID’s that will
be needed to fix them.

This MGD diagnostic (version 120.92 and
above) is even better than it used to be as it now checks for 11 new EBTax corruption
signatures that Support was seeing on a consistent basis. These lengthy Service Requests could have
been avoided with one run of the MGD which tells you right away if you have
data corruption. It’s the first thing our Payables support engineers will have you run
when you log an SR so why not be one step ahead?

The new EBTax signatures
that were included in this latest update to the MGD are pulled from the
following common solutions documents:

Wednesday Oct 03, 2012

Here's the first of what will be a series of Generic Data
Fixes (GDF) to be released by Receivables Development.

Generic Data Fix (GDF) are created by development to fix data
issues caused by bugs/issues in the application code. Other Generic
Data Fix benefits/features include:

Developed for bugs that can cause data issues.

Provides a SELECT script that uses an
identification/signature query to identify and report all data affected by
issue/condition caused by a bug.

Allow customers to view and modify what will be fixed.

Provides a separate FIX script to fix the data reported
by the SELECT script.

The FIX script creates backup tables for the data
that is fixed/updated.

Available on My Oracle Support for download

In Release 12, when creating a
refund by either of the following methods:

Applied a receipt to the Refund activity - which
creates an Invoice in Payables

Or you went directly into Payables to create a refund
for an open Credit Memo in Receivables

The Invoice in Payables that is
associated to the refund is cancelled, the corresponding refund application or
credit memo in Receivables is not properly re-instated. For the receipt
application, it still remains applied to the Refund whereas this should be automatically
unapplied. For the credit memo, it stays closed instead of getting re-opened.

Doc ID 761993.1 includes the
patch to make sure this doesn’t happen in the future as well as a GDF script to
fix the current data (Script name: ar_std_refund_unapp.sql). Download the script and run in

About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.