DBA Data[Home] [Help]

APPS.PAY_ELE_SHD SQL Statements

The following lines contain the word 'select', 'insert', 'update' or 'delete':

Line: 79

    select
     element_entry_id
    ,effective_start_date
    ,effective_end_date
    ,cost_allocation_keyflex_id
    ,assignment_id
    ,updating_action_id
    ,updating_action_type
    ,element_link_id
    ,original_entry_id
    ,creator_type
    ,entry_type
    ,comment_id
    ,null
    ,creator_id
    ,reason
    ,target_entry_id
    ,attribute_category
    ,attribute1
    ,attribute2
    ,attribute3
    ,attribute4
    ,attribute5
    ,attribute6
    ,attribute7
    ,attribute8
    ,attribute9
    ,attribute10
    ,attribute11
    ,attribute12
    ,attribute13
    ,attribute14
    ,attribute15
    ,attribute16
    ,attribute17
    ,attribute18
    ,attribute19
    ,attribute20
-- --
  ,
  entry_information_category,
  entry_information1,
  entry_information2,
  entry_information3,
  entry_information4,
  entry_information5,
  entry_information6,
  entry_information7,
  entry_information8,
  entry_information9,
  entry_information10,
  entry_information11,
  entry_information12,
  entry_information13,
  entry_information14,
  entry_information15,
  entry_information16,
  entry_information17,
  entry_information18,
  entry_information19,
  entry_information20,
  entry_information21,
  entry_information22,
  entry_information23,
  entry_information24,
  entry_information25,
  entry_information26,
  entry_information27,
  entry_information28,
  entry_information29,
  entry_information30
    ,subpriority
    ,personal_payment_method_id
    ,date_earned
    ,object_version_number
    ,source_id
    ,balance_adj_cost_flag
    ,element_type_id
    ,all_entry_values_null
    from	pay_element_entries_f
    where	element_entry_id = p_element_entry_id
    and		p_effective_date
    between	effective_start_date and effective_end_date;
Line: 224

  ,p_update                 out nocopy boolean
  ,p_update_override        out nocopy boolean
  ,p_update_change_insert   out nocopy boolean
  ) is
--
  l_proc 	varchar2(72) := g_package||'find_dt_upd_modes';
Line: 234

    select  pet.processing_type
    from    pay_element_types_f   pet,
            pay_element_entries_f pee,
            pay_element_links_f   pel
    where   pet.element_type_id = pel.element_type_id
    and     pel.element_link_id = pee.element_link_id
    and     pee.element_entry_id = p_base_key_value
    and     p_effective_date
      between pee.effective_start_date and pee.effective_end_date
    and     p_effective_date
      between pel.effective_start_date and pel.effective_end_date
    and     p_effective_date
      between pet.effective_start_date and pet.effective_end_date;
Line: 259

    ,p_update                => p_update
    ,p_update_override       => p_update_override
    ,p_update_change_insert  => p_update_change_insert
    );
Line: 281

    p_update := FALSE;
Line: 282

    p_update_override := FALSE;
Line: 283

    p_update_change_insert := FALSE;
Line: 296

  ,p_delete                out nocopy boolean
  ,p_future_change         out nocopy boolean
  ,p_delete_next_change    out nocopy boolean
  ) is
  --
  l_proc 		varchar2(72) 	:= g_package||'find_dt_del_modes';
Line: 308

    select
     t.assignment_id
    ,t.element_link_id
    from   pay_element_entries_f t
    where  t.element_entry_id = p_base_key_value
    and    p_effective_date
    between t.effective_start_date and t.effective_end_date;
Line: 317

    select  pet.processing_type
    from    pay_element_types_f   pet,
            pay_element_entries_f pee,
            pay_element_links_f   pel
    where   pet.element_type_id = pel.element_type_id
    and     pel.element_link_id = pee.element_link_id
    and     pee.element_entry_id = p_base_key_value
    and     p_effective_date
      between pee.effective_start_date and pee.effective_end_date
    and     p_effective_date
      between pel.effective_start_date and pel.effective_end_date
    and     p_effective_date
      between pet.effective_start_date and pet.effective_end_date;
