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