1 Package ota_tcc_bus AUTHID CURRENT_USER as
2 /* $Header: ottccrhi.pkh 120.0 2005/05/29 07:36:55 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |----------------------< set_security_group_id >--------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
11 -- group context.
12 --
13 -- Prerequisites:
14 -- The primary key identified by p_cross_charge_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_cross_charge_id
19 --
20 --
21 -- Post Success:
22 -- The security_group_id will be set in CLIENT_INFO.
23 --
24 -- Post Failure:
25 -- An error is raised if the value does not exist.
26 --
27 -- Access Status:
28 -- Internal Development Use Only.
29 --
30 -- {End Of Comments}
31 -- ---------------------------------------------------------------------------
32 procedure set_security_group_id
33 (p_cross_charge_id in number
34 );
35 --
36 --
37 -- ---------------------------------------------------------------------------
38 -- |---------------------< return_legislation_code >-------------------------|
39 -- ---------------------------------------------------------------------------
40 -- {Start Of Comments}
41 --
42 -- Description:
43 -- Return the legislation code for a specific primary key value
44 --
45 -- Prerequisites:
46 -- The primary key identified by p_cross_charge_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_cross_charge_id
51 --
52 --
53 -- Post Success:
54 -- The business group's legislation code will be returned.
55 --
56 -- Post Failure:
57 -- An error is raised if the value does not exist.
58 --
59 -- Access Status:
60 -- Internal Development Use Only.
61 --
62 -- {End Of Comments}
63 -- ---------------------------------------------------------------------------
64 FUNCTION return_legislation_code
65 (p_cross_charge_id in number
66 ) RETURN varchar2;
67
68 -- ----------------------------------------------------------------------------
69 -- |-----------------------< chk_overlap_cc_def>----------------------------------|
70 -- ----------------------------------------------------------------------------
71 Procedure chk_overlap_cc_def
72 (p_cross_charge_id in number
73 ,p_start_date_active in date
74 ,p_end_date_active in date
75 ,p_gl_set_of_books_id in number
76 ,p_from_to in varchar2
77 ,p_type in varchar2
78 ,p_business_group_id in number
79 ) ;
80
81 -- ----------------------------------------------------------------------------
82 -- |-------------------------< chk_end_date_ext>------------------------------|
83 -- ----------------------------------------------------------------------------
84 Procedure chk_end_date_ext
85 (p_cross_charge_id in number
86 ,p_end_date_active in date
87 );
88
89 --
90 -- ----------------------------------------------------------------------------
91 -- |------------------------------< chk_type >----------------------------|
92 -- ----------------------------------------------------------------------------
93 Procedure chk_type
94 (p_cross_charge_id in number
95 ,p_type in varchar2
96 ,p_effective_date in date) ;
97
98 -- ----------------------------------------------------------------------------
99 -- |------------------------------< chk_from_to >----------------------------|
100 -- ----------------------------------------------------------------------------
101 Procedure chk_from_to
102 (p_cross_charge_id in number
103 ,p_from_to in varchar2
104 ,p_effective_date in date) ;
105 --
106 -- ----------------------------------------------------------------------------
107 -- |---------------------------< insert_validate >----------------------------|
108 -- ----------------------------------------------------------------------------
109 -- {Start of comments}
110 --
111 -- Description:
112 -- This procedure controls the execution of all insert business rules
113 -- validation.
114 --
115 -- Prerequisites:
116 -- This private procedure is called from ins procedure.
117 --
118 -- In Parameters:
119 -- A Pl/Sql record structure.
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 insert, your business rules should be executed from 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 Row Handler Use Only.
135 --
136 -- {End of comments}
137 -- ----------------------------------------------------------------------------
138 Procedure insert_validate
139 (p_effective_date in date
140 ,p_rec in ota_tcc_shd.g_rec_type
141 );
142 --
143 -- ----------------------------------------------------------------------------
144 -- |---------------------------< update_validate >----------------------------|
145 -- ----------------------------------------------------------------------------
146 -- {Start Of Comments}
147 --
148 -- Description:
149 -- This procedure controls the execution of all update business rules
150 -- validation.
151 --
152 -- Prerequisites:
153 -- This private procedure is called from upd procedure.
154 --
155 -- In Parameters:
156 -- A Pl/Sql record structure.
157 --
158 -- Post Success:
159 -- Processing continues.
160 --
161 -- Post Failure:
162 -- If a business rules fails the error will not be handled by this procedure
163 -- unless explicity coded.
164 --
165 -- Developer Implementation Notes:
166 -- For update, your business rules should be executed from this procedure and
167 -- should ideally (unless really necessary) just be straight procedure or
168 -- function calls. Try and avoid using conditional branching logic.
169 --
170 -- Access Status:
171 -- Internal Row Handler Use Only.
172 --
173 -- {End Of Comments}
174 -- ----------------------------------------------------------------------------
175 Procedure update_validate
176 (p_effective_date in date
177 ,p_rec in ota_tcc_shd.g_rec_type
178 );
179 --
180 -- ----------------------------------------------------------------------------
181 -- |---------------------------< delete_validate >----------------------------|
182 -- ----------------------------------------------------------------------------
183 -- {Start Of Comments}
184 --
185 -- Description:
186 -- This procedure controls the execution of all delete business rules
187 -- validation.
188 --
189 -- Prerequisites:
190 -- This private procedure is called from del procedure.
191 --
192 -- In Parameters:
193 -- A Pl/Sql record structure.
194 --
195 -- Post Success:
196 -- Processing continues.
197 --
198 -- Post Failure:
199 -- If a business rules fails the error will not be handled by this procedure
200 -- unless explicity coded.
201 --
202 -- Developer Implementation Notes:
203 -- For delete, your business rules should be executed from this procedure and
204 -- should ideally (unless really necessary) just be straight procedure or
205 -- function calls. Try and avoid using conditional branching logic.
206 --
207 -- Access Status:
208 -- Internal Row Handler Use Only.
209 --
210 --
211 -- ----------------------------------------------------------------------------
212 Procedure delete_validate
213 (p_rec in ota_tcc_shd.g_rec_type
214 );
215 --
216 end ota_tcc_bus;
[Home] [Help]