eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.CN_MULTI_RATE_SCHEDULES_CUHK dependencies on CN_RATE_SCHEDULES

Line 13: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,

9: -- dimensions, and creates the appropriate set of tiers. The original object_version_number
10: -- is zero. When tiers are first created their commission amounts are null.
11: -- They can be set using the Update_Tier API.
12: PROCEDURE Create_Schedule_Pre
13: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,
14: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE,
15: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
16: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,
17: x_return_status OUT NOCOPY VARCHAR2,

Line 14: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE,

10: -- is zero. When tiers are first created their commission amounts are null.
11: -- They can be set using the Update_Tier API.
12: PROCEDURE Create_Schedule_Pre
13: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,
14: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE,
15: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
16: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,
17: x_return_status OUT NOCOPY VARCHAR2,
18: x_msg_count OUT NOCOPY NUMBER,

Line 21: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,

17: x_return_status OUT NOCOPY VARCHAR2,
18: x_msg_count OUT NOCOPY NUMBER,
19: x_msg_data OUT NOCOPY VARCHAR2);
20: PROCEDURE Create_Schedule_Post
21: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,
22: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE,
23: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
24: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,
25: x_return_status OUT NOCOPY VARCHAR2,

Line 22: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE,

18: x_msg_count OUT NOCOPY NUMBER,
19: x_msg_data OUT NOCOPY VARCHAR2);
20: PROCEDURE Create_Schedule_Post
21: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,
22: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE,
23: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
24: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,
25: x_return_status OUT NOCOPY VARCHAR2,
26: x_msg_count OUT NOCOPY NUMBER,

Line 38: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,

34: -- the table is rebuilt according to the new set of dimension assignments and the
35: -- tiers are re-created (resetting the commission amounts). If all the validations
36: -- pass, the rate schedule is updated and its object version number is incremented.
37: PROCEDURE Update_Schedule_Pre
38: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,
39: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
40: cn_api.g_miss_char,
41: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
42: cn_api.g_miss_char,

Line 39: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=

35: -- tiers are re-created (resetting the commission amounts). If all the validations
36: -- pass, the rate schedule is updated and its object version number is incremented.
37: PROCEDURE Update_Schedule_Pre
38: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,
39: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
40: cn_api.g_miss_char,
41: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
42: cn_api.g_miss_char,
43: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,

Line 41: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=

37: PROCEDURE Update_Schedule_Pre
38: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,
39: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
40: cn_api.g_miss_char,
41: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
42: cn_api.g_miss_char,
43: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,
44: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
45: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,

Line 43: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,

39: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
40: cn_api.g_miss_char,
41: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
42: cn_api.g_miss_char,
43: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,
44: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
45: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,
46: x_return_status OUT NOCOPY VARCHAR2,
47: x_msg_count OUT NOCOPY NUMBER,

Line 50: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,

46: x_return_status OUT NOCOPY VARCHAR2,
47: x_msg_count OUT NOCOPY NUMBER,
48: x_msg_data OUT NOCOPY VARCHAR2);
49: PROCEDURE Update_Schedule_Post
50: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,
51: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
52: cn_api.g_miss_char,
53: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
54: cn_api.g_miss_char,

Line 51: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=

47: x_msg_count OUT NOCOPY NUMBER,
48: x_msg_data OUT NOCOPY VARCHAR2);
49: PROCEDURE Update_Schedule_Post
50: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,
51: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
52: cn_api.g_miss_char,
53: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
54: cn_api.g_miss_char,
55: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,

Line 53: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=

49: PROCEDURE Update_Schedule_Post
50: (p_original_name IN CN_RATE_SCHEDULES.NAME%TYPE,
51: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
52: cn_api.g_miss_char,
53: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
54: cn_api.g_miss_char,
55: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,
56: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
57: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,

Line 55: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,

51: p_new_name IN CN_RATE_SCHEDULES.NAME%TYPE :=
52: cn_api.g_miss_char,
53: p_commission_unit_code IN CN_RATE_SCHEDULES.COMMISSION_UNIT_CODE%TYPE :=
54: cn_api.g_miss_char,
55: p_object_version_number IN CN_RATE_SCHEDULES.OBJECT_VERSION_NUMBER%TYPE,
56: p_dims_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type :=
57: CN_MULTI_RATE_SCHEDULES_PUB.g_miss_dim_assign_tbl,
58: x_return_status OUT NOCOPY VARCHAR2,
59: x_msg_count OUT NOCOPY NUMBER,

Line 65: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,

61:
62: -- Delete rate schedule, dimension assignments, and rate tiers.
63: -- Identify the rate schedule to be deleted by its name.
64: PROCEDURE Delete_Schedule_Pre
65: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,
66: x_return_status OUT NOCOPY VARCHAR2,
67: x_msg_count OUT NOCOPY NUMBER,
68: x_msg_data OUT NOCOPY VARCHAR2);
69: PROCEDURE Delete_Schedule_Post

Line 70: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,

66: x_return_status OUT NOCOPY VARCHAR2,
67: x_msg_count OUT NOCOPY NUMBER,
68: x_msg_data OUT NOCOPY VARCHAR2);
69: PROCEDURE Delete_Schedule_Post
70: (p_name IN CN_RATE_SCHEDULES.NAME%TYPE,
71: x_return_status OUT NOCOPY VARCHAR2,
72: x_msg_count OUT NOCOPY NUMBER,
73: x_msg_data OUT NOCOPY VARCHAR2);
74:

