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.PER_BF_PAYMENT_DETAILS_API dependencies on PER_BF_PROCESSED_ASSIGNMENTS

Line 125: -- PER_BF_PROCESSED_ASSIGNMENTS should one exist.

121: -- Declare cursors and local variables
122: --
123: --
124: -- Cursor to retrieve the ID and OVN of the row in
125: -- PER_BF_PROCESSED_ASSIGNMENTS should one exist.
126: --
127: CURSOR csr_get_pa_id_ovn IS
128: SELECT processed_assignment_id, object_version_number
129: FROM per_bf_processed_assignments

Line 129: FROM per_bf_processed_assignments

125: -- PER_BF_PROCESSED_ASSIGNMENTS should one exist.
126: --
127: CURSOR csr_get_pa_id_ovn IS
128: SELECT processed_assignment_id, object_version_number
129: FROM per_bf_processed_assignments
130: WHERE payroll_run_id = p_payroll_run_id
131: AND assignment_id = p_assignment_id;
132: --
133: -- Two tables are being used in this API, so two sets of OUT parameters will

Line 140: PER_BF_PROCESSED_ASSIGNMENTS.processed_assignment_id%TYPE;

136: l_payment_detail_id PER_BF_PAYMENT_DETAILS.payment_detail_id%TYPE;
137: l_payment_detail_ovn
138: PER_BF_PAYMENT_DETAILS.object_version_number%TYPE;
139: l_processed_assignment_id
140: PER_BF_PROCESSED_ASSIGNMENTS.processed_assignment_id%TYPE;
141: l_processed_assignment_ovn
142: PER_BF_PROCESSED_ASSIGNMENTS.object_version_number%TYPE;
143: --
144: --

Line 142: PER_BF_PROCESSED_ASSIGNMENTS.object_version_number%TYPE;

138: PER_BF_PAYMENT_DETAILS.object_version_number%TYPE;
139: l_processed_assignment_id
140: PER_BF_PROCESSED_ASSIGNMENTS.processed_assignment_id%TYPE;
141: l_processed_assignment_ovn
142: PER_BF_PROCESSED_ASSIGNMENTS.object_version_number%TYPE;
143: --
144: --
145: l_proc varchar2(72) := g_package||'create_payment_detail';
146: begin

Line 231: -- PER_BF_PROCESSED_ASSIGNMENTS.

227: hr_utility.set_location(l_proc, 35);
228: --
229: -- This is the first balance to be associated with this assignment and
230: -- payroll run, so a new row needs to be created in the table
231: -- PER_BF_PROCESSED_ASSIGNMENTS.
232: --
233: CLOSE csr_get_pa_id_ovn ;
234: --
235: per_bpa_ins.ins

Line 247: -- A row exists in PER_BF_PROCESSED_ASSIGNMENTS for this payroll run and

243: ELSE
244: --
245: hr_utility.set_location(l_proc, 36);
246: --
247: -- A row exists in PER_BF_PROCESSED_ASSIGNMENTS for this payroll run and
248: -- assignment combination, so no need to do anything as the values
249: -- for the processed_assignment_id and object_version number are
250: -- already in local variables.
251: --

Line 681: ,PER_BF_PROCESSED_ASSIGNMENTS pa

677: --
678: CURSOR csr_get_pa_id IS
679: SELECT pa.processed_assignment_id, pa.object_version_number
680: FROM PER_BF_PAYMENT_DETAILS pd
681: ,PER_BF_PROCESSED_ASSIGNMENTS pa
682: WHERE pd.payment_detail_id = p_payment_detail_id
683: AND pd.processed_assignment_id = pa.processed_assignment_id;
684: --
685: CURSOR csr_chk_pa_for_del

Line 739: -- from PER_BF_PROCESSED_ASSIGNMENTS.

735: -- Process Logic
736: --
737: -- If no other entity uses the processed_assignment row that the FK
738: -- in PER_BF_PAYMENT_DETAILS references, then the row will be removed
739: -- from PER_BF_PROCESSED_ASSIGNMENTS.
740: --
741: -- Obtain the processed assignment ID related to this row.
742: --
743: OPEN csr_get_pa_id;

Line 758: -- The row can be deleted from PER_BF_PROCESSED_ASSIGNMENTS

754: IF csr_chk_pa_for_del%NOTFOUND THEN
755: --
756: CLOSE csr_chk_pa_for_del;
757: --
758: -- The row can be deleted from PER_BF_PROCESSED_ASSIGNMENTS
759: -- so set a boolean and it will be removed later.
760: --
761: l_delete_pa_row := TRUE;
762: --