1 Package per_ctr_bus as
2 /* $Header: pectrrhi.pkh 120.2 2007/02/19 11:58:34 ssutar ship $ */
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 Parameters:
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 executed from 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 Table Handler Use Only.
33 --
34 -- {End Of Comments}
35 -- ----------------------------------------------------------------------------
36 Procedure insert_validate(p_rec in per_ctr_shd.g_rec_type,
37 p_effective_date in date);
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 Parameters:
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 executed from 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 Table Handler Use Only.
68 --
69 -- {End Of Comments}
70 -- ----------------------------------------------------------------------------
71 Procedure update_validate(p_rec in per_ctr_shd.g_rec_type
72 ,p_effective_date in date);
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 Parameters:
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 executed from 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 Table Handler Use Only.
103 --
104 -- {End Of Comments}
105 -- ----------------------------------------------------------------------------
106 Procedure delete_validate(p_rec in per_ctr_shd.g_rec_type);
107 --
108 -- ---------------------------------------------------------------------------
109 -- |---------------------< return_legislation_code >-------------------------|
110 -- ---------------------------------------------------------------------------
111 --
112 -- Description:
113 -- Return the legislation code for a specific contact relationship
114 --
115 -- Prerequisites:
116 -- The contact relationship identified by p_contact_relationship_id already exists.
117 --
118 -- In Arguments:
119 -- p_contact_relationship_id
120 --
121 -- Post Success:
122 -- If the contact relationship id is found this function will return the contact's business
123 -- group legislation code.
124 --
125 -- Post Failure:
126 -- An error is raised if the contact does not exist.
127 --
128 -- Access Status:
129 -- Internal Development Use Only.
130 --
131 function return_legislation_code
132 (p_contact_relationship_id in number
133 ) return varchar2;
134 --
135 -- ----------------------------------------------------------------------------
136 -- |------------------< chk_sequence_number >---------------------------------|
137 -- ----------------------------------------------------------------------------
138 --
139 -- Description:
140 -- Validates that the sequence number for all relationships between two people
141 -- are the same and that this sequence number is unique for that person_id. ie
142 -- the person with the contact does not have the same sequence number for a
143 -- relationship with any other person. It also validates that the sequence
144 -- number can only be updated from null.
145 --
146 --
147 -- Pre-Requisites:
148 -- None.
149 --
150 -- In Parameters:
151 -- p_contact_relationship_id
152 -- p_sequence_number
153 -- p_contact_person_id
154 -- p_person_id
155 -- p_object_version_number
156 --
157 -- Post Success:
158 -- Processing continues if the sequence number matches the sequence number
159 -- for any other relationship between these two people and does not match
160 -- a sequence number for a relationship between the person a different contact.
161 -- Also continues if updating the sequence number from null.
162 --
163 --
164 -- Post Failure:
165 -- An Application Error is raised and processing is terminated if the sequence
166 -- number is not the same as an existing sequence number for a relationship
167 -- between these two people, or if the sequence number already exists for
168 -- a relationship between the person and a different contact. Processing is
169 -- also terminated if an update is attempted where the sequence number is not
170 -- null.
171 --
172 --
173 -- Access Status:
174 -- Internal Development use only.
175 ------------------------------------------------------------------------------
176 procedure chk_sequence_number(p_contact_relationship_id in number,
177 p_sequence_number in number,
178 p_contact_person_id in number,
179 p_person_id in number,
180 p_object_version_number in number);
181 --
182 end per_ctr_bus;
[Home] [Help]