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