1 Package per_bba_bus as
2 /* $Header: pebbarhi.pkh 120.0 2005/05/31 06:02:01 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_amount_id already exists.
15 --
16 -- In Arguments:
17 -- p_balance_amount_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_amount_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_amount_id already exists.
45 --
46 -- In Arguments:
47 -- p_balance_amount_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_amount_id in number) return varchar2;
62 --
63 --
64 -- ----------------------------------------------------------------------------
65 -- |---------------------------< insert_validate >----------------------------|
66 -- ----------------------------------------------------------------------------
67 -- {Start of comments}
68 --
69 -- Description:
70 -- This procedure controls the execution of all insert business rules
71 -- validation.
72 --
73 -- Prerequisites:
74 -- This private procedure is called from ins procedure.
75 --
76 -- In Parameters:
77 -- A Pl/Sql record structre.
78 --
79 -- Post Success:
80 -- Processing continues.
81 --
82 -- Post Failure:
83 -- If a business rules fails the error will not be handled by this procedure
84 -- unless explicity coded.
85 --
86 -- Developer Implementation Notes:
87 -- For insert, your business rules should be executed from this procedure and
88 -- should ideally (unless really necessary) just be straight procedure or
89 -- function calls. Try and avoid using conditional branching logic.
90 --
91 -- Access Status:
92 -- Internal Row Handler Use Only.
93 --
94 -- {End of comments}
95 -- ----------------------------------------------------------------------------
96 Procedure insert_validate(p_effective_date in date,
97 p_rec in per_bba_shd.g_rec_type
98 );
99 --
100 -- ----------------------------------------------------------------------------
101 -- |---------------------------< update_validate >----------------------------|
102 -- ----------------------------------------------------------------------------
103 -- {Start Of Comments}
104 --
105 -- Description:
106 -- This procedure controls the execution of all update business rules
107 -- validation.
108 --
109 -- Prerequisites:
110 -- This private procedure is called from upd procedure.
111 --
112 -- In Parameters:
113 -- A Pl/Sql record structre.
114 --
115 -- Post Success:
116 -- Processing continues.
117 --
118 -- Post Failure:
119 -- If a business rules fails the error will not be handled by this procedure
120 -- unless explicity coded.
121 --
122 -- Developer Implementation Notes:
123 -- For update, your business rules should be executed from this procedure and
124 -- should ideally (unless really necessary) just be straight procedure or
125 -- function calls. Try and avoid using conditional branching logic.
126 --
127 -- Access Status:
128 -- Internal Row Handler Use Only.
129 --
130 -- {End Of Comments}
131 -- ----------------------------------------------------------------------------
132 Procedure update_validate(p_effective_date in date,
133 p_rec in per_bba_shd.g_rec_type
134 );
135 --
136 -- ----------------------------------------------------------------------------
137 -- |---------------------------< delete_validate >----------------------------|
138 -- ----------------------------------------------------------------------------
139 -- {Start Of Comments}
140 --
141 -- Description:
142 -- This procedure controls the execution of all delete business rules
143 -- validation.
144 --
145 -- Prerequisites:
146 -- This private procedure is called from del procedure.
147 --
148 -- In Parameters:
149 -- A Pl/Sql record structre.
150 --
151 -- Post Success:
152 -- Processing continues.
153 --
154 -- Post Failure:
155 -- If a business rules fails the error will not be handled by this procedure
156 -- unless explicity coded.
157 --
158 -- Developer Implementation Notes:
159 -- For delete, your business rules should be executed from this procedure and
160 -- should ideally (unless really necessary) just be straight procedure or
161 -- function calls. Try and avoid using conditional branching logic.
162 --
163 -- Access Status:
164 -- Internal Row Handler Use Only.
165 --
166 --
167 -- ----------------------------------------------------------------------------
168 Procedure delete_validate(p_rec in per_bba_shd.g_rec_type);
169 --
170 end per_bba_bus;
[Home] [Help]