APPS.CN_MULTI_RATE_SCHEDULES_PVT dependencies on CN_MULTI_RATE_SCHEDULES_PKG

Line 369: cn_multi_rate_schedules_pkg.insert_row(x_rate_schedule_id => x_rate_schedule_id,

365: --R12 MOAC Changes--End
366: );
367:
368: -- call table handler to create rate schedule record in cn_rate_schedules
369: cn_multi_rate_schedules_pkg.insert_row(x_rate_schedule_id => x_rate_schedule_id,
370: x_name => p_name,
371: x_commission_unit_code => p_commission_unit_code,
372: x_number_dim => l_number_dim,
373: --R12 MOAC Changes--Start

Line 614: cn_multi_rate_schedules_pkg.lock_row

610: where rate_schedule_id = p_rate_schedule_id;
611: -- End - R12 Notes History Query for old Rate Table Name
612:
613: -- lock rate schedule for update or delete
614: cn_multi_rate_schedules_pkg.lock_row
615: (x_rate_schedule_id => p_rate_schedule_id,
616: x_object_version_number => p_object_version_number);
617:
618: IF (p_dims_tbl.COUNT > 0) THEN

Line 654: cn_multi_rate_schedules_pkg.update_row

650: OPEN schedule_info;
651: FETCH schedule_info INTO l_commission_unit_code_old, l_number_dim;
652: CLOSE schedule_info;
653:
654: cn_multi_rate_schedules_pkg.update_row
655: (x_rate_schedule_id => p_rate_schedule_id,
656: x_name => p_name,
657: x_commission_unit_code => p_commission_unit_code,
658: x_number_dim => l_number_dim,

Line 867: cn_multi_rate_schedules_pkg.delete_row(p_rate_schedule_id);

863: WHERE rate_schedule_id = p_rate_schedule_id;
864: /* End - R12 Notes History */
865:
866: -- deleting a rate schedule causes cascading delete
867: cn_multi_rate_schedules_pkg.delete_row(p_rate_schedule_id);
868:
869: -- *********************************************************************
870: -- ************ Start - R12 Notes History ******************************
871: -- *********************************************************************