1 Package pay_pur_bus AUTHID CURRENT_USER as
2 /* $Header: pypurrhi.pkh 120.0 2005/05/29 08:01 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Definitions - Internal Development Use Only |
6 -- ----------------------------------------------------------------------------
7 --
8 -- The following two global variables should be accessed only through
9 -- return_user_key_units and return_range_or_match functions.
10 --
11 g_user_key_units PAY_USER_TABLES.USER_KEY_UNITS%TYPE;
12 g_range_or_match PAY_USER_TABLES.RANGE_OR_MATCH%TYPE;
13 --
14 -- ---------------------------------------------------------------------------
15 -- |----------------------< set_security_group_id >--------------------------|
16 -- ---------------------------------------------------------------------------
17 -- {Start Of Comments}
18 --
19 -- Description:
20 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
21 -- group context.
22 -- It is only valid to call this procedure when the primary key
23 -- is within a buisiness group context.
24 --
25 -- Prerequisites:
26 -- The primary key identified by p_user_row_id
27 -- already exists.
28 --
29 -- In Arguments:
30 -- p_user_row_id
31 --
32 --
33 -- Post Success:
34 -- The security_group_id will be set in CLIENT_INFO.
35 --
36 -- Post Failure:
37 -- An error is raised if the value does not exist.
38 -- An error is also raised when the primary key data is outside
39 -- of a buisiness group context.
40 --
41 -- Access Status:
42 -- Internal Development Use Only.
43 --
44 -- {End Of Comments}
45 -- ---------------------------------------------------------------------------
46 procedure set_security_group_id
47 (p_user_row_id in number
48 ,p_associated_column1 in varchar2 default null
49 );
50 --
51 --
52 -- ---------------------------------------------------------------------------
53 -- |---------------------< return_legislation_code >-------------------------|
54 -- ---------------------------------------------------------------------------
55 -- {Start Of Comments}
56 --
57 -- Description:
58 -- Return the legislation code for a specific primary key value
59 --
60 -- Prerequisites:
61 -- The primary key identified by p_user_row_id
62 -- already exists.
63 --
64 -- In Arguments:
65 -- p_user_row_id
66 --
67 --
68 -- Post Success:
69 -- The business group's legislation code will be returned.
70 --
71 -- Post Failure:
72 -- An error is raised if the value does not exist.
73 --
74 -- Access Status:
75 -- Internal Development Use Only.
76 --
77 -- {End Of Comments}
78 -- ---------------------------------------------------------------------------
79 FUNCTION return_legislation_code
80 (p_user_row_id in number
81 ) RETURN varchar2;
82 --
83 --
84 -- ----------------------------------------------------------------------------
85 -- |---------------------------< insert_validate >----------------------------|
86 -- ----------------------------------------------------------------------------
87 -- {Start Of Comments}
88 --
89 -- Description:
90 -- This procedure controls the execution of all insert business rules
91 -- validation.
92 --
93 -- Prerequisites:
94 -- This private procedure is called from ins procedure.
95 --
96 -- In Parameters:
97 -- A Pl/Sql record structre.
98 --
99 -- Post Success:
100 -- Processing continues.
101 --
102 -- Post Failure:
103 -- If a business rules fails the error will not be handled by this procedure
104 -- unless explicity coded.
105 --
106 -- Developer Implementation Notes:
107 -- For insert, your business rules should be executed from this procedure and
108 -- should ideally (unless really necessary) just be straight procedure or
109 -- function calls. Try and avoid using conditional branching logic.
110 --
111 -- Access Status:
112 -- Internal Row Handler Use Only.
113 --
114 -- {End Of Comments}
115 -- ----------------------------------------------------------------------------
116 Procedure insert_validate
117 (p_rec in out nocopy pay_pur_shd.g_rec_type
118 ,p_effective_date in date
119 ,p_datetrack_mode in varchar2
120 ,p_validation_start_date in date
121 ,p_validation_end_date in date
122 ,p_disable_units_check in boolean
123 ,p_disable_range_overlap_check in boolean
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 out nocopy pay_pur_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 ,p_disable_units_check in boolean
165 ,p_disable_range_overlap_check in boolean
166 );
167 --
168 -- ----------------------------------------------------------------------------
169 -- |---------------------------< delete_validate >----------------------------|
170 -- ----------------------------------------------------------------------------
171 -- {Start Of Comments}
172 --
173 -- Description:
174 -- This procedure controls the execution of all delete business rules
175 -- validation.
176 --
177 -- Prerequisites:
178 -- This private procedure is called from del procedure.
179 --
180 -- In Parameters:
181 -- A Pl/Sql record structure.
182 --
183 -- Post Success:
184 -- Processing continues.
185 --
186 -- Post Failure:
187 -- If a business rules fails the error will not be handled by this procedure
188 -- unless explicity coded.
189 --
190 -- Developer Implementation Notes:
191 -- For delete, your business rules should be executed from this procedure and
192 -- should ideally (unless really necessary) just be straight procedure or
193 -- function calls. Try and avoid using conditional branching logic.
194 --
195 -- Access Status:
196 -- Internal Row Handler Use Only.
197 --
198 -- {End Of Comments}
199 -- ----------------------------------------------------------------------------
200 Procedure delete_validate
201 (p_rec in pay_pur_shd.g_rec_type
202 ,p_effective_date in date
203 ,p_datetrack_mode in varchar2
204 ,p_disable_range_overlap_check in boolean
205 ,p_validation_start_date in date
206 ,p_validation_end_date in date
207 );
208 --
209 end pay_pur_bus;
[Home] [Help]