The following lines contain the word 'select', 'insert', 'update' or 'delete':
selected at Business Group level
reflects in Simulation output
instantaneously instead of waiting
for the cache to be cleared which is
not happening over a long period of
time or services are not bounced.
18-MAR-2013 emunisek 120.3 16408289 Added new get_context_refresh to
control the refresh of regions based
on changes to Flexfield segments.
*/
gv_package VARCHAR2(100) := 'pay_us_simulation';
SELECT paf.organization_id
FROM per_all_assignments_f paf
WHERE paf.assignment_id = cp_assignment_id
AND cp_effective_date BETWEEN paf.effective_start_date
AND paf.effective_end_date;
SELECT org.name,loc.telephone_number_1
FROM hr_all_organization_units org,
hr_locations_all loc
WHERE org.location_id=loc.location_id
AND org.organization_id = cp_organization_id;
/* Procedure : update_asg_data
Purpose : This procedure is to propagate the changes made on the
Payroll Simulator to the Assignment specific Data. This
does not include the changes to Element entries as those
changes are handled by Core Payroll Team. Only Assignment
specific changes like Address, Work Location, Tax Data etc
are propagated by this procedure.
Important : This procedure is initiated by Core Payroll Code after the
creation of Database Level Savepoint. Once the Payroll
Simulator Run is complete, the entire session will be
rolled back to the initial Savepoint. Hence the changes
made on the Payroll Simulator page will be propagated to
the actual live data through this procedure.
*/
PROCEDURE update_asg_data(p_source_action_id NUMBER,
p_effective_date DATE DEFAULT NULL)
IS
lv_procedure_name VARCHAR2(100) := '.update_asg_data';
pay_us_payslip_simulation_main.update_asg_data(
p_source_action_id => p_source_action_id,
p_effective_date => p_effective_date);
END update_asg_data;
procedure is inserted into PAY_SIMULATION_INFORMATION
table autonomously so that the data can be used to
generate the Output, post Database level rollback. Any
information required for generating Output, that will not
be available due to rollback should be captured through
archive_data procedure
*/
PROCEDURE archive_data(p_source_action_id NUMBER,
p_effective_date DATE DEFAULT NULL)
IS
lv_procedure_name VARCHAR2(100) := '.archive_data';
Important : It is necessary to update this procedure when ever we need
value selected in Flexfield Segment to be set as Profile
Option. Using the Profile Option, we can access the value
chosen in one Flexfield context in other context.
*/
PROCEDURE get_profile(p_flex_context_code IN VARCHAR2,
p_profile_tab IN OUT NOCOPY PAY_SIMULATION_PROFILE_TAB)
IS
lv_procedure_name VARCHAR2(100) := '.get_profile';
be updated accordingly.
*/
FUNCTION is_entries_affected(p_flex_context_code VARCHAR2,
p_segment_name VARCHAR2)
RETURN VARCHAR2
IS
lv_procedure_name VARCHAR2(100) := '.is_entries_affected';
SELECT run_type_id
FROM pay_run_types_f prt
WHERE prt.legislation_code = 'US'
AND RUN_METHOD = 'C'
AND RUN_TYPE_NAME = 'Regular';