DBA Data[Home] [Help]

APPS.PAY_JP_BEE_UTILITY_PKG SQL Statements

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

Line: 69

		select	start_date,
			end_date
		from	per_time_periods
		where	time_period_id = p_time_period_id;
Line: 106

	-- Date Effective Changes is available only when "Update",
	-- not available when "Insert" and "Reject".
	--
	if p_action_if_exists in ('I', 'R') then
		p_date_effective_changes := null;
Line: 112

	-- 1. Date Effective Changes is null for "Update" case, set to "Update/Change Insert"
	-- 2. Date Effective Changes "Override" is available only when Reject If Future Changes is set to "No".
	--    If set to "Yes", set Date Effective Changes to "Update/Change Insert".
	--
	elsif (p_date_effective_changes is null)
	or    ((p_reject_if_future_changes = 'Y') and (p_date_effective_changes = 'O')) then
		p_date_effective_changes := 'U';
Line: 134

		select	ivtl.name,
			iv.mandatory_flag,
			iv.hot_default_flag,
			iv.lookup_type,
			iv.default_value,
			null,
			null
		from	pay_input_values_f_tl	ivtl,
			pay_input_values_f	iv
		where	iv.element_type_id = p_element_type_id
		and	p_effective_date
			between iv.effective_start_date and iv.effective_end_date
		and	ivtl.input_value_id = iv.input_value_id
		and	ivtl.language = userenv('LANG')
		order by iv.display_sequence;
Line: 191

		select	/*+ ORDERED */
			ee.element_entry_id,
			ee.effective_start_date,
			ee.effective_end_date,
			ee.element_link_id,
			ee.cost_allocation_keyflex_id,
			cak.concatenated_segments,
			cak.segment1,
			cak.segment2,
			cak.segment3,
			cak.segment4,
			cak.segment5,
			cak.segment6,
			cak.segment7,
			cak.segment8,
			cak.segment9,
			cak.segment10,
			cak.segment11,
			cak.segment12,
			cak.segment13,
			cak.segment14,
			cak.segment15,
			cak.segment16,
			cak.segment17,
			cak.segment18,
			cak.segment19,
			cak.segment20,
			cak.segment21,
			cak.segment22,
			cak.segment23,
			cak.segment24,
			cak.segment25,
			cak.segment26,
			cak.segment27,
			cak.segment28,
			cak.segment29,
			cak.segment30,
			ee.reason,
			ee.attribute_category,
			ee.attribute1,
			ee.attribute2,
			ee.attribute3,
			ee.attribute4,
			ee.attribute5,
			ee.attribute6,
			ee.attribute7,
			ee.attribute8,
			ee.attribute9,
			ee.attribute10,
			ee.attribute11,
			ee.attribute12,
			ee.attribute13,
			ee.attribute14,
			ee.attribute15,
			ee.attribute16,
			ee.attribute17,
			ee.attribute18,
			ee.attribute19,
			ee.attribute20,
			ee.entry_information_category,
			ee.entry_information1,
			ee.entry_information2,
			ee.entry_information3,
			ee.entry_information4,
			ee.entry_information5,
			ee.entry_information6,
			ee.entry_information7,
			ee.entry_information8,
			ee.entry_information9,
			ee.entry_information10,
			ee.entry_information11,
			ee.entry_information12,
			ee.entry_information13,
			ee.entry_information14,
			ee.entry_information15,
			ee.entry_information16,
			ee.entry_information17,
			ee.entry_information18,
			ee.entry_information19,
			ee.entry_information20,
			ee.entry_information21,
			ee.entry_information22,
			ee.entry_information23,
			ee.entry_information24,
			ee.entry_information25,
			ee.entry_information26,
			ee.entry_information27,
			ee.entry_information28,
			ee.entry_information29,
			ee.entry_information30,
			ee.date_earned,
			ee.personal_payment_method_id,
			ee.subpriority
		from	per_all_assignments_f		asg,
			pay_element_links_f		el,
			pay_element_entries_f		ee,
			pay_cost_allocation_keyflex	cak
		where	asg.assignment_id = p_assignment_id
		and	p_effective_date
			between asg.effective_start_date and asg.effective_end_date
		and	el.element_type_id = p_element_type_id
		and	el.business_group_id + 0 = asg.business_group_id
		and	p_effective_date
			between el.effective_start_date and el.effective_end_date
		and	ee.assignment_id = asg.assignment_id
		and	ee.element_link_id = el.element_link_id
		and	p_effective_date
			between ee.effective_start_date and ee.effective_end_date
		and	ee.entry_type = 'E'
		and	cak.cost_allocation_keyflex_id(+) = ee.cost_allocation_keyflex_id;
Line: 302

		select	/*+ ORDERED */
			ivtl.name,
			iv.mandatory_flag,
			iv.hot_default_flag,
			iv.lookup_type,
			iv.default_value,
			liv.default_value,
			eev.screen_entry_value
		from	pay_element_entry_values_f	eev,
			pay_link_input_values_f		liv,
			pay_input_values_f		iv,
			pay_input_values_f_tl		ivtl
		where	eev.element_entry_id = p_ee_rec.element_entry_id
		and	eev.effective_start_date = p_ee_rec.effective_start_date
		and	eev.effective_end_date = p_ee_rec.effective_end_date
		and	liv.element_link_id = p_ee_rec.element_link_id
		and	liv.input_value_id = eev.input_value_id
		and	p_effective_date
			between liv.effective_start_date and liv.effective_end_date
		and	iv.input_value_id = liv.input_value_id
		and	p_effective_date
			between iv.effective_start_date and iv.effective_end_date
		and	ivtl.input_value_id = iv.input_value_id
		and	ivtl.language = userenv('LANG')
		order by iv.display_sequence;
Line: 405

	-- In this case, delete the entry from PL/SQL table for non-enterable input values.
	--
	if p_ee_rec.element_entry_id is null then
		p_is_different	:= true;
Line: 416

				-- delete the entry from PL/SQL table.
				--
				p_new_value_tbl.delete(l_index);
Line: 441

				-- delete the entry from PL/SQL table.
				-- If the entry does not exist, nothing happens.
				--
				p_new_value_tbl.delete(i);