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