==============================================================================

GENERIC DATA FIX: This is a consolidated generic datafix patch and fixes known d
ata corruption scenarios in P2P flow This patch is recommended for all Oracle Pr
ojects customers using P2P functionality.
==============================================================================
Update
Product
Release
Platform
Built

13833481
Project Costing
R12
Generic Platform
APR-15-2013 22:01:11

Instructions For Applying This Patch

==============================================================================
Preparation Tasks
==============================================================================
The tasks in this section can be completed without taking any Applications
services or users offline.
There are no tasks to be performed in this section.
Pre-install Tasks
==============================================================================
You must shut down all Application tier services before performing the
tasks in this section.
There are no tasks to be performed in this section.
Apply The Patch
==============================================================================

There are no tasks to be performed in this section.

Post-install Tasks
==============================================================================
You must complete the tasks in this section before starting up Application
tier services.
There are no tasks to be performed in this section.
Finishing Tasks
==============================================================================
You may complete the tasks in this section at any time after the update,
without taking any services or users offline.
There are no tasks to be performed in this section.

Additional Information
==============================================================================

There are no tasks to be performed in this section.

==============================================================================
Description
==============================================================================
1. Description
Old Behavior:
--------------1. Duplicate actuals interfaced to Projects for a Purchase Order
once from AP Invoices and also from PO Receipts.
2. pa_addition_flag on the receipt transactions got corrupted
even though receipts are interfaced to Projects.
3. Several receipt transactions are not getting interfaced to Projects.
4. Duplicate actuals interfaced to Projects more than once ,
from PO Receipts.
5. pa_addition_flag on the receipt,invoice transactions having
an intermediate value as 'O' irrespective of whether interfaced
to projects or not.
6. Duplicate variance interfaced to Projects more than once ,
for a PO Receipt.
7. PO receipt or receipt tax interfaced to projects with
incorrect amounts.
8. Receipt transactions having wrong pa_addition_flag
on the records whether the receipt is interfaced
to projects or not.
9. Invoice transactions having wrong pa_addition_flag
on the records whether the invoice or varaince is interfaced
to projects or not.
10. Retainage invoice transactions interfaced to projects.
New Behavior:
-------------1. There was a code bug in the PRC: Interface Supplier Costs process,
which was causing the duplicate actuals to be interfaced to Projects.
The code was fixed via bugs 5693190 and 5735012.
This datafix patch is to fix the data corruption.
2. Datafix is included in this patch to correct the pa_addition_flag
on the receipts interfaced to Projects.
3. Datafix is included in this patch which enables the eligible
receipts to be able to get interfaced to Projects.
4. Datafix is included in this patch to correct the duplicates
causing from PO Receipt alone.
5. Datafix is included in this patch to correct the pa_addition_flag
on the invoice and receipt if it is having an intermediate value
irrespective of whether interfaced to projects or not.
6. Datafix is included in this patch to correct the duplicates
variance causing from PO Receipt alone.
7. Datafix is included in this patch to correct PO receipt or receipt tax
interfaced to projects.
8. Datafix is included in this patch to correct Receipt transactions
with proper pa_addition_flag on them.
9. Datafix is included in this patch to correct Invoice transactions
with proper pa_addition_flag on them.

10. Datafix is included in this patch to correct the Retainage

invoice transactions interfaced to projects.
2. Pre-requisite or Co-requisite which is not included with this patch:
Pre-requisite: 12429587:R12.PJC.B : P2P : CONSOLIDATED CRITICAL CODEFIX
3. Patch Applicable for versions/releases:
12.1.1 and above
4. Dependent Applications:
N/A
5. Patch to be applied:
Server side.
6. Patch applicable only when a particular application installed:
N/A
7. Pre-patch application steps
Make sure to have the auto accounting setup for Supplier Cost Adjustments.
8. Post patch application steps
The following are the various cases which cover the various scenarios
that can cause the data corruption. Customer can choose to execute the
steps in the case which suits their data corruption scenario most.
CASE 1:
------Customer can execute the following steps in case there are
duplicate actuals interfaced to Projects once for an invoice matched to
PO and once for the PO Receipt.
i. Run the reporting script r5963031q.sql.
This script generates the list of receipts which is having
a wrong pa_addition_flag value irrespective of whether the
receipt is interfaced to projects or not.
Output file generated:RT5963031g.lst,RT5963031h.lst,RT5963031i.lst
NOTE: Below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. If reporting script r5963031q.sql (from step i) lists
transactions in RT5963031g.lst,RT5963031h.lst,RT5963031i.lst
, then only go ahead with this step ii (in
sequence)

