APPS.PAY_RETRO_COMP_USAGE_INTERNAL dependencies on PAY_RETRO_COMPONENT_USAGES

Line 55: ,pay_retro_component_usages rcu1

51: ,etp.business_group_id
52: ,etp.legislation_code
53: from
54: pay_element_types_f etp
55: ,pay_retro_component_usages rcu1
56: where
57: etp.element_type_id = p_element_type_id
58: and p_effective_date between etp.effective_start_date
59: and etp.effective_end_date

Line 63: (select null from pay_retro_component_usages rcu2

59: and etp.effective_end_date
60: and rcu1.creator_type = 'EC'
61: and rcu1.creator_id = etp.classification_id
62: and not exists
63: (select null from pay_retro_component_usages rcu2
64: where rcu2.creator_id = etp.element_type_id
65: and rcu2.creator_type = 'ET')
66: ;
67:

Line 184: pay_retro_component_usages

180: select
181: retro_component_usage_id
182: ,object_version_number
183: from
184: pay_retro_component_usages
185: where
186: creator_id = p_element_type_id
187: and nvl(legislation_code, -1) = p_legislation_code
188: and nvl(business_group_id , -1) = p_business_group_id

Line 277: --for pay_element_span_usages and pay_retro_component_usages tables, we need

273: ,x_business_group_id out nocopy number)
274: IS
275: --Bug#4075607
276: --In order to add business group id and legislation code to unique constraint
277: --for pay_element_span_usages and pay_retro_component_usages tables, we need
278: --to check for the both these column values for the above tables to match
279: --with the pay_element_types table values.
280: --
281: Begin