APPS.INV_QUANTITY_TREE_PVT dependencies on PJM_UNIT_EFF

Line 450: --bug 2363739 - added call to pjm_unit_eff.unit_item_effective in

446: --transaction_action_id , transfer_subinventory_code and transfer_locator_id
447:
448: -- pjm support
449: --
450: --bug 2363739 - added call to pjm_unit_eff.unit_item_effective in
451: -- build cursor, so that if build_sql is called from within the
452: -- quantity tree API, g_unit_eff_enabled is already populated.
453: -- However, we need to keep this check here since build_sql
454: -- could be called by outside APIs.

Line 456: SELECT pjm_unit_eff.enabled INTO g_unit_eff_enabled FROM dual;

452: -- quantity tree API, g_unit_eff_enabled is already populated.
453: -- However, we need to keep this check here since build_sql
454: -- could be called by outside APIs.
455: IF g_unit_eff_enabled IS NULL THEN
456: SELECT pjm_unit_eff.enabled INTO g_unit_eff_enabled FROM dual;
457: END IF;
458: IF g_unit_eff_enabled <> 'Y' THEN
459: l_onhand_qty_part := ' moq.primary_transaction_quantity ';
460: l_mmtt_qty_part := ' mmtt.primary_quantity ';

Line 941: -- bug 2752979 : adding group by to l_onhand_stmt for only PJM unit eff items.

937: --bug 1384720
938: -- Moved group by statement into subquery. This minimizes
939: -- the number of joins to the lot and sub tables.
940:
941: -- bug 2752979 : adding group by to l_onhand_stmt for only PJM unit eff items.
942:
943: IF g_unit_eff_enabled = 'Y' THEN
944: l_onhand_stmt := l_onhand_stmt ||
945: 'GROUP BY moq.organization_id,moq.inventory_item_id,moq.revision,

Line 1079: -- enabled in the pjm_unit_eff API. This will improve performance

1075: BEGIN
1076: l_cursor := dbms_sql.open_cursor;
1077:
1078: --bug 2363739 - we now call unit_effective_item instead of
1079: -- enabled in the pjm_unit_eff API. This will improve performance
1080: -- by limiting the number of times we use the PJM function to determine
1081: -- onhand quantity in build_sql. Made the call here, and not in
1082: -- build_sql, becuase the procedure takes the org and item as parameters.
1083: g_unit_eff_enabled := pjm_unit_eff.unit_effective_item(

Line 1083: g_unit_eff_enabled := pjm_unit_eff.unit_effective_item(

1079: -- enabled in the pjm_unit_eff API. This will improve performance
1080: -- by limiting the number of times we use the PJM function to determine
1081: -- onhand quantity in build_sql. Made the call here, and not in
1082: -- build_sql, becuase the procedure takes the org and item as parameters.
1083: g_unit_eff_enabled := pjm_unit_eff.unit_effective_item(
1084: x_item_id => p_inventory_item_id
1085: ,x_organization_id => p_organization_id);
1086:
1087: build_sql

Line 1756: -- If PJM unit effectivity is enabled, we need to create

1752:
1753: x_return_status := fnd_api.g_ret_sts_success;
1754:
1755: -- Bug 1918356
1756: -- If PJM unit effectivity is enabled, we need to create
1757: -- a new tree for each different sales order line id
1758: -- Bug 2363739 - now call unit_effective_item
1759: l_pjm_enabled := pjm_unit_eff.unit_effective_item(
1760: x_item_id => p_inventory_item_id

Line 1759: l_pjm_enabled := pjm_unit_eff.unit_effective_item(

1755: -- Bug 1918356
1756: -- If PJM unit effectivity is enabled, we need to create
1757: -- a new tree for each different sales order line id
1758: -- Bug 2363739 - now call unit_effective_item
1759: l_pjm_enabled := pjm_unit_eff.unit_effective_item(
1760: x_item_id => p_inventory_item_id
1761: , x_organization_id => p_organization_id);
1762: IF l_pjm_enabled IS NULL THEN
1763: l_pjm_enabled := 'N';

Line 2014: l_unit_effective := pjm_unit_eff.unit_effective_item(

2010:
2011: --BENCHMARK
2012: --check whether item is unit effective controlled
2013: /* Check item cache instead of PJM function
2014: l_unit_effective := pjm_unit_eff.unit_effective_item(
2015: x_item_id => p_inventory_item_id
2016: ,x_organization_id => p_organization_id);
2017: */
2018: l_return_value := INV_CACHE.set_item_rec(p_organization_id, p_inventory_item_id);