DBA Data[Home] [Help]

PACKAGE: APPS.PAY_RFI_BUS

Source


1 Package pay_rfi_bus AUTHID CURRENT_USER as
2 /* $Header: pyrfirhi.pkh 120.0 2005/05/29 08:19 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |---------------------< return_legislation_code >-------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- The function return_legislation_code has been removed because
10 -- user hooks are not there for this table.
11 --
12 -- {End Of Comments}
13 -- ---------------------------------------------------------------------------
14 --
15 --
16 -- ----------------------------------------------------------------------------
17 -- |---------------------------< insert_validate >----------------------------|
18 -- ----------------------------------------------------------------------------
19 -- {Start Of Comments}
20 --
21 -- Description:
22 --   This procedure controls the execution of all insert business rules
23 --   validation.
24 --
25 -- Prerequisites:
26 --   This private procedure is called from ins procedure.
27 --
28 -- In Parameters:
29 --   A Pl/Sql record structre.
30 --
31 -- Post Success:
32 --   Processing continues.
33 --
34 -- Post Failure:
35 --   If a business rules fails the error will not be handled by this procedure
36 --   unless explicity coded.
37 --
38 -- Developer Implementation Notes:
39 --   For insert, your business rules should be executed from this procedure and
40 --   should ideally (unless really necessary) just be straight procedure or
41 --   function calls. Try and avoid using conditional branching logic.
42 --
43 -- Access Status:
44 --   Internal Row Handler Use Only.
45 --
46 -- {End Of Comments}
47 -- ----------------------------------------------------------------------------
48 Procedure insert_validate
49   (p_rec                   in pay_rfi_shd.g_rec_type
50   ,p_effective_date        in date
51   ,p_datetrack_mode        in varchar2
52   ,p_validation_start_date in date
53   ,p_validation_end_date   in date
54   );
55 --
56 -- ----------------------------------------------------------------------------
57 -- |---------------------------< update_validate >----------------------------|
58 -- ----------------------------------------------------------------------------
59 -- {Start Of Comments}
60 --
61 -- Description:
62 --   This procedure controls the execution of all update business rules
63 --   validation.
64 --
65 -- Prerequisites:
66 --   This private procedure is called from upd procedure.
67 --
68 -- In Parameters:
69 --   A Pl/Sql record structre.
70 --
71 -- Post Success:
72 --   Processing continues.
73 --
74 -- Post Failure:
75 --   If a business rules fails the error will not be handled by this procedure
76 --   unless explicity coded.
77 --
78 -- Developer Implementation Notes:
79 --   For update, your business rules should be executed from this procedure and
80 --   should ideally (unless really necessary) just be straight procedure or
81 --   function calls. Try and avoid using conditional branching logic.
82 --
83 -- Access Status:
84 --   Internal Row Handler Use Only.
85 --
86 -- {End Of Comments}
87 -- ----------------------------------------------------------------------------
88 Procedure update_validate
89   (p_rec                     in pay_rfi_shd.g_rec_type
90   ,p_effective_date          in date
91   ,p_datetrack_mode          in varchar2
92   ,p_validation_start_date   in date
93   ,p_validation_end_date     in date
94   );
95 --
96 -- ----------------------------------------------------------------------------
97 -- |---------------------------< delete_validate >----------------------------|
98 -- ----------------------------------------------------------------------------
99 -- {Start Of Comments}
100 --
101 -- Description:
102 --   This procedure controls the execution of all delete business rules
103 --   validation.
104 --
105 -- Prerequisites:
106 --   This private procedure is called from del procedure.
107 --
108 -- In Parameters:
109 --   A Pl/Sql record structure.
110 --
111 -- Post Success:
112 --   Processing continues.
113 --
114 -- Post Failure:
115 --   If a business rules fails the error will not be handled by this procedure
116 --   unless explicity coded.
117 --
118 -- Developer Implementation Notes:
119 --   For delete, your business rules should be executed from this procedure and
120 --   should ideally (unless really necessary) just be straight procedure or
121 --   function calls. Try and avoid using conditional branching logic.
122 --
123 -- Access Status:
124 --   Internal Row Handler Use Only.
125 --
126 -- {End Of Comments}
127 -- ----------------------------------------------------------------------------
128 Procedure delete_validate
129   (p_rec                   in pay_rfi_shd.g_rec_type
130   ,p_effective_date        in date
131   ,p_datetrack_mode        in varchar2
132   ,p_validation_start_date in date
133   ,p_validation_end_date   in date
134   );
135 --
136 -- ----------------------------------------------------------------------------
137 -- |-------------------< chk_report_format_item_id >--------------------------|
138 -- ----------------------------------------------------------------------------
139 -- {Start Of Comments}
140 --
141 -- Description:
142 --   This procedure is used to check the validity of the
143 --   report_format_item_id that will be used for the report format item.
144 --   Though this id is generated internally, this check is necessary
145 --   because the primary key constraint on this table does not consist of this
146 --   column and hence any discrepancy in report_format_item_id will not be
147 --   caught by the primary key constraint.
148 --
149 -- Pre Conditions:
150 --   Must be called only while Insert and after the report_format_item_id
151 --   is derived.
152 --
153 --
154 -- In Arguments:
155 --   report_format_item_id
156 --
157 --
158 -- Post Success:
159 --   Processing continues.
160 --
161 --
162 -- Post Failure:
163 --   Failure might occur if the report_format_item_id is null or
164 --   there already exists a different report format item with the
165 --   same id. Errors are trapped and reported.
166 --
167 -- Access Status:
168 --   Internal Row Handler Use Only.
169 --
170 -- {End Of Comments}
171 -- ----------------------------------------------------------------------------
172 Procedure chk_report_format_item_id
173   ( p_report_format_item_id  in  number );
174 --
175 end pay_rfi_bus;