My Oracle Support Banner

List Of Code Fixes - Uninvoiced Receipts Report (URR) & Receipt Accrual Period End Process (Doc ID 1145884.1)

Last updated on MARCH 03, 2022

Applies to:

Oracle Purchasing - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.
*** *** Reviewed by JAdjei



Details

This document is a 'Primary Code Fix Note' which consolidates all the code fixes done in the problem category "Errors And Discrepancies With Uninvoiced Receipts Report (URR) & Receipt Accrual Period End Process" from year 2007.

For similar such notes refer to the Primary Note matrix,
<Note 1138043.1> Primary Note For Oracle EBS Procurement Suite - Encumbrance And Receipt Accounting

Code fix note lists the following details for the fix in a tabular format.

This document will be updated with all these details whenever a new code fix is done in the problem category.

Actions

Whenever you get an issue related to the problem category 'Uninvoiced Receipts Report (URR) & Receipt Accrual Period End Process',

1) Match your issue with the symptoms listed in the table below. The patch mentioned in the column, ' Patch number', for the record will fix the symptom mentioned.
Apply the patch in a test instance first and verify if this resolves your issue.

2) The note also contains the latest code fixes/ file versions available for the problem area discussed.
If you are unable to match your problem with the symptoms listed on the table below, verify your file versions with the versions available on the table given in the end for the respective application release. Apply the latest fix patch(es) mentioned on the table in a test instance and check if this resolves your issue.
It is always recommended that customer upgrade to lastest versions of code when ever possible to avoid running into issues already fixed.

3) If the issue is specific to Create Accounting Program after the Receipt Accrual Period end program completes successfully, and if no match is found on this note, recommend to also refer to 1179643.1 for any potential symptom match.

4) If the above actions do not resolve your issue, please log a Service Request with Oracle Support for assistance

5) Also please note, that the below error on the Receipt Accrual Period end program is a generic error and does not give much information. For these error cases, please gather FND debug log messages ( refer : )
and search for the string  'p_msg_name'  in the FND log.

The following REVERSAL events could not be processed. The event/process
status is U/U:
Note: this warning may be ignored for any events whose ledger is a cash-basis ledger

The note lists code fixes related to Uninvoiced Receipt report and Receipt Accrual Period End program in SEPARATE TABLES. The two tables at the end provide latest file version details for 
 

TABLE 1 : Code Fixes related to Uninvoiced Receipt Report

TABLE 2 : Code Fixes related to Receipt Accrual Period end program

TABLE 3
: Latest file version details  related to Uninvoiced Receipt Report

TABLE 4 : Latest file version details related to Receipt Accrual Period end program


TABLE 1 : Code Fixes related to Uninvoiced Receipt Report

Reported Release Version Symptoms Bug number Bug Abstract Root Cause Patch number Fixed file version / File version upgraded by the patch suggested Behavior after patch application
12.1.3 Incorrect translation in French of Uninvoiced Receipt Report.

Following fields are not translated
Value Yes and vendor in the parameters
<Bug 12326931> INCORRECT TRANSLATION OF UNINVOICED RECEIPT REPORT In CSTVURRB.pls, parameter p_qty_precision is never used. Some of the parameters are hard coded in English. <Patch.13067210:R12.BOM.C> CSTACREP.rtf 120.7.12010000.6
CSTVURRB.pls 120.7.12010000.11
All URR fields are translated correctly when run in a language different from English, e.g., French.
Quantity precisions are applied correctly.
12.1.2 Uninvoiced receipts report shows incorrect accrual for PO receipts due to incorrect calculation of received quantity. This issue occurs when a PO shipment has multiple distributions and the received qty is same as ordered qty at PO shipment level where as the delivered qty is not same as the ordered qty at the distribution level. e.g: PO shipment has ordered qty 10 which has 2 distributions with 1st distribution having ordered qty 6 and 2nd distribution with qty 4. Receive transaction is done for 10 but qty delivered against 1st distribution is 8 and qty delivered against 2nd distribution is 2. <Bug.9637241> RECEIPT ACCRUALS - PERIOD-END GENERATES INCORRECT ACCRUAL AMOUNTS

