1 Package ben_xer_bus as
2 /* $Header: bexerrhi.pkh 120.0 2005/05/28 12:32:39 appldev noship $ */
3 -- ---------------------------------------------------------------------------
4 -- |----------------------< set_security_group_id >--------------------------|
5 -- ---------------------------------------------------------------------------
6 -- {Start Of Comments}
7 --
8 -- Description:
9 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
10 -- group context.
11 -- It is only valid to call this procedure when the primary key
12 -- is within a buisiness group context.
13 --
14 -- Prerequisites:
15 -- The primary key identified by p_ext_data_elmt_in_rcd_id
16 -- already exists.
17 --
18 -- In Arguments:
19 -- p_ext_data_elmt_in_rcd_id
20 --
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 value does not exist.
27 -- An error is also raised when the primary key data is outside
28 -- of a buisiness group context.
29 --
30 -- Access Status:
31 -- Internal Development Use Only.
32 --
33 -- {End Of Comments}
34 -- ---------------------------------------------------------------------------
35 procedure set_security_group_id
36 (p_ext_data_elmt_in_rcd_id in number
37 );
38
39 --
40 --
41 -- ---------------------------------------------------------------------------
42 -- |---------------------< return_legislation_code >-------------------------|
43 -- ---------------------------------------------------------------------------
44 --
45 -- Description:
46 -- Return the legislation code for a specific primary key value
47 --
48 -- Prerequisites:
49 -- The primary key identified by p_ext_data_elmt_in_rcd_id already exists.
50 --
51 -- In Arguments:
52 -- p_ext_data_elmt_in_rcd_id
53 --
54 -- Post Success:
55 -- If the value is found this function will return the values business
56 -- group legislation code.
57 --
58 -- Post Failure:
59 -- An error is raised if the value does not exist.
60 --
61 -- Access Status:
62 -- Internal Development Use Only.
63 --
64 function return_legislation_code
65 (p_ext_data_elmt_in_rcd_id in number) return varchar2;
66 --
67 --
68 -- ----------------------------------------------------------------------------
69 -- |---------------------------< insert_validate >----------------------------|
70 -- ----------------------------------------------------------------------------
71 -- {Start Of Comments}
72 --
73 -- Description:
74 -- This procedure controls the execution of all insert business rules
75 -- validation.
76 --
77 -- Prerequisites:
78 -- This private procedure is called from ins procedure.
79 --
80 -- In Parameters:
81 -- A Pl/Sql record structre.
82 --
83 -- Post Success:
84 -- Processing continues.
85 --
86 -- Post Failure:
87 -- If a business rules fails the error will not be handled by this procedure
88 -- unless explicity coded.
89 --
90 -- Developer Implementation Notes:
91 -- For insert, your business rules should be executed from this procedure and
92 -- should ideally (unless really necessary) just be straight procedure or
93 -- function calls. Try and avoid using conditional branching logic.
94 --
95 -- Access Status:
96 -- Internal Row Handler Use Only.
97 --
98 -- {End Of Comments}
99 -- ----------------------------------------------------------------------------
100 Procedure insert_validate(p_rec in ben_xer_shd.g_rec_type
101 ,p_effective_date in date);
102 --
103 -- ----------------------------------------------------------------------------
104 -- |---------------------------< update_validate >----------------------------|
105 -- ----------------------------------------------------------------------------
106 -- {Start Of Comments}
107 --
108 -- Description:
109 -- This procedure controls the execution of all update business rules
110 -- validation.
111 --
112 -- Prerequisites:
113 -- This private procedure is called from upd procedure.
114 --
115 -- In Parameters:
116 -- A Pl/Sql record structre.
117 --
118 -- Post Success:
119 -- Processing continues.
120 --
121 -- Post Failure:
122 -- If a business rules fails the error will not be handled by this procedure
123 -- unless explicity coded.
124 --
125 -- Developer Implementation Notes:
126 -- For update, your business rules should be executed from this procedure and
127 -- should ideally (unless really necessary) just be straight procedure or
128 -- function calls. Try and avoid using conditional branching logic.
129 --
130 -- Access Status:
131 -- Internal Row Handler Use Only.
132 --
133 -- {End Of Comments}
134 -- ----------------------------------------------------------------------------
135 Procedure update_validate(p_rec in ben_xer_shd.g_rec_type
136 ,p_effective_date in date);
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 structre.
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 and
162 -- should ideally (unless really necessary) just be straight procedure or
163 -- 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(p_rec in ben_xer_shd.g_rec_type
171 ,p_effective_date in date);
172 --
173 end ben_xer_bus;
[Home] [Help]