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 5112: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price

5108:
5109: Fix
5110: ---
5111: Commented the code to calculate the assessable price and added a call
5112: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price
5113: correctly through various levels of defaultation.
5114:
5115: 10. 12-Nov-2008 CSahoo for bug#6012465, File Version 120.7.12000000.8
5116: Issue: ASSESSABLE PRICE FOR ITEMS DOES NOT APPEAR IN AR

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

5268: /*
5269: ||Start of bug #4567935 (115 bug3671351)
5270: ||Code added, Ramananda for bug #4567935 (115 bug3671351), Start
5271: ||Instead of deriving the assessable valeu in this trigger,
5272: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value
5273: ||The function gets the assessable value based on 5 level defaultation
5274: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
5275: */
5276:

Line 5277: v_price_list := jai_om_utils_pkg.get_oe_assessable_value

5273: ||The function gets the assessable value based on 5 level defaultation
5274: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
5275: */
5276:
5277: v_price_list := jai_om_utils_pkg.get_oe_assessable_value
5278: (
5279: p_customer_id => v_customer_id,
5280: p_ship_to_site_use_id => v_ship_to_site_use_id,
5281: p_inventory_item_id => v_inventory_item_id,

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

6054:
6055: Fix:
6056: ----
6057: Commented the code to calculate the assessable price and added a call
6058: to the jai_om_utils_pkg.get_oe_assessable_value function to calculate the assessable price
6059: correctly through various levels of defaultation
6060:
6061: 10. 2-FEB-2006 SACSETHI for bug 5631784 , forward porting bug
6062: for TCS Enchancement

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

6206:
6207: /*
6208: ||Added by Ramananda for bug #4567935 (115 bug3671351) , Start
6209: ||Instead of deriving the assessable valeu in this trigger,
6210: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value
6211: ||The function gets the assessable value based on 5 level defaultation
6212: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
6213: */
6214: v_price_list := jai_om_utils_pkg.get_oe_assessable_value

Line 6214: v_price_list := jai_om_utils_pkg.get_oe_assessable_value

6210: ||the same has been now shifted to the function jai_om_utils_pkg.get_oe_assessable_value
6211: ||The function gets the assessable value based on 5 level defaultation
6212: ||logic.Currently the assessable value was being fetched only from the so_price_list_lines
6213: */
6214: v_price_list := jai_om_utils_pkg.get_oe_assessable_value
6215: (
6216: p_customer_id => v_customer_id,
6217: p_ship_to_site_use_id => v_ship_to_site_use_id,
6218: p_inventory_item_id => v_inventory_item_id,