1 Package pay_itr_ins AUTHID CURRENT_USER as
2 /* $Header: pyitrrhi.pkh 120.0 2005/05/29 06:03:54 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |------------------------------< insert_dml >------------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- This procedure calls the dt_insert_dml control logic which handles
11 -- the actual datetrack dml.
12 --
13 -- Prerequisites:
14 -- This is an internal private procedure which must be called from the ins
15 -- procedure and must have all mandatory attributes set (except the
16 -- object_version_number which is initialised within the dt_insert_dml
17 -- procedure).
18 --
19 -- In Parameters:
20 -- A Pl/Sql record structure.
21 --
22 -- Post Success:
23 -- Processing contines.
24 --
25 -- Post Failure:
26 -- No specific error handling is required within this procedure.
27 --
28 -- Developer Implementation Notes:
29 -- None.
30 --
31 -- Access Status:
32 -- Internal Row Handler Use Only.
33 --
34 -- {End Of Comments}
35 -- ----------------------------------------------------------------------------
36 Procedure insert_dml
37 (p_rec in out nocopy pay_itr_shd.g_rec_type
38 ,p_effective_date in date
39 ,p_datetrack_mode in varchar2
40 ,p_validation_start_date in date
41 ,p_validation_end_date in date
42 );
43 --
44 -- ----------------------------------------------------------------------------
45 -- |---------------------------------< ins >----------------------------------|
46 -- ----------------------------------------------------------------------------
47 -- {Start Of Comments}
48 --
49 -- Description:
50 -- This procedure is the record interface for the insert process
51 -- for the specified entity. The role of this process is to insert a fully
52 -- validated row, into the HR schema passing back to the calling process,
53 -- any system generated values (e.g. primary and object version number
54 -- attributes). This process is the main backbone of the ins business
55 -- process. The processing of this procedure is as follows:
56 -- 1) We must lock parent rows (if any exist).
57 -- 2) The controlling validation process insert_validate is then executed
58 -- which will execute all private and public validation business rule
59 -- processes.
60 -- 3) The pre_insert process is then executed which enables any
61 -- logic to be processed before the insert dml process is executed.
62 -- 4) The insert_dml process will physical perform the insert dml into the
63 -- specified entity.
64 -- 5) The post_insert process is then executed which enables any
65 -- logic to be processed after the insert dml process.
66 --
67 -- Prerequisites:
68 -- The main parameters to the process have to be in the record
69 -- format.
70 --
71 -- In Parameters:
72 -- p_effective_date
73 -- Specifies the date of the datetrack insert operation.
74 --
75 -- Post Success:
76 -- A fully validated row will be inserted into the specified entity
77 -- without being committed.
78 --
79 -- Post Failure:
80 -- If an error has occurred, an error message will be raised.
81 --
82 -- Developer Implementation Notes:
83 -- None.
84 --
85 -- Access Status:
86 -- Internal Development Use Only.
87 --
88 -- {End Of Comments}
89 -- ----------------------------------------------------------------------------
90 Procedure ins
91 (p_effective_date in date
92 ,p_rec in out nocopy pay_itr_shd.g_rec_type
93 );
94 --
95 -- ----------------------------------------------------------------------------
96 -- |---------------------------------< ins >----------------------------------|
97 -- ----------------------------------------------------------------------------
98 -- {Start Of Comments}
99 --
100 -- Description:
101 -- This procedure is the attribute interface for the insert
102 -- process for the specified entity and is the outermost layer. The role
103 -- of this process is to insert a fully validated row into the HR schema
104 -- passing back to the calling process, any system generated values
105 -- (e.g. object version number attributes). The processing of this
106 -- procedure is as follows:
107 -- 1) The attributes are converted into a local record structure by
108 -- calling the convert_args function.
109 -- 2) After the conversion has taken place, the corresponding record ins
110 -- interface process is executed.
111 -- 3) OUT parameters are then set to their corresponding record attributes.
112 --
113 -- Prerequisites:
114 --
115 -- In Parameters:
116 -- p_effective_date
117 -- Specifies the date of the datetrack insert operation.
118 --
119 -- Post Success:
120 -- A fully validated row will be inserted for the specified entity
121 -- without being committed.
122 --
123 -- Post Failure:
124 -- If an error has occurred, an error message will be raised.
125 --
126 -- Developer Implementation Notes:
127 -- None.
128 --
129 -- Access Status:
130 -- Internal Development Use Only.
131 --
132 -- {End Of Comments}
133 -- ----------------------------------------------------------------------------
134 Procedure ins
135 (p_effective_date in date
136 ,p_element_type_id in number
137 ,p_result_name in varchar2
138 ,p_iterative_rule_type in varchar2
139 ,p_input_value_id in number default null
140 ,p_severity_level in varchar2 default null
141 ,p_business_group_id in number default null
142 ,p_legislation_code in varchar2 default null
143 ,p_iterative_rule_id out nocopy number
144 ,p_object_version_number out nocopy number
145 ,p_effective_start_date out nocopy date
146 ,p_effective_end_date out nocopy date
147 );
148 --
149 end pay_itr_ins;