1 PACKAGE BODY hr_efc_stubs AS
2 /* $Header: hrefcstb.pkb 115.3 2002/12/05 11:42:12 apholt noship $ */
3 --
4 -- Package variables.
5 -- lc_process VARCHAR2(1) ; -- to process return flag
6 --
7 -- ----------------------------------------------------------------------------
8 -- |---------------------< cust_valid_budget_unit >---------------------------|
9 -- ----------------------------------------------------------------------------
10 FUNCTION cust_valid_budget_unit(p_uom IN VARCHAR2
11 ,p_business_group_id IN NUMBER)
12 RETURN VARCHAR2 IS
13 --
14 -- Used to check the UOM against customer defined units of measure
15 --
16 lc_process varchar2(1) := 'N'; -- Set to 'Y' if unit is valid
17 --
18 BEGIN
19 --
20 -- example shown, remove if not required
21 -- IF p_uom = 'MONEY' THEN
22 -- lc_process := 'Y';
23 -- END IF;
24 --
25 RETURN lc_process ;
26 --
27 END cust_valid_budget_unit;
28 --
29 -- ----------------------------------------------------------------------------
30 -- |--------------------< cust_validate_hr_summary >--------------------------|
31 -- ----------------------------------------------------------------------------
32 --
33 -- Description:
34 --
35 -- Validates that the column in the hr_summary table should be converted.
36 -- This function must be modified to include all customer defined lookup
37 -- values for num_value1 (p_colname = 'NUM_VALUE1') and
38 -- num_value2 (p_colnname = 'NUM_VALUE2').
39 --
40 -- This function should return 'Y' if the monetary type matches, otherwise
41 -- it should return 'N'.
42 --
43 -- ----------------------------------------------------------------------------
44 FUNCTION cust_validate_hr_summary(p_colname VARCHAR2
45 ,p_item VARCHAR2
46 ,p_business_group_id NUMBER) RETURN VARCHAR2 IS
47 --
48 lc_process VARCHAR2(1);
49 --
50 BEGIN
51 --
52 IF (p_colname = 'NUM_VALUE1') THEN
53 --
54 -- Check whether or not num_value1 should be converted, by matching
55 -- the lookup type p_item with the user defined lookup types.
56 -- Else return 'N'.
57 -- e.g.
58 -- IF (p_colname = 'NUM_VALUE1') THEN
59 -- -- Oracle defined lookup
60 -- IF p_item = 'ANNUAL_REMUNERATION' THEN
61 -- lc_process := 'Y'
62 -- END IF;
63 -- END IF;
64 --
65 lc_process := 'N';
66 ELSIF (p_colname = 'NUM_VALUE2') THEN
67 --
68 -- Check whether or not num_value12should be converted, by matching
69 -- the lookup type p_item with the user defined lookup types.
70 -- Else return 'N'.
71 lc_process := 'N';
72 END IF;
73 --
74 -- return value.
75 RETURN lc_process;
76 END cust_validate_hr_summary;
77 --
78 -- ----------------------------------------------------------------------------
79 -- |----------------------< chk_customer_mapping >----------------------------|
80 -- ----------------------------------------------------------------------------
81 --
82 -- Description:
83 --
84 -- For specific customer payment_types, defined in pay_payment_types, and not
85 -- seeded by Oracle HRMS, have to define the mapping between the original
86 -- payment_type and the payment_type to be used after EFC conversion.
87 --
88 -- Post Success:
89 -- Should return the payment_type_name, and territory_code for the new
90 -- payment_type. A new payment type should ALWAYS be returned.
91 --
92 -- ----------------------------------------------------------------------------
93 procedure chk_customer_mapping(p_payment_type IN varchar2
94 ,p_territory_code IN varchar2
95 ,p_new_payment_type OUT NOCOPY varchar2
96 ,p_new_territory_code OUT NOCOPY varchar2) IS
97 --
98 BEGIN
99 --
100 -- The following is listed as an example only, and should be edited
101 -- by the customer to reflect a customer's particular payment types.
102 IF ((p_payment_type='BE Cash') AND
103 (p_territory_code = 'BE')) THEN
104 p_new_payment_type := 'Cash';
105 p_new_territory_code := '';
106 END IF;
107 --
108 END chk_customer_mapping;
109 --
110 -- ----------------------------------------------------------------------------
111 -- |----------------------< cust_find_row_size >------------------------------|
112 -- ----------------------------------------------------------------------------
113 --
114 -- Description:
115 -- Customer specific version of a function which will estimate the
116 -- size of a row. This will override the function supplied by Oracle to
117 -- estimate the size of a row.
118 -- If you wish to use the estimation function supplied by Oracle, this
119 -- function must return 0.
120 --
121 -- ----------------------------------------------------------------------------
122 FUNCTION cust_find_row_size(p_table IN varchar2) RETURN number IS
123 --
124 BEGIN
125 RETURN 0;
126 END cust_find_row_size;
127 --
128 --
129 -- ----------------------------------------------------------------------------
130 -- |------------------< cust_process_cross_bg_data >---------------------------|
131 -- ----------------------------------------------------------------------------
132 --
133 -- Description:
134 -- Customer specific version of a function which will determine if data
135 -- spanning business groups will be converted. This will override the function
136 -- supplied by Oracle for this purpose, which by default will convert the data.
137 -- If you wish NOT to convert on the next run, this function must return 'N'.
138 --
139 -- ----------------------------------------------------------------------------
140 FUNCTION cust_process_cross_bg_data RETURN varchar2 IS
141 --
142 BEGIN
143 --
144 --
145 -- Default to always convert global data
146 --
147 RETURN 'Y';
148 --
149 -- Uncomment the line below to disable global data conversion
150 --
151 -- RETURN 'N';
152 --
153 END cust_process_cross_bg_data;
154 --
155 END hr_efc_stubs;
[Home] [Help]