[Home] [Help]
29: -- but the business_group_id will be null for Global security profiles.
30: -- In this case, the cursor will not return a row and a primary key
31: -- error will be raised. For this reason, this procedure is not called
32: -- from anywhere else in the row-handler and it is recommended that
33: -- this remains the case; lookup validation should use hr_standard_lookups
34: -- not hr_lookups.
35: --
36: cursor csr_sec_grp is
37: select pbg.security_group_id,
114: -- but the business_group_id will be null for Global security profiles.
115: -- In this case, the cursor will not return a row and a primary key
116: -- error will be raised. For this reason, this procedure is not called
117: -- from anywhere else in the row-handler and it is recommended that
118: -- this remains the case; lookup validation should use hr_standard_lookups
119: -- not hr_lookups.
120:
121: cursor csr_leg_code is
122: select pbg.legislation_code
577: -- This table does not have a mandatory business_group_id
578: -- column, so client_info is not populated by calling the
579: -- per_seu_bus.set_security_group_id procedure.
580: -- Here, validation is performed without a business group context,
581: -- so any lookup code validation should use HR_STANDARD_LOOKUPS and not
582: -- HR_LOOKUPs.
583: --
584:
585: --
662: -- This table does not have a mandatory business_group_id
663: -- column, so client_info is not populated by calling the
664: -- per_seu_bus.set_security_group_id procedure.
665: -- Here, validation is performed without a business group context,
666: -- so any lookup code validation should use HR_STANDARD_LOOKUPS and not
667: -- HR_LOOKUPS.
668: --
669: -- Validate Dependent Attributes
670: --