How to remove Pending and Errored Transactions from Transaction Status Summary

This File show how to remove Pending and Errored Transactions from Transaction Status Summary from the following flash.

You can download the file from the following link:



All Receiving Transactions Fail with rvtptcontrol or RVTII-060 or RVTTH-445 or RVTTH-448 or RVTII-030 or RVTII-080 or RVTPT-020

Applies to:

Oracle Inventory Management – Version 11.5.1 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
FORM:RCVTXERT.FMB – Enter Receiving Transactions GUI
FORM:RCVTXECO.FMB – Enter Corrections GUI
EXECUTABLE:RVCTP – Receiving Transaction Processor


Receiving transactions fail with rvptcontrol or RVTII-060 or RVTTH-445 or RVTTH-448 or RVTII-030 or RVTII-080 or RVTPT-020 error (and sometimes there is no error). Sometimes the error only occurs when using RCV: Processing Mode=On-line, and sometimes only certain document types (like RMAs or Expense Purchase Orders) are affected.


In some cases this occurs after a patch has been applied.


When many transactions fail with same error it is usually because the receiving executables (RVCTP and RCVOLTM) are out of sync. The exact cause may not be known, but could be caused by one of the following:
patch application
environment parameter change
invalid objects
database crash

  1. Resolve INVALID Objects
  2. Relink receiving executables
    cd $PO_TOP/bin
    $ adrelink force=y ranlib=y “PO RCVOLTM”
    $ adrelink force=y ranlib=y “PO RVCTP”
  3. Bounce Receiving Transaction Manager:
    – $ps -ef | grep RCVOLTM (to see how many processes are running)
    -Deactivate Receiving Transaction Manager
    (System Administrator > Concurrent > Manager > Administer)
    -$ps -ef | grep RCVOLTM (repeat until no processes are running)
    -Restart Receiving Transaction Manager

    For additional information about above steps, please refer to the following notes:
    Note 1325394.1 (Troubleshooting Guide – invalid objects in E-Business Suite Environment 11i and 12)
    Note 552702.1 (How To Relink and Bounce the Receiving Executables?)
  4. Perform transaction.
  5. If the transaction still fails, bounce the database and then perform another transaction.
  6. If bouncing the database or flushing Shared Pool resolves the issue only for a few days (or a few weeks) and bounce database (or flush Shared Pool) must be repeated periodically to resolve the issue, please review the following notes:
    Note 351306.1 (RCVRCERC Receipts Fail with No Errors)
    Note 436947.1(How to Avoid OM error: ORA-06508: PL/SQL: Could Not Find Program Unit Error.)
  7. If all transactions still fail after performing the steps above, please log a Service Request with Inventory / Receiving and provide the following information:
    a. Output from “Diagnostics: Apps Check” Report using a Purchasing Responsibility:
    – Reports > Run
    – Submit a Single Request
    – Name: Diagnostics: Apps Check
    – Parameters: Application 1: Oracle Purchasing
    – Parameters: Application 2: Oracle Inventory
    – Submit the request
    – View > Requests
    – Select the Report Output (not the Log)
    **output contains file versions and other information that may be needed to progress issue or verify potential solutions; also required if bug is loggedb. Resolve all INVALID Objects; if any INVALID Objects cannot be resolved, provide Excel spreadsheet, including Column Headings of output from the following:

    select owner, object_name, object_type
    from all_objects
    where status=’INVALID’
    order by owner, object_name

    c. Provide database trace for one occurrence:

    NOTE: Make sure trace is not enabled at forms or concurrent program level when profile below is set

    1) Enable trace for a specific user:
    – Bring up the Core application – System Administrator responsibility – Move to Profile/System
    – Check off the USER box – and enter your username that you are using when getting the error
    – Search on the following profile option – ‘Initialization SQL Statement – Custom’

    2) Set this value at the User Level:

    Cut and paste the above sql statement for the ‘Initialization SQL Statement – Custom’ Profile at the User Level. This must be one complete line of text – so may be best to copy the string into notepad prior to putting it into the profile.
    **it is not required to use ‘rcvtrace.trc’; please ensure the filename is unique so only one transaction will be captured in the trace (this value is required in next step to locate the trace file)

    3) Once the profile is set, change Responsibilities then reproduce the issue

    4) To locate the trace file, use the following sql in sqlplus:

    select name, value
    from v$parameter
    where name like ‘user_dump_dest’;

    – The value is the location of the trace file on the database server
    – Please move to this directory and search for the file having trace.sup in the filename
    – This is the trace file created – please tkprof it:
    tkprof <filename.trc> <output_filename> sys=no explain=apps/<password>

    5) Upload BOTH the raw and tkprof trace files

    6) Ensure that the profile option is unset before exiting the Application.

    This is a very important step; if the Profile is not unset, unnecessary trace files will be generated.