1 Package per_par_ins AUTHID CURRENT_USER as
2 /* $Header: peparrhi.pkh 120.1 2007/06/20 07:48:33 rapandi ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |------------------------< set_base_key_value >----------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start of Comments}
8 -- Description:
9 -- This procedure is called to register the next ID value from the database
10 -- sequence.
11 --
12 -- Prerequisites:
13 --
14 -- In Parameters:
15 -- Primary Key
16 --
17 -- Post Success:
18 --
19 -- Post Failure:
20 --
21 -- Developer Implementation Notes:
22 -- None.
23 --
24 -- Access Status:
25 -- Internal Development Use Only.
26 --
27 -- {End of Comments}
28 -- ----------------------------------------------------------------------------
29 procedure set_base_key_value
30 (p_participant_id in number);
31 --
32
33 -- ----------------------------------------------------------------------------
34 -- |---------------------------------< ins >----------------------------------|
35 -- ----------------------------------------------------------------------------
36 -- {Start Of Comments}
37 --
38 -- Description:
39 -- This procedure is the record interface for the insert process
40 -- for the specified entity. The role of this process is to insert a fully
41 -- validated row, into the HR schema passing back to the calling process,
42 -- any system generated values (e.g. primary and object version number
43 -- attributes). This process is the main backbone of the ins
44 -- process. The processing of this procedure is as follows:
45 -- 1) If the p_validate parameter has been set to true then a savepoint is
46 -- issued.
47 -- 2) The controlling validation process insert_validate is then executed
48 -- which will execute all private and public validation business rule
49 -- processes.
50 -- 3) The pre_insert business process is then executed which enables any
51 -- logic to be processed before the insert dml process is executed.
52 -- 4) The insert_dml process will physical perform the insert dml into the
53 -- specified entity.
54 -- 5) The post_insert business process is then executed which enables any
55 -- logic to be processed after the insert dml process.
56 -- 6) If the p_validate parameter has been set to true an exception is
57 -- raised which is handled and processed by performing a rollback to the
58 -- savepoint which was issued at the beginning of the Ins process.
59 --
60 -- Pre Conditions:
61 -- The main parameters to the this process have to be in the record
62 -- format.
63 --
64 -- In Parameters:
65 -- p_validate
66 -- Determines if the process is to be validated. Setting this
67 -- boolean value to true will invoke the process to be validated. The
68 -- default is false. The validation is controlled by a savepoint and
69 -- rollback mechanism. The savepoint is issued at the beginning of the
70 -- process and is rollbacked at the end of the process
71 -- when all the processing has been completed. The rollback is controlled
72 -- by raising and handling the exception hr_api.validate_enabled. We use
73 -- the exception because, by raising the exception with the business
74 -- process, we can exit successfully without having any of the 'OUT'
75 -- parameters being set.
76 --
77 -- Post Success:
78 -- A fully validated row will be inserted into the specified entity
79 -- without being committed. If the p_validate parameter has been set to true
80 -- then all the work will be rolled back.
81 --
82 -- Post Failure:
83 -- If an error has occurred, an error message will be supplied with the work
84 -- rolled back.
85 --
86 -- Developer Implementation Notes:
87 -- None.
88 --
89 -- Access Status:
90 -- Internal Development Use Only.
91 --
92 -- {End Of Comments}
93 -- ----------------------------------------------------------------------------
94 Procedure ins
95 (
96 p_rec in out nocopy per_par_shd.g_rec_type,
97 p_effective_date in date ,
98 p_validate in boolean default false
99 );
100 --
101 -- ----------------------------------------------------------------------------
102 -- |---------------------------------< ins >----------------------------------|
103 -- ----------------------------------------------------------------------------
104 -- {Start Of Comments}
105 --
106 -- Description:
107 -- This procedure is the attribute interface for the insert
108 -- process for the specified entity and is the outermost layer. The role
109 -- of this process is to insert a fully validated row into the HR schema
110 -- passing back to the calling process, any system generated values
111 -- (e.g. object version number attributes).The processing of this
112 -- procedure is as follows:
113 -- 1) The attributes are converted into a local record structure by
114 -- calling the convert_args function.
115 -- 2) After the conversion has taken place, the corresponding record ins
116 -- interface process is executed.
117 -- 3) OUT parameters are then set to their corresponding record attributes.
118 --
119 -- Pre Conditions:
120 --
121 -- In Parameters:
122 -- p_validate
123 -- Determines if the process is to be validated. Setting this
124 -- Boolean value to true will invoke the process to be validated.
125 -- The default is false.
126 --
127 -- Post Success:
128 -- A fully validated row will be inserted for the specified entity
129 -- without being committed (or rollbacked depending on the p_validate
130 -- status).
131 --
132 -- Post Failure:
133 -- If an error has occurred, an error message will be supplied with the work
134 -- rolled back.
135 --
136 -- Developer Implementation Notes:
137 -- None.
138 --
139 -- Access Status:
140 -- Internal Development Use Only.
141 --
142 -- {End Of Comments}
143 -- ----------------------------------------------------------------------------
144 Procedure ins
145 (
146 p_participant_id out nocopy number,
147 p_business_group_id in number,
148 p_object_version_number out nocopy number,
149 p_questionnaire_template_id in number default null,
150 p_participation_in_table in varchar2,
151 p_participation_in_column in varchar2,
152 p_participation_in_id in number,
153 p_participation_status in varchar2 default 'OPEN',
154 p_participation_type in varchar2 default null,
155 p_last_notified_date in date default null,
156 p_date_completed in date default null,
157 p_comments in varchar2 default null,
158 p_person_id in number,
159 p_attribute_category in varchar2 default null,
160 p_attribute1 in varchar2 default null,
161 p_attribute2 in varchar2 default null,
162 p_attribute3 in varchar2 default null,
163 p_attribute4 in varchar2 default null,
164 p_attribute5 in varchar2 default null,
165 p_attribute6 in varchar2 default null,
166 p_attribute7 in varchar2 default null,
167 p_attribute8 in varchar2 default null,
168 p_attribute9 in varchar2 default null,
169 p_attribute10 in varchar2 default null,
170 p_attribute11 in varchar2 default null,
171 p_attribute12 in varchar2 default null,
172 p_attribute13 in varchar2 default null,
173 p_attribute14 in varchar2 default null,
174 p_attribute15 in varchar2 default null,
175 p_attribute16 in varchar2 default null,
176 p_attribute17 in varchar2 default null,
177 p_attribute18 in varchar2 default null,
178 p_attribute19 in varchar2 default null,
179 p_attribute20 in varchar2 default null,
180 p_participant_usage_status in varchar2 default null,
181 p_effective_date in date,
182 p_validate in boolean default false
183 );
184 --
185 end per_par_ins;
[Home] [Help]