1 Package ben_cpg_ins as
2 /* $Header: becpgrhi.pkh 120.0 2005/05/28 01:13 appldev noship $ */
3 -- ----------------------------------------------------------------------------
4 -- |------------------------< set_base_key_value >----------------------------|
5 -- ----------------------------------------------------------------------------
6 -- {Start of Comments}
7 -- Description:
8 -- This procedure is called to register the next ID value from the database
9 -- sequence.
10 --
11 -- Prerequisites:
12 --
13 -- In Parameters:
14 -- Primary Key
15 --
16 -- Post Success:
17 --
18 -- Post Failure:
19 --
20 -- Developer Implementation Notes:
21 -- None.
22 --
23 -- Access Status:
24 -- Internal Development Use Only.
25 --
26 -- {End of Comments}
27 -- ----------------------------------------------------------------------------
28 procedure set_base_key_value
29 (p_group_per_in_ler_id in number
30 ,p_group_pl_id in number
31 ,p_group_oipl_id in number);
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) The controlling validation process insert_validate is executed
46 -- which will execute all private and public validation business rule
47 -- processes.
48 -- 2) The pre_insert business process is then executed which enables any
49 -- logic to be processed before the insert dml process is executed.
50 -- 3) The insert_dml process will physical perform the insert dml into the
51 -- specified entity.
52 -- 4) The post_insert business process is then executed which enables any
53 -- logic to be processed after the insert dml process.
54 --
55 -- Prerequisites:
56 -- The main parameters to the this process have to be in the record
57 -- format.
58 --
59 -- In Parameters:
60 --
61 -- Post Success:
62 -- A fully validated row will be inserted into the specified entity
63 -- without being committed.
64 --
65 -- Post Failure:
66 -- If an error has occurred, an error message will be raised.
67 --
68 -- Developer Implementation Notes:
69 -- None.
70 --
71 -- Access Status:
72 -- Internal Development Use Only.
73 --
74 -- {End Of Comments}
75 -- ----------------------------------------------------------------------------
76 Procedure ins
77 (p_rec in out nocopy ben_cpg_shd.g_rec_type
78 );
79 --
80 -- ----------------------------------------------------------------------------
81 -- |---------------------------------< ins >----------------------------------|
82 -- ----------------------------------------------------------------------------
83 -- {Start Of Comments}
84 --
85 -- Description:
86 -- This procedure is the attribute interface for the insert
87 -- process for the specified entity and is the outermost layer. The role
88 -- of this process is to insert a fully validated row into the HR schema
89 -- passing back to the calling process, any system generated values
90 -- (e.g. object version number attributes).The processing of this
91 -- procedure is as follows:
92 -- 1) The attributes are converted into a local record structure by
93 -- calling the convert_args function.
94 -- 2) After the conversion has taken place, the corresponding record ins
95 -- interface process is executed.
96 -- 3) OUT parameters are then set to their corresponding record attributes.
97 --
98 -- Prerequisites:
99 --
100 -- In Parameters:
101 --
102 -- Post Success:
103 -- A fully validated row will be inserted for the specified entity
104 -- without being committed.
105 --
106 -- Post Failure:
107 -- If an error has occurred, an error message will be raised.
108 --
109 -- Developer Implementation Notes:
110 -- None.
111 --
112 -- Access Status:
113 -- Internal Development Use Only.
114 --
115 -- {End Of Comments}
116 -- ----------------------------------------------------------------------------
117 Procedure ins
118 (p_group_per_in_ler_id in number
119 ,p_group_pl_id in number
120 ,p_group_oipl_id in number
121 ,p_lf_evt_ocrd_dt in date
122 ,p_bdgt_pop_cd in varchar2 default null
123 ,p_due_dt in date default null
124 ,p_access_cd in varchar2 default null
125 ,p_approval_cd in varchar2 default null
126 ,p_approval_date in date default null
127 ,p_approval_comments in varchar2 default null
128 ,p_submit_cd in varchar2 default null
129 ,p_submit_date in date default null
130 ,p_submit_comments in varchar2 default null
131 ,p_dist_bdgt_val in number default null
132 ,p_ws_bdgt_val in number default null
133 ,p_rsrv_val in number default null
134 ,p_dist_bdgt_mn_val in number default null
135 ,p_dist_bdgt_mx_val in number default null
136 ,p_dist_bdgt_incr_val in number default null
137 ,p_ws_bdgt_mn_val in number default null
138 ,p_ws_bdgt_mx_val in number default null
139 ,p_ws_bdgt_incr_val in number default null
140 ,p_rsrv_mn_val in number default null
141 ,p_rsrv_mx_val in number default null
142 ,p_rsrv_incr_val in number default null
143 ,p_dist_bdgt_iss_val in number default null
144 ,p_ws_bdgt_iss_val in number default null
145 ,p_dist_bdgt_iss_date in date default null
146 ,p_ws_bdgt_iss_date in date default null
147 ,p_ws_bdgt_val_last_upd_date in date default null
148 ,p_dist_bdgt_val_last_upd_date in date default null
149 ,p_rsrv_val_last_upd_date in date default null
150 ,p_ws_bdgt_val_last_upd_by in number default null
151 ,p_dist_bdgt_val_last_upd_by in number default null
152 ,p_rsrv_val_last_upd_by in number default null
153 ,p_object_version_number out nocopy number
154 );
155 --
156 end ben_cpg_ins;
[Home] [Help]