Code limitation in file CSTVPEAB.pls due to which qty received got calculated incorrectly leading to incorrect accrual amount. This incorrect received qty and incorrect accrual amount is shown in URR <Patch.9637241:R12.BOM.C> CSTVPEAB.pls -120.11.12010000.6

URR will show the received qty correctly and will show the correct accrual amount
12.1.3 Uninvoiced Receipts Report completes with warning and would not produce output. This happens whenever the first PO to be displayed in the report was an overinvoiced PO(i.e. invoiced qty is greater than received qty)

Error seen in the OPP log(refer Doc ID 364547.1 to gather OPP log) :
 [UNEXPECTED] [21060:RT786221]
java.lang.reflect.InvocationTargetException

<Bug.10240235> CSTACREP-UNINVOICED RECEIPTS REPORT COMPLETES WITH WARNING-POST PROCESSING ERROR Code limitation in file CSTACREP.rtf <Patch.10240235:R12.BOM.C> CSTACREP.rtf -120.7.12010000.5 Uninvoiced Receipts Report completes successfully for all cases

12.1.3/12.1 Uninvoiced Receipts Report output always shows quantities in Dynamic Precision of 2 irrespective of the value entered in report parameter, Dynamic Precision. <BUG.9004549> DYNAMIC PRECISION NOT WORKING IN UNINVOICED RECEIPTS REPORT Code limitation in files CSTVURRB.pls to CSTACREP.rtf <Patch.9004549:R12.BOM.C> CSTVURRB.pls 120.7.12010000.6
CSTACREP.rtf 120.7.12010000.4
Uninvoiced Receipts Report correctly displays the decimals based on the dynamic precision
12.0.6 URR shows incorrect received qty and hence incorrect accrual amount when Receiving is done using Add to Receipt functionality. This issue primarily occurs for upgraded PO receipts <Bug.8970560> FP:12.0-12.2:WRONG ACCRUAL CALCULATION WHEN ADD TO RECEIPT

For Po receipts done using Add to Receipt functionality, same shipment header id has more than one transaction and hence received qty calculation was considering the qty for same shipment header id twice instead of summing the qty for two transactions with the same shipment header id

<Patch.8768833:R12.BOM.A>

CSTVPEAB.pls - 120.10.12000000.5


URR will calculate the received qty correctly and will show correct accrual amount even for receipts done using Add to Receipt functionality

12.0.6 & 12.1 Uninvoiced Receipts Report displays 'NaN' in the report total field <Bug.7566432> CSTACREP UNINVOICED RECEIPTS REPORT TOTAL FIELD VALUE DISPLAYS NAN Code limitation in file CSTVURRB.pls <Patch.8324216:R12.BOM.A> for R12 & <Patch.8987125:R12.BOM.C> for 12.1 CSTVURRB.pls - 120.7.12000000.8 for R12 & CSTVURRB.pls - 120.7.12010000.3 for 12.1

Uninvoiced Receipts Report displays proper value in the report
total field
11.5.10.2 PO Release Number is not completely displayed in Unvoiced Receipts Report <Bug.9060217> UNINVOICED RECEIPTS REPORT PROBLEM WITH BPA_RELEASE NUMBER The Boilerplate size for the Release Number field in report editor has a constraint <Patch.9060217> POXPORRA.rdf - 115.35.11510.22* The PO Release Number is completely displayed in
the report
11.5.10.2 When running the Uninvoiced Receipts Report for temporary labor PO's (OTL), invoiced PO's are showing up on the report (run for category Subcontract labor) <Bug.8264156> INVOICED TEMP LABOR PO'S ARE SHOWING ON UNINVOICED RECEIPTS REPORT Report POXPORRA.rdf doesn't handle service POs correctly <Patch.8264156> POXPORRA.rdf -115.35.11510.21 Fully invoiced service or temp labor POs don't
appear in the Uninvoiced Receipt report
11.5.10.2 While submitting the 'Uninvoiced Receipts Report' for say Mar-10, the POs which had uninvoiced receipts in Mar-10 but were invoiced and closed in Apr-10 are no longer in the Mar-10 report

