1 Package per_pst_shd as
2 /* $Header: pepstrhi.pkh 120.0 2005/05/31 15:38:36 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (position_structure_id number(15)
10 ,business_group_id number(15)
11 ,name varchar2(30)
12 ,comments varchar2(2000) -- pseudo column
13 ,primary_position_flag varchar2(30)
14 ,request_id number(15)
15 ,program_application_id number(15)
16 ,program_id number(15)
17 ,program_update_date date
18 ,attribute_category varchar2(30)
19 ,attribute1 varchar2(150)
20 ,attribute2 varchar2(150)
21 ,attribute3 varchar2(150)
22 ,attribute4 varchar2(150)
23 ,attribute5 varchar2(150)
24 ,attribute6 varchar2(150)
25 ,attribute7 varchar2(150)
26 ,attribute8 varchar2(150)
27 ,attribute9 varchar2(150)
28 ,attribute10 varchar2(150)
29 ,attribute11 varchar2(150)
30 ,attribute12 varchar2(150)
31 ,attribute13 varchar2(150)
32 ,attribute14 varchar2(150)
33 ,attribute15 varchar2(150)
34 ,attribute16 varchar2(150)
35 ,attribute17 varchar2(150)
36 ,attribute18 varchar2(150)
37 ,attribute19 varchar2(150)
38 ,attribute20 varchar2(150)
39 ,object_version_number number(9)
40 );
41 --
42 -- ----------------------------------------------------------------------------
43 -- | Global Definitions - Internal Development Use Only |
44 -- ----------------------------------------------------------------------------
45 --
46 g_old_rec g_rec_type; -- Global record definition
47 g_api_dml boolean; -- Global api dml status
48 --
49 -- ----------------------------------------------------------------------------
50 -- |------------------------< return_api_dml_status >-------------------------|
51 -- ----------------------------------------------------------------------------
52 -- {Start Of Comments}
53 --
54 -- Description:
55 -- This function will return the current g_api_dml private global
56 -- boolean status.
57 -- The g_api_dml status determines if at the time of the function
58 -- being executed if a dml statement (i.e. INSERT, UPDATE or DELETE)
59 -- is being issued from within an api.
60 -- If the status is TRUE then a dml statement is being issued from
61 -- within this entity api.
62 -- This function is primarily to support database triggers which
63 -- need to maintain the object_version_number for non-supported
64 -- dml statements (i.e. dml statement issued outside of the api layer).
65 --
66 -- Prerequisites:
67 -- None.
68 --
69 -- In Parameters:
70 -- None.
71 --
72 -- Post Success:
73 -- Processing continues.
74 -- If the function returns a TRUE value then, dml is being executed from
75 -- within this api.
76 --
77 -- Post Failure:
78 -- None.
79 --
80 -- Access Status:
81 -- Internal Row Handler Use Only.
82 --
83 -- {End Of Comments}
84 -- ----------------------------------------------------------------------------
85 Function return_api_dml_status Return Boolean;
86 --
87 -- ----------------------------------------------------------------------------
88 -- |---------------------------< constraint_error >---------------------------|
89 -- ----------------------------------------------------------------------------
90 -- {Start Of Comments}
91 --
92 -- Description:
93 -- This procedure is called when a constraint has been violated (i.e.
94 -- The exception hr_api.check_integrity_violated,
95 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
96 -- hr_api.unique_integrity_violated has been raised).
97 -- The exceptions can only be raised as follows:
98 -- 1) A check constraint can only be violated during an INSERT or UPDATE
99 -- dml operation.
100 -- 2) A parent integrity constraint can only be violated during an
101 -- INSERT or UPDATE dml operation.
102 -- 3) A child integrity constraint can only be violated during an
103 -- DELETE dml operation.
104 -- 4) A unique integrity constraint can only be violated during INSERT or
105 -- UPDATE dml operation.
106 --
107 -- Prerequisites:
108 -- 1) Either hr_api.check_integrity_violated,
109 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
110 -- hr_api.unique_integrity_violated has been raised with the subsequent
111 -- stripping of the constraint name from the generated error message
112 -- text.
113 -- 2) Standalone validation test which corresponds with a constraint error.
114 --
115 -- In Parameter:
116 -- p_constraint_name is in upper format and is just the constraint name
117 -- (e.g. not prefixed by brackets, schema owner etc).
118 --
119 -- Post Success:
120 -- Development dependant.
121 --
122 -- Post Failure:
123 -- Developement dependant.
124 --
125 -- Developer Implementation Notes:
126 -- For each constraint being checked the hr system package failure message
127 -- has been generated as a template only. These system error messages should
128 -- be modified as required (i.e. change the system failure message to a user
129 -- friendly defined error message).
130 --
131 -- Access Status:
132 -- Internal Development Use Only.
133 --
134 -- {End Of Comments}
135 -- ----------------------------------------------------------------------------
136 Procedure constraint_error
137 (p_constraint_name in all_constraints.constraint_name%TYPE);
138 --
139 -- ----------------------------------------------------------------------------
140 -- |-----------------------------< api_updating >-----------------------------|
141 -- ----------------------------------------------------------------------------
142 -- {Start Of Comments}
143 --
144 -- Description:
145 -- This function is used to populate the g_old_rec record with the
146 -- current row from the database for the specified primary key
147 -- provided that the primary key exists and is valid and does not
148 -- already match the current g_old_rec. The function will always return
149 -- a TRUE value if the g_old_rec is populated with the current row.
150 -- A FALSE value will be returned if all of the primary key arguments
151 -- are null.
152 --
153 -- Prerequisites:
154 -- None.
155 --
156 -- In Parameters:
157 --
158 -- Post Success:
159 -- A value of TRUE will be returned indiciating that the g_old_rec
160 -- is current.
161 -- A value of FALSE will be returned if all of the primary key arguments
162 -- have a null value (this indicates that the row has not be inserted into
163 -- the Schema), and therefore could never have a corresponding row.
164 --
165 -- Post Failure:
166 -- A failure can only occur under two circumstances:
167 -- 1) The primary key is invalid (i.e. a row does not exist for the
168 -- specified primary key values).
169 -- 2) If an object_version_number exists but is NOT the same as the current
170 -- g_old_rec value.
171 --
172 -- Developer Implementation Notes:
173 -- None.
174 --
175 -- Access Status:
176 -- Internal Development Use Only.
177 --
178 -- {End Of Comments}
179 -- ----------------------------------------------------------------------------
180 Function api_updating
181 (p_position_structure_id in number
182 ,p_object_version_number in number
183 ) Return Boolean;
184 --
185 -- ----------------------------------------------------------------------------
186 -- |---------------------------------< lck >----------------------------------|
187 -- ----------------------------------------------------------------------------
188 -- {Start of comments}
189 --
190 -- Description:
191 -- The Lck process has two main functions to perform. Firstly, the row to be
192 -- updated or deleted must be locked. The locking of the row will only be
193 -- successful if the row is not currently locked by another user.
194 -- Secondly, during the locking of the row, the row is selected into
195 -- the g_old_rec data structure which enables the current row values from
196 -- the server to be available to the api.
197 --
198 -- Prerequisites:
199 -- When attempting to call the lock the object version number (if defined)
200 -- is mandatory.
201 --
202 -- In Parameters:
203 -- The arguments to the Lck process are the primary key(s) which uniquely
204 -- identify the row and the object version number of row.
205 --
206 -- Post Success:
207 -- On successful completion of the Lck process the row to be updated or
208 -- deleted will be locked and selected into the global data structure
209 -- g_old_rec.
210 --
211 -- Post Failure:
212 -- The Lck process can fail for three reasons:
213 -- 1) When attempting to lock the row the row could already be locked by
214 -- another user. This will raise the HR_Api.Object_Locked exception.
215 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
216 -- This error is trapped and reported using the message name
217 -- 'HR_7220_INVALID_PRIMARY_KEY'.
218 -- 3) The row although existing in the HR Schema has a different object
219 -- version number than the object version number specified.
220 -- This error is trapped and reported using the message name
221 -- 'HR_7155_OBJECT_INVALID'.
222 --
223 -- Developer Implementation Notes:
224 -- For each primary key and the object version number arguments add a
225 -- call to hr_api.mandatory_arg_error procedure to ensure that these
226 -- argument values are not null.
227 --
228 -- Access Status:
229 -- Internal Development Use Only.
230 --
231 -- {End of comments}
232 -- ----------------------------------------------------------------------------
233 Procedure lck
234 (p_position_structure_id in number
235 ,p_object_version_number in number
236 );
237 --
238 -- ----------------------------------------------------------------------------
239 -- |-----------------------------< convert_args >-----------------------------|
240 -- ----------------------------------------------------------------------------
241 -- {Start Of Comments}
242 --
243 -- Description:
244 -- This function is used to turn attribute parameters into the record
245 -- structure parameter g_rec_type.
246 --
247 -- Prerequisites:
248 -- This is a private function and can only be called from the ins or upd
249 -- attribute processes.
250 --
251 -- In Parameters:
252 --
253 -- Post Success:
254 -- A returning record structure will be returned.
255 --
256 -- Post Failure:
257 -- No direct error handling is required within this function. Any possible
258 -- errors within this function will be a PL/SQL value error due to
259 -- conversion of datatypes or data lengths.
260 --
261 -- Developer Implementation Notes:
262 -- None.
263 --
264 -- Access Status:
265 -- Internal Row Handler Use Only.
266 --
267 -- {End Of Comments}
268 -- ----------------------------------------------------------------------------
269 Function convert_args
270 (p_position_structure_id in number
271 ,p_business_group_id in number
272 ,p_name in varchar2
273 ,p_comments in varchar2
274 ,p_primary_position_flag in varchar2
275 ,p_request_id in number
276 ,p_program_application_id in number
277 ,p_program_id in number
278 ,p_program_update_date in date
279 ,p_attribute_category in varchar2
280 ,p_attribute1 in varchar2
281 ,p_attribute2 in varchar2
282 ,p_attribute3 in varchar2
283 ,p_attribute4 in varchar2
284 ,p_attribute5 in varchar2
285 ,p_attribute6 in varchar2
286 ,p_attribute7 in varchar2
287 ,p_attribute8 in varchar2
288 ,p_attribute9 in varchar2
289 ,p_attribute10 in varchar2
290 ,p_attribute11 in varchar2
291 ,p_attribute12 in varchar2
292 ,p_attribute13 in varchar2
293 ,p_attribute14 in varchar2
294 ,p_attribute15 in varchar2
295 ,p_attribute16 in varchar2
296 ,p_attribute17 in varchar2
297 ,p_attribute18 in varchar2
298 ,p_attribute19 in varchar2
299 ,p_attribute20 in varchar2
300 ,p_object_version_number in number
301 )
302 Return g_rec_type;
303 --
304 end per_pst_shd;
[Home] [Help]