eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.CN_SEASONALITIES_PVT dependencies on CN_SEAS_SCHEDULES

Line 30: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG

26: -- Version : Current version 1.0
27: --
28: --
29: --
30: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
31: -- to update rows into CN_SEAS_SCHEDULES after some validations.
32: --
33: -- End of comments
34:

Line 31: -- to update rows into CN_SEAS_SCHEDULES after some validations.

27: --
28: --
29: --
30: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
31: -- to update rows into CN_SEAS_SCHEDULES after some validations.
32: --
33: -- End of comments
34:
35: PROCEDURE Update_Seasonalities

Line 50: l_rec cn_seas_schedules_PVT.seas_schedules_rec_type;

46: l_api_version CONSTANT NUMBER := 1.0;
47: l_error_code NUMBER;
48: l_count NUMBER;
49: l_validation_status VARCHAR2(30);
50: l_rec cn_seas_schedules_PVT.seas_schedules_rec_type;
51: l_return_status VARCHAR2(1);
52: l_msg_count NUMBER;
53: l_msg_data VARCHAR2(2000);
54:

Line 79: FROM CN_SEAS_SCHEDULES WHERE SEAS_SCHEDULE_ID = p_seasonalities_rec_type.SEAS_SCHEDULE_ID;

75: -- Fetch the record.
76:
77:
78: SELECT OBJECT_VERSION_NUMBER,NAME,DESCRIPTION INTO l_rec.object_version_number,l_rec.name,l_rec.description
79: FROM CN_SEAS_SCHEDULES WHERE SEAS_SCHEDULE_ID = p_seasonalities_rec_type.SEAS_SCHEDULE_ID;
80:
81: l_rec.seas_schedule_id := p_seasonalities_rec_type.SEAS_SCHEDULE_ID;
82: l_rec.validation_status := l_validation_status;
83:

Line 84: --DBMS_OUTPUT.PUT_LINE('About to call CN_SEAS_SCHEDULES');

80:
81: l_rec.seas_schedule_id := p_seasonalities_rec_type.SEAS_SCHEDULE_ID;
82: l_rec.validation_status := l_validation_status;
83:
84: --DBMS_OUTPUT.PUT_LINE('About to call CN_SEAS_SCHEDULES');
85: cn_seas_schedules_PVT.Update_Seas_Schedule
86: ( p_api_version => 1.0,
87: p_init_msg_list => FND_API.G_FALSE,
88: p_commit => FND_API.G_FALSE,

Line 85: cn_seas_schedules_PVT.Update_Seas_Schedule

81: l_rec.seas_schedule_id := p_seasonalities_rec_type.SEAS_SCHEDULE_ID;
82: l_rec.validation_status := l_validation_status;
83:
84: --DBMS_OUTPUT.PUT_LINE('About to call CN_SEAS_SCHEDULES');
85: cn_seas_schedules_PVT.Update_Seas_Schedule
86: ( p_api_version => 1.0,
87: p_init_msg_list => FND_API.G_FALSE,
88: p_commit => FND_API.G_FALSE,
89: p_validation_level => FND_API.G_VALID_LEVEL_FULL,

Line 95: --DBMS_OUTPUT.PUT_LINE('Call CN_SEAS_SCHEDULES completed validating the output');

91: x_return_status => l_return_status ,
92: x_msg_count => l_msg_count,
93: x_msg_data => l_msg_data
94: );
95: --DBMS_OUTPUT.PUT_LINE('Call CN_SEAS_SCHEDULES completed validating the output');
96: IF l_return_status <> 'S' THEN
97: --DBMS_OUTPUT.PUT_LINE('Updation on CN_SEAS_SCHEDULES Failed');
98: IF FND_MSG_PUB.Check_Msg_Level (FND_MSG_PUB.G_MSG_LVL_ERROR) THEN
99: FND_MESSAGE.SET_NAME ('CN' , 'CN_SEAS_SCH_UPD_FAIL');

Line 97: --DBMS_OUTPUT.PUT_LINE('Updation on CN_SEAS_SCHEDULES Failed');

93: x_msg_data => l_msg_data
94: );
95: --DBMS_OUTPUT.PUT_LINE('Call CN_SEAS_SCHEDULES completed validating the output');
96: IF l_return_status <> 'S' THEN
97: --DBMS_OUTPUT.PUT_LINE('Updation on CN_SEAS_SCHEDULES Failed');
98: IF FND_MSG_PUB.Check_Msg_Level (FND_MSG_PUB.G_MSG_LVL_ERROR) THEN
99: FND_MESSAGE.SET_NAME ('CN' , 'CN_SEAS_SCH_UPD_FAIL');
100: FND_MSG_PUB.Add;
101: END IF;

Line 201: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG

197: -- Version : Current version 1.0
198: --
199: --
200: --
201: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
202: -- to update rows into CN_SEAS_SCHEDULES after some validations.
203: --
204: -- End of comments
205:

Line 202: -- to update rows into CN_SEAS_SCHEDULES after some validations.

198: --
199: --
200: --
201: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
202: -- to update rows into CN_SEAS_SCHEDULES after some validations.
203: --
204: -- End of comments
205:
206: PROCEDURE Validate_Seasonalities

Line 220: l_rec cn_seas_schedules_PVT.seas_schedules_rec_type;

216: l_api_name CONSTANT VARCHAR2(30) := 'Validate_Seasonalities';
217: l_api_version CONSTANT NUMBER := 1.0;
218: l_error_code NUMBER;
219: l_seas_sch_id NUMBER;
220: l_rec cn_seas_schedules_PVT.seas_schedules_rec_type;
221: l_return_status VARCHAR2(1);
222: l_msg_count NUMBER;
223: l_msg_data VARCHAR2(2000);
224: l_sum NUMBER;

Line 263: l_rec.period_year,l_rec.start_date,L_rec.end_date from cn_seas_schedules

259: l_rec.seas_schedule_id := p_seas_schedule_rec_type.SEAS_SCHEDULE_ID;
260: l_rec.validation_status := 'VALID';
261: l_rec.object_version_number := p_seas_schedule_rec_type.object_version_number;
262: SELECT NAME,DESCRIPTION,PERIOD_YEAR,START_DATE,END_DATE INTO l_rec.name,l_rec.description,
263: l_rec.period_year,l_rec.start_date,L_rec.end_date from cn_seas_schedules
264: where seas_schedule_id = p_seas_schedule_rec_type.SEAS_SCHEDULE_ID;
265:
266: cn_seas_schedules_PVT.Update_Seas_Schedule
267: ( p_api_version => 1.0,

Line 266: cn_seas_schedules_PVT.Update_Seas_Schedule

262: SELECT NAME,DESCRIPTION,PERIOD_YEAR,START_DATE,END_DATE INTO l_rec.name,l_rec.description,
263: l_rec.period_year,l_rec.start_date,L_rec.end_date from cn_seas_schedules
264: where seas_schedule_id = p_seas_schedule_rec_type.SEAS_SCHEDULE_ID;
265:
266: cn_seas_schedules_PVT.Update_Seas_Schedule
267: ( p_api_version => 1.0,
268: p_init_msg_list => FND_API.G_FALSE,
269: p_commit => FND_API.G_FALSE,
270: p_validation_level => FND_API.G_VALID_LEVEL_FULL,