<Bug.6990834>

CLOSED POS VS 'UNINVOICED RECEIPTS REPORT'

Code limitation in file POXPORRA.rdf

<Patch.6990834>

POXPORRA.rdf -115.35.11510.20

In oracle purchasing, PO's appear in the Uninvoiced Receipt report for a period prior to the period in which the PO was invoiced and closed

11.5.10.2 For service line type Pos/Pos created with temp labor line types with match option Receipt, URR shows incorrect accrual amount and receipt Accrual-Period end program generates incorrect accrual amount

<Bug.6599022>

WRONG ACCRUAL AMOUNT GENRATED BY RVCACR AN INTO URR FOR TEMP LABOR LINE TYPES

UOM conversion was done for Service line type Pos

<Patch.6599022>

POXPORRA.rdf - 115.35.11510.19
rvcac.opc - 115.44.11510.13

URR will show the correct accrual amount for service line type Pos

11.5.10.2 Grand total of URR does not match with the accrual amount of all the transactions shown in the report

<Bug.5999097>

UNINVOICED RECEIPTS REPORT GRAND TOTAL DOES NOT MATCH REPORT

The logic used to calculate the C_GRAND_TOTAL was not correct

<Patch.5999097>

POXPORRA.rdf - 115.35.11510.18

Grand total of URR will match with the summation of accrual amount of all transactions shown in the report

11.5.10 URR does not show accruals for releases if the corresponding blanket PO is closed

<Bug.4435380>

UNINVOICED RECEIPT REPORT DOES NOT ACCRUE RELEASES IF BLANKET IS CLOSED

The Uninvoiced Recipt Report refers closed_date on the po_headers_all table when the closed_date on the po_line_locations_all (shipment) is NULL. This logic is incorrect for blankets as the blanket could be closed but the release may still be open and can be received

<Patch.4435380>

POXPORRA.rdf - 115.35.11510.9

URR will show the accruals for releases even if the blanket PO is closed

11.5.10 Uninvoiced Receipts report shows old closed purchase orders after upgrade to 11.5.10 <Bug.4921348> CST: UNINVOICED RECEIPTS REPORT PRINTS CLOSED UNINVOICED SHIPMENTS Code limitation in file POXPORRA.rdf <Patch.4921348 > POXPORRA.rdf - 115.35.11510.12 This patch introduces the parameter 'Include Closed POs' which can be added to choose whether to include or exclude closed
POs and accordingly the report will/will not show the closed POs

 

TABLE 2 : Code Fixes related to Receipt Accrual Period end program

Reported Release Version Symptoms Bug number Bug Abstract Root Cause Patch number Fixed file version / File version upgraded by the patch suggested Behavior after patch application
12.1.2 Receipt Accrual Period end program generates incorrect accrual for PO receipts due to incorrect calculation of received quantity. This issue occurs when a PO shipment has multiple distributions and the received qty is same as ordered qty at PO shipment level where as the delivered qty is not same as the ordered qty at the distribution level. e.g: PO shipment has ordered qty 10 which has 2 distributions with 1st distribution having ordered qty 6 and 2nd distribution with qty 4. Receive transaction is done for 10 but qty delivered against 1st distribution is 8 and qty delivered against 2nd distribution is 2. <Bug.9637241> RECEIPT ACCRUALS - PERIOD-END GENERATES INCORRECT ACCRUAL AMOUNTS

Code limitation in file CSTVPEAB.pls due to which qty received got calculated incorrectly leading to incorrect accrual amount <Patch.9637241:R12.BOM.C> CSTVPEAB.pls - 120.11.12010000.6

Receipt Accrual Period end program will generate accrual for the correct amount considering the correct received qty
12.0.6 Create Accounting - Receiving ends with error for Period end accruals. Error - "95937: There are either non-accountable events existing in the system of
event which could not be processed because no data could be found on transaction objects"
<Bug.9475572> CREATE ACCOUNTING RECEIVING DOES NOT GENERATE PERIOD END JOURNAL FOR OU 127

