EBS 11.5 BUG: 4649123 Measure

Source: Internet
Author: User
Tags sql error

Bug content:

Applies:

Oracle Warehouse Management-version: 11.5.10.1
Oracle inventory management-version: 11.5.10
This problem can occur on any platform.
Executable: rvctp-processing ing transaction processor

Symptoms

Mobile intransit LPN receipts error and get stuck in rcv_transactions_interface table if there are multiple shipments having the same shipment number. (I. e.: create two internal shipments with different source and destination org with the same shipment_num with packed LPN, then refreshing receept of shipment)

The same error occurs when signing Ming Direct Express receipts against a shipment that have multiple lines with the same item, there may be multiple mtl_material_transactions records created after the Transaction Completes.
(I. e. :. perform MISC receept of an item into lpn a with qty 4. do another MISC receept of another item into lpn B with qty 10; B. create intransit shipment, entering LPN a first, then LPN B Second; then C. in the destination org, perform express receept of lpn B .)

Refreshing interface errors report shows errors as follows:

Error in shipment line information (in rcv_transactions_interface)
Column name interface_transaction_id
Error message LPN validation failed. Please check log for details.

Column name interface_transaction_id
Error message WMSINB-18557: LPN validation failed. Please check log for details. or
WMSINB-19139: LPN validation failed. Please check log for details.

Column name unit_of_measure
Error message specified unit of measure conversion to primary UOM Not Defined
(Shipment unit of measure = Carton: Primary unit of measure = each)

Column name interface_transaction_id
Error message RVSSH-020: ORA-1403: No data found
Cause: a SQL error has occurred in rvssh. The SQL error is & lsql_err.
Action: take note of both this error number and the actions you were

Processing transaction processor (rvctp) log shows the generic errors as follows:

Concurrent program rvctp returned error
Cause: rvctp encountered an internal error. parameters: rvctp, immediate, 36288,
Action: note both this error number and the actions you are trying to perform. Contact your System Adm

The RVTBM-008: subroutine rvtbm_immediate_mngr () returned error
Cause: subroutine rvtbm_immediate_mngr () returned an internal error.
Action: Note this error number and the actions you are trying to perform. Contact your release E

RVTBM-120: subroutine rvtptcontrol () returned error
Cause: subroutine rvtptcontrol () returned an internal error.
Action: Note this error number and the actions you are trying to perform. contact your system administrator

Cause

As explained in bug: 4649123 pending/immediate TRX stuck in rcv_transaction_interface
For the first case, the Code lacks a join between RSH. organization_id and wlpn. organization_id so that only shipment going to the certain org is selected (shipment_num is unique within org ). as for case #2, matching logic in processing ing Preprocessor is not picking up the right line because document_line_num is not being populated in rcv_transactions_interface when refreshing intship/intreq receipts.

Solution

Apply patch: 4890926 which upgrades files
$ Inv_top/patch/115/SQL/invrcvvb. pls to version 115.107.115100.24
$ Inv_top/patch/115/SQL/invstdrb. pls to version 115.164.115100.15

References

BUG: 4616373-datafix: Pending/immediate TRX stuck in rcv_transaction_interface
Bugs: 4649123-pending/immediate TRX stuck in rcv_transaction_interface

The following are some of my actual business phenomena:
1) input two rows of data on the output interface of po_requisition_lines, with the same material
2) input two rows of data on the output interface of po_requisition_lines. The materials are different.

After approval, perform the following operations in EBS:
1) import an internal application to a sales order by running the "Create Internal Order" and "Import Order" Requests

2) confirm the delivery of the sales order and run "connecting to the stopovers"

3) Use rcv_transactions_interface to automatically receive incoming data. For more information about the code, see EBS practice-apply for an internal Po to automatically receive incoming data.

 

After the interface table is imported, run the "receive transaction processing processor" request. The following results are displayed for the above two situations:

1) In rcv_transactions_interface, the value is document_line_num, and document_line_num = po_requisition_lines.line_num

1. When there is only one material (one or more rows) in the same internal application, the data warehouse receiving process is automatically completed.

2. When multiple materials are included in the same internal application, the system automatically receives the incoming data and fails to process the data. View po_interface_errors. The error message is: invalid transaction processing type.

2) The value of rcv_transactions_interface is invalid.

1. When there is only one item (one or more rows) in the same internal application, the receiving fails automatically. View po_interface_errors. The error message is: no data is found.
2. When multiple materials are included in the same internal application, the warehouse receiving process is automatically completed.

 

Find the cause on matelink and find that the above bug content is similar to what I encountered. So I studied the interface data and found that document_line_num should correspond to line_num IN THE rcv_shipment_lines table, and then perform the test after the relevant data is corrected (document_line_num = rcv_shipment_lines.line_num, in both cases, you can receive and store data in the database without any patch repair.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.