Professional Documents
Culture Documents
1
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.
How To Remove Pending and Error Receiving Transactions from Transaction Status Summary
(Doc ID 303544.1)
In this Document
Goal
Solution
1. Remove Pending or Error Transactions (including those from WMS enabled Organizations)
2. If needed, perform transaction(s) again.
3. Generic Datafix
4. Serial Controlled Items
5. Test Your Knowledge
a. Process Records in Batch Mode (Baseline Test)
b. Delete Pending Batch Mode Transactions via Form
c. Delete Pending Batch Mode Transactions via SQL
Still Have Questions?
References
APPLIES TO:
RCV_RCVTXVTX / P_ALLOW_DELETE
GOAL
How to remove Pending and Error Transactions from the Transaction Status Summary form?
SOLUTION
It is standard functionality for Error ("Errored") and Pending transactions to be visible on the Transaction Status Summary
form (RCVTXVTX). Along with the form, the library RCVTXVTX.pld uses the VIEW rcv_view_interface_v to return rows from
the table RCV_TRANSACTIONS_INTERFACE (RTI). When records fail to process, a common approach is to delete the
interface records then try to reprocess the receipts or receiving transactions. This is a common approach and often results
in transactions processing the 2nd try. Another approach would be to remove the interface transactions and cancel the
problematic lines. Possibly this would be a useful workaround in urgent cases to avoid the issue then users could move
forward with a new receipt or with a miscellaneous receipt.
Please review the following note for additional details. Note 197860.1 - Explanation of RCV: Processing Modes, Pending
Transactions and Destination Types
1. Remove Pending or Error Transactions (including those from WMS enabled Organizations)
a. Navigate to: Purchasing Super User Responsibility (or Inventory Responsibility) > Receiving > Transaction Status
Summary
using desired criteria
b. Query
c. Click on desired line, not the
Checkbox beside the line
(note the Document Number before proceeding to the
next step in case you need to process the transaction again)
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v40u4nr5d_167&id=303544.1 1/6
01/07/2022 18:20 Document 303544.1
d. From the toolbar, click the Delete Icon (red 'X')
e. Repeat c and d until all desired transactions have been deleted
f. Save
Note: For applications release prior to Release 12.1.3 INV/RCV RUP 7, the Transaction Status Summary form is not
designed to allow users to submit or resubmit transactions from it. Error message "FRM-40200: Field is protected
against update" will occur if User attempts to select Checkbox.
See the section on R12.1 for further details on new ROI enhancement Request for this form.
Click Here to View the How to Remove Pending and Errored Transactions From Transaction Status Summary Viewlet (1,275
KB)
Note: There may be Pending Online Running records shown in the Transaction Status Summary form, these records
are processed via the Online Receiving Executable RCVOLTM.
The RCVOLTM works by the Receiving Manager utilizing the FND
fnd_transaction.synchronous (FNDCPTM) where the
transaction is written to the FND pipe buffer and the FND concurrent processor transaction manager picks it up and
processes the transaction in the order it was received in the buffer. There are times due to various situations that the
record is lost in the buffer or gets out of synch and the FNDCPTM thinks the receiving transaction is actually being
processed but in fact it is not. For these situations all you can do is locate the record in the Transaction Status
Summary form and delete the stuck pending record and process a new replacement receipt.
a. If Lot or Serial Controlled Items are associated with the transaction, please apply the patch referenced in the
following note to ensure mtl_transaction_lots_interface and mtl_serial_numbers_interface records are also deleted.
Note 1375180.1 - RCVTXVTX (Transaction Status Summary) Does Not Delete All Associated Records
1. Delete feature has been made more restrictive. To enable users to delete pending or running ROI transactions,
you must set the P_ALLOW_DELETE form parameter function to Yes for the predefined View Transactions Status
GUI (RCVTXVTX) form or the custom function that you use.
you must set the P_ALLOW_DELETE form
To enable users to delete pending or running ROI transactions,
parameter function to Yes for the predefined View Transactions Status GUI (RCVTXVTX) form
a. Go into the responsibility: Application Developer
the issue.
g. Retest
Note: The following rules apply to the delete transactions feature, you cannot delete the following transactions:
• Oracle Time and Labor (OTL) pending transactions.
Apply Patch 20547117 to allow for deletion of records via the Transaction Status Summary form, for records
from Mobile without LPN attached (ie with mobile_txn ='Y' even if lpn_group_id is populated.) Without the
patch, the user cannot delete the mobile transactions in the transaction status summary form.
R12.1.3 : Patch 20547117:R12.PO.B gives RCVTXVTX.pld 120.8.12010000.26
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v40u4nr5d_167&id=303544.1 2/6
01/07/2022 18:20 Document 303544.1
3. Generic Datafix
If records exist in rcv_transactions_interface but can not be deleted via the Transaction Status Summary form
You may use a generic datafix to remove select records, including records from WMS enabled Orgs.
a. Run the script to check the backup tables: table_check23.sql
exists, you may drop the table if the data is no
Note: if the backup table referenced in the delete script already
longer needed per your business processes, or you may use a different backup table name.
b. Run the appropriate datafix script:
In some cases, the following sql may help identifying records for a specific Purchase Order:
Reference Note 1679587.1 - Unable To Find Purchase Order To Return / Correct or Deliver APP-PO-
14094
Note 760055.1 - Are Receiving Open Interface (ROI) Transactions Listed On Transaction Status Summary Form?
Note 605300.1 - How Are Failed Receiving Open Interface (ROI) Transactions Reprocessed?
If Item is Serial Controlled and there is concern about data in mtl_serial_numbers or mtl_serial_numbers_temp, please
check the identification/solution details in Note 1472005.1 - Inventory Standard Datafix Instruction #4: Fixing Marked
Serial Numbers (MSN), Orphan Pending Serials (MSNT), and Orphan Status 6 Serials (MSN) [Video].
This section outlines steps to run a transaction in batch mode (a) then you decide that the transaction was incorrect or a
mistake (b and c) so want to remove the transaction. This also simulates a case where the transaction is in error or has
failed and you need to remove it. You will receive a purchase order quantity 10 in 3 parts: 1, 3, and 6. You will process the
quantity 1 (steps a), delete the quantity 3 (steps b), and delete quantity 6 (steps c).
Create a purchase order with quantity 10 that you will use for the tests. Perform receiving 3 separate times to create 3
sets of records that you can manipulate. The first will be processed.
3. Receive:
Navigate to
Inventory > Receiving > Receipts : Perform 3 receipts for 1, 3, 6
* Do 3 separate receipts so you get 3 groups of transactions.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v40u4nr5d_167&id=303544.1 3/6
01/07/2022 18:20 Document 303544.1
5. Run the receiving processor for the receipt quantity 1 group only:
Navigate to Inventory > Requests > Submit > Single Request > Run
"Receiving Transaction Processor" with Parameter
GROUP_ID from SQL query in #4.
In this test you will continue with the purchase order from the earlier test (a) but remove the transaction for quantity 3 via
the Form. This simulates removing a transaction that had a problem, error, or was incorrectly submitted.
3. Back in the application, remove the Receipt for the row with quantity 3:
Click row (not checkbox) > Click Red-X on toolbar to remove.
Note: If the Red-X is missing, please validate the setup for the receiving function (RCV_RCVTXVTX) to ensure the allow
delete parameter is set (‘P_ALLOW_DELETE=Y’). Steps follow:
a. Go into the responsibility: Application Developer
the issue.
g. Retest
In this test, you continue with the purchaser order created in the earlier test (a) removing the receiving transaction
quantity 6 with SQL. This simulates a case where you need to remove a transaction with an error or incorrectly processed.
Navigate to Inventory > Receiving > Transactions Status Summary : Query Receipt but do not remove the receipt.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v40u4nr5d_167&id=303544.1 4/6
01/07/2022 18:20 Document 303544.1
2. Query the receiving interface record via SQL noting the interface id (INTERFACE_TRANSACTION_ID) noting the
transaction id with quantity 6:
Note: If backup tables exist, you must first move or drop them. Examples scripts to drop the backups:
drop table
mtlt_bak;
drop table mtli_bak;
drop table
msni_bak;
drop table msnt_bak;
4. Run the delete script delivered in this document entering the receiving transaction interface id when prompted :
@delete_stuck_rti_for_R121_and_above.sql
5. Query the receiving interface record via SQL noting the interface id (INTERFACE_TRANSACTION_ID):
7. Navigate to Inventory > Receiving > Transactions Status Summary : Query Receipt -- It should no longer be available
* for r12.x: Generate data from the Receiving Analyzer: Note 2012304.1 - EBS Procurement Receiving Analyzer
* for r11i: Run the Receiving Data Collection report per Note 423279.1 - How Can The Receiving Data Collection
Script
(rcv11i_sa.sql For R11 AND R12) Be Run From Within The Oracle Application?
Join our growing Oracle Procurement Community and learn from your peers and Oracle on how to address your unique iss
You can access the main Oracle Communities page at http://communities.oracle.com (If you are enrolled, the Procuremen
already enrolled in the Procurement community, you can do so by clicking on the link Edit Subscriptions).
OR
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v40u4nr5d_167&id=303544.1 5/6
01/07/2022 18:20 Document 303544.1
REFERENCES
NOTE:263368.1 - How To Get Additional Information For Documents Associated with Records On Transaction Status
Summary Form (rcv_transactions_interface table)
NOTE:1610656.1 - New ROI Enhancement on RCVTXVTX
Transaction Status Summary Form
NOTE:352691.1 - How Do You View All the Pending/Errored RMAs in the Transaction Status Summary Form (RCVTXVTX)?
NOTE:1679587.1 - Unable To Find Purchase Order To Return / Correct / Deliver APP-PO-14094 / or Form Hangs
NOTE:1472005.1 - Inventory Standard Datafix Instruction #4: Fixing Marked Serial Numbers (MSN), Orphan Pending
Serials (MSNT), and Orphan Status 6 Serials (MSN) [Video]
NOTE:605300.1 - How Are Failed Receiving Open Interface
(ROI) Transactions Reset?
NOTE:1610653.1 - Delete Icon Is Disabled / Greyed Out on RCVTXVTX Transaction Statuses Form For Pending / Running
Transactions After RUP 7 / or Release 12.2.x
NOTE:726045.1 - What Form Functionality Is
Available to Delete Or Reprocess ROI Transactions?
NOTE:1912900.1 - Guideline to Delete Records Stuck into RCV_TRANSACTIONS_INTERFACE After
Running and Analyzing
Output from Note 263368.1
NOTE:1522732.1 - RCVTXVTX:
Transaction Status Summary Returns APP-PO-14094 For Pending Transactions Reported in
Inventory
NOTE:760055.1 - Are Receiving Open Interface (ROI) Transactions Listed On Transaction Status Summary Form And How
Are ROI Records Deleted?
NOTE:197860.1 - Explanation of RCV: Processing Modes, Pending Transactions and Destination Types
NOTE:1456471.1 - Unable To Delete Record From Transaction Status Summary Form RCVTXVTX FRM-41049:
You cannot
delete this record
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=v40u4nr5d_167&id=303544.1 6/6