The view cst_xla_rcv_ref_v is set as mandatory but it fails to return the data due to correlation with encumbrance amount <Patch.9475572:R12.BOM.A>  cstcxla.odf - 120.56.12000000.31 Create Accounting-Receiving program should create the accounting entries in SLA without this error
12.1.2 Receipt accrual period end error out
Error:ORA-01403: no data found in Package CST_PerEndAccruals_PVT Procedure Calculate_AccrualAmount

<Bug.8682612>

FP:12.1-12.2:TST1212: RECEIPT ACCRUAL PERIOD END ERROR OUT WITH ORA-01403

"Code was missing the order by line location id clause and it loops
CST_PerEndAccruals_PVT.Calculate_AccrualAmount for every line location id,hence there is possibility that records are fetched
in random order and cause process to fail"

<Patch.9637241:R12.BOM.C>

CSTVPEAB.pls -120.11.12010000.6

Receipt Accruals-Period end program will get completed successfully without this error

12.1.2 When attempting to run the 'Receipt Accruals - Period-End' program,the following error occurs. This error occurs only in fresh R12.1 instance or instance that is upgraded to 12.1 from R12

ERROR
-------
ORA-01403: no data found in Package CST_ReceiptAccrualPerEnd_PVT Procedure Seed_RcvAccounting Events.


<Bug.8786163>
RECEIPT ACCRUALS - PERIOD-END PROGRAM ENDING IN ERROR

The receiving accounting event type - Period End Accrual was missing from the rcv_accounting_event_types table

<Patch.8786163:R12.PO.B>  

rcvcraet.ldt - 120.0.12010000.3

Receipt Accruals - Period-End program will get completed successfully without this error

12.1 Receipt accrual period end program has performance issue which runs for more than 2 hrs and then error out

Error: An internal error has occurred in the program
XLA_00707_AAD_S_000016_PKG.EventClass_280. ORA-01652: unable to extend temp
segment by 2560

<Bug.9134500>

RECEIPT ACCRUALS - PERIOD-END PROGRAM END WITH ERROR

There is no index on rcv_receiving_sub_ledger.accounting_event_id

<Patch.9134500:R12.PO.B>

rvsl.odf - 120.4.12010000.2

Receipt Accruals - Period-End program will get completed successfully without this error/without this performance issue

12.0.6 & 12.1 Performance issue with Receipt Accrual-Period end program

<Bug.8940057>

1OFF:8491134:12.1.1:12.1.1:PERIOD END ACCRUAL PROCESS PERFORMANCE ISSUE

View CST_XLA_RCV_REF_V definition has a problem related to the condition with respect to rcv_accounting_events.event_type_id

<Patch.8491134:R12.BOM.A> for R12 & <Patch.8623413:R12.BOM.C> for 12.1

cstcxla.odf - 120.56.12000000.18 for R12 &
cstcxla.odf 120.67.12010000.7 for 12.1

Receipt Accruals - Period-End program will get completed successfully without any performance issue

12.0.6.12.1 & 12.1.2

Receipt Accruals - Period-End program ignores all shipments that have a closing date less than the end date of the period passed in parameter and also creates incorrect accrual amount if overreceipt is done for PO shipments and primarily in case of multiple distributions. Uninvoiced Receipts Report (URR) also shows incorrect accrual amount in this case / URR shows incorrect received qty for POs which
have match option as 'R'(receipt) and different qty received from qty delievered / URR shows received qty with more decimals when the received qty has a round value shown for Receiving transactions


<Bug.9637241>

RECEIPT ACCRUALS - PERIOD-END GENERATES INCORRECT ACCRUAL AMOUNTS

QUANTITY RECEIVED Calculation in period-end program IS INCORRECT due to code limitation

<Patch.8898491:R12.BOM.A> for R12 & <Patch.9637241:R12.BOM.C> for 12.1 and 12.1.2 

CSTVPEAB.pls - 120.10.12000000.6 &
CSTVPEAB.pls - 120.11.12010000.6 for 12.1 and 12.1.2

Receipt Accruals - Period-End program will generate accruals for correct amount

