1 Package per_pji_shd as
2 /* $Header: pepjirhi.pkh 120.0 2005/05/31 14:22:49 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (previous_job_extra_info_id number(15)
10 ,previous_job_id number(15)
11 ,information_type varchar2(40)
12 ,pji_attribute_category varchar2(30)
13 ,pji_attribute1 varchar2(150)
14 ,pji_attribute2 varchar2(150)
15 ,pji_attribute3 varchar2(150)
16 ,pji_attribute4 varchar2(150)
17 ,pji_attribute5 varchar2(150)
18 ,pji_attribute6 varchar2(150)
19 ,pji_attribute7 varchar2(150)
20 ,pji_attribute8 varchar2(150)
21 ,pji_attribute9 varchar2(150)
22 ,pji_attribute10 varchar2(150)
23 ,pji_attribute11 varchar2(150)
24 ,pji_attribute12 varchar2(150)
25 ,pji_attribute13 varchar2(150)
26 ,pji_attribute14 varchar2(150)
27 ,pji_attribute15 varchar2(150)
28 ,pji_attribute16 varchar2(150)
29 ,pji_attribute17 varchar2(150)
30 ,pji_attribute18 varchar2(150)
31 ,pji_attribute19 varchar2(150)
32 ,pji_attribute20 varchar2(150)
33 ,pji_attribute21 varchar2(150)
34 ,pji_attribute22 varchar2(150)
35 ,pji_attribute23 varchar2(150)
36 ,pji_attribute24 varchar2(150)
37 ,pji_attribute25 varchar2(150)
38 ,pji_attribute26 varchar2(150)
39 ,pji_attribute27 varchar2(150)
40 ,pji_attribute28 varchar2(150)
41 ,pji_attribute29 varchar2(150)
42 ,pji_attribute30 varchar2(150)
43 ,pji_information_category varchar2(30)
44 ,pji_information1 varchar2(150)
45 ,pji_information2 varchar2(150)
46 ,pji_information3 varchar2(150)
47 ,pji_information4 varchar2(150)
48 ,pji_information5 varchar2(150)
49 ,pji_information6 varchar2(150)
50 ,pji_information7 varchar2(150)
51 ,pji_information8 varchar2(150)
52 ,pji_information9 varchar2(150)
53 ,pji_information10 varchar2(150)
54 ,pji_information11 varchar2(150)
55 ,pji_information12 varchar2(150)
56 ,pji_information13 varchar2(150)
57 ,pji_information14 varchar2(150)
58 ,pji_information15 varchar2(150)
59 ,pji_information16 varchar2(150)
60 ,pji_information17 varchar2(150)
61 ,pji_information18 varchar2(150)
62 ,pji_information19 varchar2(150)
63 ,pji_information20 varchar2(150)
64 ,pji_information21 varchar2(150)
65 ,pji_information22 varchar2(150)
66 ,pji_information23 varchar2(150)
67 ,pji_information24 varchar2(150)
68 ,pji_information25 varchar2(150)
69 ,pji_information26 varchar2(150)
70 ,pji_information27 varchar2(150)
71 ,pji_information28 varchar2(150)
72 ,pji_information29 varchar2(150)
73 ,pji_information30 varchar2(150)
74 ,object_version_number number(9)
75 );
76 --
77 -- ----------------------------------------------------------------------------
78 -- | Global Definitions - Internal Development Use Only |
79 -- ----------------------------------------------------------------------------
80 --
81 g_old_rec g_rec_type; -- Global record definition
82 --
83 -- ----------------------------------------------------------------------------
84 -- |---------------------------< constraint_error >---------------------------|
85 -- ----------------------------------------------------------------------------
86 -- {Start Of Comments}
87 --
88 -- Description:
89 -- This procedure is called when a constraint has been violated (i.e.
90 -- The exception hr_api.check_integrity_violated,
91 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
92 -- hr_api.unique_integrity_violated has been raised).
93 -- The exceptions can only be raisedi as follows:
94 -- 1) A check constraint can only be violated during an INSERT or UPDATE
95 -- dml operation.
96 -- 2) A parent integrity constraint can only be violated during an
97 -- INSERT or UPDATE dml operation.
98 -- 3) A child integrity constraint can only be violated during an
99 -- DELETE dml operation.
100 -- 4) A unique integrity constraint can only be violated during INSERT or
101 -- UPDATE dml operation.
102 --
103 -- Prerequisites:
104 -- 1) Either hr_api.check_integrity_violated,
105 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
106 -- hr_api.unique_integrity_violated has been raised with the subsequent
107 -- stripping of the constraint name from the generated error message
108 -- text.
109 -- 2) Standalone validation test which corresponds with a constraint error.
110 --
111 -- In Parameter:
112 -- p_constraint_name is in upper format and is just the constraint name
113 -- (e.g. not prefixed by brackets, schema owner etc).
114 --
115 -- Post Success:
116 -- Development dependant.
117 --
118 -- Post Failure:
119 -- Developement dependant.
120 --
121 -- Developer Implementation Notes:
122 -- For each constraint being checked the hr system package failure message
123 -- has been generated as a template only. These system error messages should
124 -- be modified as required (i.e. change the system failure message to a user
125 -- friendly defined error message).
126 --
127 -- Access Status:
128 -- Internal Development Use Only.
129 --
130 -- {End Of Comments}
131 -- ----------------------------------------------------------------------------
132 Procedure constraint_error
133 (p_constraint_name in all_constraints.constraint_name%TYPE);
134 --
135 -- ----------------------------------------------------------------------------
136 -- |-----------------------------< api_updating >-----------------------------|
137 -- ----------------------------------------------------------------------------
138 -- {Start Of Comments}
139 --
140 -- Description:
141 -- This function is used to populate the g_old_rec record with the
142 -- current row from the database for the specified primary key
143 -- provided that the primary key exists and is valid and does not
144 -- already match the current g_old_rec. The function will always return
145 -- a TRUE value if the g_old_rec is populated with the current row.
146 -- A FALSE value will be returned if all of the primary key arguments
147 -- are null.
148 --
149 -- Prerequisites:
150 -- None.
151 --
152 -- In Parameters:
153 --
154 -- Post Success:
155 -- A value of TRUE will be returned indiciating that the g_old_rec
156 -- is current.
157 -- A value of FALSE will be returned if all of the primary key arguments
158 -- have a null value (this indicates that the row has not be inserted into
159 -- the Schema), and therefore could never have a corresponding row.
160 --
161 -- Post Failure:
162 -- A failure can only occur under two circumstances:
163 -- 1) The primary key is invalid (i.e. a row does not exist for the
164 -- specified primary key values).
165 -- 2) If an object_version_number exists but is NOT the same as the current
166 -- g_old_rec value.
167 --
168 -- Developer Implementation Notes:
169 -- None.
170 --
171 -- Access Status:
172 -- Internal Development Use Only.
173 --
174 -- {End Of Comments}
175 -- ----------------------------------------------------------------------------
176 Function api_updating
177 (p_previous_job_extra_info_id in number
178 ,p_object_version_number in number
179 ) Return Boolean;
180 --
181 -- ----------------------------------------------------------------------------
182 -- |---------------------------------< lck >----------------------------------|
183 -- ----------------------------------------------------------------------------
184 -- {Start of comments}
185 --
186 -- Description:
187 -- The Lck process has two main functions to perform. Firstly, the row to be
188 -- updated or deleted must be locked. The locking of the row will only be
189 -- successful if the row is not currently locked by another user.
190 -- Secondly, during the locking of the row, the row is selected into
191 -- the g_old_rec data structure which enables the current row values from
192 -- the server to be available to the api.
193 --
194 -- Prerequisites:
195 -- When attempting to call the lock the object version number (if defined)
196 -- is mandatory.
197 --
198 -- In Parameters:
199 -- The arguments to the Lck process are the primary key(s) which uniquely
200 -- identify the row and the object version number of row.
201 --
202 -- Post Success:
203 -- On successful completion of the Lck process the row to be updated or
204 -- deleted will be locked and selected into the global data structure
205 -- g_old_rec.
206 --
207 -- Post Failure:
208 -- The Lck process can fail for three reasons:
209 -- 1) When attempting to lock the row the row could already be locked by
210 -- another user. This will raise the HR_Api.Object_Locked exception.
211 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
212 -- This error is trapped and reported using the message name
213 -- 'HR_7220_INVALID_PRIMARY_KEY'.
214 -- 3) The row although existing in the HR Schema has a different object
215 -- version number than the object version number specified.
216 -- This error is trapped and reported using the message name
217 -- 'HR_7155_OBJECT_INVALID'.
218 --
219 -- Developer Implementation Notes:
220 -- For each primary key and the object version number arguments add a
221 -- call to hr_api.mandatory_arg_error procedure to ensure that these
222 -- argument values are not null.
223 --
224 -- Access Status:
225 -- Internal Development Use Only.
226 --
227 -- {End of comments}
228 -- ----------------------------------------------------------------------------
229 Procedure lck
230 (p_previous_job_extra_info_id in number
231 ,p_object_version_number in number
232 );
233 --
234 -- ----------------------------------------------------------------------------
235 -- |-----------------------------< convert_args >-----------------------------|
236 -- ----------------------------------------------------------------------------
237 -- {Start Of Comments}
238 --
239 -- Description:
240 -- This function is used to turn attribute parameters into the record
241 -- structure parameter g_rec_type.
242 --
243 -- Prerequisites:
244 -- This is a private function and can only be called from the ins or upd
245 -- attribute processes.
246 --
247 -- In Parameters:
248 --
249 -- Post Success:
250 -- A returning record structure will be returned.
251 --
252 -- Post Failure:
253 -- No direct error handling is required within this function. Any possible
254 -- errors within this function will be a PL/SQL value error due to
255 -- conversion of datatypes or data lengths.
256 --
257 -- Developer Implementation Notes:
258 -- None.
259 --
260 -- Access Status:
261 -- Internal Row Handler Use Only.
262 --
263 -- {End Of Comments}
264 -- ----------------------------------------------------------------------------
265 Function convert_args
266 (p_previous_job_extra_info_id in number
267 ,p_previous_job_id in number
268 ,p_information_type in varchar2
269 ,p_pji_attribute_category in varchar2
270 ,p_pji_attribute1 in varchar2
271 ,p_pji_attribute2 in varchar2
272 ,p_pji_attribute3 in varchar2
273 ,p_pji_attribute4 in varchar2
274 ,p_pji_attribute5 in varchar2
275 ,p_pji_attribute6 in varchar2
276 ,p_pji_attribute7 in varchar2
277 ,p_pji_attribute8 in varchar2
278 ,p_pji_attribute9 in varchar2
279 ,p_pji_attribute10 in varchar2
280 ,p_pji_attribute11 in varchar2
281 ,p_pji_attribute12 in varchar2
282 ,p_pji_attribute13 in varchar2
283 ,p_pji_attribute14 in varchar2
284 ,p_pji_attribute15 in varchar2
285 ,p_pji_attribute16 in varchar2
286 ,p_pji_attribute17 in varchar2
287 ,p_pji_attribute18 in varchar2
288 ,p_pji_attribute19 in varchar2
289 ,p_pji_attribute20 in varchar2
290 ,p_pji_attribute21 in varchar2
291 ,p_pji_attribute22 in varchar2
292 ,p_pji_attribute23 in varchar2
293 ,p_pji_attribute24 in varchar2
294 ,p_pji_attribute25 in varchar2
295 ,p_pji_attribute26 in varchar2
296 ,p_pji_attribute27 in varchar2
297 ,p_pji_attribute28 in varchar2
298 ,p_pji_attribute29 in varchar2
299 ,p_pji_attribute30 in varchar2
300 ,p_pji_information_category in varchar2
301 ,p_pji_information1 in varchar2
302 ,p_pji_information2 in varchar2
303 ,p_pji_information3 in varchar2
304 ,p_pji_information4 in varchar2
305 ,p_pji_information5 in varchar2
306 ,p_pji_information6 in varchar2
307 ,p_pji_information7 in varchar2
308 ,p_pji_information8 in varchar2
309 ,p_pji_information9 in varchar2
310 ,p_pji_information10 in varchar2
311 ,p_pji_information11 in varchar2
312 ,p_pji_information12 in varchar2
313 ,p_pji_information13 in varchar2
314 ,p_pji_information14 in varchar2
315 ,p_pji_information15 in varchar2
316 ,p_pji_information16 in varchar2
317 ,p_pji_information17 in varchar2
318 ,p_pji_information18 in varchar2
319 ,p_pji_information19 in varchar2
320 ,p_pji_information20 in varchar2
321 ,p_pji_information21 in varchar2
322 ,p_pji_information22 in varchar2
323 ,p_pji_information23 in varchar2
324 ,p_pji_information24 in varchar2
325 ,p_pji_information25 in varchar2
326 ,p_pji_information26 in varchar2
327 ,p_pji_information27 in varchar2
328 ,p_pji_information28 in varchar2
329 ,p_pji_information29 in varchar2
330 ,p_pji_information30 in varchar2
331 ,p_object_version_number in number
332 )
333 Return g_rec_type;
334 --
335 end per_pji_shd;
[Home] [Help]