1 Package per_bpa_bus as
2 /* $Header: pebparhi.pkh 120.0 2005/05/31 06:17:30 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |---------------------< return_legislation_code >-------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- Return the legislation code for a specific primary key value
11 --
12 -- Prerequisites:
13 -- The primary key identified by p_processed_assignment_id already exists.
14 --
15 -- In Arguments:
16 -- p_processed_assignment_id
17 --
18 -- Post Success:
19 -- The business group's legislation code will be returned.
20 --
21 -- Post Failure:
22 -- An error is raised if the value does not exist.
23 --
24 -- Access Status:
25 -- Internal Development Use Only.
26 --
27 -- {End Of Comments}
28 -- ---------------------------------------------------------------------------
29 FUNCTION return_legislation_code
30 (p_processed_assignment_id in number
31 ) RETURN varchar2;
32 --
33 --
34 -- ----------------------------------------------------------------------------
35 -- |---------------------------< insert_validate >----------------------------|
36 -- ----------------------------------------------------------------------------
37 -- {Start of comments}
38 --
39 -- Description:
40 -- This procedure controls the execution of all insert business rules
41 -- validation.
42 --
43 -- Prerequisites:
44 -- This private procedure is called from ins procedure.
45 --
46 -- In Parameters:
47 -- A Pl/Sql record structure.
48 --
49 -- Post Success:
50 -- Processing continues.
51 --
52 -- Post Failure:
53 -- If a business rules fails the error will not be handled by this procedure
54 -- unless explicity coded.
55 --
56 -- Developer Implementation Notes:
57 -- For insert, your business rules should be executed from this procedure and
58 -- should ideally (unless really necessary) just be straight procedure or
59 -- function calls. Try and avoid using conditional branching logic.
60 --
61 -- Access Status:
62 -- Internal Row Handler Use Only.
63 --
64 -- {End of comments}
65 -- ----------------------------------------------------------------------------
66 Procedure insert_validate
67 (p_effective_date in date
68 ,p_rec in per_bpa_shd.g_rec_type
69 );
70 --
71 -- ----------------------------------------------------------------------------
72 -- |---------------------------< update_validate >----------------------------|
73 -- ----------------------------------------------------------------------------
74 -- {Start Of Comments}
75 --
76 -- Description:
77 -- This procedure controls the execution of all update business rules
78 -- validation.
79 --
80 -- Prerequisites:
81 -- This private procedure is called from upd procedure.
82 --
83 -- In Parameters:
84 -- A Pl/Sql record structure.
85 --
86 -- Post Success:
87 -- Processing continues.
88 --
89 -- Post Failure:
90 -- If a business rules fails the error will not be handled by this procedure
91 -- unless explicity coded.
92 --
93 -- Developer Implementation Notes:
94 -- For update, your business rules should be executed from this procedure and
95 -- should ideally (unless really necessary) just be straight procedure or
96 -- function calls. Try and avoid using conditional branching logic.
97 --
98 -- Access Status:
99 -- Internal Row Handler Use Only.
100 --
101 -- {End Of Comments}
102 -- ----------------------------------------------------------------------------
103 Procedure update_validate
104 (p_effective_date in date
105 ,p_rec in per_bpa_shd.g_rec_type
106 );
107 --
108 -- ----------------------------------------------------------------------------
109 -- |---------------------------< delete_validate >----------------------------|
110 -- ----------------------------------------------------------------------------
111 -- {Start Of Comments}
112 --
113 -- Description:
114 -- This procedure controls the execution of all delete business rules
115 -- validation.
116 --
117 -- Prerequisites:
118 -- This private procedure is called from del procedure.
119 --
120 -- In Parameters:
121 -- A Pl/Sql record structre.
122 --
123 -- Post Success:
124 -- Processing continues.
125 --
126 -- Post Failure:
127 -- If a business rules fails the error will not be handled by this procedure
128 -- unless explicity coded.
129 --
130 -- Developer Implementation Notes:
131 -- For delete, your business rules should be executed from this procedure and
132 -- should ideally (unless really necessary) just be straight procedure or
133 -- function calls. Try and avoid using conditional branching logic.
134 --
135 -- Access Status:
136 -- Internal Row Handler Use Only.
137 --
138 --
139 -- ----------------------------------------------------------------------------
140 Procedure delete_validate
141 (p_rec in per_bpa_shd.g_rec_type
142 );
143 --
144 end per_bpa_bus;
[Home] [Help]