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