APPS.GME_COMPLETE_BATCH_STEP_PVT dependencies on GME_RELEASE_BATCH_STEP_PVT

Line 67: gme_release_batch_step_pvt.release_step

63: -- about calling release batch if the batch is pending because release step will take
64: -- care of this; check for step control batch and not a phantom done in pub
65: IF p_batch_step_rec.step_status = gme_common_pvt.g_step_pending THEN
66: -- actual start date already populated in p_batch_step_rec
67: gme_release_batch_step_pvt.release_step
68: (p_batch_step_rec => p_batch_step_rec
69: ,p_batch_header_rec => p_batch_header_rec
70: ,x_batch_step_rec => l_batch_step_rec
71: ,x_exception_material_tbl => x_exception_material_tbl

Line 267: gme_release_batch_step_pvt.process_dependent_steps

263: /* If this procedure is invoked while completing the entire batch */
264: /* then there is no need to go through the recursive procedure as */
265: /* the complete batch call completes all the steps */
266: IF p_batch_header_rec.batch_status <> gme_common_pvt.g_batch_completed THEN
267: gme_release_batch_step_pvt.process_dependent_steps
268: (p_batch_step_rec => p_batch_step_rec
269: ,p_batch_header_rec => p_batch_header_rec
270: ,x_exception_material_tbl => x_exception_material_tbl
271: ,x_return_status => l_return_status);