DBA Data[Home] [Help]

PACKAGE: APPS.PER_SUB_BUS

Source


1 Package per_sub_bus as
2 /* $Header: pesubrhi.pkh 120.0 2005/05/31 22:09:52 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------< chk_start_date >-----------------------------|
6 -- ----------------------------------------------------------------------------
7 -- Description
8 --   This procedure checks that the start date for the subject is valid. This
9 --   includes checking that the start date of the subject is before the end
10 --   date of the subject. This procedure also ensures that the start and end
11 --   dates of the subject are within the start and end dates of the
12 --   qualification.
13 --
14 -- Pre-Conditions
15 --   None.
16 --
17 -- In Parameters
18 --   p_subjects_taken_id        PK
19 --   p_qualification_id         ID of referenced qualification record.
20 --   p_start_date               start date of subject
21 --   p_end_date                 end date of subject
22 --   p_object_version_number    object version number
23 --
24 -- Post Success
25 --   Processing continues
26 --
27 -- Post Failure
28 --   Error raised.
29 --
30 -- Access Status
31 --   Internal table handler use only.
32 --
33 Procedure chk_start_date (p_subjects_taken_id     in number,
34                           p_qualification_id      in number,
35 			  p_start_date            in date,
36 			  p_end_date              in date,
37 			  p_object_version_number in number);
38 --
39  Procedure chk_end_date (p_subjects_taken_id     in number,
40                          p_qualification_id      in number,
41 			  p_start_date            in date,
42 			  p_end_date              in date,
43 			  p_object_version_number in number);
44 --
45 -- ----------------------------------------------------------------------------
46 -- |---------------------------< insert_validate >----------------------------|
47 -- ----------------------------------------------------------------------------
48 -- {Start Of Comments}
49 --
50 -- Description:
51 --   This procedure controls the execution of all insert business rules
52 --   validation.
53 --
54 -- Pre Conditions:
55 --   This private procedure is called from ins procedure.
56 --
57 -- In Parameters:
58 --   A Pl/Sql record structre.
59 --
60 -- Post Success:
61 --   Processing continues.
62 --
63 -- Post Failure:
64 --   If a business rules fails the error will not be handled by this procedure
65 --   unless explicity coded.
66 --
67 -- Developer Implementation Notes:
68 --   For insert, your business rules should be executed from this procedure and
69 --   should ideally (unless really necessary) just be straight procedure or
70 --   function calls. Try and avoid using conditional branching logic.
71 --
72 -- Access Status:
73 --   Internal Table Handler Use Only.
74 --
75 -- {End Of Comments}
76 -- ----------------------------------------------------------------------------
77 Procedure insert_validate(p_rec            in per_sub_shd.g_rec_type,
78 			  p_effective_date in date);
79 --
80 -- ----------------------------------------------------------------------------
81 -- |---------------------------< update_validate >----------------------------|
82 -- ----------------------------------------------------------------------------
83 -- {Start Of Comments}
84 --
85 -- Description:
86 --   This procedure controls the execution of all update business rules
87 --   validation.
88 --
89 -- Pre Conditions:
90 --   This private procedure is called from upd procedure.
91 --
92 -- In Parameters:
93 --   A Pl/Sql record structre.
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 update, your business rules should be executed from this procedure and
104 --   should ideally (unless really necessary) just be straight procedure or
105 --   function calls. Try and avoid using conditional branching logic.
106 --
107 -- Access Status:
108 --   Internal Table Handler Use Only.
109 --
110 -- {End Of Comments}
111 -- ----------------------------------------------------------------------------
112 Procedure update_validate(p_rec            in per_sub_shd.g_rec_type,
113 			  p_effective_date in date);
114 --
115 -- ----------------------------------------------------------------------------
116 -- |---------------------------< delete_validate >----------------------------|
117 -- ----------------------------------------------------------------------------
118 -- {Start Of Comments}
119 --
120 -- Description:
121 --   This procedure controls the execution of all delete business rules
122 --   validation.
123 --
124 -- Pre Conditions:
125 --   This private procedure is called from del procedure.
126 --
127 -- In Parameters:
128 --   A Pl/Sql record structre.
129 --
130 -- Post Success:
131 --   Processing continues.
132 --
133 -- Post Failure:
134 --   If a business rules fails the error will not be handled by this procedure
135 --   unless explicity coded.
136 --
137 -- Developer Implementation Notes:
138 --   For delete, your business rules should be executed from this procedure and
139 --   should ideally (unless really necessary) just be straight procedure or
140 --   function calls. Try and avoid using conditional branching logic.
141 --
142 -- Access Status:
143 --   Internal Table Handler Use Only.
144 --
145 -- {End Of Comments}
146 -- ----------------------------------------------------------------------------
147 Procedure delete_validate(p_rec in per_sub_shd.g_rec_type);
148 --
149 end per_sub_bus;