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