1 Package per_ppc_del as
2 /* $Header: peppcrhi.pkh 120.1 2006/03/14 18:16:34 scnair noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------------< del >----------------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- This procedure is the record interface for the delete process
11 -- for the specified entity. The role of this process is to delete the
12 -- row from the HR schema. This process is the main backbone of the del
13 -- business process. The processing of this procedure is as follows:
14 -- 1) If the p_validate parameter has been set to true then a savepoint is
15 -- issued.
16 -- 2) The controlling validation process delete_validate is then executed
17 -- which will execute all private and public validation business rule
18 -- processes.
19 -- 3) The pre_delete process is then executed which enables any
20 -- logic to be processed before the delete dml process is executed.
21 -- 4) The delete_dml process will physical perform the delete dml for the
22 -- specified row.
23 -- 5) The post_delete process is then executed which enables any
24 -- logic to be processed after the delete dml process.
25 -- 6) If the p_validate parameter has been set to true an exception is raised
26 -- which is handled and processed by performing a rollback to the
27 -- savepoint which was issued at the beginning of the del process.
28 -- p_validation_strength can be set to determine if the components of an
29 -- approved proposal can be deleted. This is so that a whole approved
30 -- proposal can be deleted.
31 --
32 -- Pre Conditions:
33 -- The main parameters to the business process have to be in the record
34 -- format.
35 --
36 -- In Parameters:
37 -- p_validate
38 -- Determines if the process is to be validated. Setting this
39 -- boolean value to true will invoke the process to be validated. The
40 -- default is false. The validation is controlled by a savepoint and
41 -- rollback mechanism. The savepoint is issued at the beginning of the
42 -- process and is rollbacked at the end of the process
43 -- when all the processing has been completed. The rollback is controlled
44 -- by raising and handling the exception hr_api.validate_enabled. We use
45 -- the exception because, by raising the exception with the business
46 -- process, we can exit successfully without having any of the 'OUT'
47 -- parameters being set.
48 -- p_validation_strength
49 -- Determines how strong the validation should be. Should always be set
50 -- to STRONG unless called from the delete proposal api which is trying
51 -- to delete a whole proposal and it's components. In this case it should
52 -- be set to WEAK and the condition that you cannot delete the components
53 -- of an approved proposal will be ignored.
54 --
55 -- Post Success:
56 -- The specified row will be fully validated and deleted for the specified
57 -- entity without being committed. If the p_validate parameter has been set
58 -- to true then all the work will be rolled back.
59 --
60 -- Post Failure:
61 -- If an error has occurred, an error message will be supplied with the work
62 -- rolled back.
63 --
64 -- Developer Implementation Notes:
65 -- None.
66 --
67 -- Access Status:
68 -- Internal Development Use Only.
69 --
70 -- {End Of Comments}
71 -- ----------------------------------------------------------------------------
72 Procedure del
73 (
74 p_rec in per_ppc_shd.g_rec_type,
75 p_validation_strength in varchar2 default 'STRONG',
76 p_validate in boolean default false
77 );
78 --
79 -- ----------------------------------------------------------------------------
80 -- |---------------------------------< del >----------------------------------|
81 -- ----------------------------------------------------------------------------
82 -- {Start Of Comments}
83 --
84 -- Description:
85 -- This procedure is the attribute interface for the delete
86 -- process for the specified entity and is the outermost layer. The role
87 -- of this process is to validate and delete the specified row from the
88 -- HR schema. The processing of this procedure is as follows:
89 -- 1) The attributes are converted into a local record structure by
90 -- explicitly coding the attribute parameters into the g_rec_type
91 -- datatype.
92 -- 2) After the conversion has taken place, the corresponding record del
93 -- interface process is executed.
94 --
95 -- Pre Conditions:
96 --
97 -- In Parameters:
98 -- p_validate
99 -- Determines if the process is to be validated. Setting this
100 -- Boolean value to true will invoke the process to be validated.
101 -- The default is false.
102 -- p_validation_strength
103 -- Determines how strong the validation should be. Should always be set
104 -- to STRONG unless called from the delete proposal api which is trying
105 -- to delete a whole proposal and it's components. In this case it should
106 -- be set to WEAK and the condition that you cannot delete the components
107 -- of an approved proposal will be ignored.
108 --
109 -- Post Success:
110 -- The specified row will be fully validated and deleted for the specified
111 -- entity without being committed (or rollbacked depending on the
112 -- p_validate status).
113 --
114 -- Post Failure:
115 -- If an error has occurred, an error message will be supplied with the work
116 -- rolled back.
117 --
118 -- Developer Implementation Notes:
119 -- The attrbute in parameters should be modified as to the business process
120 -- requirements.
121 --
122 -- Access Status:
123 -- Internal Development Use Only.
124 --
125 -- {End Of Comments}
126 -- ----------------------------------------------------------------------------
127 Procedure del
128 (
129 p_component_id in number,
130 p_object_version_number in number,
131 p_validation_strength in varchar2 default 'STRONG',
132 p_validate in boolean default false
133 );
134 --
135 end per_ppc_del;
[Home] [Help]