[Home] [Help]
759:
760:
761: --Bug 3140760
762: --A sales order has a representation in two tables
763: --OE_HEADERS_ALL.HEADER_ID and MTL_SALES_ORDERS.SALES_ORDER_ID
764: --Given a header id, finding the equivalent sales_order_id is a little tricky
765: --Similar logic is done in the view QA_SALES_ORDERS_LOV_V
766: --Function below is built for Convenience purpose
767: --This function takes a SO Header id (OE_HEADERS_ALL.HEADER_ID)
764: --Given a header id, finding the equivalent sales_order_id is a little tricky
765: --Similar logic is done in the view QA_SALES_ORDERS_LOV_V
766: --Function below is built for Convenience purpose
767: --This function takes a SO Header id (OE_HEADERS_ALL.HEADER_ID)
768: --Computes the equivalent Sales_order_id in Mtl_sales_orders and return it
769: --
770: FUNCTION OEHEADER_TO_MTLSALES ( p_oe_header_id IN NUMBER )
771: RETURN NUMBER
772: IS
777: -- bug 4328665
778: -- Added the function to_char() to the
779: -- filtering condition
780: -- mso.segment1 = oe.order_number
781: -- so that the index MTL_SALES_ORDERS_N1 is
782: -- refrerred to; while selecting the data from
783: -- MTL_SALES_ORDERS table, instead of doing
784: -- a FTS.
785: -- ntungare Wed May 2 03:50:09 PDT 2007
779: -- filtering condition
780: -- mso.segment1 = oe.order_number
781: -- so that the index MTL_SALES_ORDERS_N1 is
782: -- refrerred to; while selecting the data from
783: -- MTL_SALES_ORDERS table, instead of doing
784: -- a FTS.
785: -- ntungare Wed May 2 03:50:09 PDT 2007
786: --
787: CURSOR mtl_so_cur IS
785: -- ntungare Wed May 2 03:50:09 PDT 2007
786: --
787: CURSOR mtl_so_cur IS
788: SELECT mso.sales_order_id
789: FROM mtl_sales_orders mso,
790: oe_order_headers_all oe,
791: qa_customers_lov_v rc,
792: oe_transaction_types_tl ot,
793: fnd_languages fl