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.PSP_MATRIX_DRIVER_PKG dependencies on PSP_DEFAULT_LABOR_SCHEDULES

Line 986: FROM psp_default_labor_schedules pdls,

982: IS
983: SELECT pdls.organization_id,
984: pmd.period_start_date,
985: pmd.period_end_date
986: FROM psp_default_labor_schedules pdls,
987: psp_matrix_driver pmd
988: WHERE pdls.org_schedule_id = pmd.schedule_line_id
989: AND pmd.run_id = F_run_id
990: GROUP BY pdls.organization_id,

Line 1002: FROM psp_default_labor_schedules pdls,

998: F_period_end_date DATE,
999: F_run_id NUMBER)
1000: IS
1001: SELECT pdls.org_schedule_id
1002: FROM psp_default_labor_schedules pdls,
1003: psp_matrix_driver pmd
1004: WHERE pdls.organization_id = F_organization_id
1005: AND pdls.schedule_begin_date <= F_period_end_date
1006: AND pdls.schedule_end_date >= F_period_start_date

Line 1016: psp_default_labor_schedules pdls

1012: IS
1013: SELECT min(pmd1.period_start_date) period_start_date,
1014: pdls.organization_id
1015: FROM psp_matrix_driver pmd1,
1016: psp_default_labor_schedules pdls
1017: WHERE pmd1.run_id = F_run_id
1018: AND pmd1.schedule_line_id = pdls.org_schedule_id
1019: GROUP BY pdls.organization_id;
1020:

Line 1045: FROM psp_default_labor_schedules

1041:
1042: CURSOR c_all_org
1043: IS
1044: SELECT distinct organization_id
1045: FROM psp_default_labor_schedules
1046: WHERE business_group_id = p_business_group_id
1047: AND set_of_books_id = p_set_of_books_id;
1048:
1049:

Line 1101: FROM psp_default_labor_schedules pdls1,

1097: UPDATE psp_matrix_driver pmd
1098: SET period_start_date = period_start_date + 1
1099: WHERE run_id =l_run_id
1100: AND EXISTS (SELECT 1
1101: FROM psp_default_labor_schedules pdls1,
1102: psp_default_labor_schedules pdls2
1103: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1104: AND pdls1.organization_id=pdls2.organization_id
1105: AND pdls1.org_schedule_id<>pdls2.org_schedule_id

Line 1102: psp_default_labor_schedules pdls2

1098: SET period_start_date = period_start_date + 1
1099: WHERE run_id =l_run_id
1100: AND EXISTS (SELECT 1
1101: FROM psp_default_labor_schedules pdls1,
1102: psp_default_labor_schedules pdls2
1103: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1104: AND pdls1.organization_id=pdls2.organization_id
1105: AND pdls1.org_schedule_id<>pdls2.org_schedule_id
1106: AND pdls2.schedule_end_date=pmd.period_start_date);

Line 1112: FROM psp_default_labor_schedules pdls1,

1108: UPDATE psp_matrix_driver pmd
1109: SET period_end_date = period_end_date - 1
1110: WHERE run_id =l_run_id
1111: AND EXISTS (SELECT pmd.period_end_date
1112: FROM psp_default_labor_schedules pdls1,
1113: psp_default_labor_schedules pdls2
1114: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1115: AND pdls2.organization_id=pdls1.organization_id
1116: AND pdls2.schedule_begin_date=pmd.period_end_date

Line 1113: psp_default_labor_schedules pdls2

1109: SET period_end_date = period_end_date - 1
1110: WHERE run_id =l_run_id
1111: AND EXISTS (SELECT pmd.period_end_date
1112: FROM psp_default_labor_schedules pdls1,
1113: psp_default_labor_schedules pdls2
1114: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1115: AND pdls2.organization_id=pdls1.organization_id
1116: AND pdls2.schedule_begin_date=pmd.period_end_date
1117: AND pdls1.org_schedule_id<>pdls2.org_schedule_id);

Line 1181: data from psp_default_labor_schedules.It sorts the pool of begin and end dates

1177:
1178: Date Created By : 05-SEP-2001
1179:
1180: Purpose : This procedure is introduced to populate psp_matrix_driver with the
1181: data from psp_default_labor_schedules.It sorts the pool of begin and end dates
1182: specified on the various schedule lines. After the sort it inserts the dates into
1183: pl/sql table thereby forming distinct periods of consistent charging instructions.
1184: Once the pl/sql table is loaded, the start and end dates of the distinct periods are
1185: inserted into the temp table.As the cursor parses through each record a correponding

Line 1208: FROM psp_default_labor_schedules

1204: SELECT org_schedule_id l_id,
1205: schedule_begin_date sbd,
1206: schedule_end_date sed,
1207: schedule_percent sp
1208: FROM psp_default_labor_schedules
1209: WHERE organization_id = s_id
1210: AND business_group_id = p_business_group_id
1211: AND set_of_books_id = p_set_of_books_id;
1212:

Line 1217: FROM psp_default_labor_schedules

1213: --Get the dates (schedule begin dates and end dates) in ascending order of dates. If a date is present in
1214: --begin as well as the end date, bring the End Date first.
1215: CURSOR dates(s_id NUMBER) IS
1216: SELECT schedule_begin_date dat , 'B'
1217: FROM psp_default_labor_schedules
1218: WHERE organization_id = s_id
1219: AND business_group_id = p_business_group_id
1220: AND set_of_books_id = p_set_of_books_id
1221: UNION

Line 1223: FROM psp_default_labor_schedules

1219: AND business_group_id = p_business_group_id
1220: AND set_of_books_id = p_set_of_books_id
1221: UNION
1222: SELECT schedule_end_date dat , 'E'
1223: FROM psp_default_labor_schedules
1224: WHERE organization_id = s_id
1225: AND business_group_id = p_business_group_id
1226: AND set_of_books_id = p_set_of_books_id
1227: ORDER BY 1, 2 ;