1 Package pqp_pty_bus as
2 /* $Header: pqptyrhi.pkh 120.0.12000000.1 2007/01/16 04:29:04 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_pension_type_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_pension_type_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_pension_type_id in number
38 ,p_associated_column1 in varchar2 default null
39 );
40 --
41 --
42 -- ---------------------------------------------------------------------------
43 -- |---------------------< return_legislation_code >-------------------------|
44 -- ---------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 -- Return the legislation code for a specific primary key value
49 --
50 -- Prerequisites:
51 -- The primary key identified by p_pension_type_id
52 -- already exists.
53 --
54 -- In Arguments:
55 -- p_pension_type_id
56 --
57 --
58 -- Post Success:
59 -- The business group's legislation code will be returned.
60 --
61 -- Post Failure:
62 -- An error is raised if the value does not exist.
63 --
64 -- Access Status:
65 -- Internal Development Use Only.
66 --
67 -- {End Of Comments}
68 -- ---------------------------------------------------------------------------
69 FUNCTION return_legislation_code
70 (p_pension_type_id in number
71 ) RETURN varchar2;
72 --
73 --
74 -- ----------------------------------------------------------------------------
75 -- |---------------------------< insert_validate >----------------------------|
76 -- ----------------------------------------------------------------------------
77 -- {Start Of Comments}
78 --
79 -- Description:
80 -- This procedure controls the execution of all insert business rules
81 -- validation.
82 --
83 -- Prerequisites:
84 -- This private procedure is called from ins procedure.
85 --
86 -- In Parameters:
87 -- A Pl/Sql record structre.
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 -- Developer Implementation Notes:
97 -- For insert, your business rules should be executed from this procedure and
98 -- should ideally (unless really necessary) just be straight procedure or
99 -- function calls. Try and avoid using conditional branching logic.
100 --
101 -- Access Status:
102 -- Internal Row Handler Use Only.
103 --
104 -- {End Of Comments}
105 -- ----------------------------------------------------------------------------
106 Procedure insert_validate
107 (p_rec in pqp_pty_shd.g_rec_type
108 ,p_effective_date in date
109 ,p_datetrack_mode in varchar2
110 ,p_validation_start_date in date
111 ,p_validation_end_date in out nocopy date
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 structre.
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 -- Developer Implementation Notes:
137 -- For update, your business rules should be executed from this procedure and
138 -- should ideally (unless really necessary) just be straight procedure or
139 -- function calls. Try and avoid using conditional branching logic.
140 --
141 -- Access Status:
142 -- Internal Row Handler Use Only.
143 --
144 -- {End Of Comments}
145 -- ----------------------------------------------------------------------------
146 Procedure update_validate
147 (p_rec in pqp_pty_shd.g_rec_type
148 ,p_effective_date in date
149 ,p_datetrack_mode in varchar2
150 ,p_validation_start_date in date
151 ,p_validation_end_date in out nocopy date
152 );
153 --
154 -- ----------------------------------------------------------------------------
155 -- |---------------------------< delete_validate >----------------------------|
156 -- ----------------------------------------------------------------------------
157 -- {Start Of Comments}
158 --
159 -- Description:
160 -- This procedure controls the execution of all delete business rules
161 -- validation.
162 --
163 -- Prerequisites:
164 -- This private procedure is called from del procedure.
165 --
166 -- In Parameters:
167 -- A Pl/Sql record structure.
168 --
169 -- Post Success:
170 -- Processing continues.
171 --
172 -- Post Failure:
173 -- If a business rules fails the error will not be handled by this procedure
174 -- unless explicity coded.
175 --
176 -- Developer Implementation Notes:
177 -- For delete, your business rules should be executed from this procedure and
178 -- should ideally (unless really necessary) just be straight procedure or
179 -- function calls. Try and avoid using conditional branching logic.
180 --
181 -- Access Status:
182 -- Internal Row Handler Use Only.
183 --
184 -- {End Of Comments}
185 -- ----------------------------------------------------------------------------
186 Procedure delete_validate
187 (p_rec in pqp_pty_shd.g_rec_type
188 ,p_effective_date in date
189 ,p_datetrack_mode in varchar2
190 ,p_validation_start_date in date
191 ,p_validation_end_date in date
192 );
193 --
194 end pqp_pty_bus;
[Home] [Help]