Run the data fix script s5963031.sql which would stamps the
correct pa_addition_flag value on the receipts.
NOTE: Above script will ask for an input
'Case_num' enter value as '1' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
iii. If the reporting script r5963031q.sql in step i
generates listing of invoice transactions which are
interfaced to Projects even though the receipt transactions for
the corresponding PO Distributions already exist in Projects.
Output file generated: o5963031b.lst
iv.

If reporting script r5963031q.sql (from step iii) lists

transactions in o5963031b.lst, then only go ahead with this
step iv and v (in sequence)
Run data fix script s5963031.sql which would reverse the
duplicates identified by reporting script r5963031q.sql.
NOTE: Above script will ask for an input
'Case_num' enter value as '11' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql

v. Run the "PRC: Distribute Supplier Cost Adjustments" process in

all the OUs which will create the cost distribution lines for the
reversals and make sure that all the EIs are successfully
processed.
vi. Once above data fix s5963031.sql and PRC:Distribute supplier
cost adjustment process are successfully completed, now
run the data fix script s5963031.sql.
This script corrects the flags on CDL and Invoice Distributions
for the reversed transactions in step iv.
NOTE: Above script will ask for an input
'Case_num' enter value as '111' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
vii. Verification Step:

Once data fix is successfully completed(from steps iv ,v &vi),

please run the reporting script r5963031q.sql again and now it
should not list any transactions in RT5963031g.lst,RT5963031h.lst
,RT5963031i.lst and o5963031b.lst.
CASE 2:
------Customer can execute the following scripts in case receipts or returns
which got stuck in purchasing and not interfaced to Projects.
i. Run the script r5963031q.sql
This script generates the receipts or returns which got stuck in
purchasing and not interfaced to Projects.
Output file generated: rec5963031.lst
NOTE: Below script will ask for for an input
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. Run script s5963031.sql only if there is any transactions listed in
step i from rec5963031.lst.
This script enables the receipts/return transactions identified
in step i to be able to interface to Projects.
NOTE: Above script will ask for an input
'Case_num' enter value as '2' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
iii. Verification Step:
Once data fix is successfully completed(from steps ii),
please run the reporting script r5963031q.sql again and now it
should not list any transactions in rec5963031.lst.
CASE 3:
------Customer can execute the following scripts in case the pa_addition_flag on
the receipt,invoice transactions having an intermediate value as 'O'
irrespective of whether interfaced to projects or not

i. Run the script r5963031q.sql

This script generates the invoices which is having an intermediate
pa_addition_flag value irrespective of whether invoice's interfaced
to projects or not.
Output file generated:INV5963031.lst,IN5963031b.lst,VAR5963031b.lst
NOTE: Below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. Run script s5963031.sql only if there is any transactions listed in
output file INV5963031.lst,IN5963031b.lst,VAR5963031b.lst from
step i.
This script populates the correct pa_addition_flag value on the
invoices which are holding an intermediate value as 'O' previously.
NOTE: Above script will ask for an input
'Case_num' enter value as '3' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql

iii. If the reporting script r5963031q.sql in step i

lists the receipts which is having an intermediate
pa_addition_flag value irrespective of whether receipt's interfaced
to projects or not.
Output file generated: RT5963031b.lst,IRT5963031c.lst
iv. Run script s5963031.sql only if there is any transactions listed
in output file RT5963031b.lst,RT5963031c.lst from step iii.
This script populated the correct pa_addition_flag value on the
receipt's which are holding an intermediate value as 'O'
previously.
NOTE: Above script will ask for an input
'Case_num' enter value as '31' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,

sqlplus <user name>/<password>@<database name> @s5963031.sql

v. Verification Step:
Once data fix is successfully completed(from steps ii or iv),
please run the reporting script r5963031q.sql (from steps i or
iii) again and now it should not list any transactions in the
generated output file INV5963031.lst,IN5963031b.lst,VAR5963031b.lst
,RT5963031b.lst and RT5963031c.lst.

