1 Package pay_ele_bus as
2 /* $Header: pyelerhi.pkh 120.0 2005/05/29 04:33:12 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_element_entry_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_element_entry_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_element_entry_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_element_entry_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_element_entry_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_element_entry_id in number
66 ) RETURN varchar2;
67 --
68 -- ----------------------------------------------------------------------------
69 -- |-----------------------< derive_element_type_id >-------------------------|
70 -- ----------------------------------------------------------------------------
71 -- {Start of Comments}
72 --
73 -- Description:
74 -- This function derives the element_type_id from the element_link_id, the
75 -- resulting element_type_id will be used to populate the denormalised column,
76 -- element_type_id on pay_element_entries_f.
77 --
78 -- Pre Conditions:
79 -- None
80 --
81 -- In Arguments:
82 -- p_element_link_id number
83 -- p_effective_date date
84 --
85 -- Post Success:
86 -- The corresponding element_type_id will be returned, and used to populate
87 -- the element_type_id on pay_element_entries_f.
88 --
89 -- Post Failure:
90 -- None
91 --
92 -- {End of Comments}
93 -- ----------------------------------------------------------------------------
94 FUNCTION derive_element_type_id (p_element_link_id in number
95 ,p_effective_date in date)
96 RETURN number;
97 --
98 -- ----------------------------------------------------------------------------
99 -- |---------------------------< insert_validate >----------------------------|
100 -- ----------------------------------------------------------------------------
101 -- {Start Of Comments}
102 --
103 -- Description:
104 -- This procedure controls the execution of all insert business rules
105 -- validation.
106 --
107 -- Prerequisites:
108 -- This private procedure is called from ins procedure.
109 --
110 -- In Parameters:
111 -- A Pl/Sql record structre.
112 --
113 -- Post Success:
114 -- Processing continues.
115 --
116 -- Post Failure:
117 -- If a business rules fails the error will not be handled by this procedure
118 -- unless explicity coded.
119 --
120 -- Developer Implementation Notes:
121 -- For insert, your business rules should be executed from this procedure and
122 -- should ideally (unless really necessary) just be straight procedure or
123 -- function calls. Try and avoid using conditional branching logic.
124 --
125 -- Access Status:
126 -- Internal Row Handler Use Only.
127 --
128 -- {End Of Comments}
129 -- ----------------------------------------------------------------------------
130 Procedure insert_validate
131 (p_rec in pay_ele_shd.g_rec_type
132 ,p_effective_date in date
133 ,p_datetrack_mode in varchar2
134 ,p_validation_start_date in date
135 ,p_validation_end_date in date
136 );
137 --
138 -- ----------------------------------------------------------------------------
139 -- |---------------------------< update_validate >----------------------------|
140 -- ----------------------------------------------------------------------------
141 -- {Start Of Comments}
142 --
143 -- Description:
144 -- This procedure controls the execution of all update business rules
145 -- validation.
146 --
147 -- Prerequisites:
148 -- This private procedure is called from upd procedure.
149 --
150 -- In Parameters:
151 -- A Pl/Sql record structre.
152 --
153 -- Post Success:
154 -- Processing continues.
155 --
156 -- Post Failure:
157 -- If a business rules fails the error will not be handled by this procedure
158 -- unless explicity coded.
159 --
160 -- Developer Implementation Notes:
161 -- For update, your business rules should be executed from this procedure and
162 -- should ideally (unless really necessary) just be straight procedure or
163 -- function calls. Try and avoid using conditional branching logic.
164 --
165 -- Access Status:
166 -- Internal Row Handler Use Only.
167 --
168 -- {End Of Comments}
169 -- ----------------------------------------------------------------------------
170 Procedure update_validate
171 (p_rec in pay_ele_shd.g_rec_type
172 ,p_effective_date in date
173 ,p_datetrack_mode in varchar2
174 ,p_validation_start_date in date
175 ,p_validation_end_date in date
176 );
177 --
178 -- ----------------------------------------------------------------------------
179 -- |---------------------------< delete_validate >----------------------------|
180 -- ----------------------------------------------------------------------------
181 -- {Start Of Comments}
182 --
183 -- Description:
184 -- This procedure controls the execution of all delete business rules
185 -- validation.
186 --
187 -- Prerequisites:
188 -- This private procedure is called from del procedure.
189 --
190 -- In Parameters:
191 -- A Pl/Sql record structure.
192 --
193 -- Post Success:
194 -- Processing continues.
195 --
196 -- Post Failure:
197 -- If a business rules fails the error will not be handled by this procedure
198 -- unless explicity coded.
199 --
200 -- Developer Implementation Notes:
201 -- For delete, your business rules should be executed from this procedure and
202 -- should ideally (unless really necessary) just be straight procedure or
203 -- function calls. Try and avoid using conditional branching logic.
204 --
205 -- Access Status:
206 -- Internal Row Handler Use Only.
207 --
208 -- {End Of Comments}
209 -- ----------------------------------------------------------------------------
210 Procedure delete_validate
211 (p_rec in pay_ele_shd.g_rec_type
212 ,p_effective_date in date
213 ,p_datetrack_mode in varchar2
214 ,p_validation_start_date in date
215 ,p_validation_end_date in date
216 );
217 --
218 end pay_ele_bus;
[Home] [Help]