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.AR_CHARGE_SCHEDULE_PKG dependencies on FND_API

Line 201: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,

197: --------------
198: -- Public APIS
199: --------------
200: PROCEDURE create_schedule
201: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
202: P_SCHEDULE_NAME IN VARCHAR2,
203: P_SCHEDULE_DESCRIPTION IN VARCHAR2,
204: P_ATTRIBUTE_CATEGORY IN VARCHAR2 DEFAULT NULL,
205: P_ATTRIBUTE1 IN VARCHAR2 DEFAULT NULL,

Line 227: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,

223: x_msg_count OUT NOCOPY NUMBER,
224: x_msg_data OUT NOCOPY VARCHAR2);
225:
226: PROCEDURE update_schedule
227: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
228: P_SCHEDULE_ID IN NUMBER,
229: P_SCHEDULE_DESCRIPTION IN VARCHAR2,
230: P_ATTRIBUTE_CATEGORY IN VARCHAR2 DEFAULT NULL,
231: P_ATTRIBUTE1 IN VARCHAR2 DEFAULT NULL,

Line 252: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,

248: x_msg_count OUT NOCOPY NUMBER,
249: x_msg_data OUT NOCOPY VARCHAR2);
250:
251: PROCEDURE create_schedule_header
252: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
253: P_SCHEDULE_ID IN NUMBER,
254: P_SCHEDULE_HEADER_TYPE IN VARCHAR2,
255: P_AGING_BUCKET_ID IN NUMBER,
256: P_START_DATE IN DATE,

Line 282: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,

278: x_msg_count OUT NOCOPY NUMBER,
279: x_msg_data OUT NOCOPY VARCHAR2);
280:
281: PROCEDURE Update_schedule_header
282: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
283: P_SCHEDULE_HEADER_ID IN NUMBER,
284: P_END_DATE IN DATE,
285: P_STATUS IN VARCHAR2,
286: P_ATTRIBUTE_CATEGORY IN VARCHAR2 DEFAULT NULL,

Line 308: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,

304: x_msg_count OUT NOCOPY NUMBER,
305: x_msg_data OUT NOCOPY VARCHAR2);
306:
307: PROCEDURE create_schedule_line
308: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
309: P_SCHEDULE_HEADER_ID IN NUMBER,
310: P_SCHEDULE_ID IN NUMBER,
311: P_AGING_BUCKET_ID IN NUMBER,
312: P_AGING_BUCKET_LINE_ID IN NUMBER,

Line 338: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,

334: x_msg_count OUT NOCOPY NUMBER,
335: x_msg_data OUT NOCOPY VARCHAR2);
336:
337: PROCEDURE Update_schedule_line
338: (p_init_msg_list IN VARCHAR2 := fnd_api.g_false,
339: P_SCHEDULE_line_ID IN NUMBER,
340: P_amount IN NUMBER,
341: P_rate IN NUMBER,
342: P_ATTRIBUTE_CATEGORY IN VARCHAR2 DEFAULT NULL,