DBA Data[Home] [Help]

PACKAGE: APPS.PAY_PPR_BUS

Source


1 Package pay_ppr_bus as
2 /* $Header: pypprrhi.pkh 120.0 2005/05/29 07:45 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 --    It is only valid to call this procedure when the primary key
13 --    is within a buisiness group context.
14 --
15 --  Prerequisites:
16 --    The primary key identified by p_status_processing_rule_id
17 --     already exists.
18 --
19 --  In Arguments:
20 --    p_status_processing_rule_id
21 --
22 --
23 --  Post Success:
24 --    The security_group_id will be set in CLIENT_INFO.
25 --
26 --  Post Failure:
27 --    An error is raised if the value does not exist.
28 --    An error is also raised when the primary key data is outside
29 --    of a buisiness group context.
30 --
31 --  Access Status:
32 --    Internal Development Use Only.
33 --
34 -- {End Of Comments}
35 -- ---------------------------------------------------------------------------
36 procedure set_security_group_id
37   (p_status_processing_rule_id            in number
38   ,p_associated_column1                   in varchar2 default null
39   );
40 --
41 -- ----------------------------------------------------------------------------
42 -- |------------------------< set_effective_end_date >------------------------|
43 -- ----------------------------------------------------------------------------
44 --
45 -- Description:
46 --   This procedure is used to set the effective end date of the status
47 --   processing rule based on the end date of Element, formula or Future
48 --   Status Processing Rule.
49 --
50 --  Prerequisites:
51 --
52 --  In Arguments:
53 --   p_effective_date			Effective date
54 --   p_status_processing_rule_id        Status processing rule id
55 --   p_element_type_id                  Element Type id
56 --   p_formula_id                       Formula Id
57 --   p_assignment_status_type_id        Assignment status type id
58 --   p_processing_rule                  Processing rule
59 --   p_business_group_id
60 --   p_legislation_code
61 --   p_datetrack_mode                   Datetrack mode
62 --   p_validation_start_date
63 --
64 --  OUT parameter
65 --    p_validation_end_date             validation end date
66 --
67 --
68 --  Post Success:
69 --    Returns end date of Status Processing Rule.
70 --
71 --  Post Failure:
72 --
73 --  Access Status:
74 --    Internal Development Use Only.
75 --
76 -- {End Of Comments}
77 -- ---------------------------------------------------------------------------
78 Procedure set_effective_end_date
79   (p_effective_date             in  date
80   ,p_status_processing_rule_id  in  number
81   ,p_element_type_id            in  number
82   ,p_formula_id                 in  number
83   ,p_assignment_status_type_id  in  number
84   ,p_processing_rule            in  varchar2
85   ,p_business_group_id          in  number
86   ,p_legislation_code           in  varchar2
87   ,p_datetrack_mode             in  varchar2 default null
88   ,p_validation_start_date      in  date
89   ,p_validation_end_date        in out nocopy date
90   );
91 --
92 --
93 -- ---------------------------------------------------------------------------
94 -- |---------------------< return_legislation_code >-------------------------|
95 -- ---------------------------------------------------------------------------
96 -- {Start Of Comments}
97 --
98 --  Description:
99 --    Return the legislation code for a specific primary key value
100 --
101 --  Prerequisites:
102 --    The primary key identified by p_status_processing_rule_id
103 --     already exists.
104 --
105 --  In Arguments:
106 --    p_status_processing_rule_id
107 --
108 --
109 --  Post Success:
110 --    The business group's legislation code will be returned.
111 --
112 --  Post Failure:
113 --    An error is raised if the value does not exist.
114 --
115 --  Access Status:
116 --    Internal Development Use Only.
117 --
118 -- {End Of Comments}
119 -- ---------------------------------------------------------------------------
120 FUNCTION return_legislation_code
121   (p_status_processing_rule_id            in     number
122   ) RETURN varchar2;
123 --
124 --
125 -- ----------------------------------------------------------------------------
126 -- |---------------------------< insert_validate >----------------------------|
127 -- ----------------------------------------------------------------------------
128 -- {Start Of Comments}
129 --
130 -- Description:
131 --   This procedure controls the execution of all insert business rules
132 --   validation.
133 --
134 -- Prerequisites:
135 --   This private procedure is called from ins procedure.
136 --
137 -- In Parameters:
138 --   A Pl/Sql record structre.
139 --
140 -- Post Success:
141 --   Processing continues.
142 --
143 -- Post Failure:
144 --   If a business rules fails the error will not be handled by this procedure
145 --   unless explicity coded.
146 --
147 -- Developer Implementation Notes:
148 --   For insert, your business rules should be executed from this procedure and
149 --   should ideally (unless really necessary) just be straight procedure or
150 --   function calls. Try and avoid using conditional branching logic.
151 --
152 -- Access Status:
153 --   Internal Row Handler Use Only.
154 --
155 -- {End Of Comments}
156 -- ----------------------------------------------------------------------------
157 Procedure insert_validate
158   (p_rec                   in pay_ppr_shd.g_rec_type
159   ,p_effective_date        in date
160   ,p_datetrack_mode        in varchar2
161   ,p_validation_start_date in date
162   ,p_validation_end_date   in date
163   ,p_processing_rule       OUT NOCOPY varchar2
164   ,p_formula_mismatch_warning OUT NOCOPY boolean
165   );
166 --
167 -- ----------------------------------------------------------------------------
168 -- |---------------------------< update_validate >----------------------------|
169 -- ----------------------------------------------------------------------------
170 -- {Start Of Comments}
171 --
172 -- Description:
173 --   This procedure controls the execution of all update business rules
174 --   validation.
175 --
176 -- Prerequisites:
177 --   This private procedure is called from upd procedure.
178 --
179 -- In Parameters:
180 --   A Pl/Sql record structre.
181 --
182 -- Post Success:
183 --   Processing continues.
184 --
185 -- Post Failure:
186 --   If a business rules fails the error will not be handled by this procedure
187 --   unless explicity coded.
188 --
189 -- Developer Implementation Notes:
190 --   For update, your business rules should be executed from this procedure and
191 --   should ideally (unless really necessary) just be straight procedure or
192 --   function calls. Try and avoid using conditional branching logic.
193 --
194 -- Access Status:
195 --   Internal Row Handler Use Only.
196 --
197 -- {End Of Comments}
198 -- ----------------------------------------------------------------------------
199 Procedure update_validate
200   (p_rec                     in pay_ppr_shd.g_rec_type
201   ,p_effective_date          in date
202   ,p_datetrack_mode          in varchar2
203   ,p_validation_start_date   in date
204   ,p_validation_end_date     in date
205   ,p_processing_rule       OUT NOCOPY varchar2
206   ,p_formula_mismatch_warning OUT NOCOPY boolean
207   );
208 --
209 -- ----------------------------------------------------------------------------
210 -- |---------------------------< delete_validate >----------------------------|
211 -- ----------------------------------------------------------------------------
212 -- {Start Of Comments}
213 --
214 -- Description:
215 --   This procedure controls the execution of all delete business rules
216 --   validation.
217 --
218 -- Prerequisites:
219 --   This private procedure is called from del procedure.
220 --
221 -- In Parameters:
222 --   A Pl/Sql record structure.
223 --
224 -- Post Success:
225 --   Processing continues.
226 --
227 -- Post Failure:
228 --   If a business rules fails the error will not be handled by this procedure
229 --   unless explicity coded.
230 --
231 -- Developer Implementation Notes:
232 --   For delete, your business rules should be executed from this procedure and
233 --   should ideally (unless really necessary) just be straight procedure or
234 --   function calls. Try and avoid using conditional branching logic.
235 --
236 -- Access Status:
237 --   Internal Row Handler Use Only.
238 --
239 -- {End Of Comments}
240 -- ----------------------------------------------------------------------------
241 Procedure delete_validate
242   (p_rec                   in pay_ppr_shd.g_rec_type
243   ,p_effective_date        in date
244   ,p_datetrack_mode        in varchar2
245   ,p_validation_start_date in date
246   ,p_validation_end_date   in date
247   );
248 --
249 end pay_ppr_bus;