1 Package hxc_hph_bus AUTHID CURRENT_USER as
2 /* $Header: hxchphrhi.pkh 120.0 2005/05/29 05:37:21 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |----------------------< set_security_group_id >--------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
11 -- group context.
12 --
13 -- Prerequisites:
14 -- The primary key identified by p_pref_hierarchy_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_pref_hierarchy_id
19 --
20 --
21 -- Post Success:
22 -- The security_group_id will be set in CLIENT_INFO.
23 --
24 -- Post Failure:
25 -- An error is raised if the value does not exist.
26 --
27 -- Access Status:
28 -- Internal Development Use Only.
29 --
30 -- {End Of Comments}
31 -- ---------------------------------------------------------------------------
32 procedure set_security_group_id
33 (p_pref_hierarchy_id in number
34 );
35 --
36 --
37 -- ---------------------------------------------------------------------------
38 -- |---------------------< return_legislation_code >-------------------------|
39 -- ---------------------------------------------------------------------------
40 -- {Start Of Comments}
41 --
42 -- Description:
43 -- Return the legislation code for a specific primary key value
44 --
45 -- Prerequisites:
46 -- The primary key identified by p_pref_hierarchy_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_pref_hierarchy_id
51 --
52 --
53 -- Post Success:
54 -- The business group's legislation code will be returned.
55 --
56 -- Post Failure:
57 -- An error is raised if the value does not exist.
58 --
59 -- Access Status:
60 -- Internal Development Use Only.
61 --
62 -- {End Of Comments}
63 -- ---------------------------------------------------------------------------
64 FUNCTION return_legislation_code
65 (p_pref_hierarchy_id in number
66 ) RETURN varchar2;
67 --
68 --
69 -- ----------------------------------------------------------------------------
70 -- |-----------------------------< get_top_level >---------------------------------|
71 -- ----------------------------------------------------------------------------
72 -- {Start Of Comments}
73 --
74 -- Description:
75 -- This function return the top level id of a particular none in the hierarchy
76 --
77 function get_top_level_id(p_pref_id in number)
78 return number;
79 --
80 -- -------------------------------------------------------------------------------------
81 -- |-----------------------------< get_top_level_name >---------------------------------|
82 -- ------------------------------------------------------------------------------------
83 -- {Start Of Comments}
84 --
85 -- Description:
86 -- This function return the top level id of a particular none in the hierarchy
87 --
88 function get_top_level_name(p_pref_id in number)
89 return varchar2;
90
91 --
92 -- ----------------------------------------------------------------------------
93 -- |---------------------------< insert_validate >----------------------------|
94 -- ----------------------------------------------------------------------------
95 -- {Start of comments}
96 --
97 -- Description:
98 -- This procedure controls the execution of all insert business rules
99 -- validation.
100 --
101 -- Prerequisites:
102 -- This private procedure is called from ins procedure.
103 --
104 -- In Parameters:
105 -- A Pl/Sql record structure.
106 --
107 -- Post Success:
108 -- Processing continues.
109 --
110 -- Post Failure:
111 -- If a business rules fails the error will not be handled by this procedure
112 -- unless explicity coded.
113 --
114 -- Developer Implementation Notes:
115 -- For insert, your business rules should be executed from this procedure and
116 -- should ideally (unless really necessary) just be straight procedure or
117 -- function calls. Try and avoid using conditional branching logic.
118 --
119 -- Access Status:
120 -- Internal Row Handler Use Only.
121 --
122 -- {End of comments}
123 -- ----------------------------------------------------------------------------
124 Procedure insert_validate
125 (p_effective_date in date
126 ,p_rec in hxc_hph_shd.g_rec_type
127 );
128 --
129 -- ----------------------------------------------------------------------------
130 -- |---------------------------< update_validate >----------------------------|
131 -- ----------------------------------------------------------------------------
132 -- {Start Of Comments}
133 --
134 -- Description:
135 -- This procedure controls the execution of all update business rules
136 -- validation.
137 --
138 -- Prerequisites:
139 -- This private procedure is called from upd procedure.
140 --
141 -- In Parameters:
142 -- A Pl/Sql record structure.
143 --
144 -- Post Success:
145 -- Processing continues.
146 --
147 -- Post Failure:
148 -- If a business rules fails the error will not be handled by this procedure
149 -- unless explicity coded.
150 --
151 -- Developer Implementation Notes:
152 -- For update, your business rules should be executed from this procedure and
153 -- should ideally (unless really necessary) just be straight procedure or
154 -- function calls. Try and avoid using conditional branching logic.
155 --
156 -- Access Status:
157 -- Internal Row Handler Use Only.
158 --
159 -- {End Of Comments}
160 -- ----------------------------------------------------------------------------
161 Procedure update_validate
162 (p_effective_date in date
163 ,p_rec in hxc_hph_shd.g_rec_type
164 );
165 --
166 -- ----------------------------------------------------------------------------
167 -- |---------------------------< delete_validate >----------------------------|
168 -- ----------------------------------------------------------------------------
169 -- {Start Of Comments}
170 --
171 -- Description:
172 -- This procedure controls the execution of all delete business rules
173 -- validation.
174 --
175 -- Prerequisites:
176 -- This private procedure is called from del procedure.
177 --
178 -- In Parameters:
179 -- A Pl/Sql record structure.
180 --
181 -- Post Success:
182 -- Processing continues.
183 --
184 -- Post Failure:
185 -- If a business rules fails the error will not be handled by this procedure
186 -- unless explicity coded.
187 --
188 -- Developer Implementation Notes:
189 -- For delete, your business rules should be executed from this procedure and
190 -- should ideally (unless really necessary) just be straight procedure or
191 -- function calls. Try and avoid using conditional branching logic.
192 --
193 -- Access Status:
194 -- Internal Row Handler Use Only.
195 --
196 --
197 -- ----------------------------------------------------------------------------
198 Procedure delete_validate
199 (p_rec in hxc_hph_shd.g_rec_type
200 );
201 --
202 end hxc_hph_bus;
[Home] [Help]