DBA Data[Home] [Help]

PACKAGE: APPS.OTA_PLE_BUS

Source


1 Package ota_ple_bus AUTHID CURRENT_USER as
2 /* $Header: otple01t.pkh 115.0 99/07/16 00:53:01 porting ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------< insert_validate >----------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 --   This procedure controls the execution of all insert business rules
11 --   validation.
12 --
13 -- Pre Conditions:
14 --   This private procedure is called from ins procedure.
15 --
16 -- In Arguments:
17 --   A Pl/Sql record structre.
18 --
19 -- Post Success:
20 --   Processing continues.
21 --
22 -- Post Failure:
23 --   If a business rules fails the error will not be handled by this procedure
24 --   unless explicity coded.
25 --
26 -- Developer Implementation Notes:
27 --   For insert, your business rules should be coded within this procedure and
28 --   should ideally (unless really necessary) just be straight procedure or
29 --   function calls. Try and avoid using conditional branching logic.
30 --
31 -- Access Status:
32 --   Internal Development Use Only.
33 --
34 -- {End Of Comments}
35 -- ----------------------------------------------------------------------------
36 Procedure insert_validate(p_rec in ota_ple_shd.g_rec_type);
37 --
38 -- ----------------------------------------------------------------------------
39 -- |---------------------------< handle_leap_years >--------------------------|
40 -- ----------------------------------------------------------------------------
41 -- {Start Of Comments}
42 --
43 -- Description:
44 --   This procedure is used to handle price list entries so that the leap years
45 -- are handled correctly.
46 --
47 -- Pre Conditions:
48 --
49 -- In Arguments:
50 --   p_start_date = Start date of new price list.
51 --   p_dates_difference = Amount of days to add to new start date.
52 --
53 -- Post Success:
54 --   Processing continues.
55 --
56 -- Post Failure:
57 --
58 -- Developer Implementation Notes:
59 --   This procedure should be used for all conditions where a date is
60 -- calculated by using a number of days added to a certain date.
61 --
62 -- Access Status:
63 --   Internal Development Use Only.
64 --
65 -- {End Of Comments}
66 -- ----------------------------------------------------------------------------
67 Procedure handle_leap_years(p_start_date in out date,
68                             p_dates_difference  number,
69                             p_difference        number);
70 
71 --
72 -- ----------------------------------------------------------------------------
73 -- |---------------------------< consider_leap_years >------------------------|
74 -- ----------------------------------------------------------------------------
75 -- {Start Of Comments}
76 --
77 -- Description:
78 --   This procedure is used to calculate how many leap days occur within a
79 -- certain time period.
80 --
81 -- Pre Conditions:
82 --
83 -- In Arguments:
84 --   p_old_tpl_id = Event Id.
85 --   p_dates_difference = Amount of days to add to start date of event id.
86 --   p_difference = Amount of leap days in old start date to new start date
87 --   period.
88 --
89 -- Post Success:
90 --   Processing continues.
91 --
92 -- Post Failure:
93 --
94 -- Developer Implementation Notes:
95 --   This procedure should be used for all conditions where a date is
96 -- calculated by using a number of days added to a certain date.
97 --
98 -- Access Status:
99 --   Internal Development Use Only.
100 --
101 -- {End Of Comments}
102 -- ----------------------------------------------------------------------------
103 Procedure consider_leap_years(p_old_tpl_id        number,
104                               p_dates_difference  in out number);
105 --
106 -- ----------------------------------------------------------------------------
107 -- |---------------------------< update_validate >----------------------------|
108 -- ----------------------------------------------------------------------------
109 -- {Start Of Comments}
110 --
111 -- Description:
112 --   This procedure controls the execution of all update business rules
113 --   validation.
114 --
115 -- Pre Conditions:
116 --   This private procedure is called from upd procedure.
117 --
118 -- In Arguments:
119 --   A Pl/Sql record structre.
120 --
121 -- Post Success:
122 --   Processing continues.
123 --
124 -- Post Failure:
125 --   If a business rules fails the error will not be handled by this procedure
126 --   unless explicity coded.
127 --
128 -- Developer Implementation Notes:
129 --   For update, your business rules should be coded within this procedure and
130 --   should ideally (unless really necessary) just be straight procedure or
131 --   function calls. Try and avoid using conditional branching logic.
132 --
133 -- Access Status:
134 --   Internal Development Use Only.
135 --
136 -- {End Of Comments}
137 -- ----------------------------------------------------------------------------
138 Procedure update_validate(p_rec in ota_ple_shd.g_rec_type);
139 --
140 -- ----------------------------------------------------------------------------
141 -- |---------------------------< delete_validate >----------------------------|
142 -- ----------------------------------------------------------------------------
143 -- {Start Of Comments}
144 --
145 -- Description:
146 --   This procedure controls the execution of all delete business rules
147 --   validation.
148 --
149 -- Pre Conditions:
150 --   This private procedure is called from del procedure.
151 --
152 -- In Arguments:
153 --   A Pl/Sql record structre.
154 --
155 -- Post Success:
156 --   Processing continues.
157 --
158 -- Post Failure:
159 --   If a business rules fails the error will not be handled by this procedure
160 --   unless explicity coded.
161 --
162 -- Developer Implementation Notes:
163 --   For delete, your business rules should be coded within this procedure and
164 --   should ideally (unless really necessary) just be straight procedure or
165 --   function calls. Try and avoid using conditional branching logic.
166 --
167 -- Access Status:
168 --   Internal Development Use Only.
169 --
170 -- {End Of Comments}
171 -- ----------------------------------------------------------------------------
172 Procedure delete_validate(p_rec in ota_ple_shd.g_rec_type);
173 --
174 -- ici insert ple.h
175 --
176 --****************************************************************************
177 --				PLE SPECIFICATION
178 --				ADDITIONAL PUBLIC PROCEDURES
179 --****************************************************************************
180 --
181 -- Version    Date        Author    	Reason
182 --  10.7     19Apr95    lparient.FR	Added widen_entries_dates
183 --				Added select_entries parameter in copy_entries
184 --
185 -- ----------------------------------------------------------------------------
186 -- |------------------------------< copy_price >------------------------------|
187 -- ----------------------------------------------------------------------------
188 -- Written by Kurt Fisher (kfisher.)
189 --
190 -- PUBLIC
191 -- Description:
192 --   Copies all pricelist entry information from a given activity version to
193 --   another activity version.
194 --
195 Procedure copy_price
196   (
197    p_activity_version_from in  number
198   ,p_activity_version_to   in  number
199   );
200 --
201 -- ----------------------------------------------------------------------------
202 -- |-----------------------------< copy_price_list_entries >------------------|
203 -- ----------------------------------------------------------------------------
204 --
205 -- PUBLIC
206 -- Description:
207 --	Procedure called from client side.
208 --
209 procedure copy_price_list_entries (
210         p_price_list_id         number,
211         p_increase_date         date,
212 	p_enddate		date,
213         p_increase_rate         number,
214         p_round_direction       varchar2,
215         p_round_factor          number,
216 	p_select_entries	char,
217 	p_starting_from		date
218 );
219 --
220 -- ----------------------------------------------------------------------------
221 -- |-----------------------------< copy_price_list >--------------------------|
222 -- ----------------------------------------------------------------------------
223 --
224 -- PUBLIC
225 -- Description:
226 --  	Procedure called from OTA_TPL_BUS
227 --
228 procedure copy_price_list(
229 	p_old_price_list_id	    in number,
230 	p_new_price_list_id	    in number,
231         p_increase_rate         number,
232         p_round_direction       varchar2,
233         p_round_factor          number,
234 	p_old_startdate	in date,
235 	p_new_startdate	in date,
236 	p_old_enddate		in date,
237 	p_new_enddate		in date);
238 --
239 -- ----------------------------------------------------------------------------
240 -- |---------------------< widen_entries_date >-------------------------------|
241 -- ----------------------------------------------------------------------------
242 --
243 -- PUBLIC
244 -- Description:
245 --      Procedure called from OTA_TPL_BUS
246 --
247 procedure widen_entries_dates (
248 	p_price_list_id 	in number
249 	,p_old_startdate	in date
250 	,p_new_startdate	in date
251 	,p_old_enddate		in date
252 	,p_new_enddate		in date
253 );
254 --
255 --****************************************************************************
256 --****************************************************************************
257 --
258 --
259 end ota_ple_bus;