1 package PAY_ASSG_COST_SS as
2 /* $Header: pyacosss.pkh 120.0.12010000.2 2008/11/29 21:26:33 pgongada noship $ */
3 -- ----------------------------------------------------------------------------
4 -- |----------------------------< CREATE_ASSG_COST >--------------------------|
5 -- ----------------------------------------------------------------------------
6 -- {Start Of Comments}
7 --
8 -- Description:
9 -- This API creates transaction and stores the costing KFF data into
10 -- transaction tables
11 --
12 -- Prerequisites:
13 -- The transaction must exist.
14 --
15 -- In Parameters:
16 -- Name Reqd Type Description
17 -- p_validate no boolean If true, then validation alone will be performed and
18 -- the database will remain unchanged. If false and all
19 -- validation checks pass, then the database will be modified.
20 -- p_item_type Yes varchar2 Identifies Item type
21 -- p_item_key Yes varchar2 Identifies Item key
22 -- p_actid Yes number The ID number of the activity that this procedure is
23 -- called from.
24 -- p_login_person_id Yes number Login ID of the user.
25 -- p_effective_date Yes Date Effective Date
26 -- p_assignment_id Yes number Assignment id of the person whose costing is getting created/changed
27 -- p_business_group_id Yes number Business Group ID
28 -- p_proportion Yes number Proportion
29 -- p_segment1 No varchar2 Segment1 value
30 -- p_segment2 No varchar2 Segment2 value
31 -- p_segment3 No varchar2 Segment3 value
32 -- p_segment4 No varchar2 Segment4 value
33 -- p_segment5 No varchar2 Segment5 value
34 -- p_segment6 No varchar2 Segment6 value
35 -- p_segment7 No varchar2 Segment7 value
36 -- p_segment8 No varchar2 Segment8 value
37 -- p_segment9 No varchar2 Segment9 value
38 -- p_segment10 No varchar2 Segment10 value
39 -- p_segment11 No varchar2 Segment11 value
40 -- p_segment12 No varchar2 Segment12 value
41 -- p_segment13 No varchar2 Segment13 value
42 -- p_segment14 No varchar2 Segment14 value
43 -- p_segment15 No varchar2 Segment15 value
44 -- p_segment16 No varchar2 Segment16 value
45 -- p_segment17 No varchar2 Segment17 value
46 -- p_segment18 No varchar2 Segment18 value
47 -- p_segment19 No varchar2 Segment19 value
48 -- p_segment20 No varchar2 Segment20 value
49 -- p_segment21 No varchar2 Segment21 value
50 -- p_segment22 No varchar2 Segment22 value
51 -- p_segment23 No varchar2 Segment23 value
52 -- p_segment24 No varchar2 Segment24 value
53 -- p_segment25 No varchar2 Segment25 value
54 -- p_segment26 No varchar2 Segment26 value
55 -- p_segment27 No varchar2 Segment27 value
56 -- p_segment28 No varchar2 Segment28 value
57 -- p_segment29 No varchar2 Segment29 value
58 -- p_segment30 No varchar2 Segment30 value
59 -- p_cost_allocation_keyflex_id Yes Number Cost allocation keyflex id
60 --
61 -- Post Success:
65 -- Out Parameters:
62 -- A transaction will be created and the values into the transaction tables
63 -- as well. It sets the following out parameters.
64 --
66 -- p_trasaction_id Number Identifies the transaction created.
67 -- p_transaction_step_id Number Identifies the transaction step created.
68 --
69 -- Post Failure:
70 -- An exception is raised and nothing will be created.
71 --
72 -- Access Status:
73 -- Internal Development Use Only.
74 --
75 -- {End Of Comments}
76 --
77 PROCEDURE CREATE_ASSG_COST(
78 P_ITEM_TYPE IN VARCHAR2
79 ,P_ITEM_KEY IN VARCHAR2
80 ,P_ACTID IN NUMBER
81 ,P_LOGIN_PERSON_ID IN NUMBER
82 ,P_EFFECTIVE_DATE IN DATE
83 ,P_ASSIGNMENT_ID IN NUMBER
84 ,P_BUSINESS_GROUP_ID IN NUMBER
85 ,P_PROPORTION IN NUMBER
86 ,P_COST_ALLOCATION_KEYFLEX_ID IN NUMBER
87 ,P_SEGMENT1 IN VARCHAR2 DEFAULT NULL
88 ,P_SEGMENT2 IN VARCHAR2 DEFAULT NULL
89 ,P_SEGMENT3 IN VARCHAR2 DEFAULT NULL
90 ,P_SEGMENT4 IN VARCHAR2 DEFAULT NULL
91 ,P_SEGMENT5 IN VARCHAR2 DEFAULT NULL
92 ,P_SEGMENT6 IN VARCHAR2 DEFAULT NULL
93 ,P_SEGMENT7 IN VARCHAR2 DEFAULT NULL
94 ,P_SEGMENT8 IN VARCHAR2 DEFAULT NULL
95 ,P_SEGMENT9 IN VARCHAR2 DEFAULT NULL
96 ,P_SEGMENT10 IN VARCHAR2 DEFAULT NULL
97 ,P_SEGMENT11 IN VARCHAR2 DEFAULT NULL
98 ,P_SEGMENT12 IN VARCHAR2 DEFAULT NULL
99 ,P_SEGMENT13 IN VARCHAR2 DEFAULT NULL
100 ,P_SEGMENT14 IN VARCHAR2 DEFAULT NULL
101 ,P_SEGMENT15 IN VARCHAR2 DEFAULT NULL
102 ,P_SEGMENT16 IN VARCHAR2 DEFAULT NULL
103 ,P_SEGMENT17 IN VARCHAR2 DEFAULT NULL
104 ,P_SEGMENT18 IN VARCHAR2 DEFAULT NULL
105 ,P_SEGMENT19 IN VARCHAR2 DEFAULT NULL
106 ,P_SEGMENT20 IN VARCHAR2 DEFAULT NULL
107 ,P_SEGMENT21 IN VARCHAR2 DEFAULT NULL
108 ,P_SEGMENT22 IN VARCHAR2 DEFAULT NULL
109 ,P_SEGMENT23 IN VARCHAR2 DEFAULT NULL
110 ,P_SEGMENT24 IN VARCHAR2 DEFAULT NULL
111 ,P_SEGMENT25 IN VARCHAR2 DEFAULT NULL
112 ,P_SEGMENT26 IN VARCHAR2 DEFAULT NULL
113 ,P_SEGMENT27 IN VARCHAR2 DEFAULT NULL
114 ,P_SEGMENT28 IN VARCHAR2 DEFAULT NULL
115 ,P_SEGMENT29 IN VARCHAR2 DEFAULT NULL
116 ,P_SEGMENT30 IN VARCHAR2 DEFAULT NULL
117 ,P_CONCATENATED_SEGMENTS IN VARCHAR2 DEFAULT NULL
118 ,P_EFFECTIVE_START_DATE IN DATE DEFAULT NULL
119 ,P_EFFECTIVE_END_DATE IN DATE DEFAULT NULL
120 ,P_TRANSACTION_ID OUT NOCOPY NUMBER
121 ,P_TRANSACTION_STEP_ID OUT NOCOPY NUMBER
122 );
123 -- ----------------------------------------------------------------------------
124 -- |----------------------------< CREATE_DATA >-------------------------------|
125 -- ----------------------------------------------------------------------------
126 -- {Start Of Comments}
127 --
128 -- Description:
129 -- This API creates data into base tables PAY_COST_ALLOCATIONS_F,
130 -- PAY_COST_ALLOCATION_KEYFLEX.
131 --
132 -- Prerequisites:
133 -- The transaction must exist.
134 --
135 -- In Parameters:
136 -- Name Reqd Type Description
137 -- p_validate no boolean If true, then validation alone will be performed and
138 -- the database will remain unchanged. If false and all
139 -- validation checks pass, then the database will be modified.
140 -- p_transaction_step_id Yes Number Identifies the transaction id.
141 -- p_effective_date No Date Identifies the effective date
142 --
143 -- Post Success:
144 -- The data will be created in PAY_COST_ALLOCATIONS_F, PAY_COST_ALLOCATION_KEYFLEX
145 -- It also updated the workflow table with the detials.
146 --
147 --
148 -- Post Failure:
149 -- An exception is raised and nothing will be created.
150 --
151 -- Access Status:
152 -- Internal Development Use Only.
153 --
154 -- {End Of Comments}
155 --
156 PROCEDURE CREATE_DATA(
157 p_validate in boolean default false
158 ,p_transaction_step_id in number
159 );
160 -- ----------------------------------------------------------------------------
161 -- |----------------------------< UPDATE_ASSG_COST >--------------------------|
162 -- ----------------------------------------------------------------------------
163 -- {Start Of Comments}
164 --
165 -- Description:
166 -- This API creates transaction and stores the costing KFF data into
167 -- transaction tables
168 --
169 -- Prerequisites:
170 -- The transaction must exist.
171 --
172 -- In Parameters:
173 -- Name Reqd Type Description
174 -- p_validate no boolean If true, then validation alone will be performed and
175 -- the database will remain unchanged. If false and all
176 -- validation checks pass, then the database will be modified.
180 -- p_login_person_id Yes number Login ID of the user.
177 -- p_item_type Yes varchar2 Identifies Item type
178 -- p_item_key Yes varchar2 Identifies Item key
179 -- p_actid in number
181 -- p_effective_date Yes Date Effective Date
182 -- p_assignment_id Yes number Assignment id of the person whose costing is getting changed
183 -- p_business_group_id Yes number Business Group ID
184 -- p_proportion No number Proportion
185 -- p_cost_allocation_id Yes number Identifies which cost allocation to be changed.
186 -- p_cost_allocation_keyflex_id Yes number Identifies the cost keyflex id.
187 -- p_object_version_number Yes number Object version number
188 -- p_segment1 No varchar2 Segment1 value
189 -- p_segment2 No varchar2 Segment2 value
190 -- p_segment3 No varchar2 Segment3 value
191 -- p_segment4 No varchar2 Segment4 value
192 -- p_segment5 No varchar2 Segment5 value
193 -- p_segment6 No varchar2 Segment6 value
194 -- p_segment7 No varchar2 Segment7 value
195 -- p_segment8 No varchar2 Segment8 value
196 -- p_segment9 No varchar2 Segment9 value
197 -- p_segment10 No varchar2 Segment10 value
198 -- p_segment11 No varchar2 Segment11 value
199 -- p_segment12 No varchar2 Segment12 value
200 -- p_segment13 No varchar2 Segment13 value
201 -- p_segment14 No varchar2 Segment14 value
202 -- p_segment15 No varchar2 Segment15 value
203 -- p_segment16 No varchar2 Segment16 value
204 -- p_segment17 No varchar2 Segment17 value
205 -- p_segment18 No varchar2 Segment18 value
206 -- p_segment19 No varchar2 Segment19 value
207 -- p_segment20 No varchar2 Segment20 value
208 -- p_segment21 No varchar2 Segment21 value
209 -- p_segment22 No varchar2 Segment22 value
210 -- p_segment23 No varchar2 Segment23 value
211 -- p_segment24 No varchar2 Segment24 value
212 -- p_segment25 No varchar2 Segment25 value
213 -- p_segment26 No varchar2 Segment26 value
214 -- p_segment27 No varchar2 Segment27 value
215 -- p_segment28 No varchar2 Segment28 value
216 -- p_segment29 No varchar2 Segment29 value
217 -- p_segment30 No varchar2 Segment30 value
218 --
219 -- Post Success:
220 -- A transaction will be created and the values into the transaction tables
221 -- as well. It sets the following out parameters.
222 --
223 -- Out Parameters:
224 -- p_trasaction_id Number Identifies the transaction created.
225 -- p_transaction_step_id Number Identifies the transaction step created.
226 --
227 -- Post Failure:
228 -- An exception is raised and nothing will be created.
229 --
230 -- Access Status:
231 -- Internal Development Use Only.
232 --
233 -- {End Of Comments}
234 --
235 PROCEDURE UPDATE_ASSG_COST(
236 P_ITEM_TYPE IN VARCHAR2
237 ,P_ITEM_KEY IN VARCHAR2
238 ,P_ACTID IN NUMBER
239 ,P_LOGIN_PERSON_ID IN NUMBER
240 ,P_UPDATE_MODE IN VARCHAR2 DEFAULT 'UPDATE'
241 ,P_EFFECTIVE_DATE IN DATE DEFAULT SYSDATE
242 ,P_ASSIGNMENT_ID IN NUMBER
243 ,P_COST_ALLOCATION_ID IN NUMBER
244 ,P_BUSINESS_GROUP_ID IN NUMBER
245 ,P_COST_ALLOCATION_KEYFLEX_ID IN NUMBER
246 ,P_OBJECT_VERSION_NUMBER IN NUMBER
247 ,P_PROPORTION IN NUMBER default hr_api.g_number
248 ,P_SEGMENT1 IN VARCHAR2 default hr_api.g_varchar2
249 ,P_SEGMENT2 IN VARCHAR2 default hr_api.g_varchar2
250 ,P_SEGMENT3 IN VARCHAR2 default hr_api.g_varchar2
251 ,P_SEGMENT4 IN VARCHAR2 default hr_api.g_varchar2
252 ,P_SEGMENT5 IN VARCHAR2 default hr_api.g_varchar2
253 ,P_SEGMENT6 IN VARCHAR2 default hr_api.g_varchar2
254 ,P_SEGMENT7 IN VARCHAR2 default hr_api.g_varchar2
255 ,P_SEGMENT8 IN VARCHAR2 default hr_api.g_varchar2
256 ,P_SEGMENT9 IN VARCHAR2 default hr_api.g_varchar2
257 ,P_SEGMENT10 IN VARCHAR2 default hr_api.g_varchar2
258 ,P_SEGMENT11 IN VARCHAR2 default hr_api.g_varchar2
259 ,P_SEGMENT12 IN VARCHAR2 default hr_api.g_varchar2
260 ,P_SEGMENT13 IN VARCHAR2 default hr_api.g_varchar2
261 ,P_SEGMENT14 IN VARCHAR2 default hr_api.g_varchar2
262 ,P_SEGMENT15 IN VARCHAR2 default hr_api.g_varchar2
263 ,P_SEGMENT16 IN VARCHAR2 default hr_api.g_varchar2
264 ,P_SEGMENT17 IN VARCHAR2 default hr_api.g_varchar2
265 ,P_SEGMENT18 IN VARCHAR2 default hr_api.g_varchar2
266 ,P_SEGMENT19 IN VARCHAR2 default hr_api.g_varchar2
267 ,P_SEGMENT20 IN VARCHAR2 default hr_api.g_varchar2
268 ,P_SEGMENT21 IN VARCHAR2 default hr_api.g_varchar2
269 ,P_SEGMENT22 IN VARCHAR2 default hr_api.g_varchar2
270 ,P_SEGMENT23 IN VARCHAR2 default hr_api.g_varchar2
274 ,P_SEGMENT27 IN VARCHAR2 default hr_api.g_varchar2
271 ,P_SEGMENT24 IN VARCHAR2 default hr_api.g_varchar2
272 ,P_SEGMENT25 IN VARCHAR2 default hr_api.g_varchar2
273 ,P_SEGMENT26 IN VARCHAR2 default hr_api.g_varchar2
275 ,P_SEGMENT28 IN VARCHAR2 default hr_api.g_varchar2
276 ,P_SEGMENT29 IN VARCHAR2 default hr_api.g_varchar2
277 ,P_SEGMENT30 IN VARCHAR2 default hr_api.g_varchar2
278 ,P_CONCATENATED_SEGMENTS IN VARCHAR2 DEFAULT hr_api.g_varchar2
279 ,P_EFFECTIVE_START_DATE IN DATE DEFAULT NULL
280 ,P_EFFECTIVE_END_DATE IN DATE DEFAULT NULL
281 ,P_TRANSACTION_ID OUT NOCOPY NUMBER
282 ,P_TRANSACTION_STEP_ID OUT NOCOPY NUMBER
283 );
284 -- ----------------------------------------------------------------------------
285 -- |----------------------------< UPDATE_DATA >-------------------------------|
286 -- ----------------------------------------------------------------------------
287 -- {Start Of Comments}
288 --
289 -- Description:
290 -- This API updates data into base tables PAY_COST_ALLOCATIONS_F,
291 -- PAY_COST_ALLOCATION_KEYFLEX.
292 --
293 -- Prerequisites:
294 -- The transaction must exist.
295 --
296 -- In Parameters:
297 -- Name Reqd Type Description
298 -- p_validate no boolean If true, then validation alone will be performed and
299 -- the database will remain unchanged. If false and all
300 -- validation checks pass, then the database will be modified.
301 -- p_transaction_step_id Yes Number Identifies the transaction id.
302 -- p_effective_date No Date Identifies the effective date.
303 --
304 -- Post Success:
305 -- The data will be updated in PAY_COST_ALLOCATIONS_F, PAY_COST_ALLOCATION_KEYFLEX
306 -- It also updated the workflow table with the details.
307 --
308 --
309 -- Post Failure:
310 -- An exception is raised and nothing will be created.
311 --
312 -- Access Status:
313 -- Internal Development Use Only.
314 --
315 -- {End Of Comments}
316 --
317 PROCEDURE UPDATE_DATA(
318 P_VALIDATE IN BOOLEAN DEFAULT FALSE
319 ,P_TRANSACTION_STEP_ID IN NUMBER
320 );
321
322 -- ----------------------------------------------------------------------------
323 -- |----------------------------< DELETE_ASSG_COST >--------------------------|
324 -- ----------------------------------------------------------------------------
325 -- {Start Of Comments}
326 --
327 -- Description:
328 -- This API creates transaction and stores the costing KFF data into
329 -- transaction tables pertaining to delete operation.
330 --
331 -- Prerequisites:
332 --
333 --
334 -- In Parameters:
335 -- Name Reqd Type Description
336 -- p_validate no boolean If true, then validation alone will be performed and
337 -- the database will remain unchanged. If false and all
338 -- validation checks pass, then the database will be modified.
339 -- p_item_type Yes varchar2 Identifies Item type
340 -- p_item_key Yes varchar2 Identifies Item key
341 -- p_actid Yes number Identifies Activity Id.
342 -- p_login_person_id Yes number Login ID of the user.
343 -- p_effective_date Yes Date Effective Date
344 -- p_assignment_id Yes number Assignment id of the person whose costing is getting changed
345 -- p_business_group_id Yes number Business Group ID
346 -- p_cost_allocation_id Yes number Identifies which cost allocation to be changed.
347 -- p_object_version_number Yes number Object version number
348 -- Post Success:
349 -- A transaction will be created and the values into the transaction tables
350 -- as well. It sets the following out parameters.
351 --
352 -- Out Parameters:
353 -- p_trasaction_id Number Identifies the transaction created.
354 -- p_transaction_step_id Number Identifies the transaction step created.
355 --
356 -- Post Failure:
357 -- An exception is raised and nothing will be created.
358 --
359 -- Access Status:
360 -- Internal Development Use Only.
361 --
362 -- {End Of Comments}
363 --
364 PROCEDURE DELETE_ASSG_COST(
365 P_ITEM_TYPE IN VARCHAR2
366 ,P_ITEM_KEY IN VARCHAR2
367 ,P_ACTID IN NUMBER
368 ,P_LOGIN_PERSON_ID IN NUMBER
369 ,P_DELETE_MODE IN VARCHAR2 DEFAULT 'DELETE'
370 ,P_EFFECTIVE_DATE IN DATE
371 ,P_ASSIGNMENT_ID IN NUMBER
372 ,P_BUSINESS_GROUP_ID IN NUMBER
373 ,P_COST_ALLOCATION_ID IN NUMBER
374 ,P_OBJECT_VERSION_NUMBER IN NUMBER
375 ,P_CONCATENATED_SEGMENTS IN VARCHAR2 DEFAULT NULL
376 ,P_EFFECTIVE_START_DATE IN DATE DEFAULT NULL
377 ,P_EFFECTIVE_END_DATE IN DATE DEFAULT NULL
378 ,P_TRANSACTION_ID OUT NOCOPY NUMBER
379 ,P_TRANSACTION_STEP_ID OUT NOCOPY NUMBER
380 );
381 -- ----------------------------------------------------------------------------
382 -- |----------------------------< DELETE_DATA >-------------------------------|
383 -- ----------------------------------------------------------------------------
384 -- {Start Of Comments}
385 --
386 -- Description:
387 -- This API deletes data into base tables PAY_COST_ALLOCATIONS_F.
388 --
389 -- Prerequisites:
390 -- The transaction must exist.
391 --
392 -- In Parameters:
393 -- Name Reqd Type Description
394 -- p_validate no boolean If true, then validation alone will be performed and
395 -- the database will remain unchanged. If false and all
396 -- validation checks pass, then the database will be modified.
397 -- p_transaction_step_id Yes Number Identifies the transaction id.
398 -- p_effective_date No Date Identifies the effective date.
399 --
400 -- Post Success:
401 -- The data will be deleted in PAY_COST_ALLOCATIONS_F
402 -- It also updates the workflow table with the details.
403 --
404 --
405 -- Post Failure:
406 -- An exception is raised and nothing will be created.
407 --
408 -- Access Status:
409 -- Internal Development Use Only.
410 --
411 -- {End Of Comments}
412 --
413 PROCEDURE DELETE_DATA(
414 P_VALIDATE IN BOOLEAN DEFAULT FALSE
415 ,P_TRANSACTION_STEP_ID IN NUMBER
416 );
417 end PAY_ASSG_COST_SS;
[Home] [Help]