Line 81: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

77: -- to insert the dimension. If a dimension is inserted in the middle, all the existing
78: -- dimension assignments with equal or higher sequence number are pushed up by one sequence
79: -- number.
80: PROCEDURE Create_Dimension_Assign_Pre
81: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
82: p_rate_dimension_name IN CN_RATE_DIMENSIONS.NAME%TYPE,
83: p_rate_dim_sequence IN CN_RATE_SCH_DIMS.RATE_DIM_SEQUENCE%TYPE,
84: x_return_status OUT NOCOPY VARCHAR2,
85: x_msg_count OUT NOCOPY NUMBER,

Line 88: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

84: x_return_status OUT NOCOPY VARCHAR2,
85: x_msg_count OUT NOCOPY NUMBER,
86: x_msg_data OUT NOCOPY VARCHAR2);
87: PROCEDURE Create_Dimension_Assign_Post
88: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
89: p_rate_dimension_name IN CN_RATE_DIMENSIONS.NAME%TYPE,
90: p_rate_dim_sequence IN CN_RATE_SCH_DIMS.RATE_DIM_SEQUENCE%TYPE,
91: x_return_status OUT NOCOPY VARCHAR2,
92: x_msg_count OUT NOCOPY NUMBER,

Line 101: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

97: -- new dimension name according to the dimension you wish to reassign. Finally pass in the
98: -- rate dimension sequence number and object_version_number. If you do not pass in the
99: -- rate dimension sequence, the new dimension takes the same sequence number.
100: PROCEDURE Update_Dimension_Assign_Pre
101: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
102: p_orig_rate_dim_name IN CN_RATE_DIMENSIONS.NAME%TYPE,
103: p_new_rate_dim_name IN CN_RATE_DIMENSIONS.NAME%TYPE := cn_api.g_miss_char,
104: p_rate_dim_sequence IN CN_RATE_SCH_DIMS.RATE_DIM_SEQUENCE%TYPE :=
105: cn_api.g_miss_num,

Line 111: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

107: x_return_status OUT NOCOPY VARCHAR2,
108: x_msg_count OUT NOCOPY NUMBER,
109: x_msg_data OUT NOCOPY VARCHAR2);
110: PROCEDURE Update_Dimension_Assign_Post
111: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
112: p_orig_rate_dim_name IN CN_RATE_DIMENSIONS.NAME%TYPE,
113: p_new_rate_dim_name IN CN_RATE_DIMENSIONS.NAME%TYPE := cn_api.g_miss_char,
114: p_rate_dim_sequence IN CN_RATE_SCH_DIMS.RATE_DIM_SEQUENCE%TYPE :=
115: cn_api.g_miss_num,

Line 124: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

120:
121: -- Delete a rate dimension assignment by identifying the rate schedule and rate dimension
122: -- name.
123: PROCEDURE Delete_Dimension_Assign_Pre
124: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
125: p_rate_dimension_name IN CN_RATE_DIMENSIONS.NAME%TYPE,
126: x_return_status OUT NOCOPY VARCHAR2,
127: x_msg_count OUT NOCOPY NUMBER,
128: x_msg_data OUT NOCOPY VARCHAR2);

Line 130: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

126: x_return_status OUT NOCOPY VARCHAR2,
127: x_msg_count OUT NOCOPY NUMBER,
128: x_msg_data OUT NOCOPY VARCHAR2);
129: PROCEDURE Delete_Dimension_Assign_Post
130: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
131: p_rate_dimension_name IN CN_RATE_DIMENSIONS.NAME%TYPE,
132: x_return_status OUT NOCOPY VARCHAR2,
133: x_msg_count OUT NOCOPY NUMBER,
134: x_msg_data OUT NOCOPY VARCHAR2);

Line 141: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

137: -- sequence numbers. The number of values in the rate dimension tier sequence table
138: -- should correspond to the number of dimensions and the values should be in the
139: -- same order as the dimensions.
140: PROCEDURE Update_Rate_Pre
141: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
142: p_tier_coordinates_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.tier_coordinates_tbl,
143: p_commission_amount IN CN_RATE_TIERS.COMMISSION_AMOUNT%TYPE,
144: p_object_version_number IN CN_RATE_TIERS.OBJECT_VERSION_NUMBER%TYPE,
145: x_return_status OUT NOCOPY VARCHAR2,

Line 149: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,

145: x_return_status OUT NOCOPY VARCHAR2,
146: x_msg_count OUT NOCOPY NUMBER,
147: x_msg_data OUT NOCOPY VARCHAR2);
148: PROCEDURE Update_Rate_Post
149: (p_rate_schedule_name IN CN_RATE_SCHEDULES.NAME%TYPE,
150: p_tier_coordinates_tbl IN CN_MULTI_RATE_SCHEDULES_PUB.tier_coordinates_tbl,
151: p_commission_amount IN CN_RATE_TIERS.COMMISSION_AMOUNT%TYPE,
152: p_object_version_number IN CN_RATE_TIERS.OBJECT_VERSION_NUMBER%TYPE,
153: x_return_status OUT NOCOPY VARCHAR2,