1 Package ota_tfh_api_bus AUTHID CURRENT_USER as
2 /* $Header: ottfh01t.pkh 120.0 2005/05/29 07:40:27 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------< insert_validate >----------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- This procedure controls the execution of all insert business rules
11 -- validation.
12 --
13 -- Pre Conditions:
14 -- This private procedure is called from ins procedure.
15 --
16 -- In Arguments:
17 -- A Pl/Sql record structre.
18 --
19 -- Post Success:
20 -- Processing continues.
21 --
22 -- Post Failure:
23 -- If a business rules fails the error will not be handled by this procedure
24 -- unless explicity coded.
25 --
26 -- Developer Implementation Notes:
27 -- For insert, your business rules should be coded within this procedure and
28 -- should ideally (unless really necessary) just be straight procedure or
29 -- function calls. Try and avoid using conditional branching logic.
30 --
31 -- Access Status:
32 -- Internal Development Use Only.
33 --
34 -- {End Of Comments}
35 -- ----------------------------------------------------------------------------
36 Procedure insert_validate( p_rec in out nocopy ota_tfh_api_shd.g_rec_type
37 , p_transaction_type in varchar2);
38 --
39 -- ----------------------------------------------------------------------------
40 -- |---------------------------< update_validate >----------------------------|
41 -- ----------------------------------------------------------------------------
42 -- {Start Of Comments}
43 --
44 -- Description:
45 -- This procedure controls the execution of all update business rules
46 -- validation.
47 --
48 -- Pre Conditions:
49 -- This private procedure is called from upd procedure.
50 --
51 -- In Arguments:
52 -- A Pl/Sql record structre.
53 --
54 -- Post Success:
55 -- Processing continues.
56 --
57 -- Post Failure:
58 -- If a business rules fails the error will not be handled by this procedure
59 -- unless explicity coded.
60 --
61 -- Developer Implementation Notes:
62 -- For update, your business rules should be coded within this procedure and
63 -- should ideally (unless really necessary) just be straight procedure or
64 -- function calls. Try and avoid using conditional branching logic.
65 --
66 -- Access Status:
67 -- Internal Development Use Only.
68 --
69 -- {End Of Comments}
70 -- ----------------------------------------------------------------------------
71 Procedure update_validate( p_rec in out nocopy ota_tfh_api_shd.g_rec_type
72 , p_transaction_type in varchar2);
73 --
74 -- ----------------------------------------------------------------------------
75 -- |---------------------------< delete_validate >----------------------------|
76 -- ----------------------------------------------------------------------------
77 -- {Start Of Comments}
78 --
79 -- Description:
80 -- This procedure controls the execution of all delete business rules
81 -- validation.
82 --
83 -- Pre Conditions:
84 -- This private procedure is called from del procedure.
85 --
86 -- In Arguments:
87 -- A Pl/Sql record structre.
88 --
89 -- Post Success:
90 -- Processing continues.
91 --
92 -- Post Failure:
93 -- If a business rules fails the error will not be handled by this procedure
94 -- unless explicity coded.
95 --
96 -- Developer Implementation Notes:
97 -- For delete, your business rules should be coded within this procedure and
98 -- should ideally (unless really necessary) just be straight procedure or
99 -- function calls. Try and avoid using conditional branching logic.
100 --
101 -- Access Status:
102 -- Internal Development Use Only.
103 --
104 -- {End Of Comments}
105 -- ----------------------------------------------------------------------------
106 Procedure delete_validate(p_rec in ota_tfh_api_shd.g_rec_type);
107 --
108
109 -- ---------------------------------------------------------------------------
110 -- |----------------------< set_security_group_id >--------------------------|
111 -- ---------------------------------------------------------------------------
112 -- {Start Of Comments}
113 --
114 -- Description:
115 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
116 -- group context.
117 --
118 -- Prerequisites:
119 -- The primary key identified by p_finance_header_id
120 -- already exists.
121 --
122 -- In Arguments:
123 -- p_finance_header_id
124 --
125 --
126 -- Post Success:
127 -- The security_group_id will be set in CLIENT_INFO.
128 --
129 -- Post Failure:
130 -- An error is raised if the value does not exist.
131 --
132 -- Access Status:
133 -- Internal Development Use Only.
134 --
135 -- {End Of Comments}
136 -- ---------------------------------------------------------------------------
137 procedure set_security_group_id
138 (p_finance_header_id in number
139 ,p_associated_column1 in varchar2 default null
140 );
141 --
142
143 --
144 -- ----------------------------------------------------------------------------
145 -- |-----------------------< return_legislation_code >-------------------------|
146 -- ----------------------------------------------------------------------------
147 --
148 -- {Start Of Comments}
149 --
150 -- Description:
151 -- This function will be used by the user hooks. This will be used
152 -- of by the user hooks of ota_finance_headers business process.
153 --
154 -- Pre Conditions:
155 -- This function will be called by the user hook packages.
156 --
157 -- In Arguments:
158 -- p_finance_header_id
159 --
160 -- Post Success:
161 -- Processing continues.
162 --
163 -- Post Failure:
164 -- Errors out
165 --
166 -- Developer Implementation Notes:
167 --
168 -- Access Status:
169 -- Internal Development Use Only.
170 --
171 -- {End Of Comments}
172 --------------------------------------------------------------------------------
173 --
174
175 Function return_legislation_code
176 ( p_finance_header_id in number
177 ) return varchar2;
178
179
180
181 end ota_tfh_api_bus;
[Home] [Help]