[Home] [Help]
248:
249:
250: cursor c_location_id is
251: SELECT ship_to_location_id
252: FROM po_line_locations_all
253: WHERE po_header_id = p_po_header_id
254: AND po_line_id = p_po_line_id;
255:
256:
1138: v_debug BOOLEAN; --File.Sql.35 Cbabu := false;
1139: v_myfilehandle UTL_FILE.FILE_TYPE;
1140: v_utl_file_name VARCHAR2(100); --File.Sql.35 Cbabu := 'update_57f4_on_receiving.log';
1141: v_utl_location VARCHAR2(512);
1142: v_po_uom po_line_locations_all.unit_meas_lookup_code%type;
1143:
1144: CURSOR c_po_uom is
1145: select unit_meas_lookup_code
1146: from po_line_locations_all
1142: v_po_uom po_line_locations_all.unit_meas_lookup_code%type;
1143:
1144: CURSOR c_po_uom is
1145: select unit_meas_lookup_code
1146: from po_line_locations_all
1147: where line_location_id = p_po_line_location_id;
1148:
1149: CURSOR c_po_line_uom is
1150: select unit_meas_lookup_code
1427: is preventing the entry of control into the code paths which update the RTV form.
1428:
1429: 5. 01-mar-2004 ssumaith - bug# 3446045 file version 618.2.
1430:
1431: unit_meas_lookup_code column in the po_line_locations_all table is null in the clients
1432: instance . The value in this field is being used as a basis of uom comparison. This
1433: is causing wrong uom conversion and return quantuty is not getting updated correctly
1434: when uom is changed.
1435:
1433: is causing wrong uom conversion and return quantuty is not getting updated correctly
1434: when uom is changed.
1435:
1436: This has been corrected by using the unit_meas_lookup_code of the po_lines_all table
1437: in case the value retreived from the po_line_locations_all table is null.
1438:
1439: 6 03-JUN-2004 Vijay Shankar for Bug# 3644845, Version:115.1
1440: return quantity is not getting updated when one of the OSP component is sent through Secondary form because the
1441: code assumes that the components related to n OSP items will be sent in one form. Now the code is modified by