APPS.PA_SCHEDULE_PUB dependencies on PA_DEBUG

Line 87: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.update_schedule');

83: --Clear the global PL/SQL message table
84: FND_MSG_PUB.initialize;
85:
86: -- Initialize the Error Stack
87: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.update_schedule');
88:
89: -- Issue API savepoint if the transaction is to be committed
90: IF (p_commit = FND_API.G_TRUE) THEN
91: SAVEPOINT SCH_PUB_UPDATE_SCH;

Line 501: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.update_schedule');

497: --Clear the global PL/SQL message table
498: FND_MSG_PUB.initialize;
499:
500: -- Initialize the Error Stack
501: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.update_schedule');
502:
503: -- Issue API savepoint if the transaction is to be committed
504: IF (l_commit_tbl(k) = FND_API.G_TRUE) THEN
505: SAVEPOINT SCH_PUB_UPDATE_SCH;

Line 733: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.update_schedule');

729: --Clear the global PL/SQL message table
730: FND_MSG_PUB.initialize;
731:
732: -- Initialize the Error Stack
733: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.update_schedule');
734:
735: -- Issue API savepoint if the transaction is to be committed
736: IF (l_commit_tbl(k) = FND_API.G_TRUE) THEN
737: SAVEPOINT SCH_PUB_UPDATE_SCH;

Line 940: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.single_update_schedule');

936: -- Initialize the return status to success
937: x_return_status := FND_API.G_RET_STS_SUCCESS ;
938:
939: -- Initialize the Error Stack
940: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.single_update_schedule');
941:
942: -- Issue API savepoint if the transaction is to be committed
943: IF p_commit = FND_API.G_TRUE THEN
944: SAVEPOINT SCH_PUB_SINGLE_UPDATE_SCH;

Line 1174: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.mass_update_schedule');

1170: FND_MSG_PUB.initialize;
1171: END IF;
1172:
1173: -- Initialize the Error Stack
1174: PA_DEBUG.init_err_stack('PA_SCHEDULE_PUB.mass_update_schedule');
1175:
1176:
1177: ----------------------------------------------------------------------------------------------
1178: --

Line 3749: fnd_profile.get('PA_DEBUG_MODE',l_debug_mode);

3745: -- Storing the status for error handling
3746: l_x_return_status := FND_API.G_RET_STS_SUCCESS;
3747:
3748: -- 2843435
3749: fnd_profile.get('PA_DEBUG_MODE',l_debug_mode);
3750:
3751: -- 4370082
3752: IF l_debug_mode = 'Y' THEN
3753: pa_debug.set_process('PLSQL','LOG',l_debug_mode);

Line 3753: pa_debug.set_process('PLSQL','LOG',l_debug_mode);

3749: fnd_profile.get('PA_DEBUG_MODE',l_debug_mode);
3750:
3751: -- 4370082
3752: IF l_debug_mode = 'Y' THEN
3753: pa_debug.set_process('PLSQL','LOG',l_debug_mode);
3754: END IF;
3755:
3756: -- End of 2843435
3757:

Line 3825: pa_debug.write_file('CREATE_NEW_CAL_SCHEDULES: '||'LOG', 'msg_count = '||FND_MSG_PUB.Count_Msg);

3821: -- to the report file. Therefore, we have to raise expected errors.
3822: IF l_x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
3823:
3824: IF l_debug_mode = 'Y' THEN
3825: pa_debug.write_file('CREATE_NEW_CAL_SCHEDULES: '||'LOG', 'msg_count = '||FND_MSG_PUB.Count_Msg);
3826: END IF;
3827:
3828: FOR l_counter IN 1..FND_MSG_PUB.Count_Msg LOOP
3829: pa_interface_utils_pub.get_messages ( p_encoded => FND_API.G_FALSE

Line 3834: pa_debug.write_file('CREATE_NEW_CAL_SCHEDULES: '||'LOG', x_msg_data);

3830: ,p_msg_index => l_counter
3831: ,p_data => x_msg_data
3832: ,p_msg_index_out => l_msg_index_out);
3833: IF l_debug_mode = 'Y' THEN
3834: pa_debug.write_file('CREATE_NEW_CAL_SCHEDULES: '||'LOG', x_msg_data);
3835: END IF;
3836: END LOOP;
3837:
3838: RAISE l_exception;