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