1 Package ben_xic_bus AUTHID CURRENT_USER as
2 /* $Header: bexicrhi.pkh 120.2 2005/06/08 15:56:05 tjesumic 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_ext_incl_chg_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_ext_incl_chg_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_ext_incl_chg_id in number
38 );
39 --
40 --
41 --
42 -- ---------------------------------------------------------------------------
43 -- |---------------------< return_legislation_code >-------------------------|
44 -- ---------------------------------------------------------------------------
45 --
46 -- Description:
47 -- Return the legislation code for a specific primary key value
48 --
49 -- Prerequisites:
50 -- The primary key identified by p_ext_incl_chg_id already exists.
51 --
52 -- In Arguments:
53 -- p_ext_incl_chg_id
54 --
55 -- Post Success:
56 -- If the value is found this function will return the values business
57 -- group legislation code.
58 --
59 -- Post Failure:
60 -- An error is raised if the value does not exist.
61 --
62 -- Access Status:
63 -- Internal Development Use Only.
64 --
65 function return_legislation_code
66 (p_ext_incl_chg_id in number) 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 structre.
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 and
93 -- should ideally (unless really necessary) just be straight procedure or
94 -- 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(p_rec in ben_xic_shd.g_rec_type
102 ,p_effective_date in date);
103 --
104 -- ----------------------------------------------------------------------------
105 -- |---------------------------< update_validate >----------------------------|
106 -- ----------------------------------------------------------------------------
107 -- {Start Of Comments}
108 --
109 -- Description:
110 -- This procedure controls the execution of all update business rules
111 -- validation.
112 --
113 -- Prerequisites:
114 -- This private procedure is called from upd procedure.
115 --
116 -- In Parameters:
117 -- A Pl/Sql record structre.
118 --
119 -- Post Success:
120 -- Processing continues.
121 --
122 -- Post Failure:
123 -- If a business rules fails the error will not be handled by this procedure
124 -- unless explicity coded.
125 --
126 -- Developer Implementation Notes:
127 -- For update, your business rules should be executed from this procedure and
128 -- should ideally (unless really necessary) just be straight procedure or
129 -- function calls. Try and avoid using conditional branching logic.
130 --
131 -- Access Status:
132 -- Internal Row Handler Use Only.
133 --
134 -- {End Of Comments}
135 -- ----------------------------------------------------------------------------
136 Procedure update_validate(p_rec in ben_xic_shd.g_rec_type
137 ,p_effective_date in date);
138 --
139 -- ----------------------------------------------------------------------------
140 -- |---------------------------< delete_validate >----------------------------|
141 -- ----------------------------------------------------------------------------
142 -- {Start Of Comments}
143 --
144 -- Description:
145 -- This procedure controls the execution of all delete business rules
146 -- validation.
147 --
148 -- Prerequisites:
149 -- This private procedure is called from del procedure.
150 --
151 -- In Parameters:
152 -- A Pl/Sql record structre.
153 --
154 -- Post Success:
155 -- Processing continues.
156 --
157 -- Post Failure:
158 -- If a business rules fails the error will not be handled by this procedure
159 -- unless explicity coded.
160 --
161 -- Developer Implementation Notes:
162 -- For delete, your business rules should be executed from this procedure and
163 -- should ideally (unless really necessary) just be straight procedure or
164 -- function calls. Try and avoid using conditional branching logic.
165 --
166 -- Access Status:
167 -- Internal Row Handler Use Only.
168 --
169 -- {End Of Comments}
170 -- ----------------------------------------------------------------------------
171 Procedure delete_validate(p_rec in ben_xic_shd.g_rec_type
172 ,p_effective_date in date);
173 --
174 end ben_xic_bus;
[Home] [Help]