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.PAY_HR_OTC_RETRIEVAL_INTERFACE dependencies on HXC_BEE_PREF_ADJ_LINES

Line 773: -- HXC_BEE_PREF_ADJ_LINES with the details that were previously transferred

769: -- For automatic reversal batch creation if there is a rule evaluation pref
770: -- change.
771:
772: -- Earlier hxc_gen_retrieve_utils.chk_retrieve would have populated
773: -- HXC_BEE_PREF_ADJ_LINES with the details that were previously transferred
774: -- and had a preference change before transfer this time.
775: -- Check the count of those records which are for time store. Now we
776: -- are running OTM batches. Meaning, if there was an earlier batch, it would
777: -- have been from time store. There needs to be reverse batches for those.

Line 788: FROM hxc_bee_pref_adj_lines

784: -- the result is only 1 or 0.
785:
786: SELECT COUNT(*)
787: INTO l_dup_count
788: FROM hxc_bee_pref_adj_lines
789: WHERE batch_source = 'Time Store'
790: AND ROWNUM < 2 ;
791:
792:

Line 2204: FROM hxc_bee_pref_adj_lines

2200: -- exists or not. We dont want the exact number, just wanna know if it exists or not.
2201:
2202: SELECT COUNT(*)
2203: INTO l_dup_count
2204: FROM hxc_bee_pref_adj_lines
2205: WHERE batch_source = 'OTM'
2206: AND ROWNUM < 2;
2207:
2208:

Line 2390: -- which has an entry in hxc_bee_pref_adj_lines table, with

2386:
2387: -- Private procedure create_bld_blk_table
2388: -- populates the detail bld blks plsql table like gen. retrieval
2389: -- 1. Pull out the bb details from hxc_time_building_blocks table
2390: -- which has an entry in hxc_bee_pref_adj_lines table, with
2391: -- batch_source as Time Store.
2392: -- 2. Update hxc_bee_pref_adj_lines table with these values for
2393: -- the corresponding bb_ids and ovns.
2394: -- 3. Pull out these into a plsql table for the format prescribed in

Line 2392: -- 2. Update hxc_bee_pref_adj_lines table with these values for

2388: -- populates the detail bld blks plsql table like gen. retrieval
2389: -- 1. Pull out the bb details from hxc_time_building_blocks table
2390: -- which has an entry in hxc_bee_pref_adj_lines table, with
2391: -- batch_source as Time Store.
2392: -- 2. Update hxc_bee_pref_adj_lines table with these values for
2393: -- the corresponding bb_ids and ovns.
2394: -- 3. Pull out these into a plsql table for the format prescribed in
2395: -- hxc_generic_retrieval_pkg, so that it can use the batch creation API.
2396:

Line 2420: FROM hxc_bee_pref_adj_lines

2416: FROM hxc_time_building_blocks
2417: WHERE (time_building_block_id,object_version_number)
2418: IN ( SELECT detail_bb_id,
2419: detail_bb_ovn
2420: FROM hxc_bee_pref_adj_lines
2421: WHERE batch_source = 'Time Store');
2422:
2423: CURSOR get_blocks
2424: IS

Line 2441: FROM hxc_bee_pref_adj_lines

2437: changed,
2438: deleted,
2439: timecard_id,
2440: timecard_ovn
2441: FROM hxc_bee_pref_adj_lines
2442: WHERE batch_source = 'Time Store'
2443: order by detail_bb_id
2444: ;
2445:

Line 2456: UPDATE hxc_bee_pref_adj_lines

2452: CLOSE get_bb_details;
2453:
2454: FOR i IN t_bb_details.FIRST..t_bb_details.LAST
2455: LOOP
2456: UPDATE hxc_bee_pref_adj_lines
2457: SET type = t_bb_details(i).type,
2458: scope = t_bb_details(i).scope,
2459: hours = t_bb_details(i).measure ,
2460: start_time = t_bb_details(i).start_time ,

Line 2530: FROM hxc_bee_pref_adj_lines

2526: hxc_time_attributes hat
2527: WHERE hau.time_attribute_id = hat.time_attribute_id
2528: AND (hau.time_building_block_id,
2529: hau.time_building_block_ovn) IN ( SELECT detail_bb_id, detail_bb_ovn
2530: FROM hxc_bee_pref_adj_lines
2531: WHERE batch_source = 'Time Store')
2532: ORDER BY hau.time_building_block_id,
2533: hat.bld_blk_info_type_id;
2534:

Line 2745: DELETE FROM hxc_bee_pref_adj_lines

2741: l_retro_adj_batch_id
2742: );
2743:
2744: -- you dont need the duplicate adjustment lines of this batch source, so delete them.
2745: DELETE FROM hxc_bee_pref_adj_lines
2746: WHERE batch_source = 'Time Store';
2747:
2748: EXCEPTION
2749: WHEN OTHERS THEN

Line 2761: -- for the details in hxc_bee_pref_adj_lines table with OTM as batch source.

2757:
2758:
2759: -- Bug 6121705
2760: -- This procedure is used to create reversal batches with Batch source as OTM
2761: -- for the details in hxc_bee_pref_adj_lines table with OTM as batch source.
2762: -- hxc_generic_retrieval_utils.chk_retrieve would have populated these
2763: -- records for which there is a history of a different preference for rules
2764: -- evaluation.
2765:

Line 2789: FROM hxc_bee_pref_adj_lines,

2785: WHERE ( date_worked,
2786: assignment_id )
2787: in ( SELECT date_earned,
2788: assignment_id
2789: FROM hxc_bee_pref_adj_lines,
2790: per_all_assignments_f paf,
2791: per_assignment_status_types pas
2792: WHERE resource_id = person_id
2793: AND batch_source = 'OTM'

Line 2820: FROM hxc_bee_pref_adj_lines hoa,

2816: FROM hxt_batch_values_v
2817: WHERE (date_worked ,assignment_id) in
2818: ( SELECT date_earned,
2819: paf.assignment_id
2820: FROM hxc_bee_pref_adj_lines hoa,
2821: per_all_assignments_f paf
2822: WHERE hoa.resource_id = paf.person_id
2823: AND hoa.date_earned BETWEEN paf.effective_start_date
2824: AND paf.effective_end_date

Line 2870: FROM hxc_bee_pref_adj_lines

2866: -- Check if there is anything left there. If no TC was transferred, no need of the
2867: -- adj dup batch.
2868: SELECT COUNT(*)
2869: INTO l_rec_count
2870: FROM hxc_bee_pref_adj_lines
2871: WHERE batch_source = 'OTM'
2872: AND rownum < 2;
2873:
2874: IF l_rec_count > 0

Line 2894: DELETE FROM hxc_bee_pref_adj_lines

2890:
2891: create_batch_line(p_batch_id => l_new_batch);
2892:
2893:
2894: DELETE FROM hxc_bee_pref_adj_lines
2895: WHERE batch_source = 'OTM';
2896: END IF;
2897:
2898: