[Home] [Help]
313: IS
314: SELECT
315: sum(qty_matched)
316: FROM
317: JAI_OM_LC_MATCHINGS
318: WHERE
319: order_header_id = pr_new.source_header_id AND
320: -- order_line_id = pr_new.source_line_id AND --commented by csahoo for bug#5686360
321: delivery_detail_id = cp_delivery_detail_id AND
336: where line_id = pr_new.source_line_id;
337:
338: cursor c_lc_mtch_dlry_line is
339: select order_line_id
340: from JAI_OM_LC_MATCHINGS
341: where delivery_detail_id = v_delivery_detail_id;
342: r_order_line c_order_line%rowtype;
343: r_lc_mtch_dlry_line c_lc_mtch_dlry_line%rowtype;
344: ln_lc_update_cnt number;
555: Added another condition in the WHEN Clause of the trigger to check that the trigger
556: fires only when the Released_status field is set to 'C' and does not fire
557: on updates of other fields at which point the releaed_status is 'C'.
558:
559: Also the update statement , which updates the released_flag in the JAI_OM_LC_MATCHINGS table
560: has been commented , because the update should happen after the shipping has completed.
561:
562: Also an error message has to be thrown , when shipping is done , for an order
563: where the tax amounts in the JAI_OM_OE_SO_TAXES and JAI_OM_OE_SO_LINES do not tally.
1121: fetch c_lc_mtch_dlry_line into r_lc_mtch_dlry_line;
1122: close c_lc_mtch_dlry_line;
1123: if pr_new.source_line_id <> r_lc_mtch_dlry_line.order_line_id then
1124:
1125: update JAI_OM_LC_MATCHINGS
1126: set order_line_id = pr_new.source_line_id
1127: where delivery_detail_id = v_delivery_detail_id
1128: -- and order_line_id = r_order_line.split_from_line_id
1129: and release_flag is null;
1688: HEADER_ID = pr_new.SOURCE_HEADER_ID;
1689:
1690: CURSOR C_MATCHED_QTY_CUR IS
1691: SELECT SUM(QTY_MATCHED)
1692: FROM JAI_OM_LC_MATCHINGS
1693: WHERE ORDER_HEADER_ID = pr_new.SOURCE_HEADER_ID
1694: -- AND ORDER_LINE_ID = pr_new.SOURCE_LINE_ID --commented by csahoo for bug#5680459
1695: AND delivery_detail_id = pr_new.delivery_detail_id -- bug# 3541960
1696: AND RELEASE_FLAG IS NULL;
1708: where line_id = pr_new.source_line_id;
1709:
1710: cursor c_lc_mtch_dlry_line is
1711: select order_line_id
1712: from JAI_OM_LC_MATCHINGS
1713: where delivery_detail_id = pr_new.delivery_detail_id;
1714: r_order_line c_order_line%rowtype;
1715: r_lc_mtch_dlry_line c_lc_mtch_dlry_line%rowtype;
1716: ln_lc_update_cnt number;
2031: 19.31/03/2004 ssumaith - bug# 3541960 file version 619.1
2032:
2033: Issue :- when an lc enabled order is split and shipped , interface trip stop was going into error.
2034: The reason for this error is because for a delivery , the sum of matched quantity in the
2035: JAI_OM_LC_MATCHINGS table is compared to the quantity shipped for the delivery detail id being processed.
2036:
2037: Solution :- This issue is solved by comparing the delivery_detail_id also when getting the matched quantity.
2038: By including the delivery detail in the where clause , ensuring that in case of split orders
2039: also the shipment can go through without any errors.
2481: fetch c_lc_mtch_dlry_line into r_lc_mtch_dlry_line;
2482: close c_lc_mtch_dlry_line;
2483: if pr_new.source_line_id <> r_lc_mtch_dlry_line.order_line_id then
2484:
2485: update JAI_OM_LC_MATCHINGS
2486: set order_line_id = pr_new.source_line_id
2487: where delivery_detail_id = pr_new.Delivery_Detail_Id
2488: -- and order_line_id = r_order_line.split_from_line_id
2489: and release_flag is null;
2494:
2495: -- End, bug#5680459 csahoo
2496:
2497:
2498: UPDATE JAI_OM_LC_MATCHINGS
2499: SET RELEASE_FLAG = 'Y'
2500: WHERE DELIVERY_DETAIL_ID = pr_new.Delivery_Detail_id;
2501: END IF;
2502: