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