CASE 4:
------Customer can execute the following scripts in case the Duplicate actuals
interfaced to Projects more than once from PO Receipts.
i. Run the script r5963031q.sql
This script generates the receipt transaction list which are
interfaced to Projects more than once.
Output file generated: RT5963031a.lst
NOTE: Below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. Run script s5963031.sql only if there is any transactions listed
from output file RT5963031a.lst generated in step i.
This script reverses the duplicate actual transactions identified
in step i .
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
NOTE: Above script will ask for an input
'Case_num' enter value as '4' to the script.
iii.Run the "PRC: Distribute Supplier Cost Adjustments" process in
all the OUs which will create the cost distribution lines for the
reversals and make sure that all the EIs are successfully
processed.
iv. Run script s5963031.sql after completing the step iii.

How to execute the script:

==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
NOTE: Above script will ask for an input
'Case_num' enter value as '41' to the script.
v. Verification Step:
Once data fix is successfully completed(from steps iv),
please run the reporting script r5963031q.sql (from steps i) again
and now it should not list any transactions in the output file
RT5963031a.lst.

CASE 5:
------Customer can execute the following scripts in case the Duplicate
variance interfaced to Projects more than once for a PO Receipt.
i. Run the script r5963031q.sql
This script generates the variance transaction list which are
interfaced to Projects more than once.
Output file generated: VARduplicatesb.lst
NOTE: Below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. Run script s5963031.sql only if there is any transactions listed
from the ouput file VARduplicatesb.lst generated in step i.
This script reverses the duplicate actual transactions identified
in step i .
NOTE: Above script will ask for an input
'Case_num' enter value as '5' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
iii. Run the "PRC: Distribute Supplier Cost Adjustments" process in

all the OUs which will create the cost distribution lines for the
reversals and make sure that all the EI's are successfully
processed.
iv. Run script s5963031.sql after completing the step iii.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
NOTE: Above script will ask for an input
'Case_num' enter value as '51' to the script.
v. Verification Step:
Once data fix is successfully completed(from steps iv),
please run the reporting script r5963031q.sql (from steps i) again
and now it should not list any transactions in the output file
VARduplicatesb.lst.
CASE 6:
------Customer can execute the following steps in case PO receipt,tax
interfaced to projects with incorrect amounts.
i. Run the script r5963031q.sql
This script generates the receipt return transactions list
that got interfaced to projects, with incorrect amounts.
Output file generated: o8533366.lst.
NOTE: The below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql

ii. Run the script a8533366_4.sql only if there is any transactions

listed in step i output file o8533366.lst.
This script creates reversal expenditure items for the
receipts of transaction types,RETURN TO RECEIVING or CORRECT,
that got interfaced to projects, with incorrect amounts.
NOTE: The below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and

specific date range otherwise the script will run

for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @a8533366_4.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @a8533366_4.sql
iii. Run "PRC: Distribute Supplier Cost Adjustments" process
in all Operating Units listed in step i and ensure that all the
expenditure items are cost distributed without any errors.
iv. After running the process in step iii, Run the script
b8533366_4.sql
This script marks the Transfer_status_code on the Cost
Distribution Lines corresponding to the expenditure items in PA,
for the receipts that got interfaced with incorrect amounts, and
also the reversal expenditure items created by script
a8533366.sql to G. It marks the PA_Addition_Flag on the receipts
that got interfaced with incorrect amounts,back to N.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @b8533366_4.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @b8533366_4.sql
v. After completing all the steps till step iv, please run the
PRC: Interface Supplier Costs process in all the Operating Units.
vi. This should fix the PO receipt,tax interfaced to PA, with
incorrect amounts.
vii. Once data fix is successfully completed(from steps ii,iii,iv and
v),please run the reporting script r5963031q.sql again and now it
should not list any transactions in the output file o8533366.lst.
CASE 7:
------Customer can execute the following steps in case the
pa_addition_flag is wrong on receipt transactions.
i. Run the reporting script r5963031q.sql.
This script generates the list of receipts which is having
a wrong pa_addition_flag value irrespective of whether the
receipt is interfaced to projects or not.
Output file generated:RT5963031g.lst,RT5963031h.lst,RT5963031i.lst
NOTE: The below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.

