1 Package hr_trn_ins AUTHID CURRENT_USER as
2 /* $Header: hrtrnrhi.pkh 120.1 2005/06/24 16:35:50 svittal noship $ */
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_transaction_id in number);
31 --
32 -- ----------------------------------------------------------------------------
33 -- |---------------------------------< ins >----------------------------------|
34 -- ----------------------------------------------------------------------------
35 -- {Start Of Comments}
36 --
37 -- Description:
38 -- This procedure is the record interface for the insert process
39 -- for the specified entity. The role of this process is to insert a fully
40 -- validated row, into the HR schema passing back to the calling process,
41 -- any system generated values (e.g. primary and object version number
42 -- attributes). This process is the main backbone of the ins
43 -- process. The processing of this procedure is as follows:
44 -- 1) If the p_validate parameter has been set to true then a savepoint is
45 -- issued.
46 -- 2) The controlling validation process insert_validate is then executed
47 -- which will execute all private and public validation business rule
48 -- processes.
49 -- 3) The pre_insert business process is then executed which enables any
50 -- logic to be processed before the insert dml process is executed.
51 -- 4) The insert_dml process will physical perform the insert dml into the
52 -- specified entity.
53 -- 5) The post_insert business process is then executed which enables any
54 -- logic to be processed after the insert dml process.
55 -- 6) If the p_validate parameter has been set to true an exception is
56 -- raised which is handled and processed by performing a rollback to the
57 -- savepoint which was issued at the beginning of the Ins process.
58 --
59 -- Pre Conditions:
60 -- The main parameters to the this process have to be in the record
61 -- format.
62 --
63 -- In Parameters:
64 -- p_validate
65 -- Determines if the process is to be validated. Setting this
66 -- boolean value to true will invoke the process to be validated. The
67 -- default is false. The validation is controlled by a savepoint and
68 -- rollback mechanism. The savepoint is issued at the beginning of the
69 -- process and is rollbacked at the end of the process
70 -- when all the processing has been completed. The rollback is controlled
71 -- by raising and handling the exception hr_api.validate_enabled. We use
72 -- the exception because, by raising the exception with the business
73 -- process, we can exit successfully without having any of the 'OUT'
74 -- parameters being set.
75 --
76 -- Post Success:
77 -- A fully validated row will be inserted into the specified entity
78 -- without being committed. If the p_validate parameter has been set to true
79 -- then all the work will be rolled back.
80 --
81 -- Post Failure:
82 -- If an error has occurred, an error message will be supplied with the work
83 -- rolled back.
84 --
85 -- Developer Implementation Notes:
86 -- None.
87 --
88 -- Access Status:
89 -- Internal Development Use Only.
90 --
91 -- {End Of Comments}
92 -- ----------------------------------------------------------------------------
93 Procedure ins
94 (
95 p_rec in out nocopy hr_trn_shd.g_rec_type,
96 p_validate in boolean default false
97 );
98 --
99 -- ----------------------------------------------------------------------------
100 -- |---------------------------------< ins >----------------------------------|
101 -- ----------------------------------------------------------------------------
102 -- {Start Of Comments}
103 --
104 -- Description:
105 -- This procedure is the attribute interface for the insert
106 -- process for the specified entity and is the outermost layer. The role
107 -- of this process is to insert a fully validated row into the HR schema
108 -- passing back to the calling process, any system generated values
109 -- (e.g. object version number attributes).The processing of this
110 -- procedure is as follows:
111 -- 1) The attributes are converted into a local record structure by
112 -- calling the convert_args function.
113 -- 2) After the conversion has taken place, the corresponding record ins
114 -- interface process is executed.
115 -- 3) OUT parameters are then set to their corresponding record attributes.
116 --
117 -- Pre Conditions:
118 --
119 -- In Parameters:
120 -- p_validate
121 -- Determines if the process is to be validated. Setting this
122 -- Boolean value to true will invoke the process to be validated.
123 -- The default is false.
124 --
125 -- Post Success:
126 -- A fully validated row will be inserted for the specified entity
127 -- without being committed (or rollbacked depending on the p_validate
128 -- status).
129 --
130 -- Post Failure:
131 -- If an error has occurred, an error message will be supplied with the work
132 -- rolled back.
133 --
134 -- Developer Implementation Notes:
135 -- None.
136 --
137 -- Access Status:
138 -- Internal Development Use Only.
139 --
140 -- {End Of Comments}
141 -- ----------------------------------------------------------------------------
142 Procedure ins
143 (
144 p_transaction_id out nocopy number,
145 p_creator_person_id in number,
146 p_transaction_privilege in varchar2,
147 p_validate in boolean default false
148 );
149 --
150 -- Overloaded procedure to accomodate extra columns
151
152 Procedure ins
153 (
154 p_transaction_id out nocopy number,
155 p_creator_person_id in number,
156 p_transaction_privilege in varchar2,
157 p_product_code in varchar2 default null,
158 p_url in varchar2 default null,
159 p_status in varchar2 default null,
160 p_section_display_name in varchar2 default null,
161 p_function_id in number,
162 p_transaction_ref_table in varchar2 default null,
163 p_transaction_ref_id in number default null,
164 p_transaction_type in varchar2 default null,
165 p_assignment_id in number default null,
166 p_api_addtnl_info in varchar2 default null,
167 p_selected_person_id in number default null,
168 p_item_type in varchar2 default null,
169 p_item_key in varchar2 default null,
170 p_transaction_effective_date in date default null,
171 p_process_name in varchar2 default null,
172 p_plan_id in number default null,
173 p_rptg_grp_id in number default null,
174 p_effective_date_option in varchar2 default null,
175 p_validate in boolean default false,
176 p_creator_role in varchar2 default null,
177 p_last_update_role in varchar2 default null,
178 p_parent_transaction_id in number default null,
179 p_relaunch_function in varchar2 default null,
180 p_transaction_group in varchar2 default null,
181 p_transaction_identifier in varchar2 default null,
182 p_transaction_document in CLOB default null
183 ) ;
184 --
185 -- p_plan_id, p_rptg_grp_id, p_effective_date_option added by sanej
186
187 end hr_trn_ins;
[Home] [Help]