Line: 360

   ,p_delete                        => p_delete
   ,p_future_change                 => p_future_change
   ,p_delete_next_change            => p_delete_next_change
   );
Line: 383

    p_delete := FALSE;
Line: 385

    p_delete_next_change := FALSE;
Line: 425

  update  pay_element_entries_f t
  set     t.effective_end_date    = p_new_effective_end_date
    ,     t.object_version_number = l_object_version_number
  where   t.element_entry_id        = p_base_key_value
  and     p_effective_date
  between t.effective_start_date and t.effective_end_date;
Line: 468

    select
     element_entry_id
    ,effective_start_date
    ,effective_end_date
    ,cost_allocation_keyflex_id
    ,assignment_id
    ,updating_action_id
    ,updating_action_type
    ,element_link_id
    ,original_entry_id
    ,creator_type
    ,entry_type
    ,comment_id
    ,null
    ,creator_id
    ,reason
    ,target_entry_id
    ,attribute_category
    ,attribute1
    ,attribute2
    ,attribute3
    ,attribute4
    ,attribute5
    ,attribute6
    ,attribute7
    ,attribute8
    ,attribute9
    ,attribute10
    ,attribute11
    ,attribute12
    ,attribute13
    ,attribute14
    ,attribute15
    ,attribute16
    ,attribute17
    ,attribute18
    ,attribute19
    ,attribute20
-- --
  ,
  entry_information_category,
  entry_information1,
  entry_information2,
  entry_information3,
  entry_information4,
  entry_information5,
  entry_information6,
  entry_information7,
  entry_information8,
  entry_information9,
  entry_information10,
  entry_information11,
  entry_information12,
  entry_information13,
  entry_information14,
  entry_information15,
  entry_information16,
  entry_information17,
  entry_information18,
  entry_information19,
  entry_information20,
  entry_information21,
  entry_information22,
  entry_information23,
  entry_information24,
  entry_information25,
  entry_information26,
  entry_information27,
  entry_information28,
  entry_information29,
  entry_information30
    ,subpriority
    ,personal_payment_method_id
    ,date_earned
    ,object_version_number
    ,source_id
    ,balance_adj_cost_flag
    ,element_type_id
    ,all_entry_values_null
    from    pay_element_entries_f
    where   element_entry_id = p_element_entry_id
    and	    p_effective_date
    between effective_start_date and effective_end_date
    for update nowait;
Line: 556

    select hc.comment_text
    from   hr_comments hc
    where  hc.comment_id = pay_ele_shd.g_old_rec.comment_id;
Line: 563

    select assignment_id
    from   per_all_assignments_f
    where  assignment_id = pay_ele_shd.g_old_rec.assignment_id
    for update nowait;
Line: 600

  If (p_datetrack_mode <> hr_api.g_insert) then
    --
    -- We must select and lock the current row.
    --
    Open  C_Sel1;
Line: 627

        (p_datetrack_mode = hr_api.g_update             or
         p_datetrack_mode = hr_api.g_correction         or
         p_datetrack_mode = hr_api.g_update_override    or
         p_datetrack_mode = hr_api.g_update_change_insert)) then
       Open C_Sel3;
Line: 651

	-- Simply select the row for update to lock it in exclusive mode
	-- as we are taking this functionality out of the validate_dt_mode
	-- below
	for i in c_sel4 loop
	  null;
Line: 724

  SELECT piv.lookup_type,
         piv.value_set_id
  FROM   pay_input_values_f piv
  WHERE  piv.input_value_id = p_input_value_id
  AND    nvl(p_effective_date,sysdate)
                          between piv.effective_start_date
                              and piv.effective_end_date;