1 Package ota_lci_ins AUTHID CURRENT_USER as
2 /* $Header: otlcirhi.pkh 120.0.12000000.1 2007/01/18 04:39:57 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_learning_path_id in number
30 ,p_category_usage_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) The controlling validation process insert_validate is executed
45 -- which will execute all private and public validation business rule
46 -- processes.
47 -- 2) The pre_insert business process is then executed which enables any
48 -- logic to be processed before the insert dml process is executed.
49 -- 3) The insert_dml process will physical perform the insert dml into the
50 -- specified entity.
51 -- 4) The post_insert business process is then executed which enables any
52 -- logic to be processed after the insert dml process.
53 --
54 -- Prerequisites:
55 -- The main parameters to the this process have to be in the record
56 -- format.
57 --
58 -- In Parameters:
59 --
60 -- Post Success:
61 -- A fully validated row will be inserted into the specified entity
62 -- without being committed.
63 --
64 -- Post Failure:
65 -- If an error has occurred, an error message will be raised.
66 --
67 -- Developer Implementation Notes:
68 -- None.
69 --
70 -- Access Status:
71 -- Internal Development Use Only.
72 --
73 -- {End Of Comments}
74 -- ----------------------------------------------------------------------------
75 Procedure ins
76 (p_effective_date in date
77 ,p_rec in out nocopy ota_lci_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_effective_date in date
119 ,p_learning_path_id in number
120 ,p_category_usage_id in number
121 ,p_start_date_active in date
122 ,p_primary_flag in varchar2 default null
123 ,p_end_date_active in date default null
124 ,p_attribute_category in varchar2 default null
125 ,p_attribute1 in varchar2 default null
126 ,p_attribute2 in varchar2 default null
127 ,p_attribute3 in varchar2 default null
128 ,p_attribute4 in varchar2 default null
129 ,p_attribute5 in varchar2 default null
130 ,p_attribute6 in varchar2 default null
131 ,p_attribute7 in varchar2 default null
132 ,p_attribute8 in varchar2 default null
133 ,p_attribute9 in varchar2 default null
134 ,p_attribute10 in varchar2 default null
135 ,p_attribute11 in varchar2 default null
136 ,p_attribute12 in varchar2 default null
137 ,p_attribute13 in varchar2 default null
138 ,p_attribute14 in varchar2 default null
139 ,p_attribute15 in varchar2 default null
140 ,p_attribute16 in varchar2 default null
141 ,p_attribute17 in varchar2 default null
142 ,p_attribute18 in varchar2 default null
143 ,p_attribute19 in varchar2 default null
144 ,p_attribute20 in varchar2 default null
145 -- ,p_learning_path_id out nocopy number
146 -- ,p_category_usage_id out nocopy number
147 ,p_object_version_number out nocopy number
148 );
149 --
150 end ota_lci_ins;
[Home] [Help]