In this Document
  Purpose
  Last Review Date
  Instructions for the Reader
  Troubleshooting Details
     INTRODUCTION
     TESTCASE INFORMATION
     DOCUMENTATION
     SETUP
     PROCESSING OVERVIEW
     LOGGING
     TRACING
     RELATED PROCESSING
     CODE FILES
     KNOWN ISSUES AND RELEVANT NOTES
  References

Applies to:

Purpose

Last Review Date

Instructions for the Reader

Troubleshooting Details

INTRODUCTION

Oracle Purchasing allows buyers to make price changes on global blanket agreements and on blanket agreements. Retroactive Price Update on Purchasing Documents automatically updates the latest price on purchase orders and blanket releases referencing the modified agreements.
Prior to 11.5.10, the price can be updated only for the PO's / Releases which have not been received /invoiced.
From 11.5.10, Oracle Purchasing can optionally update prices on orders to reflect the latest agreement price, even if there has been receiving and invoicing activities against them.

TESTCASE INFORMATION

It is very important to understand the problem in detail which will be helpful to diagnose the issue and find the cause & solution. The following questions would help in understanding the issue better & diagnose the issue in the correct direction.

• Does this problem occur every time or Is this intermittent issue ?
• Is this issue reproducible at will with other agreements also or Is this issue specific to particular Agreement ?
• Does this issue occur for both increase & decrease in the agreement price ?
• Has this worked before? if so what has changed ?
• Is the issue with Customization or issue exists with core code also ?
• Please check the setup information ( Refer the Note 561161.1 )
• Detailed information on the problem encountered.
• Retroactive pricing can be updated in two ways. 
  • While approving the BPA, by selecting the option 'Apply Price Update to Existing POs and Releases'
  • By running the ???Retroactive Price Update on Purchasing Documents??? concurrent program.

      Does the issue occur in the both the methods of updating the Retroactive Pricing?

DOCUMENTATION

User Guide: Oracle Purchasing User???s Guide, Chapter: Reports and Processes > Retroactive Price Update on Purchasing Documents, Page: 9-162 to 9-164

The following note also covers the functionality.

Note 561161.1 Retroactive Pricing

SETUP

Following setup is required to enable the retroactive pricing. 

• Set the profile "PO: Allow Retroactive Pricing of POs".
• Set the Archive mode for Standard POs and Releases to 'Approve' in the Document Types Form.
• Enter Retroactive Price Adjustment Account in the Receiving Options Form.
• Retroactive Pricing is not supported for the Agreements that are cumulatively priced.
• Retroactive Pricing is not supported in encumbered environments.

PROCESSING OVERVIEW

The Retroactive Pricing updates the prices of purchase orders or releases based on the profile PO: Allow Retroactive Pricing of POs. 

• The Agreement Lines that have been retroactively changed are selected.
   
• Only the price updates from blanket agreement lines that are currently in the Approved / Closed statuses are considered for Retroactive pricing.
   
• All the releases against these Blanket Agreement Lines / Standard POs against these Global Agreement Lines are selected for the new Price update. If the Prices are different, then new price is updated in the releases / Standard POs against Blanket Agreements / Global Agreements.
   
• Retroactive pricing does not consider the blanket releases or purchase orders in the following status: 
  In Process
  Pre-Approved
  Reserved
  Frozen
  Finally Closed
  Cancelled
   
• If the Releases / Standard POs were in Approved state already, then the new revision number is updated, authorization status is set to 'Requires Reapproval'& Workflow is initiated to approve the Releases / Standard POs.
   
• PO Change Order Workflow can be configured to allow automatic re???approval of the updated releases and purchase orders.
   
• PO Change Order Workflow attribute 'Change Order Header Auto Approve Retroactively Priced Releases' should be set as 'Y' for automatic re-approval.
   
• If the profile 'PO: Allow Retroactive Pricing of POs' is set to 'All Releases' and
  Blanket Releases / Standard POs that are already received are retroactively updated then corresponding accounting entries will be created.
   
  Receive Transaction: 
  Receiving Inspection Account ??? Debit for the Changed Amount 
  Accrual Account ??? Credit for the Changed Amount.
   
  Deliver Transaction: 
  Retroactive Account ??? Debit for the Changed Amount. 
  Receiving Inspection Account ??? Credit for the Changed Amount.
   
• If the profile 'PO: Allow Retroactive Pricing of POs' is set to 'All Releases' and
  Blanket Releases / Standard POs that are already invoiced are retroactively updated then price adjustment invoices are created in Oracle Payables when the 'Create Adjusting Documents in Payables Program' is run.

LOGGING

For the Retroactive Pricing related issues, Log messages can be used to further analyze the issue. 

