DBA Data[Home] [Help]

PACKAGE: APPS.PER_ABT_BUS

Source


1 Package per_abt_bus as
2 /* $Header: peabtrhi.pkh 120.0 2005/05/31 04:48 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |---------------------< return_legislation_code >-------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 --  Description:
10 --    Return the legislation code for a specific primary key value
11 --
12 --  Prerequisites:
13 --    The primary key identified by p_absence_attendance_type_id
14 --     already exists.
15 --
16 --  In Arguments:
17 --    p_absence_attendance_type_id
18 --
19 --
20 --  Post Success:
21 --    The business group's legislation code will be returned.
22 --
23 --  Post Failure:
24 --    An error is raised if the value does not exist.
25 --
26 --  Access Status:
27 --    Internal Development Use Only.
28 --
29 -- {End Of Comments}
30 -- ---------------------------------------------------------------------------
31 FUNCTION return_legislation_code
32   (p_absence_attendance_type_id           in     number
33   ,p_language                             in     varchar2
34   ) RETURN varchar2;
35 --
36 --
37 -- ----------------------------------------------------------------------------
38 -- |---------------------------< insert_validate >----------------------------|
39 -- ----------------------------------------------------------------------------
40 -- {Start of comments}
41 --
42 -- Description:
43 --   This procedure controls the execution of all insert business rules
44 --   validation.
45 --
46 -- Prerequisites:
47 --   This private procedure is called from ins procedure.
48 --
49 -- In Parameters:
50 --   A Pl/Sql record structure.
51 --
52 -- Post Success:
53 --   Processing continues.
54 --
55 -- Post Failure:
56 --   If a business rules fails the error will not be handled by this procedure
57 --   unless explicity coded.
58 --
59 -- Developer Implementation Notes:
60 --   For insert, your business rules should be executed from this procedure
61 --   and should ideally (unless really necessary) just be straight procedure
62 --   or function calls. Try and avoid using conditional branching logic.
63 --
64 -- Access Status:
65 --   Internal Row Handler Use Only.
66 --
67 -- {End of comments}
68 -- ----------------------------------------------------------------------------
69 Procedure insert_validate
70   (p_rec                          in per_abt_shd.g_rec_type
71   ,p_absence_attendance_type_id   in number
72   );
73 --
74 -- ----------------------------------------------------------------------------
75 -- |---------------------------< update_validate >----------------------------|
76 -- ----------------------------------------------------------------------------
77 -- {Start Of Comments}
78 --
79 -- Description:
80 --   This procedure controls the execution of all update business rules
81 --   validation.
82 --
83 -- Prerequisites:
84 --   This private procedure is called from upd procedure.
85 --
86 -- In Parameters:
87 --   A Pl/Sql record structure.
88 --
89 -- Post Success:
90 --   Processing continues.
91 --
92 -- Post Failure:
93 --   If a business rules fails the error will not be handled by this procedure
94 --   unless explicity coded.
95 --
96 -- Access Status:
97 --   Internal Row Handler Use Only.
98 --
99 -- {End Of Comments}
100 -- ----------------------------------------------------------------------------
101 Procedure update_validate
102   (p_rec                          in per_abt_shd.g_rec_type
103   );
104 --
105 -- ----------------------------------------------------------------------------
106 -- |---------------------------< delete_validate >----------------------------|
107 -- ----------------------------------------------------------------------------
108 -- {Start Of Comments}
109 --
110 -- Description:
111 --   This procedure controls the execution of all delete business rules
112 --   validation.
113 --
114 -- Prerequisites:
115 --   This private procedure is called from del procedure.
116 --
117 -- In Parameters:
118 --   A Pl/Sql record structure.
119 --
120 -- Post Success:
121 --   Processing continues.
122 --
123 -- Post Failure:
124 --   If a business rules fails the error will not be handled by this procedure
125 --   unless explicity coded.
126 --
127 -- Developer Implementation Notes:
128 --   For delete, your business rules should be executed from this procedure
129 --   and should ideally (unless really necessary) just be straight procedure
130 --   or function calls. Try and avoid using conditional branching logic.
131 --
132 -- Access Status:
133 --   Internal Row Handler Use Only.
134 --
135 -- {End Of Comments}
136 -- ----------------------------------------------------------------------------
137 Procedure delete_validate
138   (p_rec              in per_abt_shd.g_rec_type
139   );
140 --
141 -- ----------------------------------------------------------------------------
142 -- |---------------------------< set_translation_globals >--------------------|
143 -- ----------------------------------------------------------------------------
144 -- {Start Of Comments}
145 --
146 -- Description:
147 --   This procedure sets global variables for subsequent validation from the form
148 --
149 -- Prerequisites:
150 --   This procedure is called from from the TRANSLATIONS trigger in the form
151 --
152 -- In Parameters:
153 --
154 -- Developer Implementation Notes:
155 -- The code replicates logic of chk_name,changes will need to be maintained there also.
156 --
157 -- Access Status:
158 --   Forms MLS Widget Only.
159 --
160 -- {End Of Comments}
161 -- ----------------------------------------------------------------------------
162 Procedure set_translation_globals
163   (p_business_group_id              in number
164   );
165 --
166 -- ----------------------------------------------------------------------------
167 -- |---------------------------< validate_translation >------------------------|
168 -- ----------------------------------------------------------------------------
169 -- {Start Of Comments}
170 --
171 -- Description:
172 --   This procedure performs the validation for the MLS widget.
173 --
174 -- Prerequisites:
175 --   This procedure is called from from the MLS widget.
176 --
177 -- In Parameters:
178 --
179 -- Post Success:
180 --   Processing continues.
181 --
182 -- Post Failure:
183 --   If a business rules fails the error will not be handled by this procedure
184 --
188 --   Forms MLS Widget Only.
185 -- Developer Implementation Notes:
186 --
187 -- Access Status:
189 --
190 -- {End Of Comments}
191 -- ----------------------------------------------------------------------------
192 Procedure validate_translation
193   (p_absence_attendance_type_id     in number
194   ,p_language                       in varchar2
195   ,p_name                           in varchar2
196   );
197 --
198 end per_abt_bus;