1 Package psp_erd_shd as
2 /* $Header: PSPEDRHS.pls 120.3 2006/01/25 01:49 dpaudel noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (effort_report_detail_id number(15)
10 ,effort_report_id number(15)
11 ,object_version_number number(9)
12 ,assignment_id number(15)
13 ,assignment_number varchar2(30)
14 ,gl_sum_criteria_segment_name varchar2(2000)
15 ,gl_segment1 varchar2(25)
16 ,gl_segment2 varchar2(25)
17 ,gl_segment3 varchar2(25)
18 ,gl_segment4 varchar2(25)
19 ,gl_segment5 varchar2(25)
20 ,gl_segment6 varchar2(25)
21 ,gl_segment7 varchar2(25)
22 ,gl_segment8 varchar2(25)
23 ,gl_segment9 varchar2(25)
24 ,gl_segment10 varchar2(25)
25 ,gl_segment11 varchar2(25)
26 ,gl_segment12 varchar2(25)
27 ,gl_segment13 varchar2(25)
28 ,gl_segment14 varchar2(25)
29 ,gl_segment15 varchar2(25)
30 ,gl_segment16 varchar2(25)
31 ,gl_segment17 varchar2(25)
32 ,gl_segment18 varchar2(25)
33 ,gl_segment19 varchar2(25)
34 ,gl_segment20 varchar2(25)
35 ,gl_segment21 varchar2(25)
36 ,gl_segment22 varchar2(25)
37 ,gl_segment23 varchar2(25)
38 ,gl_segment24 varchar2(25)
39 ,gl_segment25 varchar2(25)
40 ,gl_segment26 varchar2(25)
41 ,gl_segment27 varchar2(25)
42 ,gl_segment28 varchar2(25)
43 ,gl_segment29 varchar2(25)
44 ,gl_segment30 varchar2(25)
45 ,project_id number(15)
46 ,project_number varchar2(25)
47 ,project_name varchar2(30)
48 ,expenditure_organization_id number(15)
49 ,exp_org_name varchar2(240)
50 ,expenditure_type varchar2(30)
51 ,task_id number(15)
52 ,task_number varchar2(25)
53 ,task_name varchar2(30)
54 ,award_id number(15)
55 ,award_number varchar2(240)
56 ,award_short_name varchar2(30)
57 ,actual_salary_amt number
58 ,payroll_percent number
59 ,proposed_salary_amt number
60 ,proposed_effort_percent number
61 ,committed_cost_share number
62 ,schedule_start_date date
63 ,schedule_end_date date
64 ,ame_transaction_id varchar2(50)
65 ,investigator_name varchar2(240)
66 ,investigator_person_id number(15)
67 ,investigator_org_name varchar2(240)
68 ,investigator_primary_org_id number(15)
69 ,value1 number
70 ,value2 number
71 ,value3 number
72 ,value4 number
73 ,value5 number
74 ,value6 number
75 ,value7 number
76 ,value8 number
77 ,value9 number
78 ,value10 number
79 ,attribute1 varchar2(1000)
80 ,attribute2 varchar2(1000)
81 ,attribute3 varchar2(1000)
82 ,attribute4 varchar2(1000)
83 ,attribute5 varchar2(1000)
84 ,attribute6 varchar2(1000)
85 ,attribute7 varchar2(1000)
86 ,attribute8 varchar2(1000)
87 ,attribute9 varchar2(1000)
88 ,attribute10 varchar2(1000)
89 ,grouping_category varchar2(30)
90 );
91 --
92 -- ----------------------------------------------------------------------------
93 -- | Global Definitions - Internal Development Use Only |
94 -- ----------------------------------------------------------------------------
95 --
96 g_old_rec g_rec_type; -- Global record definition
97 -- Global table name
98 g_tab_nam constant varchar2(30) := 'PSP_EFF_REPORT_DETAILS';
99 --
100 -- ----------------------------------------------------------------------------
101 -- |---------------------------< constraint_error >---------------------------|
102 -- ----------------------------------------------------------------------------
103 -- {Start Of Comments}
104 --
105 -- Description:
106 -- This procedure is called when a constraint has been violated (i.e.
107 -- The exception hr_api.check_integrity_violated,
108 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
109 -- hr_api.unique_integrity_violated has been raised).
110 -- The exceptions can only be raised as follows:
111 -- 1) A check constraint can only be violated during an INSERT or UPDATE
112 -- dml operation.
113 -- 2) A parent integrity constraint can only be violated during an
114 -- INSERT or UPDATE dml operation.
115 -- 3) A child integrity constraint can only be violated during an
116 -- DELETE dml operation.
117 -- 4) A unique integrity constraint can only be violated during INSERT or
118 -- UPDATE dml operation.
119 --
120 -- Prerequisites:
121 -- 1) Either hr_api.check_integrity_violated,
122 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
123 -- hr_api.unique_integrity_violated has been raised with the subsequent
124 -- stripping of the constraint name from the generated error message
125 -- text.
126 -- 2) Standalone validation test which corresponds with a constraint error.
127 --
128 -- In Parameter:
129 -- p_constraint_name is in upper format and is just the constraint name
130 -- (e.g. not prefixed by brackets, schema owner etc).
131 --
132 -- Post Success:
133 -- Development dependant.
134 --
135 -- Post Failure:
136 -- Developement dependant.
137 --
138 -- Developer Implementation Notes:
139 -- For each constraint being checked the hr system package failure message
140 -- has been generated as a template only. These system error messages should
141 -- be modified as required (i.e. change the system failure message to a user
142 -- friendly defined error message).
143 --
144 -- Access Status:
145 -- Internal Development Use Only.
146 --
147 -- {End Of Comments}
148 -- ----------------------------------------------------------------------------
149 Procedure constraint_error
150 (p_constraint_name in all_constraints.constraint_name%TYPE);
151 --
152 -- ----------------------------------------------------------------------------
153 -- |-----------------------------< api_updating >-----------------------------|
154 -- ----------------------------------------------------------------------------
155 -- {Start Of Comments}
156 --
157 -- Description:
158 -- This function is used to populate the g_old_rec record with the
159 -- current row from the database for the specified primary key
160 -- provided that the primary key exists and is valid and does not
161 -- already match the current g_old_rec. The function will always return
162 -- a TRUE value if the g_old_rec is populated with the current row.
163 -- A FALSE value will be returned if all of the primary key arguments
164 -- are null.
165 --
166 -- Prerequisites:
167 -- None.
168 --
169 -- In Parameters:
170 --
171 -- Post Success:
172 -- A value of TRUE will be returned indiciating that the g_old_rec
173 -- is current.
174 -- A value of FALSE will be returned if all of the primary key arguments
175 -- have a null value (this indicates that the row has not be inserted into
176 -- the Schema), and therefore could never have a corresponding row.
177 --
178 -- Post Failure:
179 -- A failure can only occur under two circumstances:
180 -- 1) The primary key is invalid (i.e. a row does not exist for the
181 -- specified primary key values).
182 -- 2) If an object_version_number exists but is NOT the same as the current
183 -- g_old_rec value.
184 --
185 -- Developer Implementation Notes:
186 -- None.
187 --
188 -- Access Status:
192 -- ----------------------------------------------------------------------------
189 -- Internal Development Use Only.
190 --
191 -- {End Of Comments}
193 Function api_updating
194 (p_effort_report_detail_id in number
195 ,p_object_version_number in number
196 ) Return Boolean;
197 --
198 -- ----------------------------------------------------------------------------
199 -- |---------------------------------< lck >----------------------------------|
200 -- ----------------------------------------------------------------------------
201 -- {Start of comments}
202 --
203 -- Description:
204 -- The Lck process has two main functions to perform. Firstly, the row to be
205 -- updated or deleted must be locked. The locking of the row will only be
206 -- successful if the row is not currently locked by another user.
210 --
207 -- Secondly, during the locking of the row, the row is selected into
208 -- the g_old_rec data structure which enables the current row values from
209 -- the server to be available to the api.
211 -- Prerequisites:
212 -- When attempting to call the lock the object version number (if defined)
213 -- is mandatory.
214 --
215 -- In Parameters:
216 -- The arguments to the Lck process are the primary key(s) which uniquely
217 -- identify the row and the object version number of row.
218 --
219 -- Post Success:
220 -- On successful completion of the Lck process the row to be updated or
221 -- deleted will be locked and selected into the global data structure
222 -- g_old_rec.
223 --
224 -- Post Failure:
225 -- The Lck process can fail for three reasons:
226 -- 1) When attempting to lock the row the row could already be locked by
227 -- another user. This will raise the HR_Api.Object_Locked exception.
228 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
229 -- This error is trapped and reported using the message name
230 -- 'HR_7220_INVALID_PRIMARY_KEY'.
231 -- 3) The row although existing in the HR Schema has a different object
232 -- version number than the object version number specified.
233 -- This error is trapped and reported using the message name
234 -- 'HR_7155_OBJECT_INVALID'.
235 --
236 -- Developer Implementation Notes:
237 -- For each primary key and the object version number arguments add a
238 -- call to hr_api.mandatory_arg_error procedure to ensure that these
239 -- argument values are not null.
240 --
241 -- Access Status:
242 -- Internal Development Use Only.
243 --
244 -- {End of comments}
245 -- ----------------------------------------------------------------------------
246 Procedure lck
247 (p_effort_report_detail_id in number
248 ,p_object_version_number in number
249 );
250 --
251 -- ----------------------------------------------------------------------------
252 -- |-----------------------------< convert_args >-----------------------------|
253 -- ----------------------------------------------------------------------------
254 -- {Start Of Comments}
255 --
256 -- Description:
257 -- This function is used to turn attribute parameters into the record
258 -- structure parameter g_rec_type.
259 --
260 -- Prerequisites:
261 -- This is a private function and can only be called from the ins or upd
262 -- attribute processes.
263 --
264 -- In Parameters:
265 --
266 -- Post Success:
267 -- A returning record structure will be returned.
268 --
269 -- Post Failure:
270 -- No direct error handling is required within this function. Any possible
271 -- errors within this function will be a PL/SQL value error due to
272 -- conversion of datatypes or data lengths.
273 --
274 -- Developer Implementation Notes:
275 -- None.
276 --
277 -- Access Status:
278 -- Internal Row Handler Use Only.
279 --
280 -- {End Of Comments}
281 -- ----------------------------------------------------------------------------
282 Function convert_args
283 (p_effort_report_detail_id in number
284 ,p_effort_report_id in number
285 ,p_object_version_number in number
286 ,p_assignment_id in number
287 ,p_assignment_number in varchar2
288 ,p_gl_sum_criteria_segment_name in varchar2
289 ,p_gl_segment1 in varchar2
290 ,p_gl_segment2 in varchar2
291 ,p_gl_segment3 in varchar2
292 ,p_gl_segment4 in varchar2
293 ,p_gl_segment5 in varchar2
294 ,p_gl_segment6 in varchar2
295 ,p_gl_segment7 in varchar2
299 ,p_gl_segment11 in varchar2
296 ,p_gl_segment8 in varchar2
297 ,p_gl_segment9 in varchar2
298 ,p_gl_segment10 in varchar2
300 ,p_gl_segment12 in varchar2
301 ,p_gl_segment13 in varchar2
302 ,p_gl_segment14 in varchar2
303 ,p_gl_segment15 in varchar2
304 ,p_gl_segment16 in varchar2
305 ,p_gl_segment17 in varchar2
306 ,p_gl_segment18 in varchar2
307 ,p_gl_segment19 in varchar2
308 ,p_gl_segment20 in varchar2
309 ,p_gl_segment21 in varchar2
310 ,p_gl_segment22 in varchar2
314 ,p_gl_segment26 in varchar2
311 ,p_gl_segment23 in varchar2
312 ,p_gl_segment24 in varchar2
313 ,p_gl_segment25 in varchar2
315 ,p_gl_segment27 in varchar2
316 ,p_gl_segment28 in varchar2
317 ,p_gl_segment29 in varchar2
318 ,p_gl_segment30 in varchar2
319 ,p_project_id in number
320 ,p_project_number in varchar2
321 ,p_project_name in varchar2
322 ,p_expenditure_organization_id in number
323 ,p_exp_org_name in varchar2
324 ,p_expenditure_type in varchar2
325 ,p_task_id in number
326 ,p_task_number in varchar2
327 ,p_task_name in varchar2
328 ,p_award_id in number
329 ,p_award_number in varchar2
330 ,p_award_short_name in varchar2
331 ,p_actual_salary_amt in number
332 ,p_payroll_percent in number
333 ,p_proposed_salary_amt in number
334 ,p_proposed_effort_percent in number
335 ,p_committed_cost_share in number
336 ,p_schedule_start_date in date
337 ,p_schedule_end_date in date
338 ,p_ame_transaction_id in varchar2
339 ,p_investigator_name in varchar2
340 ,p_investigator_person_id in number
341 ,p_investigator_org_name in varchar2
342 ,p_investigator_primary_org_id in number
343 ,p_value1 in number
344 ,p_value2 in number
345 ,p_value3 in number
346 ,p_value4 in number
347 ,p_value5 in number
348 ,p_value6 in number
349 ,p_value7 in number
350 ,p_value8 in number
351 ,p_value9 in number
352 ,p_value10 in number
353 ,p_attribute1 in varchar2
354 ,p_attribute2 in varchar2
355 ,p_attribute3 in varchar2
356 ,p_attribute4 in varchar2
357 ,p_attribute5 in varchar2
358 ,p_attribute6 in varchar2
359 ,p_attribute7 in varchar2
360 ,p_attribute8 in varchar2
361 ,p_attribute9 in varchar2
362 ,p_attribute10 in varchar2
363 ,p_grouping_category in varchar2
364 )
365 Return g_rec_type;
366 --
367 end psp_erd_shd;
[Home] [Help]