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