[Home] [Help]
669: -- effective date so that the event is created on a correct date
670: -- ----------------------------------------------------------------------------
671: --
672: FUNCTION eval_one_off_cases
673: (p_sub_evt_grp_tbl pay_interpreter_pkg.t_detailed_output_tab_rec
674: ,p_assignment_id NUMBER
675: ,p_comment_text VARCHAR2
676: ,p_effective_date DATE)
677: RETURN DATE IS
1077: (
1078: p_assignment_id IN NUMBER
1079: ,p_start_date IN DATE
1080: ,p_master_events_table
1081: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1082: )
1083: IS
1084: --
1085: -- The following 3 PLSQL tables are required as return placeholders for
1082: )
1083: IS
1084: --
1085: -- The following 3 PLSQL tables are required as return placeholders for
1086: -- the procedure pay_interpreter_pkg.entry_affected. The results from
1087: -- these tables is CURRENTLY IGNORED.
1088: --
1089: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1090: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1085: -- The following 3 PLSQL tables are required as return placeholders for
1086: -- the procedure pay_interpreter_pkg.entry_affected. The results from
1087: -- these tables is CURRENTLY IGNORED.
1088: --
1089: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1090: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1091: l_pro_type_tab pay_interpreter_pkg.t_proration_type_table_type;
1092: --
1093: -- The business group id of the assignent
1086: -- the procedure pay_interpreter_pkg.entry_affected. The results from
1087: -- these tables is CURRENTLY IGNORED.
1088: --
1089: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1090: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1091: l_pro_type_tab pay_interpreter_pkg.t_proration_type_table_type;
1092: --
1093: -- The business group id of the assignent
1094: --
1087: -- these tables is CURRENTLY IGNORED.
1088: --
1089: l_proration_dates pay_interpreter_pkg.t_proration_dates_table_type;
1090: l_proration_changes pay_interpreter_pkg.t_proration_type_table_type;
1091: l_pro_type_tab pay_interpreter_pkg.t_proration_type_table_type;
1092: --
1093: -- The business group id of the assignent
1094: --
1095: l_business_group_id NUMBER;
1099: dbg('Executing interpret_all_asgnmnt_changes ....');
1100: --
1101: -- Get the business group id for the assignment (p_assignment_id)
1102: -- this is not strictly necessary, but improves the performance
1103: -- of pay_interpreter_pkg.entry_affected
1104: --
1105: l_business_group_id := get_business_group_id(p_assignment_id);
1106: --
1107: -- Call the Payroll Events Model (PEM) interpreter to identify all
1116: dbg('l_business_group_id: '||l_business_group_id);
1117: --
1118: IF l_business_group_id is not null THEN
1119: --
1120: pay_interpreter_pkg.entry_affected(
1121: p_element_entry_id => c_ee_id
1122: ,p_assignment_action_id => NULL
1123: ,p_assignment_id => p_assignment_id
1124: ,p_mode => NULL -- pickup events of all types including
1145: -- interpreter version which does not take the business group parameters.
1146: -- Note: This version is inefficient, but we don't want to miss any events
1147: -- which has happened to an assignment
1148: --
1149: pay_interpreter_pkg.entry_affected(
1150: p_element_entry_id => c_ee_id
1151: ,p_assignment_action_id => NULL
1152: ,p_assignment_id => p_assignment_id
1153: ,p_mode => NULL
1509: -- Find the earliest event in the master event group PLSQL table for a given
1510: -- sub event group id.
1511: -- ============================================================================
1512: --
1513: -- This procedure calls pay_interpreter_pkg.get_subset_given_new_evg to
1514: -- process the alreadu identified events in the master event group, to see
1515: -- if any of those events are in the sub event group.
1516: --
1517: -- If any events are found in the sub event group, then the earliest event date
1516: --
1517: -- If any events are found in the sub event group, then the earliest event date
1518: -- found is returned via p_event_date to the calling process.
1519: --
1520: -- The package pay_interpreter_pkg.get_subset_given_new_evg returns a PLSQL
1521: -- table similar to the one passed in, but only containing those rows that
1522: -- are relevant to these event queues. The earliest of the records found in
1523: -- the returned PLSQL table, is then used to update the event queues.
1524: --
1535: ,p_comment_text VARCHAR2 -- Text used by debug comments to indicate
1536: -- which queue's sub eveng group is being
1537: -- processed.
1538: ,p_master_events_table -- The Master Event Group PLSQL table.
1539: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1540: ,p_event_date OUT nocopy DATE -- Event date of the earliest sub event found
1541: -- in the passed in event group and
1542: -- master events table
1543: ,p_sub_evt_grp_tbl OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1539: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1540: ,p_event_date OUT nocopy DATE -- Event date of the earliest sub event found
1541: -- in the passed in event group and
1542: -- master events table
1543: ,p_sub_evt_grp_tbl OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1544: -- This array is only relevant as an
1545: -- output value when p_event_capture_mode
1546: -- is 'S'.
1547: --
1559: --
1560: -- We only care about the earliest change for an assignment. l_min_date is
1561: -- used to store the earliest effective_date date found in the PLSQL table
1562: -- l_sub_evt_grp_tbl returned from the call to
1563: -- pay_interpreter_pkg.get_subset_given_new_evg
1564: --
1565: --
1566: l_min_date DATE;
1567: l_effective_date DATE;
1594: -- Find all the events in the master event group for the assignment that
1595: -- relate to the sub event group for changes relevant to the assignment
1596: -- events fact.
1597: --
1598: dbg('Calling pay_interpreter_pkg.get_subset_given_new_evg ...');
1599: --
1600: pay_interpreter_pkg.get_subset_given_new_evg
1601: (p_filter_event_group_id => p_sub_event_grp_id
1602: ,p_complete_detail_tab => p_master_events_table
1596: -- events fact.
1597: --
1598: dbg('Calling pay_interpreter_pkg.get_subset_given_new_evg ...');
1599: --
1600: pay_interpreter_pkg.get_subset_given_new_evg
1601: (p_filter_event_group_id => p_sub_event_grp_id
1602: ,p_complete_detail_tab => p_master_events_table
1603: ,p_subset_detail_tab => p_sub_evt_grp_tbl
1604: );
1800: ,p_comment_text VARCHAR2 -- Text used by debug comments to indicate
1801: -- which queue's sub eveng group is being
1802: -- processed.
1803: ,p_master_events_table -- The Master Event Group PLSQL table.
1804: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type
1805: ,p_event_date OUT nocopy DATE -- Event date of the earliest sub event found
1806: -- in the passed in event group and
1807: -- master events table
1808: )
1811: -- The following PLSQL table will hold the events found from the master
1812: -- event group that relate to sub event group for the passed in sub event
1813: -- group id (p_sub_event_grp_id). It's return value is ignored
1814: --
1815: l_sub_evt_grp_tbl pay_interpreter_pkg.t_detailed_output_table_type;
1816: --
1817: BEGIN
1818: --
1819: Find_sub_event_group_events
1843: PROCEDURE Process_supervisor_events
1844: (p_assignment_id IN NUMBER
1845: ,p_start_date IN DATE
1846: ,p_master_events_table
1847: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type)
1848: IS
1849: --
1850: -- l_min_date is used to store the earliest effective_date date found
1851: -- by the procedure Find_sub_event_group_events for the sub event group
2045: --
2046: PROCEDURE Update_Absence_Dim_Evnt_Q
2047: (p_assignment_id IN NUMBER
2048: ,p_start_date IN DATE -- The date the events were captured from
2049: ,p_sub_evt_grp_tbl IN pay_interpreter_pkg.t_detailed_output_table_type
2050: -- The events found in the sub event group
2051: -- that need to be processed to identify
2052: -- which absence_attendance_ids have had
2053: -- events.
2198: PROCEDURE Process_assgnmnt_evnt_changes
2199: (p_assignment_id IN NUMBER
2200: ,p_start_date IN DATE
2201: ,p_master_events_table
2202: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type)
2203: IS
2204: --
2205: -- l_min_date is used to store the earliest effective_date date found
2206: -- by the procedure Find_sub_event_group_events for the sub event group
2266: PROCEDURE Process_absence_dim_changes
2267: (p_assignment_id IN NUMBER
2268: ,p_start_date IN DATE
2269: ,p_master_events_table
2270: IN OUT nocopy pay_interpreter_pkg.t_detailed_output_table_type)
2271: IS
2272: --
2273: -- l_min_date is used to store the earliest effective_date date found
2274: -- by the procedure Find_sub_event_group_events for the sub event group
2277: --
2278: -- The following PLSQL table will hold the sub events returned by
2279: -- Find_sub_event_group_events.
2280: --
2281: l_sub_evt_grp_tbl pay_interpreter_pkg.t_detailed_output_table_type;
2282: --
2283: BEGIN
2284: --
2285: dbg('Executing Process_absence_evnt_changes ....');
2351: (p_assignment_id NUMBER
2352: ,p_start_date DATE)
2353: IS
2354: --
2355: l_master_events_table pay_interpreter_pkg.t_detailed_output_table_type;
2356: --
2357: BEGIN
2358: --
2359: interpret_all_asgnmnt_changes(p_assignment_id