APPS.GMF_COPY_ITEM_COST dependencies on CM_SCST_LED

Line 919: * in cm_cmpt_dtl nor delete them from cm_scst_led/cm_acst_led.

915: * Try update of cm_cmpt_dtl first
916: * Update can fail for two reasons: either the row is not there
917: * or, the row exists but is frozen (rollover_ind = 1)
918: * If the costs are frozen in the target period then do not update the rows
919: * in cm_cmpt_dtl nor delete them from cm_scst_led/cm_acst_led.
920: * The item cost rows should be left untouched in the target period even if
921: * one of the components is frozen.
922: */
923:

Line 1128: cm_scst_led

1124: * Update cmpt_dtl
1125: */
1126:
1127: DELETE FROM
1128: cm_scst_led
1129: WHERE
1130: cmpntcost_id = l_updins_cc_id
1131: ;
1132:

Line 1463: * Deletes the child rows from cm_scst_led, cm_acst_led and sets

1459: * PROCEDURE
1460: * delete_item_costs
1461: *
1462: * DESCRIPTION
1463: * Deletes the child rows from cm_scst_led, cm_acst_led and sets
1464: * cmpntcost_id to null in cm_brdn_dtl for the cost parameters passed
1465: * NOTE: We do not have to worry about rollover_ind here since this procedure
1466: * is not even called if the item is frozen in the target period.
1467: *

Line 1526: cm_scst_led

1522: gmf_util.trace( SQL%ROWCOUNT || ' rows deleted from acst_led', 3 );
1523:
1524: -- Delete rows from scst_led
1525: DELETE FROM
1526: cm_scst_led
1527: WHERE
1528: cmpntcost_id = r_cc_id.cmpntcost_id
1529: ;
1530: