DBA Data[Home] [Help]

PACKAGE: APPS.BEN_PRY_BUS

Source


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