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_SEAS_SCHEDULES_PVT dependencies on CN_SEASONALITIES

Line 31: -- and CN_SEASONALITIES_PKG to insert rows into CN_SEAS_SCHEDULES

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

Line 32: -- and CN_SEASONALITIES after some validations.

28: --
29: --
30: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
31: -- and CN_SEASONALITIES_PKG to insert rows into CN_SEAS_SCHEDULES
32: -- and CN_SEASONALITIES after some validations.
33: --
34: -- End of comments
35:
36:

Line 57: CURSOR cn_seasonalities_cur(p_period_year NUMBER) IS

53: l_end_date DATE;
54: l_seas_schedule_id NUMBER;
55: l_cal_int_types NUMBER;
56:
57: CURSOR cn_seasonalities_cur(p_period_year NUMBER) IS
58: SELECT cp.period_id,cp.period_name,ccpit.interval_number,ccpit.cal_per_int_type_id
59: FROM cn_period_statuses cp,cn_cal_per_int_types ccpit
60: WHERE period_year = p_period_year and cp.period_id = ccpit.cal_period_id and interval_type_id = -1002;
61:

Line 142: -- rows into CN_SEASONALITIES.

138: P_VALIDATION_STATUS => 'INVALID'
139: );
140:
141: -- Select SEAS_SCHEDULE_ID just created to use it for insertion of
142: -- rows into CN_SEASONALITIES.
143:
144: SELECT SEAS_SCHEDULE_ID INTO l_seas_schedule_id
145: FROM CN_SEAS_SCHEDULES WHERE NAME like p_seas_schedules_rec_type.name;
146:

Line 165: -- to insert rows into the CN_SEASONALITIES.

161: END IF;
162:
163:
164: -- Create a CURSOR OF VALUES FOR the Period and use table handler
165: -- to insert rows into the CN_SEASONALITIES.
166: FOR l_seas_sch IN cn_seasonalities_cur(p_seas_schedules_rec_type.period_year) LOOP
167: --DBMS_OUTPUT.PUT_LINE('In the Loop');
168: CN_SEASONALITIES_pkg.insert_row(
169: P_SEASONALITY_ID => -99,

Line 166: FOR l_seas_sch IN cn_seasonalities_cur(p_seas_schedules_rec_type.period_year) LOOP

162:
163:
164: -- Create a CURSOR OF VALUES FOR the Period and use table handler
165: -- to insert rows into the CN_SEASONALITIES.
166: FOR l_seas_sch IN cn_seasonalities_cur(p_seas_schedules_rec_type.period_year) LOOP
167: --DBMS_OUTPUT.PUT_LINE('In the Loop');
168: CN_SEASONALITIES_pkg.insert_row(
169: P_SEASONALITY_ID => -99,
170: P_SEAS_SCHEDULE_ID => l_seas_schedule_id,

Line 168: CN_SEASONALITIES_pkg.insert_row(

164: -- Create a CURSOR OF VALUES FOR the Period and use table handler
165: -- to insert rows into the CN_SEASONALITIES.
166: FOR l_seas_sch IN cn_seasonalities_cur(p_seas_schedules_rec_type.period_year) LOOP
167: --DBMS_OUTPUT.PUT_LINE('In the Loop');
168: CN_SEASONALITIES_pkg.insert_row(
169: P_SEASONALITY_ID => -99,
170: P_SEAS_SCHEDULE_ID => l_seas_schedule_id,
171: P_CAL_PER_INT_TYPE_ID => l_seas_sch.CAL_PER_INT_TYPE_ID,
172: P_PERIOD_ID => l_seas_sch.PERIOD_ID,

Line 177: --DBMS_OUTPUT.PUT_LINE('Created rows successfully in CN_SEASONALITIES');

173: P_PCT_SEASONALITY => 0.0
174: );
175: END LOOP;
176:
177: --DBMS_OUTPUT.PUT_LINE('Created rows successfully in CN_SEASONALITIES');
178: -- End of API body.
179: << end_Create_Seas_Schedule >>
180: NULL;
181:

Line 475: -- and CN_SEASONALITIES_PKG to delete rows into CN_SEAS_SCHEDULES

471: --
472: --
473: --
474: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
475: -- and CN_SEASONALITIES_PKG to delete rows into CN_SEAS_SCHEDULES
476: -- and CN_SEASONALITIES after the validations are done.
477: --
478: -- End of comments
479:

Line 476: -- and CN_SEASONALITIES after the validations are done.

472: --
473: --
474: -- Notes : This procedure uses the table handler CN_SEAS_SCHEDULES_PKG
475: -- and CN_SEASONALITIES_PKG to delete rows into CN_SEAS_SCHEDULES
476: -- and CN_SEASONALITIES after the validations are done.
477: --
478: -- End of comments
479:
480: PROCEDURE Delete_Seas_Schedule

Line 519: -- from CN_SEAS_SCHEDULES and CN_SEASONALITIES.

515: -- ********************
516: -- VALIDATION
517: -- ********************
518: -- Validations to be checked before we decide to delete the entries
519: -- from CN_SEAS_SCHEDULES and CN_SEASONALITIES.
520: SELECT COUNT(role_id) INTO l_role_quota_cate_count FROM CN_ROLE_QUOTA_CATES WHERE seas_schedule_id = P_SEAS_SCHEDULE_ID;
521:
522: IF (l_role_quota_cate_count > 0) THEN
523: IF FND_MSG_PUB.Check_Msg_Level (FND_MSG_PUB.G_MSG_LVL_ERROR) THEN

Line 533: -- Delete entries from CN_SEASONALITIES.

529:
530: -- Delete entries from CN_SEAS_SCHEDULES
531: CN_SEAS_SCHEDULES_pkg.delete_row (P_SEAS_SCHEDULE_ID => l_seas_sch_id);
532:
533: -- Delete entries from CN_SEASONALITIES.
534: CN_SEASONALITIES_pkg.delete_row (P_SEAS_SCHEDULE_ID => l_seas_sch_id);
535:
536: -- End of API body.
537: << end_Delete_Seas_Schedule >>

Line 534: CN_SEASONALITIES_pkg.delete_row (P_SEAS_SCHEDULE_ID => l_seas_sch_id);

530: -- Delete entries from CN_SEAS_SCHEDULES
531: CN_SEAS_SCHEDULES_pkg.delete_row (P_SEAS_SCHEDULE_ID => l_seas_sch_id);
532:
533: -- Delete entries from CN_SEASONALITIES.
534: CN_SEASONALITIES_pkg.delete_row (P_SEAS_SCHEDULE_ID => l_seas_sch_id);
535:
536: -- End of API body.
537: << end_Delete_Seas_Schedule >>
538: NULL;

Line 661: from cn_seasonalities

657: x_return_status := FND_API.G_RET_STS_SUCCESS;
658:
659: -- API body
660: select seas_schedule_id,sum(pct_seasonality) into l_seas_schedule_id,l_pct_seasonality
661: from cn_seasonalities
662: where seas_schedule_id = p_seas_schedules_id group by seas_schedule_id;
663:
664: x_seas_schedule_sum := l_pct_seasonality;
665: