DBA Data[Home] [Help]

APPS.PAY_US_PAYSLIP_SIMULATION_MAIN dependencies on PAY_SIMULATION_INFORMATION

Line 45: retrieve the information from PAY_SIMULATION_INFORMATION table*/

41: gv_ptd_balance_dimension VARCHAR2(80) := '_ASG_GRE_PTD';
42: gv_run_balance_dimension VARCHAR2(80) := '_ASG_GRE_RUN';
43:
44: /*Below cursors are used by PAY_PAYROLL_XML_EXTRACT_PKG Package to
45: retrieve the information from PAY_SIMULATION_INFORMATION table*/
46:
47: /* Action Context Type "ACTION INFO" is used in the Payroll Simulator
48: Code to designate the records that hold the information related to
49: Payroll and Assignment Actions */

Line 54: FROM pay_simulation_information psi

50:
51: CURSOR get_leg_code(cp_action_context_id NUMBER)
52: IS
53: SELECT psi.action_information4
54: FROM pay_simulation_information psi
55: WHERE psi.action_information2 = TO_CHAR(cp_action_context_id)
56: AND psi.action_context_type = 'ACTION INFO'
57: AND psi.action_information_category = 'SIMULATION_ACTION_INFORMATION';
58:

Line 62: FROM pay_simulation_information psi

58:
59: CURSOR c_bgid (cp_assgn_action_id NUMBER)
60: IS
61: SELECT psi.action_information3
62: FROM pay_simulation_information psi
63: WHERE psi.action_information2 = TO_CHAR(cp_assgn_action_id)
64: AND psi.action_context_type = 'ACTION INFO'
65: AND psi.action_information_category = 'SIMULATION_ACTION_INFORMATION';
66:

Line 71: FROM pay_simulation_information

67: CURSOR csr_get_archived_regions(cp_action_context_id NUMBER,
68: cp_action_information_id NUMBER)
69: IS
70: SELECT DISTINCT action_information_category
71: FROM pay_simulation_information
72: WHERE ((action_context_type = 'AAP'
73: AND action_context_id = cp_action_context_id)
74: OR (action_context_type = 'PA'
75: AND action_context_id =

Line 77: FROM pay_simulation_information

73: AND action_context_id = cp_action_context_id)
74: OR (action_context_type = 'PA'
75: AND action_context_id =
76: (SELECT action_context_id
77: FROM pay_simulation_information
78: WHERE action_information2 = TO_CHAR(cp_action_context_id)
79: AND action_context_type = 'ACTION INFO')))
80: OR (action_information_id = cp_action_information_id
81: AND cp_action_information_id IS NOT NULL)

Line 120: FROM pay_simulation_information

116: action_information27,
117: action_information28,
118: action_information29,
119: action_information30
120: FROM pay_simulation_information
121: WHERE ((action_context_id = p_action_context_id AND action_context_type = 'AAP') OR
122: (action_context_id = (SELECT action_context_id
123: FROM pay_simulation_information
124: WHERE action_information2 = TO_CHAR(p_action_context_id)

Line 123: FROM pay_simulation_information

119: action_information30
120: FROM pay_simulation_information
121: WHERE ((action_context_id = p_action_context_id AND action_context_type = 'AAP') OR
122: (action_context_id = (SELECT action_context_id
123: FROM pay_simulation_information
124: WHERE action_information2 = TO_CHAR(p_action_context_id)
125: AND action_context_type = 'ACTION INFO')
126: AND action_context_type = 'PA'
127: AND ((action_information1 = p_category_filter AND

Line 141: FROM pay_simulation_information psi

137: psi.tax_unit_id,
138: psi.effective_date,
139: psi.action_information1 payroll_action_id,
140: psi.assignment_id
141: FROM pay_simulation_information psi
142: WHERE psi.action_information2 = TO_CHAR(cp_assignment_action_id)
143: AND psi.action_information1 = TO_CHAR(psi.action_context_id)
144: AND psi.action_context_type = 'ACTION INFO'
145: AND psi.action_information_category = 'SIMULATION_ACTION_INFORMATION' ;

Line 156: FROM pay_simulation_information psi

152: action_information8,
153: action_information10,
154: action_information12,
155: action_information13
156: FROM pay_simulation_information psi
157: WHERE psi.action_context_type = 'PA'
158: AND psi.action_information_category = 'ADDRESS DETAILS'
159: AND psi.action_information14 = 'Employer Address'
160: AND psi.action_context_id=cp_payroll_action_id

Line 173: FROM pay_simulation_information psi

169: CURSOR get_net_pay (cp_assignment_action_id NUMBER,
170: cp_dimension VARCHAR2)
171: IS
172: SELECT psi.action_information15
173: FROM pay_simulation_information psi
174: WHERE psi.action_context_id = cp_assignment_action_id
175: AND psi.action_context_type = 'AAP'
176: AND psi.action_information_category = 'AC SUMMARY '||cp_dimension;
177:

Line 197: Run to the table PAY_SIMULATION_INFORMATION. This

193: p_effective_date DATE DEFAULT NULL);
194:
195: /* Procedure : archive_data
196: Purpose : This procedure captures the results of Payroll Simulator
197: Run to the table PAY_SIMULATION_INFORMATION. This
198: procedure is similar to the Payroll Archiver procedure
199: PAY_US_ACTION_ARCH.ACTION_ARCHIVE_DATA. The regular
200: Payroll Archiver procedure is based on Prepayments where
201: as the current procedure is based on actual Payroll Run

Line 207: procedure is inserted into PAY_SIMULATION_INFORMATION

203: Important : The Data archival process is similar to the regular
204: Payroll Archiver except the Payment related data will be
205: skipped here as there are no Prepayments executed as part
206: of Payroll Simulation. All the data gathered during this
207: procedure is inserted into PAY_SIMULATION_INFORMATION
208: table autonomously so that the data can be used to
209: generate the Output, post Database level rollback. Any
210: information required for generating Output, that will not
211: be available due to rollback should be captured through

Line 246: and saved autonomously to PAY_SIMULATION_INFORMATION table

242: Database level rollback of changes made during Payroll
243: Simulation run. Hence any information required for
244: generating Output, that will not be available due to
245: rollback should be captured through archive_data procedure
246: and saved autonomously to PAY_SIMULATION_INFORMATION table
247: Parameter p_xml_code is to allow the Customers the ability
248: to use Custom XML Code. This is hidden from Customers as
249: of now and will be enabled if required in future. The
250: entire code to support Custom XML Code is already in

Line 268: PAY_SIMULATION_INFORMATION with ACTION_CONTEXT_TYPE as

264: available to the user. For US Localization, we are using
265: this procedure to determine all those "Element Name -
266: Input Value" combinations applicable to the current
267: Assignment. These combinations are stored to table
268: PAY_SIMULATION_INFORMATION with ACTION_CONTEXT_TYPE as
269: "INPUTSLOV". This data is used by the LOV Queries related
270: to Earnings and Deductions regions of Payroll Simulator.
271: Important : This procedure is initiated from Payroll Simulator Page
272: and the data gathered by this procedure will not be