1 Package pqp_aat_bus as
2 /* $Header: pqaatrhi.pkh 120.2.12010000.1 2008/07/28 11:07:11 appldev ship $ */
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_assignment_attribute_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_assignment_attribute_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_assignment_attribute_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_assignment_attribute_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_assignment_attribute_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_assignment_attribute_id in number
66 ) RETURN varchar2;
67 --
68 --
69 -- ---------------------------------------------------------------------------+
70 -- |-----------------------< chk_primary_exists >-----------------------------|
71 -- ---------------------------------------------------------------------------+
72 -- {Start Of Comments}
73 --
74 -- Description:
75 -- This procedure is used to ensure that an assignment does not have a
76 -- secondary company car without a primary company car.
77 --
78 -- {End Of Comments}
79 -- ---------------------------------------------------------------------------+
80 Procedure chk_primary_exists
81 (p_primary_company_car in number,
82 p_secondary_company_car in number
83 );
84 --
85 --
86 -- ---------------------------------------------------------------------------+
87 -- |---------------------------< insert_validate >----------------------------|
88 -- ---------------------------------------------------------------------------+
89 -- {Start Of Comments}
90 --
91 -- Description:
92 -- This procedure controls the execution of all insert business rules
93 -- validation.
94 --
95 -- Prerequisites:
96 -- This private procedure is called from ins procedure.
97 --
98 -- In Parameters:
99 -- A Pl/Sql record structre.
100 --
101 -- Post Success:
102 -- Processing continues.
103 --
104 -- Post Failure:
105 -- If a business rules fails the error will not be handled by this procedure
106 -- unless explicity coded.
107 --
108 -- Developer Implementation Notes:
109 -- For insert, your business rules should be executed from this procedure and
110 -- should ideally (unless really necessary) just be straight procedure or
111 -- function calls. Try and avoid using conditional branching logic.
112 --
113 -- Access Status:
114 -- Internal Row Handler Use Only.
115 --
116 -- {End Of Comments}
117 -- ---------------------------------------------------------------------------+
118 Procedure insert_validate
119 (p_rec in pqp_aat_shd.g_rec_type
120 ,p_effective_date in date
121 ,p_datetrack_mode in varchar2
122 ,p_validation_start_date in date
123 ,p_validation_end_date in date
124 );
125 --
126 -- ---------------------------------------------------------------------------+
127 -- |---------------------------< update_validate >----------------------------|
128 -- ---------------------------------------------------------------------------+
129 -- {Start Of Comments}
130 --
131 -- Description:
132 -- This procedure controls the execution of all update business rules
133 -- validation.
134 --
135 -- Prerequisites:
136 -- This private procedure is called from upd procedure.
137 --
138 -- In Parameters:
139 -- A Pl/Sql record structre.
140 --
141 -- Post Success:
142 -- Processing continues.
143 --
144 -- Post Failure:
145 -- If a business rules fails the error will not be handled by this procedure
146 -- unless explicity coded.
147 --
148 -- Developer Implementation Notes:
149 -- For update, your business rules should be executed from this procedure and
150 -- should ideally (unless really necessary) just be straight procedure or
151 -- function calls. Try and avoid using conditional branching logic.
152 --
153 -- Access Status:
154 -- Internal Row Handler Use Only.
155 --
156 -- {End Of Comments}
157 -- ---------------------------------------------------------------------------+
158 Procedure update_validate
159 (p_rec in pqp_aat_shd.g_rec_type
160 ,p_effective_date in date
161 ,p_datetrack_mode in varchar2
162 ,p_validation_start_date in date
163 ,p_validation_end_date in date
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 -- {End Of Comments}
197 -- ---------------------------------------------------------------------------+
198 Procedure delete_validate
199 (p_rec in pqp_aat_shd.g_rec_type
200 ,p_effective_date in date
201 ,p_datetrack_mode in varchar2
202 ,p_validation_start_date in date
203 ,p_validation_end_date in date
204 );
205 --
206 end pqp_aat_bus;
[Home] [Help]