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.CS_CHARGE_DETAILS_PVT dependencies on FND_GLOBAL

Line 42: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,

38: x_msg_data OUT NOCOPY VARCHAR2,
39: --p_resp_appl_id IN NUMBER := NULL,
40: --p_resp_id IN NUMBER := NULL,
41: --p_user_id IN NUMBER := NULL,
42: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,
43: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,
44: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,
45: p_login_id IN NUMBER := NULL,
46: p_transaction_control IN VARCHAR2 := FND_API.G_TRUE,

Line 43: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,

39: --p_resp_appl_id IN NUMBER := NULL,
40: --p_resp_id IN NUMBER := NULL,
41: --p_user_id IN NUMBER := NULL,
42: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,
43: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,
44: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,
45: p_login_id IN NUMBER := NULL,
46: p_transaction_control IN VARCHAR2 := FND_API.G_TRUE,
47: p_est_detail_rec IN CS_Charge_Details_PUB.Charges_Rec_Type);

Line 44: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,

40: --p_resp_id IN NUMBER := NULL,
41: --p_user_id IN NUMBER := NULL,
42: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,
43: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,
44: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,
45: p_login_id IN NUMBER := NULL,
46: p_transaction_control IN VARCHAR2 := FND_API.G_TRUE,
47: p_est_detail_rec IN CS_Charge_Details_PUB.Charges_Rec_Type);
48:

Line 66: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,

62: x_msg_data OUT NOCOPY VARCHAR2,
63: --p_resp_appl_id IN NUMBER := NULL,
64: --p_resp_id IN NUMBER := NULL,
65: -- p_user_id IN NUMBER := NULL,
66: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,
67: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,
68: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,
69: p_login_id IN NUMBER := NULL,
70: p_transaction_control IN VARCHAR2 := FND_API.G_TRUE,

Line 67: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,

63: --p_resp_appl_id IN NUMBER := NULL,
64: --p_resp_id IN NUMBER := NULL,
65: -- p_user_id IN NUMBER := NULL,
66: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,
67: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,
68: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,
69: p_login_id IN NUMBER := NULL,
70: p_transaction_control IN VARCHAR2 := FND_API.G_TRUE,
71: p_est_detail_rec IN CS_Charge_Details_PUB.Charges_Rec_Type);

Line 68: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,

64: --p_resp_id IN NUMBER := NULL,
65: -- p_user_id IN NUMBER := NULL,
66: p_resp_appl_id IN NUMBER := FND_GLOBAL.RESP_APPL_ID,
67: p_resp_id IN NUMBER := FND_GLOBAL.RESP_ID,
68: p_user_id IN NUMBER := FND_GLOBAL.USER_ID,
69: p_login_id IN NUMBER := NULL,
70: p_transaction_control IN VARCHAR2 := FND_API.G_TRUE,
71: p_est_detail_rec IN CS_Charge_Details_PUB.Charges_Rec_Type);
72: