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