eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.JAI_AR_RCTLA_TRIGGER_PKG dependencies on JAI_OM_UTILS_PKG

Line 6493: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price

6489:
6490: Fix
6491: ---
6492: Commented the code to calculate the assessable price and added a call
6493: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price
6494: correctly through various levels of defaultation.
6495:
6496: 10. 12-Nov-2008 CSahoo for bug#6012465, File Version 120.7.12000000.8
6497: Issue: ASSESSABLE PRICE FOR ITEMS DOES NOT APPEAR IN AR

Line 6710: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value

6706: /*
6707: ||Start of bug #4567935 (115 bug3671351)
6708: ||Code added, Ramananda for bug #4567935 (115 bug3671351), Start
6709: ||Instead of deriving the assessable valeu in this trigger,
6710: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value
6711: ||The function gets the assessable value based on 5 level defaultation
6712: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
6713: */
6714:

Line 6715: v_price_list := jai_om_utils_pkg.get_oe_assessable_value

6711: ||The function gets the assessable value based on 5 level defaultation
6712: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
6713: */
6714:
6715: v_price_list := jai_om_utils_pkg.get_oe_assessable_value
6716: (
6717: p_customer_id => v_customer_id,
6718: p_ship_to_site_use_id =>v_site_use_id, /*Bug 8371741*/
6719: p_inventory_item_id => v_inventory_item_id,

Line 7517: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price

7513:
7514: Fix:
7515: ----
7516: Commented the code to calculate the assessable price and added a call
7517: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price
7518: correctly through various levels of defaultation
7519:
7520: 10. 2-FEB-2006 SACSETHI for bug 5631784 , forward porting bug
7521: for TCS Enchancement

Line 7690: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value

7686:
7687: /*
7688: ||Added by Ramananda for bug #4567935 (115 bug3671351) , Start
7689: ||Instead of deriving the assessable valeu in this trigger,
7690: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value
7691: ||The function gets the assessable value based on 5 level defaultation
7692: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
7693: */
7694: v_price_list := jai_om_utils_pkg.get_oe_assessable_value

Line 7694: v_price_list := jai_om_utils_pkg.get_oe_assessable_value

7690: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value
7691: ||The function gets the assessable value based on 5 level defaultation
7692: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
7693: */
7694: v_price_list := jai_om_utils_pkg.get_oe_assessable_value
7695: (
7696: p_customer_id => v_customer_id,
7697: p_ship_to_site_use_id => v_bill_to_site_use_id, /*Bug 8371741*/
7698: p_inventory_item_id => v_inventory_item_id,