12.0.6 & 12.1 & 12.1.2

On submitting the Receipt Accruals-Period end program, multiple create accounting programs get spawned and there is a huge performance issue

<Bug.7191665>

PERIOD END ACCURAL PROCESS KICKS OFF MULTUPLE CREATE ACCOUNTING

Due to code limitation, Api xla_accounting_pub_pkg.accounting_program_events
is called with p_gl_posting_flag as 'N' due to which SLA calls create accounting program multiple times.

<Patch.9456733:R12.BOM.A> for R12 &
<Patch.9600743:R12.BOM.C> for 12.1 and 12.1.2

CSTVRAPB.pls - 120.12.12000000.6 for R12 & CSTVRAPB.pls 120.12.12010000.6
for 12.1

Receipt Accruals Period end program will not spawn the Create Accounting program at all. Create Accounting process needs to be done explicitely after running the period end program

12.0.6 & 12.1

Receipt Accruals-Period end program errors out with the message 'XLA_AP_NO_ENCUM_TYPE' in fnd log
"An encumbrance type is required for encumbrance journal entries. Please provide an encumbrance type for the subledger journal entry"
<Bug.9790838>

RECEIPT ACCRUALS --- PERIOD END ENDS IN ERROR

Code limitation in file psavbcxb.pls

<Patch.9100984:R12.PSA.A> for R12 & <Patch.9100984:R12.PSA.B> for 12.1

psavbcxb.pls - 120.31.12000000.22for R12 & psavbcxb.pls - 120.34.12010000.19 for 12.1

Receipt Accrual Period end program will generate the accruals without this error

12.0.6 & 12.1

Receipt Accruals-Period end program errors out in encumbrance enabled environment - XLA data is not getting created but Receiving subledger has the accounting entries.

FND log error: 'XLA_AP_NO_ENCUM_TYPE'

"An encumbrance type is required for encumbrance journal entries. Please provide an encumbrance type for the subledger journal entry"
<Bug.9325101>

CREATE ACCOUNTING PERIOD END ACCRUAL: MISSING ENC TYPE ID

While creating the accrual reversal entry (reverse of the original distribution), the copylineinfo(overloaded) procedure does not contain the necessary code to copy the encum_type_id in the case of non-upgraded entries or non-bflow entries

<Patch.9325101:R12.XLA.A> for R12 & <Patch.9325101:R12.XLA.B> for 12.1

xlajelns.pkb -120.175.12000000.64 for R12 &
xlajelns.pkb -120.197.12010000.20 for 12.1


Receipt Accrual Period end program will generate the accruals and encumbrance reversal without this error

12.0.6 & 12.1

Receipt Accruals-Period end program errors out with BFLOW event for 11i Pos when the program is submitted in R12 instance.

ERROR in FND log:
XLA_AP_INVALID_CCID and XLA_AP_BFLOW_PE_NOT_FOUND


<Bug.8935054>

RECEIPT ACCRUALS - PERIOD END PROCESS ENDS IN ERROR

MPA_ has been added to the reversal_code, even though 11i upgraded data and it is looking for bflow entry

<Patch.8935054:R12.XLA.A> for R12 & <Patch.8935054:R12.XLA.B> for 12.1

xlacpalt.pkb -120.64.12000000.6 for R12 &
xlacpalt.pkb -120.66.12010000.4 for 12.1


Receipt Accrual Period end program will generate the accruals without this error

12.0.6 & 12.1

Receipt Accruals-Period end program errors out in encumbrance enabled environment:
Is a fresh R12 installation not an upgraded.

Error on FND log : p_msg_name = XLA_AP_BFLOW_PE_NOT_FOUND
<Bug.9176206> ENCUMBRANCE REVERSALS NOT BEING CREATED FOR PERIOD END ACCRUALS

ENC_UPG_OPTION = Y is not correct for fresh R12 install. But fnd log shows the statement "ENC_UPG_OPTION = Y"

<Patch.9037877:R12.PSA.A>
for R12 & <Patch.9037877:R12.PSA.B> for 12.1

