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