DBA Data[Home] [Help]

PACKAGE: APPS.BEN_REG_BUS

Source


1 Package ben_reg_bus as
2 /* $Header: beregrhi.pkh 120.0.12010000.1 2008/07/29 13:01:25 appldev ship $ */
3 --
4 --
5 --  ---------------------------------------------------------------------------
6 --  |---------------------< return_legislation_code >-------------------------|
7 --  ---------------------------------------------------------------------------
8 --
9 --  Description:
10 --    Return the legislation code for a specific primary key value
11 --
12 --  Prerequisites:
13 --    The primary key identified by p_regn_id already exists.
14 --
15 --  In Arguments:
16 --    p_regn_id
17 --
18 --  Post Success:
19 --    If the value is found this function will return the values business
20 --    group legislation code.
21 --
22 --  Post Failure:
23 --    An error is raised if the value does not exist.
24 --
25 --  Access Status:
26 --    Internal Development Use Only.
27 --
28 function return_legislation_code
29   (p_regn_id in number) return varchar2;
30 --
31 -- ----------------------------------------------------------------------------
32 -- |---------------------------< chk_name >----------------------------|
33 -- ----------------------------------------------------------------------------
34 -- {Start Of Comments}
35 --
36 -- Description
37 --   This procedure is used to check that the name field is unique
38 --   on insert and on update.
39 --
40 -- Pre Conditions
41 --   None.
42 --
43 -- In Parameters
44 --   regn_id PK of record being inserted or updated.
45 --   name that is beeing inserted ot updated to.
46 --   effective_date Effective Date of session
47 --   business group ID
48 --   object_version_number Object version number of record being
49 --                         inserted or updated.
50 --
51 -- Post Success
52 --   Processing continues
53 --
54 -- Post Failure
55 --   Errors handled by the procedure
56 --
57 -- Access Status
58 --   HR Development Internal use only.
59 --
60 --
61 -- {End Of Comments}
62 -- ----------------------------------------------------------------------------
63 Procedure chk_name(p_regn_id                     in number,
64                    p_name                        in varchar2,
65                    p_effective_date              in date,
66                    p_validation_start_date         in date,
67                    p_validation_end_date           in date,
68                    p_business_group_id           in number,
69                    p_object_version_number       in number);
70 --
71 -- ----------------------------------------------------------------------------
72 -- |---------------------------< insert_validate >----------------------------|
73 -- ----------------------------------------------------------------------------
74 -- {Start Of Comments}
75 --
76 -- Description:
77 --   This procedure controls the execution of all insert business rules
78 --   validation.
79 --
80 -- Prerequisites:
81 --   This private procedure is called from ins procedure.
82 --
83 -- In Parameters:
84 --   A Pl/Sql record structre.
85 --
86 -- Post Success:
87 --   Processing continues.
88 --
89 -- Post Failure:
90 --   If a business rules fails the error will not be handled by this procedure
91 --   unless explicity coded.
92 --
93 -- Developer Implementation Notes:
94 --   For insert, your business rules should be executed from this procedure and
95 --   should ideally (unless really necessary) just be straight procedure or
96 --   function calls. Try and avoid using conditional branching logic.
97 --
98 -- Access Status:
99 --   Internal Row Handler Use Only.
100 --
101 -- {End Of Comments}
102 -- ----------------------------------------------------------------------------
103 Procedure insert_validate
104 	(p_rec 			 in ben_reg_shd.g_rec_type,
105 	 p_effective_date	 in date,
106 	 p_datetrack_mode	 in varchar2,
107 	 p_validation_start_date in date,
108 	 p_validation_end_date	 in date);
109 --
110 -- ----------------------------------------------------------------------------
111 -- |---------------------------< update_validate >----------------------------|
112 -- ----------------------------------------------------------------------------
113 -- {Start Of Comments}
114 --
115 -- Description:
116 --   This procedure controls the execution of all update business rules
117 --   validation.
118 --
119 -- Prerequisites:
120 --   This private procedure is called from upd procedure.
121 --
122 -- In Parameters:
123 --   A Pl/Sql record structre.
124 --
125 -- Post Success:
126 --   Processing continues.
127 --
128 -- Post Failure:
129 --   If a business rules fails the error will not be handled by this procedure
130 --   unless explicity coded.
131 --
132 -- Developer Implementation Notes:
133 --   For update, your business rules should be executed from this procedure and
134 --   should ideally (unless really necessary) just be straight procedure or
135 --   function calls. Try and avoid using conditional branching logic.
136 --
137 -- Access Status:
138 --   Internal Row Handler Use Only.
139 --
140 -- {End Of Comments}
141 -- ----------------------------------------------------------------------------
142 Procedure update_validate
143 	(p_rec 			 in ben_reg_shd.g_rec_type,
144 	 p_effective_date	 in date,
145 	 p_datetrack_mode	 in varchar2,
146 	 p_validation_start_date in date,
147 	 p_validation_end_date	 in date);
148 --
149 -- ----------------------------------------------------------------------------
150 -- |---------------------------< delete_validate >----------------------------|
151 -- ----------------------------------------------------------------------------
152 -- {Start Of Comments}
153 --
154 -- Description:
155 --   This procedure controls the execution of all delete business rules
156 --   validation.
157 --
158 -- Prerequisites:
159 --   This private procedure is called from del procedure.
160 --
161 -- In Parameters:
162 --   A Pl/Sql record structre.
163 --
164 -- Post Success:
165 --   Processing continues.
166 --
167 -- Post Failure:
168 --   If a business rules fails the error will not be handled by this procedure
169 --   unless explicity coded.
170 --
171 -- Developer Implementation Notes:
172 --   For delete, your business rules should be executed from this procedure and
173 --   should ideally (unless really necessary) just be straight procedure or
174 --   function calls. Try and avoid using conditional branching logic.
175 --
176 -- Access Status:
177 --   Internal Row Handler Use Only.
178 --
179 -- {End Of Comments}
180 -- ----------------------------------------------------------------------------
181 Procedure delete_validate
182 	(p_rec 			 in ben_reg_shd.g_rec_type,
183 	 p_effective_date	 in date,
184 	 p_datetrack_mode	 in varchar2,
185 	 p_validation_start_date in date,
186 	 p_validation_end_date	 in date);
187 --
188 end ben_reg_bus;