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