1 Package ghr_cca_ins AUTHID CURRENT_USER as
2 /* $Header: ghccarhi.pkh 120.0 2005/05/29 02:50:17 appldev noship $ */
3 -- ----------------------------------------------------------------------------
4 -- |------------------------< set_base_key_value >----------------------------|
5 -- ----------------------------------------------------------------------------
6 -- {Start of Comments}
7 -- Description:
8 -- This procedure is called to register the next ID value from the database
9 -- sequence.
10 --
11 -- Prerequisites:
12 --
13 -- In Parameters:
14 -- Primary Key
15 --
16 -- Post Success:
17 --
18 -- Post Failure:
19 --
20 -- Developer Implementation Notes:
21 -- None.
22 --
23 -- Access Status:
24 -- Internal Development Use Only.
25 --
26 -- {End of Comments}
27 -- ----------------------------------------------------------------------------
28 procedure set_base_key_value
29 (p_compl_appeal_id in number);
30 --
31 -- ----------------------------------------------------------------------------
32 -- |---------------------------------< ins >----------------------------------|
33 -- ----------------------------------------------------------------------------
34 -- {Start Of Comments}
35 --
36 -- Description:
37 -- This procedure is the record interface for the insert process
38 -- for the specified entity. The role of this process is to insert a fully
39 -- validated row, into the HR schema passing back to the calling process,
40 -- any system generated values (e.g. primary and object version number
41 -- attributes). This process is the main backbone of the ins
42 -- process. The processing of this procedure is as follows:
43 -- 1) The controlling validation process insert_validate is executed
44 -- which will execute all private and public validation business rule
45 -- processes.
46 -- 2) The pre_insert business process is then executed which enables any
47 -- logic to be processed before the insert dml process is executed.
48 -- 3) The insert_dml process will physical perform the insert dml into the
49 -- specified entity.
50 -- 4) The post_insert business process is then executed which enables any
51 -- logic to be processed after the insert dml process.
52 --
53 -- Prerequisites:
54 -- The main parameters to the this process have to be in the record
55 -- format.
56 --
57 -- In Parameters:
58 --
59 -- Post Success:
60 -- A fully validated row will be inserted into the specified entity
61 -- without being committed.
62 --
63 -- Post Failure:
64 -- If an error has occurred, an error message will be raised.
65 --
66 -- Developer Implementation Notes:
67 -- None.
68 --
69 -- Access Status:
70 -- Internal Development Use Only.
71 --
72 -- {End Of Comments}
73 -- ----------------------------------------------------------------------------
74 Procedure ins
75 (p_effective_date in date
76 ,p_rec in out nocopy ghr_cca_shd.g_rec_type
77 );
78 --
79 -- ----------------------------------------------------------------------------
80 -- |---------------------------------< ins >----------------------------------|
81 -- ----------------------------------------------------------------------------
82 -- {Start Of Comments}
83 --
84 -- Description:
85 -- This procedure is the attribute interface for the insert
86 -- process for the specified entity and is the outermost layer. The role
87 -- of this process is to insert a fully validated row into the HR schema
88 -- passing back to the calling process, any system generated values
89 -- (e.g. object version number attributes).The processing of this
90 -- procedure is as follows:
91 -- 1) The attributes are converted into a local record structure by
92 -- calling the convert_args function.
93 -- 2) After the conversion has taken place, the corresponding record ins
94 -- interface process is executed.
95 -- 3) OUT parameters are then set to their corresponding record attributes.
96 --
97 -- Prerequisites:
98 --
99 -- In Parameters:
100 --
101 -- Post Success:
102 -- A fully validated row will be inserted for the specified entity
103 -- without being committed.
104 --
105 -- Post Failure:
106 -- If an error has occurred, an error message will be raised.
107 --
108 -- Developer Implementation Notes:
109 -- None.
110 --
111 -- Access Status:
112 -- Internal Development Use Only.
113 --
114 -- {End Of Comments}
115 -- ----------------------------------------------------------------------------
116 Procedure ins
117 (p_effective_date in date
118 ,p_complaint_id in number
119 ,p_appeal_date in date default null
120 ,p_appealed_to in varchar2 default null
121 ,p_reason_for_appeal in varchar2 default null
122 ,p_source_decision_date in date default null
123 ,p_docket_num in varchar2 default null
124 ,p_org_notified_of_appeal in date default null
125 ,p_agency_recvd_req_for_files in date default null
126 ,p_files_due in date default null
127 ,p_files_forwd in date default null
128 ,p_agcy_recvd_appellant_brief in date default null
129 ,p_agency_brief_due in date default null
130 ,p_appellant_brief_forwd_org in date default null
131 ,p_org_forwd_brief_to_agency in date default null
132 ,p_agency_brief_forwd in date default null
133 ,p_decision_date in date default null
134 ,p_dec_recvd_by_agency in date default null
135 ,p_decision in varchar2 default null
136 ,p_dec_forwd_to_org in date default null
137 ,p_agency_rfr_suspense in date default null
138 ,p_request_for_rfr in date default null
139 ,p_rfr_docket_num in varchar2 default null
140 ,p_rfr_requested_by in varchar2 default null
141 ,p_agency_rfr_due in date default null
142 ,p_rfr_forwd_to_org in date default null
143 ,p_org_forwd_rfr_to_agency in date default null
144 ,p_agency_forwd_rfr_ofo in date default null
145 ,p_rfr_decision in varchar2 default null
146 ,p_rfr_decision_date in date default null
147 ,p_agency_recvd_rfr_dec in date default null
148 ,p_rfr_decision_forwd_to_org in date default null
149 ,p_compl_appeal_id out nocopy number
150 ,p_object_version_number out nocopy number
151 );
152 --
153 end ghr_cca_ins;