psavbcxb.pls - 120.31.12000000.16 for R12 & psavbcxb.pls - 120.34.12010000.13


Receipt Accrual Period end program will generate the accruals and encumbrance reversal without this error

12.0.6

Receipt Accruals-Period end program errors out with BFLOW event for 11i Pos when the program is submitted in R12 instance / Period End Accrual doesn't create encumbrance reversal if the PO is currently Closed but was not closed at the last day of the period


<Bug.7029188>

RECEIPT PERIOD END ACCURAL PROCESS ERRORED OUT DUE TO BFLOW EVENT FOR 11I'S POS

Receiving Accounting Event entity and Period End AccrualEvent class was using view psa_cst_xla_upg_v to find out the upgrade option , which got join with cst_xla_inv_reg_v view on Transaction ID. But Costing is not populating transaction id in rcv_transaction table while in process of period end accrual. Hence join was failing and SLA Source 'ENC_UPG_OPTION' was getting set to 'N' always. This 'N' causes SLA to look for prior entry thru business flow rather than upgrade flow and hence finally erroring out with bflow not found error

<Patch.7029188:R12.PSA.B> & <Patch.7033488:R12.BOM.A>

psampst.odf  120.50.12000000.5 & cstxlaaad.ldt - 120.22.12000000.18 & cstxlaemseed.ldt - 120.0.12000000.5

Receipt Accrual Period end program will generate the accruals for both 11i and R12 Pos without this error

12.0.6 & 12.1

Subledger Multiperiod accounting and accrual reversal program - performance issue

<Bug.8234582>

SLOW SUBLEDGER MULTIPERIOD ACCOUNTING AND ACCRUAL REVERSAL REPORT

In CURSOR cur_event_class the select clause is joining with xla_ae_headers for all DISTINCT event type codes, reporting view name of an application

<Patch.8234582:R12.XLA.A> for R12 & <Patch.8234582:R12.XLA.B> for 12.1 (Controlled release)

xlarpmpa.pkb - 120.5.12000000.3
xlarpmpb.pkb - 120.8.12000000.5  for R12 & xlarpmpa.pkb - 120.5.12010000.3
xlarpmpb.pkb - 120.8.12010000.5 for 12.1

"The 'Subledger Multiperiod Accounting and Accrual Reversal
Report' takes less time to complete
"

12.0.4

Receipt Accruals-Period end program runs for 2 hrs

<Bug.7296737>

RECEIPT ACCRUALS - PERIOD END (CSTVRAPS) RUNS ABOUT 2 HOURS

Receipt accrual period end performance issue has a single SQL to access to period end PO in all the cases. The SQL is accessing some useless tables

<Patch.7296737:R12.BOM.A>

CSTVPEAB.pls - 120.10.12000000.3

Receipt Accruals Period end program will run without any performance issue

11.5.10 Receipt Accruals - Period-End does not consider the minimum accrual amount when collecting the data. It always considers the minimum accrual amount plus one. <Bug.10121178> PO ACCRUAL PERIOD END PROGRAM NOT CONSIDERING MINIMUM ACCRUAL AMOUNT Wrong Comparision condition between accrual amount and minimum accrual amount
accrual amount was considered only when accrual amount > minimum accrual amount (report parameter value), it should have been '>='
accrual amount >= minimum accrual amount
<Patch 10121178> rvcac.opc 115.44.11510.20 accrual amount accrued will be correct.
11.5.10 Performance issue with Receipt Accrual-Period end program

<Bug.5566438>

FP11I9-11I10 :CST:RECEIPT ACCRUALS - PERIOD-END PERFORMANCE IS SLOW

Shipment cursor goes for full table scan on PO_HEADERS_ALL and then accesses PO_LINE_LOCATIONS_ALL while the better path
would be to access PO_LINE_LOCATIONS_ALL first

<Patch 17390844>

rvcac.opc - 115.44.11510.27

Receipt Accruals Period end program will run without any performance issue

 

TABLE 3 : Latest file version details related to Uninvoiced Receipt Report

