4 -- ----------------------------------------------------------------------------
1 Package OTA_BST_API AUTHID CURRENT_USER as
2 /* $Header: otbst01t.pkh 120.1 2005/06/23 02:16:35 ssur noship $ */
3 --
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (
10 booking_status_type_id number(9),
11 business_group_id number(9),
12 active_flag varchar2(30),
13 default_flag varchar2(30),
14 name varchar2(80),
15 object_version_number number(9), -- Increased length
16 type varchar2(30),
17 comments varchar2(2000),
18 description varchar2(240),
19 bst_information_category varchar2(30),
20 bst_information1 varchar2(150),
21 bst_information2 varchar2(150),
22 bst_information3 varchar2(150),
23 bst_information4 varchar2(150),
24 bst_information5 varchar2(150),
25 bst_information6 varchar2(150),
26 bst_information7 varchar2(150),
27 bst_information8 varchar2(150),
28 bst_information9 varchar2(150),
29 bst_information10 varchar2(150),
30 bst_information11 varchar2(150),
31 bst_information12 varchar2(150),
32 bst_information13 varchar2(150),
33 bst_information14 varchar2(150),
34 bst_information15 varchar2(150),
35 bst_information16 varchar2(150),
36 bst_information17 varchar2(150),
37 bst_information18 varchar2(150),
38 bst_information19 varchar2(150),
39 bst_information20 varchar2(150)
40 );
41 --
42 --
43 -- ---------------------------------------------------------------------------
44 -- |----------------------< set_security_group_id >--------------------------|
45 -- ---------------------------------------------------------------------------
46 -- {Start Of Comments}
47 --
48 -- Description:
49 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
50 -- group context.
51 --
52 -- Prerequisites:
53 -- The primary key identified by p_booking_status_type_id
54 -- already exists.
55 --
56 -- In Arguments:
57 -- p_booking_status_type_id
58 --
59 --
60 -- Post Success:
61 -- The security_group_id will be set in CLIENT_INFO.
62 --
63 -- Post Failure:
64 -- An error is raised if the value does not exist.
65 --
66 -- Access Status:
67 -- Internal Development Use Only.
68 --
69 -- {End Of Comments}
70 -- ---------------------------------------------------------------------------
71 procedure set_security_group_id
72 (p_booking_status_type_id in number
73 ,p_associated_column1 in varchar2 default null
74 );
75 --
76 --
80 -- {Start Of Comments}
77 -- ---------------------------------------------------------------------------
78 -- |---------------------< return_legislation_code >-------------------------|
79 -- ---------------------------------------------------------------------------
81 --
82 -- Description:
83 -- Return the legislation code for a specific primary key value
84 --
85 -- Prerequisites:
86 -- The primary key identified by p_booking_status_type_id
87 -- already exists.
88 --
89 -- In Arguments:
90 -- p_booking_status_type_id
91 --
92 --
93 -- Post Success:
94 -- The business group's legislation code will be returned.
95 --
96 -- Post Failure:
97 -- An error is raised if the value does not exist.
98 --
99 -- Access Status:
100 -- Internal Development Use Only.
101 --
102 -- {End Of Comments}
103 -- ---------------------------------------------------------------------------
104 FUNCTION return_legislation_code
105 (p_booking_status_type_id in number
106 ) RETURN varchar2;
107 --
108 -- ----------------------------------------------------------------------------
109 -- ----------------------< GET_BOOKING_STATUS_TYPE_ID >------------------------
110 -- ----------------------------------------------------------------------------
111 --
112 --
113 -- Returns the BOOKING_STATUS_TYPE_ID corresponding to
114 -- P_BUSINESS_GROUP_ID / P_NAME
115 --
116 function GET_BOOKING_STATUS_TYPE_ID
117 (
118 P_BUSINESS_GROUP_ID in number,
119 P_NAME in varchar2
120 )
121 return number;
122 --
123 -- ----------------------------------------------------------------------------
124 -- -----------------------< GET_BOOKING_STATUS_TYPE >--------------------------
125 -- ----------------------------------------------------------------------------
126 --
127 -- Returns the BOOKING_STATUS_TYPE corresponding to
128 -- P_BOOKING_STATUS_TYPE_ID
129 --
130 function GET_BOOKING_STATUS_TYPE (
131 P_BOOKING_STATUS_TYPE_ID in number
132 ) return varchar2;
133 --
134 -- ----------------------------------------------------------------------------
135 -- ---------------------< DEFAULT_BOOKING_STATUS_TYPE >------------------------
136 -- ----------------------------------------------------------------------------
137 --
138 --
139 -- Takes business group and booking status type and retrieves default
140 -- booking status type id and name.
141 --
142 procedure DEFAULT_BOOKING_STATUS_TYPE
143 (
144 P_BUSINESS_GROUP_ID in number,
145 P_TYPE in varchar2,
146 P_EVENT_STATUS in varchar2,
147 P_BOOKING_STATUS_TYPE_ID out nocopy number,
148 P_NAME out nocopy varchar2
149 );
150
151 -- ----------------------------------------------------------------------------
152 -- |------------------------< set_base_key_value >----------------------------|
153 -- ----------------------------------------------------------------------------
154 -- {Start of Comments}
155 -- Description:
156 -- This procedure is called to register the next ID value from the database
157 -- sequence.
158 --
159 -- Prerequisites:
160 --
161 -- In Parameters:
162 -- Primary Key
163 --
164 -- Post Success:
165 --
166 -- Post Failure:
167 --
168 -- Developer Implementation Notes:
169 -- None.
170 --
171 -- Access Status:
172 -- Internal Development Use Only.
173 --
174 -- {End of Comments}
175 -- ----------------------------------------------------------------------------
176 procedure set_base_key_value
177 (p_booking_status_type_id in number);
178 --
179 --
180 -- ----------------------------------------------------------------------------
181 -- ---------------------------< CHECK_UNIQUE_NAME >----------------------------
182 -- ----------------------------------------------------------------------------
183 --
184 -- Check that a business status type name is unique within the
185 -- business group.
186 --
187 procedure CHECK_UNIQUE_NAME
188 (
189 P_BUSINESS_GROUP_ID in number,
190 P_NAME in varchar2,
191 P_BOOKING_STATUS_TYPE_ID in number default 0
192 );
193 --
194 -- ----------------------------------------------------------------------------
195 -- ----------------------------< CHECK_TDB_EXISTS >----------------------------
196 -- ----------------------------------------------------------------------------
197 --
198 -- Delete not allowed if any OTA_TRANING_DELEGATES rows exist for
199 -- this BOOKING_STATUS_TYPE_ID.
200 --
201 procedure CHECK_TDB_EXISTS
202 (
203 P_BOOKING_STATUS_TYPE_ID in number
204 );
205 --
206 -- ----------------------------------------------------------------------------
207 -- ----------------------------< CHECK_BSH_EXISTS >----------------------------
208 -- ----------------------------------------------------------------------------
209 --
210 -- Delete not allowed if any OTA_BOOKING_STATUS_HISTORIES rows exist
211 -- for this BOOKING_STATUS_TYPE_ID.
212 --
213 procedure CHECK_BSH_EXISTS
214 (
215 P_BOOKING_STATUS_TYPE_ID in number
216 );
217 -- ----------------------------------------------------------------------------
218 -- ----------------------------< CHECK_BSE_EXISTS >----------------------------
219 -- ----------------------------------------------------------------------------
220 --
221 -- Delete not allowed if any OTA_BOOKING_TYPE_EXCL rows exist
225 (
222 -- for this BOOKING_STATUS_TYPE_ID.
223 --
224 procedure CHECK_BSE_EXISTS
226 P_BOOKING_STATUS_TYPE_ID in number
227 );
228 --
229 -- ----------------------------------------------------------------------------
230 -- |------------------------< return_api_dml_status >-------------------------|
231 -- ----------------------------------------------------------------------------
232 -- {Start Of Comments}
233 --
234 -- Description:
235 -- This function will return the current g_api_dml private global
236 -- boolean status.
237 -- The g_api_dml status determines if at the time of the function
238 -- being executed if a dml statement (i.e. INSERT, UPDATE or DELETE)
239 -- is being issued from within an api.
240 -- If the status is TRUE then a dml statement is being issued from
241 -- within this entity api.
242 -- This function is primarily to support database triggers which
243 -- need to maintain the object_version_number for non-supported
244 -- dml statements (i.e. dml statement issued outside of the api layer).
245 --
246 -- Pre Conditions:
247 -- None.
248 --
249 -- In Arguments:
250 -- None.
251 --
252 -- Post Success:
253 -- Processing continues.
254 -- If the function returns a TRUE value then, dml is being executed from
255 -- within this api.
256 --
257 -- Post Failure:
258 -- None.
259 --
260 -- {End Of Comments}
261 -- ----------------------------------------------------------------------------
262 Function return_api_dml_status Return Boolean;
263 --
264 -- ----------------------------------------------------------------------------
265 -- |---------------------------------< lck >----------------------------------|
266 -- ----------------------------------------------------------------------------
267 -- {Start Of Comments}
268 --
269 -- Description:
270 -- The Lck process has two main functions to perform. Firstly, the row to be
271 -- updated or deleted must be locked. The locking of the row will only be
272 -- successful if the row is not currently locked by another user.
273 -- Secondly, during the locking of the row, the row is selected into
274 -- the g_old_rec data structure which enables the current row values from the
275 -- server to be available to the api.
276 --
277 -- Pre Conditions:
278 -- When attempting to call the lock the object version number (if defined)
279 -- is mandatory.
280 --
281 -- In Arguments:
282 -- The arguments to the Lck process are the primary key(s) which uniquely
283 -- identify the row and the object version number of row.
284 --
285 -- Post Success:
286 -- On successful completion of the Lck process the row to be updated or
287 -- deleted will be locked and selected into the global data structure
288 -- g_old_rec.
289 --
290 -- Post Failure:
291 -- The Lck process can fail for three reasons:
292 -- 1) When attempting to lock the row the row could already be locked by
293 -- another user. This will raise the HR_Api.Object_Locked exception.
294 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
295 -- This error is trapped and reported using the message name
296 -- 'HR_7220_INVALID_PRIMARY_KEY'.
297 -- 3) The row although existing in the HR Schema has a different object
298 -- version number than the object version number specified.
299 -- This error is trapped and reported using the message name
300 -- 'HR_7155_OBJECT_INVALID'.
301 --
302 -- Developer Implementation Notes:
303 -- For each primary key and the object version number arguments add a
304 -- call to hr_api.mandatory_arg_error procedure to ensure that these
305 -- argument values are not null.
306 --
307 -- {End Of Comments}
308 -- ----------------------------------------------------------------------------
309 Procedure lck
310 (
311 p_booking_status_type_id in number,
312 p_object_version_number in number
313 );
314 --
315 -- ----------------------------------------------------------------------------
316 -- |---------------------------------< ins >----------------------------------|
317 -- ----------------------------------------------------------------------------
318 -- {Start Of Comments}
319 --
320 -- Description:
321 -- This procedure is the record interface for the insert business process
322 -- for the specified entity. The role of this process is to insert a fully
323 -- validated row, into the HR schema passing back to the calling process,
324 -- any system generated values (e.g. primary and object version number
325 -- attributes). This process is the main backbone of the ins business
326 -- process. The processing of this procedure is as follows:
327 -- 1) If the p_validate argument has been set to true then a savepoint is
328 -- issued.
329 -- 2) The controlling validation process insert_validate is then executed
330 -- which will execute all private and public validation business rule
331 -- processes.
332 -- 3) The pre_insert business process is then executed which enables any
333 -- logic to be processed before the insert dml process is executed.
334 -- 4) The insert_dml process will physical perform the insert dml into the
335 -- specified entity.
336 -- 5) The post_insert business process is then executed which enables any
337 -- logic to be processed after the insert dml process.
338 -- 6) If the p_validate argument has been set to true an exception is raised
339 -- which is handled and processed by performing a rollback to the
340 -- savepoint which was issued at the beginning of the Ins process.
341 --
342 -- Pre Conditions:
343 -- The main arguments to the business process have to be in the record
347 -- p_validate
344 -- format.
345 --
346 -- In Arguments:
348 -- Determines if the business process is to be validated. Setting this
349 -- boolean value to true will invoke the process to be validated. The
350 -- default is false. The validation is controlled by a savepoint and
351 -- rollback mechanism. The savepoint is issued at the beginning of the
352 -- business process and is rollbacked at the end of the business process
353 -- when all the processing has been completed. The rollback is controlled
354 -- by raising and handling the exception hr_api.validate_enabled. We use
355 -- the exception because, by raising the exception with the business
356 -- process, we can exit successfully without having any of the 'OUT'
357 -- arguments being set.
358 --
359 -- Post Success:
360 -- A fully validated row will be inserted into the specified entity
361 -- without being committed. If the p_validate argument has been set to true
362 -- then all the work will be rolled back.
363 --
364 -- Post Failure:
365 -- If an error has occurred, an error message will be supplied with the work
366 -- rolled back.
367 --
368 -- Developer Implementation Notes:
369 --
370 -- {End Of Comments}
371 -- ----------------------------------------------------------------------------
372 Procedure ins
373 (
374 p_rec in out nocopy g_rec_type,
375 p_validate in boolean default false
376 );
377 --
378 -- ----------------------------------------------------------------------------
379 -- |---------------------------------< ins >----------------------------------|
380 -- ----------------------------------------------------------------------------
381 -- {Start Of Comments}
382 --
383 -- Description:
384 -- This procedure is the attribute interface for the insert business
385 -- process for the specified entity and is the outermost layer. The role
386 -- of this process is to insert a fully validated row into the HR schema
387 -- passing back to the calling process, any system generated values
388 -- (e.g. object version number attributes).The processing of this
389 -- procedure is as follows:
390 -- 1) The attributes are converted into a local record structure by
391 -- calling the convert_defs function.
392 -- 2) After the conversion has taken place, the corresponding record ins
393 -- interface business process is executed.
394 -- 3) OUT arguments are then set to their corresponding record arguments.
395 --
396 -- Pre Conditions:
397 --
398 -- In Arguments:
399 -- p_validate
400 -- Determines if the business process is to be validated. Setting this
401 -- Boolean value to true will invoke the process to be validated.
402 -- The default is false.
403 --
404 -- Post Success:
405 -- A fully validated row will be inserted for the specified entity
406 -- without being committed (or rollbacked depending on the p_validate
407 -- status).
408 --
409 -- Post Failure:
410 -- If an error has occurred, an error message will be supplied with the work
411 -- rolled back.
412 --
413 -- Developer Implementation Notes:
414 --
415 -- {End Of Comments}
416 -- ----------------------------------------------------------------------------
417 Procedure ins
418 (
419 p_booking_status_type_id out nocopy number,
420 p_business_group_id in number,
421 p_active_flag in varchar2,
422 p_default_flag in varchar2,
423 p_name in varchar2,
424 p_object_version_number out nocopy number,
425 p_type in varchar2,
426 p_comments in varchar2 default null,
427 p_description in varchar2 default null,
428 p_bst_information_category in varchar2 default null,
429 p_bst_information1 in varchar2 default null,
430 p_bst_information2 in varchar2 default null,
431 p_bst_information3 in varchar2 default null,
432 p_bst_information4 in varchar2 default null,
433 p_bst_information5 in varchar2 default null,
434 p_bst_information6 in varchar2 default null,
435 p_bst_information7 in varchar2 default null,
436 p_bst_information8 in varchar2 default null,
437 p_bst_information9 in varchar2 default null,
438 p_bst_information10 in varchar2 default null,
439 p_bst_information11 in varchar2 default null,
440 p_bst_information12 in varchar2 default null,
441 p_bst_information13 in varchar2 default null,
442 p_bst_information14 in varchar2 default null,
443 p_bst_information15 in varchar2 default null,
444 p_bst_information16 in varchar2 default null,
445 p_bst_information17 in varchar2 default null,
446 p_bst_information18 in varchar2 default null,
447 p_bst_information19 in varchar2 default null,
448 p_bst_information20 in varchar2 default null,
449 p_validate in boolean default false
450 );
451 --
452 -- ----------------------------------------------------------------------------
453 -- |---------------------------------< upd >----------------------------------|
454 -- ----------------------------------------------------------------------------
455 -- {Start Of Comments}
456 --
457 -- Description:
458 -- This procedure is the record interface for the update business
459 -- process for the specified entity. The role of this process is
460 -- to update a fully validated row for the HR schema passing back
464 -- procedure is as follows:
461 -- to the calling process, any system generated values (e.g.
462 -- object version number attribute). This process is the main
463 -- backbone of the upd business process. The processing of this
465 -- 1) If the p_validate argument has been set to true then a savepoint
466 -- is issued.
467 -- 2) The row to be updated is then locked and selected into the record
468 -- structure g_old_rec.
469 -- 3) Because on update arguments which are not part of the update do not
470 -- have to be defaulted, we need to build up the updated row by
471 -- converting any system defaulted arguments to their corresponding
472 -- value.
473 -- 4) The controlling validation process update_validate is then executed
474 -- which will execute all private and public validation business rule
475 -- processes.
476 -- 5) The pre_update business process is then executed which enables any
477 -- logic to be processed before the update dml process is executed.
478 -- 6) The update_dml process will physical perform the update dml into the
479 -- specified entity.
480 -- 7) The post_update business process is then executed which enables any
481 -- logic to be processed after the update dml process.
482 -- 8) If the p_validate argument has been set to true an exception is
483 -- raised which is handled and processed by performing a rollback to
484 -- the savepoint which was issued at the beginning of the upd process.
485 --
486 -- Pre Conditions:
487 -- The main arguments to the business process have to be in the record
488 -- format.
489 --
490 -- In Arguments:
491 -- p_validate
492 -- Determines if the business process is to be validated. Setting this
493 -- boolean value to true will invoke the process to be validated. The
494 -- default is false. The validation is controlled by a savepoint and
495 -- rollback mechanism. The savepoint is issued at the beginning of the
496 -- business process and is rollbacked at the end of the business process
497 -- when all the processing has been completed. The rollback is controlled
498 -- by raising and handling the exception hr_api.validate_enabled. We use
499 -- the exception because, by raising the exception with the business
500 -- process, we can exit successfully without having any of the 'OUT'
501 -- arguments being set.
502 --
503 -- Post Success:
504 -- The specified row will be fully validated and updated for the specified
505 -- entity without being committed. If the p_validate argument has been set
506 -- to true then all the work will be rolled back.
507 --
508 -- Post Failure:
509 -- If an error has occurred, an error message will be supplied with the work
510 -- rolled back.
511 --
512 -- Developer Implementation Notes:
513 --
514 -- {End Of Comments}
515 -- ----------------------------------------------------------------------------
516 Procedure upd
517 (
518 p_rec in out nocopy g_rec_type,
519 p_validate in boolean default false
520 );
521 --
522 -- ----------------------------------------------------------------------------
523 -- |---------------------------------< upd >----------------------------------|
524 -- ----------------------------------------------------------------------------
525 -- {Start Of Comments}
526 --
527 -- Description:
528 -- This procedure is the attribute interface for the update business
529 -- process for the specified entity and is the outermost layer. The role
530 -- of this process is to update a fully validated row into the HR schema
531 -- passing back to the calling process, any system generated values
532 -- (e.g. object version number attributes).The processing of this
533 -- procedure is as follows:
534 -- 1) The attributes are converted into a local record structure by
535 -- calling the convert_defs function.
536 -- 2) After the conversion has taken place, the corresponding record upd
537 -- interface business process is executed.
538 -- 3) OUT arguments are then set to their corresponding record arguments.
539 --
540 -- Pre Conditions:
541 --
542 -- In Arguments:
543 -- p_validate
544 -- Determines if the business process is to be validated. Setting this
545 -- Boolean value to true will invoke the process to be validated.
546 -- The default is false.
547 --
548 -- Post Success:
549 -- A fully validated row will be updated for the specified entity
550 -- without being committed (or rollbacked depending on the p_validate
551 -- status).
552 --
553 -- Post Failure:
554 -- If an error has occurred, an error message will be supplied with the work
555 -- rolled back.
556 --
557 -- Developer Implementation Notes:
558 --
559 -- {End Of Comments}
560 -- ----------------------------------------------------------------------------
561 Procedure upd
562 (
563 p_booking_status_type_id in number,
564 p_business_group_id in number default hr_api.g_number,
565 p_active_flag in varchar2 default hr_api.g_varchar2,
566 p_default_flag in varchar2 default hr_api.g_varchar2,
567 p_name in varchar2 default hr_api.g_varchar2,
568 p_object_version_number in out nocopy number,
569 p_type in varchar2 default hr_api.g_varchar2,
570 p_comments in varchar2 default hr_api.g_varchar2,
571 p_description in varchar2 default hr_api.g_varchar2,
572 p_bst_information_category in varchar2 default hr_api.g_varchar2,
573 p_bst_information1 in varchar2 default hr_api.g_varchar2,
574 p_bst_information2 in varchar2 default hr_api.g_varchar2,
575 p_bst_information3 in varchar2 default hr_api.g_varchar2,
579 p_bst_information7 in varchar2 default hr_api.g_varchar2,
576 p_bst_information4 in varchar2 default hr_api.g_varchar2,
577 p_bst_information5 in varchar2 default hr_api.g_varchar2,
578 p_bst_information6 in varchar2 default hr_api.g_varchar2,
580 p_bst_information8 in varchar2 default hr_api.g_varchar2,
581 p_bst_information9 in varchar2 default hr_api.g_varchar2,
582 p_bst_information10 in varchar2 default hr_api.g_varchar2,
583 p_bst_information11 in varchar2 default hr_api.g_varchar2,
584 p_bst_information12 in varchar2 default hr_api.g_varchar2,
585 p_bst_information13 in varchar2 default hr_api.g_varchar2,
586 p_bst_information14 in varchar2 default hr_api.g_varchar2,
587 p_bst_information15 in varchar2 default hr_api.g_varchar2,
588 p_bst_information16 in varchar2 default hr_api.g_varchar2,
589 p_bst_information17 in varchar2 default hr_api.g_varchar2,
590 p_bst_information18 in varchar2 default hr_api.g_varchar2,
591 p_bst_information19 in varchar2 default hr_api.g_varchar2,
592 p_bst_information20 in varchar2 default hr_api.g_varchar2,
593 p_validate in boolean default false
594 );
595 --
596 -- ----------------------------------------------------------------------------
597 -- |---------------------------------< del >----------------------------------|
598 -- ----------------------------------------------------------------------------
599 -- {Start Of Comments}
600 --
601 -- Description:
602 -- This procedure is the record interface for the delete business process
603 -- for the specified entity. The role of this process is to delete the
604 -- row from the HR schema. This process is the main backbone of the del
605 -- business process. The processing of this procedure is as follows:
606 -- 1) If the p_validate argument has been set to true then a savepoint is
607 -- issued.
608 -- 2) The controlling validation process delete_validate is then executed
609 -- which will execute all private and public validation business rule
610 -- processes.
611 -- 3) The pre_delete business process is then executed which enables any
612 -- logic to be processed before the delete dml process is executed.
613 -- 4) The delete_dml process will physical perform the delete dml for the
614 -- specified row.
615 -- 5) The post_delete business process is then executed which enables any
616 -- logic to be processed after the delete dml process.
617 -- 6) If the p_validate argument has been set to true an exception is raised
618 -- which is handled and processed by performing a rollback to the
619 -- savepoint which was issued at the beginning of the del process.
620 --
621 -- Pre Conditions:
622 -- The main arguments to the business process have to be in the record
623 -- format.
624 --
625 -- In Arguments:
626 -- p_validate
627 -- Determines if the business process is to be validated. Setting this
628 -- boolean value to true will invoke the process to be validated. The
629 -- default is false. The validation is controlled by a savepoint and
630 -- rollback mechanism. The savepoint is issued at the beginning of the
631 -- business process and is rollbacked at the end of the business process
632 -- when all the processing has been completed. The rollback is controlled
633 -- by raising and handling the exception hr_api.validate_enabled. We use
634 -- the exception because, by raising the exception with the business
635 -- process, we can exit successfully without having any of the 'OUT'
636 -- arguments being set.
637 --
638 -- Post Success:
639 -- The specified row will be fully validated and deleted for the specified
640 -- entity without being committed. If the p_validate argument has been set
641 -- to true then all the work will be rolled back.
642 --
643 -- Post Failure:
644 -- If an error has occurred, an error message will be supplied with the work
645 -- rolled back.
646 --
647 -- Developer Implementation Notes:
648 --
649 -- {End Of Comments}
650 -- ----------------------------------------------------------------------------
651 Procedure del
652 (
653 p_rec in g_rec_type,
654 p_validate in boolean default false
655 );
656 --
657 -- ----------------------------------------------------------------------------
658 -- |---------------------------------< del >----------------------------------|
659 -- ----------------------------------------------------------------------------
660 -- {Start Of Comments}
661 --
662 -- Description:
663 -- This procedure is the attribute interface for the delete business
664 -- process for the specified entity and is the outermost layer. The role
665 -- of this process is to validate and delete the specified row from the
666 -- HR schema. The processing of this procedure is as follows:
667 -- 1) The attributes are converted into a local record structure by
668 -- explicitly coding the attribute arguments into the g_rec_type
669 -- datatype.
670 -- 2) After the conversion has taken place, the corresponding record del
671 -- interface business process is executed.
672 --
673 -- Pre Conditions:
674 --
675 -- In Arguments:
676 -- p_validate
677 -- Determines if the business process is to be validated. Setting this
678 -- Boolean value to true will invoke the process to be validated.
679 -- The default is false.
680 --
681 -- Post Success:
682 -- The specified row will be fully validated and deleted for the specified
683 -- entity without being committed (or rollbacked depending on the
684 -- p_validate status).
685 --
686 -- Post Failure:
687 -- If an error has occurred, an error message will be supplied with the work
688 -- rolled back.
689 --
690 -- Developer Implementation Notes:
691 -- The attrbute in arguments should be modified as to the business process
692 -- requirements.
693 --
694 -- {End Of Comments}
695 -- ----------------------------------------------------------------------------
696 Procedure del
697 (
698 p_booking_status_type_id in number,
699 p_object_version_number in number,
700 p_validate in boolean default false
701 );
702 --
703 end OTA_BST_API;
[Home] [Help]