1 Package per_apl_upd AUTHID CURRENT_USER as
2 /* $Header: peaplrhi.pkh 120.1 2005/10/25 00:30:44 risgupta noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------------< upd >----------------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- This procedure is the record interface for the update
11 -- process for the specified entity. The role of this process is
12 -- to update a fully validated row for the HR schema passing back
13 -- to the calling process, any system generated values (e.g.
14 -- object version number attribute). This process is the main
15 -- backbone of the upd business process. The processing of this
16 -- procedure is as follows:
17 -- 1) If the p_validate parameter has been set to true then a savepoint
18 -- is issued.
19 -- 2) The row to be updated is then locked and selected into the record
20 -- structure g_old_rec.
21 -- 3) Because on update parameters which are not part of the update do not
22 -- have to be defaulted, we need to build up the updated row by
23 -- converting any system defaulted parameters to their corresponding
24 -- value.
25 -- 4) The controlling validation process update_validate is then executed
26 -- which will execute all private and public validation business rule
27 -- processes.
28 -- 5) The pre_update process is then executed which enables any
29 -- logic to be processed before the update dml process is executed.
30 -- 6) The update_dml process will physical perform the update dml into the
31 -- specified entity.
32 -- 7) The post_update process is then executed which enables any
33 -- logic to be processed after the update dml process.
34 -- 8) If the p_validate parameter has been set to true an exception is
35 -- raised which is handled and processed by performing a rollback to
36 -- the savepoint which was issued at the beginning of the upd process.
37 --
38 -- Pre Conditions:
39 -- The main parameters to the business process have to be in the record
40 -- format.
41 --
42 -- In Parameters:
43 -- p_validate
44 -- Determines if the process is to be validated. Setting this
45 -- boolean value to true will invoke the process to be validated. The
46 -- default is false. The validation is controlled by a savepoint and
47 -- rollback mechanism. The savepoint is issued at the beginning of the
48 -- process and is rollbacked at the end of the process
49 -- when all the processing has been completed. The rollback is controlled
50 -- by raising and handling the exception hr_api.validate_enabled. We use
51 -- the exception because, by raising the exception with the
52 -- process, we can exit successfully without having any of the 'OUT'
53 -- parameters being set.
54 --
55 -- p_effective_date
56 -- Mandatory parameter used for calls to the standard lookup value
57 -- derivation procedures.
58 --
59 -- Post Success:
60 -- The specified row will be fully validated and updated for the specified
61 -- entity without being committed. If the p_validate argument has been set
62 -- to true then all the work will be rolled back.
63 --
64 -- Post Failure:
65 -- If an error has occurred, an error message will be supplied with the work
66 -- rolled back.
67 --
68 -- Developer Implementation Notes:
69 -- None.
70 --
71 -- Access Status:
72 -- Internal Development Use Only.
73 --
74 -- {End Of Comments}
75 -- ----------------------------------------------------------------------------
76 Procedure upd
77 (
78 p_rec in out nocopy per_apl_shd.g_rec_type,
79 p_effective_date in date,
80 p_validate in boolean default false
81 );
82 --
83 -- ----------------------------------------------------------------------------
84 -- |---------------------------------< upd >----------------------------------|
85 -- ----------------------------------------------------------------------------
86 -- {Start Of Comments}
87 --
88 -- Description:
89 -- This procedure is the attribute interface for the update
90 -- process for the specified entity and is the outermost layer. The role
91 -- of this process is to update a fully validated row into the HR schema
92 -- passing back to the calling process, any system generated values
93 -- (e.g. object version number attributes). The processing of this
94 -- procedure is as follows:
95 -- 1) The attributes are converted into a local record structure by
96 -- calling the convert_defs function.
97 -- 2) After the conversion has taken place, the corresponding record upd
98 -- interface process is executed.
99 -- 3) OUT parameters are then set to their corresponding record attributes.
100 --
101 -- Pre Conditions:
102 --
103 -- In Parameters:
104 -- p_validate
105 -- Determines if the process is to be validated. Setting this
106 -- Boolean value to true will invoke the process to be validated.
107 -- The default is false.
108 --
109 -- p_effective_date
110 -- Mandatory parameter used for calls to the standard lookup value
111 -- derivation procedures.
112 --
113 -- Post Success:
114 -- A fully validated row will be updated for the specified entity
115 -- without being committed (or rollbacked depending on the p_validate
116 -- status).
117 --
118 -- Post Failure:
119 -- If an error has occurred, an error message will be supplied with the work
120 -- rolled back.
121 --
122 -- Developer Implementation Notes:
123 -- None.
124 --
125 -- Access Status:
126 -- Internal Development Use Only.
127 --
128 -- {End Of Comments}
129 -- ----------------------------------------------------------------------------
130 Procedure upd
131 (
132 p_application_id in number,
133 p_date_received in date default hr_api.g_date,
134 p_comments in varchar2 default hr_api.g_varchar2,
135 p_current_employer in varchar2 default hr_api.g_varchar2,
136 p_date_end in date default hr_api.g_date,
137 p_projected_hire_date in date default hr_api.g_date,
138 p_successful_flag in varchar2 default hr_api.g_varchar2,
139 p_termination_reason in varchar2 default hr_api.g_varchar2,
140 p_request_id in number default hr_api.g_number,
141 p_program_application_id in number default hr_api.g_number,
142 p_program_id in number default hr_api.g_number,
143 p_program_update_date in date default hr_api.g_date,
144 p_appl_attribute_category in varchar2 default hr_api.g_varchar2,
145 p_appl_attribute1 in varchar2 default hr_api.g_varchar2,
146 p_appl_attribute2 in varchar2 default hr_api.g_varchar2,
147 p_appl_attribute3 in varchar2 default hr_api.g_varchar2,
148 p_appl_attribute4 in varchar2 default hr_api.g_varchar2,
149 p_appl_attribute5 in varchar2 default hr_api.g_varchar2,
150 p_appl_attribute6 in varchar2 default hr_api.g_varchar2,
151 p_appl_attribute7 in varchar2 default hr_api.g_varchar2,
152 p_appl_attribute8 in varchar2 default hr_api.g_varchar2,
153 p_appl_attribute9 in varchar2 default hr_api.g_varchar2,
154 p_appl_attribute10 in varchar2 default hr_api.g_varchar2,
155 p_appl_attribute11 in varchar2 default hr_api.g_varchar2,
156 p_appl_attribute12 in varchar2 default hr_api.g_varchar2,
157 p_appl_attribute13 in varchar2 default hr_api.g_varchar2,
158 p_appl_attribute14 in varchar2 default hr_api.g_varchar2,
159 p_appl_attribute15 in varchar2 default hr_api.g_varchar2,
160 p_appl_attribute16 in varchar2 default hr_api.g_varchar2,
161 p_appl_attribute17 in varchar2 default hr_api.g_varchar2,
162 p_appl_attribute18 in varchar2 default hr_api.g_varchar2,
163 p_appl_attribute19 in varchar2 default hr_api.g_varchar2,
164 p_appl_attribute20 in varchar2 default hr_api.g_varchar2,
165 p_object_version_number in out nocopy number,
166 p_effective_date in date,
167 p_validate in boolean default false
168 );
169 --
170 end per_apl_upd;
[Home] [Help]