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 1020: FROM psp_default_labor_schedules pdls,

1016: IS
1017: SELECT pdls.organization_id,
1018: pmd.period_start_date,
1019: pmd.period_end_date
1020: FROM psp_default_labor_schedules pdls,
1021: psp_matrix_driver pmd
1022: WHERE pdls.org_schedule_id = pmd.schedule_line_id
1023: AND pmd.run_id = F_run_id
1024: GROUP BY pdls.organization_id,

Line 1036: FROM psp_default_labor_schedules pdls,

1032: F_period_end_date DATE,
1033: F_run_id NUMBER)
1034: IS
1035: SELECT pdls.org_schedule_id
1036: FROM psp_default_labor_schedules pdls,
1037: psp_matrix_driver pmd
1038: WHERE pdls.organization_id = F_organization_id
1039: AND pdls.schedule_begin_date <= F_period_end_date
1040: AND pdls.schedule_end_date >= F_period_start_date

Line 1050: psp_default_labor_schedules pdls

1046: IS
1047: SELECT min(pmd1.period_start_date) period_start_date,
1048: pdls.organization_id
1049: FROM psp_matrix_driver pmd1,
1050: psp_default_labor_schedules pdls
1051: WHERE pmd1.run_id = F_run_id
1052: AND pmd1.schedule_line_id = pdls.org_schedule_id
1053: GROUP BY pdls.organization_id;
1054:

Line 1079: FROM psp_default_labor_schedules

1075:
1076: CURSOR c_all_org
1077: IS
1078: SELECT distinct organization_id
1079: FROM psp_default_labor_schedules
1080: WHERE business_group_id = p_business_group_id
1081: AND set_of_books_id = p_set_of_books_id;
1082:
1083:

Line 1135: FROM psp_default_labor_schedules pdls1,

1131: UPDATE psp_matrix_driver pmd
1132: SET period_start_date = period_start_date + 1
1133: WHERE run_id =l_run_id
1134: AND EXISTS (SELECT 1
1135: FROM psp_default_labor_schedules pdls1,
1136: psp_default_labor_schedules pdls2
1137: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1138: AND pdls1.organization_id=pdls2.organization_id
1139: AND pdls1.org_schedule_id<>pdls2.org_schedule_id

Line 1136: psp_default_labor_schedules pdls2

1132: SET period_start_date = period_start_date + 1
1133: WHERE run_id =l_run_id
1134: AND EXISTS (SELECT 1
1135: FROM psp_default_labor_schedules pdls1,
1136: psp_default_labor_schedules pdls2
1137: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1138: AND pdls1.organization_id=pdls2.organization_id
1139: AND pdls1.org_schedule_id<>pdls2.org_schedule_id
1140: AND pdls2.schedule_end_date=pmd.period_start_date);

Line 1146: FROM psp_default_labor_schedules pdls1,

1142: UPDATE psp_matrix_driver pmd
1143: SET period_end_date = period_end_date - 1
1144: WHERE run_id =l_run_id
1145: AND EXISTS (SELECT pmd.period_end_date
1146: FROM psp_default_labor_schedules pdls1,
1147: psp_default_labor_schedules pdls2
1148: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1149: AND pdls2.organization_id=pdls1.organization_id
1150: AND pdls2.schedule_begin_date=pmd.period_end_date

Line 1147: psp_default_labor_schedules pdls2

1143: SET period_end_date = period_end_date - 1
1144: WHERE run_id =l_run_id
1145: AND EXISTS (SELECT pmd.period_end_date
1146: FROM psp_default_labor_schedules pdls1,
1147: psp_default_labor_schedules pdls2
1148: WHERE pdls1.org_schedule_id=pmd.schedule_line_id
1149: AND pdls2.organization_id=pdls1.organization_id
1150: AND pdls2.schedule_begin_date=pmd.period_end_date
1151: AND pdls1.org_schedule_id<>pdls2.org_schedule_id);

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

1211:
1212: Date Created By : 05-SEP-2001
1213:
1214: Purpose : This procedure is introduced to populate psp_matrix_driver with the
1215: data from psp_default_labor_schedules.It sorts the pool of begin and end dates
1216: specified on the various schedule lines. After the sort it inserts the dates into
1217: pl/sql table thereby forming distinct periods of consistent charging instructions.
1218: Once the pl/sql table is loaded, the start and end dates of the distinct periods are
1219: inserted into the temp table.As the cursor parses through each record a correponding

Line 1242: FROM psp_default_labor_schedules

1238: SELECT org_schedule_id l_id,
1239: schedule_begin_date sbd,
1240: schedule_end_date sed,
1241: schedule_percent sp
1242: FROM psp_default_labor_schedules
1243: WHERE organization_id = s_id
1244: AND business_group_id = p_business_group_id
1245: AND set_of_books_id = p_set_of_books_id;
1246:

Line 1251: FROM psp_default_labor_schedules

1247: --Get the dates (schedule begin dates and end dates) in ascending order of dates. If a date is present in
1248: --begin as well as the end date, bring the End Date first.
1249: CURSOR dates(s_id NUMBER) IS
1250: SELECT schedule_begin_date dat , 'B'
1251: FROM psp_default_labor_schedules
1252: WHERE organization_id = s_id
1253: AND business_group_id = p_business_group_id
1254: AND set_of_books_id = p_set_of_books_id
1255: UNION

Line 1257: FROM psp_default_labor_schedules

1253: AND business_group_id = p_business_group_id
1254: AND set_of_books_id = p_set_of_books_id
1255: UNION
1256: SELECT schedule_end_date dat , 'E'
1257: FROM psp_default_labor_schedules
1258: WHERE organization_id = s_id
1259: AND business_group_id = p_business_group_id
1260: AND set_of_books_id = p_set_of_books_id
1261: ORDER BY 1, 2 ;