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