1 Package ghr_caa_bus AUTHID CURRENT_USER as
2 /* $Header: ghcaarhi.pkh 120.0 2005/05/29 02:47:19 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_compl_agency_appeal_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_compl_agency_appeal_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_compl_agency_appeal_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_compl_agency_appeal_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_compl_agency_appeal_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_compl_agency_appeal_id in number
66 ) RETURN varchar2;
67 --
68
69 PROCEDURE chk_reason_for_appeal(p_compl_agency_appeal_id in ghr_compl_agency_appeals.compl_agency_appeal_id%TYPE,
70 p_reason_for_appeal in ghr_compl_agency_appeals.reason_for_appeal%TYPE,
71 p_effective_date in date,
72 p_object_version_number in number);
73
74 PROCEDURE chk_decision(p_compl_agency_appeal_id in ghr_compl_agency_appeals.compl_agency_appeal_id%TYPE,
75 p_decision in ghr_compl_agency_appeals.decision%TYPE,
76 p_effective_date in date,
77 p_object_version_number in number);
78
79 PROCEDURE chk_rfr_requested_by(p_compl_agency_appeal_id in ghr_compl_agency_appeals.compl_agency_appeal_id%TYPE,
80 p_rfr_requested_by in ghr_compl_agency_appeals.rfr_requested_by%TYPE,
81 p_effective_date in date,
82 p_object_version_number in number);
83
84 PROCEDURE chk_rfr_decision(p_compl_agency_appeal_id in ghr_compl_agency_appeals.compl_agency_appeal_id%TYPE,
85 p_rfr_decision in ghr_compl_agency_appeals.rfr_decision%TYPE,
86 p_effective_date in date,
87 p_object_version_number in number);
88
89 --
90 -- ----------------------------------------------------------------------------
91 -- |---------------------------< insert_validate >----------------------------|
92 -- ----------------------------------------------------------------------------
93 -- {Start of comments}
94 --
95 -- Description:
96 -- This procedure controls the execution of all insert business rules
97 -- validation.
98 --
99 -- Prerequisites:
100 -- This private procedure is called from ins procedure.
101 --
102 -- In Parameters:
103 -- A Pl/Sql record structure.
104 --
105 -- Post Success:
106 -- Processing continues.
107 --
108 -- Post Failure:
109 -- If a business rules fails the error will not be handled by this procedure
110 -- unless explicity coded.
111 --
112 -- Developer Implementation Notes:
113 -- For insert, your business rules should be executed from this procedure
114 -- and should ideally (unless really necessary) just be straight procedure
115 -- or function calls. Try and avoid using conditional branching logic.
116 --
117 -- Access Status:
118 -- Internal Row Handler Use Only.
119 --
120 -- {End of comments}
121 -- ----------------------------------------------------------------------------
122 Procedure insert_validate
123 (p_effective_date in date
124 ,p_rec in ghr_caa_shd.g_rec_type
125 );
126 --
127 -- ----------------------------------------------------------------------------
128 -- |---------------------------< update_validate >----------------------------|
129 -- ----------------------------------------------------------------------------
130 -- {Start Of Comments}
131 --
132 -- Description:
133 -- This procedure controls the execution of all update business rules
134 -- validation.
135 --
136 -- Prerequisites:
137 -- This private procedure is called from upd procedure.
138 --
139 -- In Parameters:
140 -- A Pl/Sql record structure.
141 --
142 -- Post Success:
143 -- Processing continues.
144 --
145 -- Post Failure:
146 -- If a business rules fails the error will not be handled by this procedure
147 -- unless explicity coded.
148 --
149 -- Access Status:
150 -- Internal Row Handler Use Only.
151 --
152 -- {End Of Comments}
153 -- ----------------------------------------------------------------------------
154 Procedure update_validate
155 (p_effective_date in date
156 ,p_rec in ghr_caa_shd.g_rec_type
157 );
158 --
159 -- ----------------------------------------------------------------------------
160 -- |---------------------------< delete_validate >----------------------------|
161 -- ----------------------------------------------------------------------------
162 -- {Start Of Comments}
163 --
164 -- Description:
165 -- This procedure controls the execution of all delete business rules
166 -- validation.
167 --
168 -- Prerequisites:
169 -- This private procedure is called from del procedure.
170 --
171 -- In Parameters:
172 -- A Pl/Sql record structure.
173 --
174 -- Post Success:
175 -- Processing continues.
176 --
177 -- Post Failure:
178 -- If a business rules fails the error will not be handled by this procedure
179 -- unless explicity coded.
180 --
181 -- Developer Implementation Notes:
182 -- For delete, your business rules should be executed from this procedure
183 -- and should ideally (unless really necessary) just be straight procedure
184 -- or function calls. Try and avoid using conditional branching logic.
185 --
186 -- Access Status:
187 -- Internal Row Handler Use Only.
188 --
189 -- {End Of Comments}
190 -- ----------------------------------------------------------------------------
191 Procedure delete_validate
192 (p_rec in ghr_caa_shd.g_rec_type
193 );
194 --
195 end ghr_caa_bus;
[Home] [Help]