How to execute the script:

==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. If reporting script r5963031q.sql (from step i) lists
transactions in output file RT5963031g.lst,RT5963031h.lst,
RT5963031i.lst, then only go ahead with this step ii (in
sequence)
Run data fix script s5963031.sql which would stamps the
correct pa_addition_flag value on the receipts.
NOTE: Above script will ask for an input
'Case_num' enter value as '7' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
iii. Run the "PRC: Interface supplier cost" process in
all the OUs which will interface the receipt
transactions which got struck earlier.
iv. Once data fix is successfully completed(from steps ii and iii),
please run the reporting script r5963031q.sql again and now it
should not list any transactions in output file RT5963031g.lst,
RT5963031h.lst,RT5963031i.lst.
CASE 8:
------Customer can execute the following steps in case the
pa_addition_flag is wrong on invoice transactions.
i. Run the reporting script r5963031q.sql.
This script generates the list of invoice which is having
a wrong pa_addition_flag value irrespective of whether the
invoice is interfaced to projects or not.
Output file generated:INV13833481.lst,INV13833481b.lst,
INV13833481c.lst and INV13833481d.lst.
NOTE: The below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql

ii. If reporting script r5963031q.sql (from step i) lists

transactions in out put file INV13833481.lst,INV13833481b.lst,
INV13833481c.lst and INV13833481d.lst, then only go ahead
with this step ii (in sequence)
Run data fix script s5963031.sql which would stamps the
correct pa_addition_flag value on the receipts.
NOTE: Above script will ask for an input
'Case_num' enter value as '8' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
iii. Run the "PRC: Interface supplier cost" process in
all the OUs which will interface the invoice
transactions which got struck earlier.
iv. Once data fix is successfully completed(from steps ii and iii),
please run the reporting script r5963031q.sql again and now it
should not list any transactions in out put file INV13833481.lst,
INV13833481b.lst,INV13833481c.lst and INV13833481d.lst.
CASE 9:
------Customer can execute the following steps in case the
Retainage type invoice transactions interface to projects.
i. Run the reporting script r5963031q.sql.
This script generates the list of invoice which is having
a wrong pa_addition_flag value irrespective of whether the
invoice is interfaced to projects or not.
Output file generated:INV13833481e.lst.
NOTE: The below script will ask for
'Start_project_num','End_project_num'
,'EI_Start_date','EI_End_date' enter only one value at a time if
you wish to run the script for specific projects and
specific date range otherwise the script will run
for all the projects across the date.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @r5963031q.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @r5963031q.sql
ii. If reporting script r5963031q.sql (from step i) lists
transactions in output file INV13833481e.lst, then only go ahead
with this step ii (in sequence)
Run data fix script s5963031.sql which would reverse
the invoice transactions interfaced to projects.
NOTE: Above script will ask for an input
'Case_num' enter value as '9' to the script.

How to execute the script:

==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql
iii. Run "PRC: Distribute Supplier Cost Adjustments" process
in all Operating Units listed in step i and ensure that all the
expenditure items are cost distributed without any errors.
iv.

After running the process in step iii, Run the script s5963031.sql
This script marks the Transfer_status_code on the Cost
Distribution Lines corresponding to the expenditure items in PA,
for the invoice transactions of type 'RETAINAGE', and also the
reversal expenditure items created by script s5963031.sql to G.
It marks the PA_Addition_Flag on the invoice's that got
interfaced to projects wrongly,back to G.
NOTE: Above script will ask for an input
'Case_num' enter value as '91' to the script.
How to execute the script:
==========================
At the sqlplus prompt, SQLPLUS> @s5963031.sql
At unix/linux prompt,
sqlplus <user name>/<password>@<database name> @s5963031.sql

iv. Once data fix is successfully completed(from steps ii,iii and iv),
please run the reporting script r5963031q.sql again and now it
should not list any transactions in output file INV13833481e.lst.
After completing all the steps , please run the
PRC: Interface Supplier Costs process with the Interface Supplier
invoices as 'Yes' and Interface Receipt Accruals as 'Yes' in all ORG's.
This should fix the duplicate actual's in AP/PO and receipts not getting
interfaced to Projects and are stuck in Purchasing.
9. Successful patch installation checks:
All script files should be copied to the source area.