[Home] [Help]
666: -- effective date so that the event is created on a correct date
667: -- ----------------------------------------------------------------------------
668: --
669: FUNCTION eval_one_off_cases
670: (p_sub_evt_grp_tbl pay_interpreter_pkg.t_detailed_output_tab_rec
671: ,p_assignment_id NUMBER
672: ,p_comment_text VARCHAR2
673: ,p_effective_date DATE)
674: RETURN DATE IS
1074: (
1075: p_assignment_id IN NUMBER
1076: ,p_start_date IN DATE
1077: ,p_master_events_table
1078: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1079: )
1080: IS
1081: --
1082: -- The following 3 PLSQL tables are required as return placeholders for
1079: )
1080: IS
1081: --
1082: -- The following 3 PLSQL tables are required as return placeholders for
1083: -- the procedure pay_interpreter_pkg.entry_affected. The results from
1084: -- these tables is CURRENTLY IGNORED.
1085: --
1086: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1087: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1082: -- The following 3 PLSQL tables are required as return placeholders for
1083: -- the procedure pay_interpreter_pkg.entry_affected. The results from
1084: -- these tables is CURRENTLY IGNORED.
1085: --
1086: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1087: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1088: l_pro_type_tab pay_interpreter_pkg.t_proration_type_table_type;
1089: --
1090: -- The business group id of the assignent
1083: -- the procedure pay_interpreter_pkg.entry_affected. The results from
1084: -- these tables is CURRENTLY IGNORED.
1085: --
1086: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1087: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1088: l_pro_type_tab pay_interpreter_pkg.t_proration_type_table_type;
1089: --
1090: -- The business group id of the assignent
1091: --
1084: -- these tables is CURRENTLY IGNORED.
1085: --
1086: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1087: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1088: l_pro_type_tab pay_interpreter_pkg.t_proration_type_table_type;
1089: --
1090: -- The business group id of the assignent
1091: --
1092: l_business_group_id NUMBER;
1096: dbg('Executing interpret_all_asgnmnt_changes ....');
1097: --
1098: -- Get the business group id for the assignment (p_assignment_id)
1099: -- this is not strictly necessary, but improves the performance
1100: -- of pay_interpreter_pkg.entry_affected
1101: --
1102: l_business_group_id := get_business_group_id(p_assignment_id);
1103: --
1104: -- Call the Payroll Events Model (PEM) interpreter to identify all
1113: dbg('l_business_group_id: '||l_business_group_id);
1114: --
1115: IF l_business_group_id is not null THEN
1116: --
1117: pay_interpreter_pkg.entry_affected(
1118: p_element_entry_id => c_ee_id
1119: ,p_assignment_action_id => NULL
1120: ,p_assignment_id => p_assignment_id
1121: ,p_mode => NULL -- pickup events of all types including
1142: -- interpreter version which does not take the business group parameters.
1143: -- Note: This version is inefficient, but we don't want to miss any events
1144: -- which has happened to an assignment
1145: --
1146: pay_interpreter_pkg.entry_affected(
1147: p_element_entry_id => c_ee_id
1148: ,p_assignment_action_id => NULL
1149: ,p_assignment_id => p_assignment_id
1150: ,p_mode => NULL
1506: -- Find the earliest event in the master event group PLSQL table for a given
1507: -- sub event group id.
1508: -- ============================================================================
1509: --
1510: -- This procedure calls pay_interpreter_pkg.get_subset_given_new_evg to
1511: -- process the alreadu identified events in the master event group, to see
1512: -- if any of those events are in the sub event group.
1513: --
1514: -- If any events are found in the sub event group, then the earliest event date
1513: --
1514: -- If any events are found in the sub event group, then the earliest event date
1515: -- found is returned via p_event_date to the calling process.
1516: --
1517: -- The package pay_interpreter_pkg.get_subset_given_new_evg returns a PLSQL
1518: -- table similar to the one passed in, but only containing those rows that
1519: -- are relevant to these event queues. The earliest of the records found in
1520: -- the returned PLSQL table, is then used to update the event queues.
1521: --
1532: ,p_comment_text VARCHAR2 -- Text used by debug comments to indicate
1533: -- which queue's sub eveng group is being
1534: -- processed.
1535: ,p_master_events_table -- The Master Event Group PLSQL table.
1536: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1537: ,p_event_date OUT nocopy DATE -- Event date of the earliest sub event found
1538: -- in the passed in event group and
1539: -- master events table
1540: ,p_sub_evt_grp_tbl OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1536: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1537: ,p_event_date OUT nocopy DATE -- Event date of the earliest sub event found
1538: -- in the passed in event group and
1539: -- master events table
1540: ,p_sub_evt_grp_tbl OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1541: -- This array is only relevant as an
1542: -- output value when p_event_capture_mode
1543: -- is 'S'.
1544: --
1556: --
1557: -- We only care about the earliest change for an assignment. l_min_date is
1558: -- used to store the earliest effective_date date found in the PLSQL table
1559: -- l_sub_evt_grp_tbl returned from the call to
1560: -- pay_interpreter_pkg.get_subset_given_new_evg
1561: --
1562: --
1563: l_min_date DATE;
1564: l_effective_date DATE;
1591: -- Find all the events in the master event group for the assignment that
1592: -- relate to the sub event group for changes relevant to the assignment
1593: -- events fact.
1594: --
1595: dbg('Calling pay_interpreter_pkg.get_subset_given_new_evg ...');
1596: --
1597: pay_interpreter_pkg.get_subset_given_new_evg
1598: (p_filter_event_group_id => p_sub_event_grp_id
1599: ,p_complete_detail_tab => p_master_events_table
1593: -- events fact.
1594: --
1595: dbg('Calling pay_interpreter_pkg.get_subset_given_new_evg ...');
1596: --
1597: pay_interpreter_pkg.get_subset_given_new_evg
1598: (p_filter_event_group_id => p_sub_event_grp_id
1599: ,p_complete_detail_tab => p_master_events_table
1600: ,p_subset_detail_tab => p_sub_evt_grp_tbl
1601: );
1797: ,p_comment_text VARCHAR2 -- Text used by debug comments to indicate
1798: -- which queue's sub eveng group is being
1799: -- processed.
1800: ,p_master_events_table -- The Master Event Group PLSQL table.
1801: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1802: ,p_event_date OUT nocopy DATE -- Event date of the earliest sub event found
1803: -- in the passed in event group and
1804: -- master events table
1805: )
1808: -- The following PLSQL table will hold the events found from the master
1809: -- event group that relate to sub event group for the passed in sub event
1810: -- group id (p_sub_event_grp_id). It's return value is ignored
1811: --
1812: l_sub_evt_grp_tbl pay_interpreter_pkg.t_detailed_output_table_type;
1813: --
1814: BEGIN
1815: --
1816: Find_sub_event_group_events
1840: PROCEDURE Process_supervisor_events
1841: (p_assignment_id IN NUMBER
1842: ,p_start_date IN DATE
1843: ,p_master_events_table
1844: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type)
1845: IS
1846: --
1847: -- l_min_date is used to store the earliest effective_date date found
1848: -- by the procedure Find_sub_event_group_events for the sub event group
2042: --
2043: PROCEDURE Update_Absence_Dim_Evnt_Q
2044: (p_assignment_id IN NUMBER
2045: ,p_start_date IN DATE -- The date the events were captured from
2046: ,p_sub_evt_grp_tbl IN pay_interpreter_pkg.t_detailed_output_table_type
2047: -- The events found in the sub event group
2048: -- that need to be processed to identify
2049: -- which absence_attendance_ids have had
2050: -- events.
2195: PROCEDURE Process_assgnmnt_evnt_changes
2196: (p_assignment_id IN NUMBER
2197: ,p_start_date IN DATE
2198: ,p_master_events_table
2199: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type)
2200: IS
2201: --
2202: -- l_min_date is used to store the earliest effective_date date found
2203: -- by the procedure Find_sub_event_group_events for the sub event group
2263: PROCEDURE Process_absence_dim_changes
2264: (p_assignment_id IN NUMBER
2265: ,p_start_date IN DATE
2266: ,p_master_events_table
2267: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type)
2268: IS
2269: --
2270: -- l_min_date is used to store the earliest effective_date date found
2271: -- by the procedure Find_sub_event_group_events for the sub event group
2274: --
2275: -- The following PLSQL table will hold the sub events returned by
2276: -- Find_sub_event_group_events.
2277: --
2278: l_sub_evt_grp_tbl pay_interpreter_pkg.t_detailed_output_table_type;
2279: --
2280: BEGIN
2281: --
2282: dbg('Executing Process_absence_evnt_changes ....');
2348: (p_assignment_id NUMBER
2349: ,p_start_date DATE)
2350: IS
2351: --
2352: l_master_events_table pay_interpreter_pkg.t_detailed_output_table_type;
2353: --
2354: BEGIN
2355: --
2356: interpret_all_asgnmnt_changes(p_assignment_id