1. FND Log Message: 
   a. Set the following profile options at the user level.
    
   

   Set FND: Debug Log Enabled= 'Yes'
   Set FND: Debug Log Level = 'Statement'
   Set FND: Debug Log Module = 'po.plsql%'

    
   b. Run the following query to find the max log sequence from fnd_log_messages table.
    
   

   Select max(log_Sequence) from fnd_log_messages;

    
   c. Reproduce the issue.
    
   d. Run the following query to get the log messages.
    
   

   SELECT module, log_sequence, message_text, timestamp
   FROM fnd_log_messages
   WHERE module like 'po.plsql%'
   AND log_sequence > [max log sequence noted from output of query b]
   order by log_sequence
   

    
2. Workflow Output:
   Provide the wfstatus.sql output for the BPA.  Refer to this Note 134960.1 to run the wfstatus.sql
    
3. Concurrent Log:
   To get the detailed log information for the concurrent program POXRPDP: Retroactive Price Update of Purchasing Documents Program.
   a.

   Set the Profile ???PO:Set Concurrent Debug to ON??? as ???Yes???
   

    
   b. Reproduce the issue by running the concurrent program POXRPDP: ???Retroactive Price Update of Purchasing Documents??? Program.
    
   c. Provide the concurrent program log file.
    
4. Workflow Attribute Value:
   Run the following query to check the value of the workflow attribute 'Change Order Header Auto Approve Retroactively Priced Releases' 
    
   

   select rtrim(w.name) name,
   w.text_default Value,
   rtrim(w.item_type) item_type,
   'Change Order Header Auto Approve Retroactively Priced Releases' Attribute
   from wf_item_attributes w
   where w.NAME = 'CO_H_RETROACTIVE_AUTOAPPROVAL' ;

TRACING

Steps to get Database Trace:

• Set the profile option " Initialization SQL statement - custom " at user level to
   
  

  BEGIN FND_CTL.FND_SESS_CTL ('','','TRUE','TRUE','LOG', 'ALTER SESSION SET TRACEFILE_IDENTIFIER =''UniqueIdentifier'' EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12'''); END;

   
  This must be one complete line of text.
  Navigation:
  System Administrator Responsibility
  Profile > System
   
• Reproduce the issue.
   
• On reproduction the trace file will contain Unique Identifier mentioned in the trace file identifier. Upload all the trace files containing this identifier and matching the timestamp of the action.
  The trace files can be retrieved from the database server, the output of the following query will give the path of the trace file.
   
  

  select value from v$parameter where name like 'user_dump_dest';

   

RELATED PROCESSING

Availability of Recalculate Price option in Purchase order/Release form:

Recalculate price option is also related with updating the price of PO / Release.
For standard purchase order lines that reference a source document / Release shipments, if user manually changes the price derived from the source document, Recalculate price option can be used to reset/derive the price again.

So the availability of Recalculate price option in Purchase order/Release form should also be dependent on the Retroactive option.

The following table describes the availability of Recalculate price option in PO/Release form with related to Retroactive option under all possible conditions.

If price can be manually updated, then recalculate price should be available from the menu.


# The following table describes the behaviour of the Retroactive pricing in all possible scenario ( ie ) whether the PO/Release Price can be updated manually and/or through concurrent program based on the Retroactive profile option value and PO/Release status.

CODE FILES

KNOWN ISSUES AND RELEVANT NOTES

• Note.401004.1 Blanket Release Action History Showing 'Update Closure Status Rolled Up' With Closure Status OPEN
• Note.554450.1 Retroactive Price Update Not Updating Releases After BPA Change Is Submitted For Approval
• Note.330724.1 Able to Recalculate Price With PO Allow Retroactive Pricing of Pos set to Never
• Note.368484.1 Retroactive Pricing Does Not Update The Revised Date On Blanket Releases
• Note.470314.1 "Retroactive Price Update Of Purchasing Documents"Cause Wrong Quantity_billed
• Note.403604.1 Purchase Orders When They are 'Forwarded To' Another User are Automatically Approved Even When There is an Increase in Price or Unit
• Note.369779.1 Po Output For Communication Not Spawned After Retroactive Price Change
  

• Note.313320.1 Retroactive Pricing Not Creating The Correct Accounting for Receipt Corrections
• Note.454734.1 Incorrect Price on Receiving Transactions When Purchase Order is not Approved
• Note.315576.1 Pay on Receipt Invoice Created With the Receiving Price Instead of the Retroactive Price Updated Price On the Purchase Order
  

• Note.555470.1 Automatic Offset Method and Retroactive Pricing Functionality
• Note.297360.1 Documentation Wrong On Retroactive Pricing