[Home] [Help]
307:
308:
309: cursor c_location_id is
310: SELECT ship_to_location_id
311: FROM po_line_locations_all
312: WHERE po_header_id = p_po_header_id
313: AND po_line_id = p_po_line_id;
314:
315:
1261: v_debug BOOLEAN; --File.Sql.35 Cbabu := false;
1262: v_myfilehandle UTL_FILE.FILE_TYPE;
1263: v_utl_file_name VARCHAR2(100); --File.Sql.35 Cbabu := 'update_57f4_on_receiving.log';
1264: v_utl_location VARCHAR2(512);
1265: v_po_uom po_line_locations_all.unit_meas_lookup_code%type;
1266:
1267: CURSOR c_po_uom is
1268: select unit_meas_lookup_code
1269: from po_line_locations_all
1265: v_po_uom po_line_locations_all.unit_meas_lookup_code%type;
1266:
1267: CURSOR c_po_uom is
1268: select unit_meas_lookup_code
1269: from po_line_locations_all
1270: where line_location_id = p_po_line_location_id;
1271:
1272: CURSOR c_po_line_uom is
1273: select unit_meas_lookup_code
1592: is preventing the entry of control into the code paths which update the RTV form.
1593:
1594: 5. 01-mar-2004 ssumaith - bug# 3446045 file version 618.2.
1595:
1596: unit_meas_lookup_code column in the po_line_locations_all table is null in the clients
1597: instance . The value in this field is being used as a basis of uom comparison. This
1598: is causing wrong uom conversion and return quantuty is not getting updated correctly
1599: when uom is changed.
1600:
1598: is causing wrong uom conversion and return quantuty is not getting updated correctly
1599: when uom is changed.
1600:
1601: This has been corrected by using the unit_meas_lookup_code of the po_lines_all table
1602: in case the value retreived from the po_line_locations_all table is null.
1603:
1604: 6 03-JUN-2004 Vijay Shankar for Bug# 3644845, Version:115.1
1605: return quantity is not getting updated when one of the OSP component is sent through Secondary form because the
1606: code assumes that the components related to n OSP items will be sent in one form. Now the code is modified by