Release version Latest file Version Patch
11.5.10
POXPORRA.rdf - 115.35.11510.22
<Patch.9060217>
12.0.6 CSTVPEAB.pls - 120.10.12000000.6
CSTVURRB.pls - 120.7.12000000.8
CSTACREP.rtf - 120.7.12000000.4
<Patch.8898491:R12.BOM.A>
<Patch.8324216:R12.BOM.A>
12.1.1 CSTVPEAB.pls - 120.11.12010000.6
CSTVURRB.pls 120.7.12010000.6
CSTACREP.rtf 120.7.12010000.4
<Patch.9637241:R12.BOM.C>
<Patch.9004549:R12.BOM.C>
12.1.2 CSTVPEAB.pls - 120.11.12010000.6
CSTVURRB.pls 120.7.12010000.6
CSTACREP.rtf 120.7.12010000.4
<Patch.9637241:R12.BOM.C>
<Patch.9004549:R12.BOM.C>
12.1.3 CSTACREP.rtf 120.7.12010000.6 ( URR XML template )
CSTVURRB.pls 120.7.12010000.13
<Patch.22460439:R12.BOM.C>

 

TABLE 4 : Latest file version details related to Receipt Accrual Period end program

Release version Latest file Version Patch
11.5.10
rvcac.opc - 115.44.11510.27
<Patch 17390844>
12.0.6

CSTVPEAB.pls - 120.10.12000000.6

CSTVRAPB.pls - 120.12.12000000.6
cstcxla.odf 120.56.12000000.31
rvsl.odf 120.1.12000000.7

psavbcxb.pls - 120.31.12000000.22

cstxlaaad.ldt - 120.22.12000000.18 & cstxlaemseed.ldt - 120.0.12000000.5 

xlajelns.pkb -120.175.12000000.64

<Patch.8898491:R12.BOM.A>

<Patch.9777235:R12.BOM.A>

<Patch.8491134:R12.BOM.A>

<Patch.9100984:R12.PSA.A>

<Patch.7033488:R12.BOM.A>

 

<Patch.9325101:R12.XLA.A>

12.1.1

CSTVPEAB.pls - 120.11.12010000.6

CSTVRAPB.pls 120.12.12010000.6

cstcxla.odf - 120.67.12010000.23
rvsl.odf 120.4.12010000.3

rcvcraet.ldt - 120.0.12010000.3

psavbcxb.pls - 120.34.12010000.19 

psampst.odf 120.52.12010000.3
psa7029064run0.sql 120.1.12010000.1
psa7029064run1.sql 120.1.12010000.1
psa7029064run2.sql 120.1.12010000.1  

xlajelns.pkb -120.197.12010000.20

<Patch.9637241:R12.BOM.C>

<Patch.9600743:R12.BOM.C>

<Patch.10244514:R12.BOM.C>

<Patch.8786163:R12.PO.B>

<Patch.9134500:R12.PO.B>

 

<Patch.8623413:R12.BOM.C>

<Patch.9100984:R12.PSA.B>

<Patch.7029188:R12.PSA.B>

<Patch.9325101:R12.XLA.B>

12.1.2 CSTVPEAB.pls - 120.11.12010000.6

CSTVRAPB.pls 120.12.12010000.6

cstcxla.odf - 120.67.12010000.23
rvsl.odf 120.4.12010000.3
<Patch.9637241:R12.BOM.C>

<Patch.9600743:R12.BOM.C>

<Patch.10244514:R12.BOM.C>
12.1.3

CSTVPEAB.pls - 120.11.12010000.12
cstcxla.odf - cstcxla.odf - 120.67.12010000.39
rvsl.odf - 120.4.12010000.3

<Patch.14029278:R12.BOM.C>
<Patch.16311768:R12.BOM.C>
<Patch.16230254:R12.BOM.C>

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
 
TABLE 1 : Code Fixes related to Uninvoiced Receipt Report
 TABLE 2 : Code Fixes related to Receipt Accrual Period end program
 TABLE 3 : Latest file version details related to Uninvoiced Receipt Report
 TABLE 4 : Latest file version details related to Receipt Accrual Period end program
Contacts
 Still Have Questions?
References

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