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