APPS.JTM_COMMON_CON_PROG_PUB dependencies on FND_API

Line 66: p_init_msg_list VARCHAR2(1) := FND_API.G_TRUE;

62: x_return_status VARCHAR2(1);
63: -- For each procedure, it should init the FND_MESSAGE Stack.
64:
65: p_api_version_number NUMBER := 1.0;
66: p_init_msg_list VARCHAR2(1) := FND_API.G_TRUE;
67: p_validation_level NUMBER :=FND_API.G_VALID_LEVEL_FULL;
68:
69: x_msg_data VARCHAR2(2000);
70: x_msg_index_out NUMBER;

Line 67: p_validation_level NUMBER :=FND_API.G_VALID_LEVEL_FULL;

63: -- For each procedure, it should init the FND_MESSAGE Stack.
64:
65: p_api_version_number NUMBER := 1.0;
66: p_init_msg_list VARCHAR2(1) := FND_API.G_TRUE;
67: p_validation_level NUMBER :=FND_API.G_VALID_LEVEL_FULL;
68:
69: x_msg_data VARCHAR2(2000);
70: x_msg_index_out NUMBER;
71: x_msg_count NUMBER;

Line 81: x_return_status := FND_API.G_RET_STS_SUCCESS;

77:
78: -- Update JTM_CON_REQUEST_FREQUENCY , BOUNCE CURRENT_ROUND with 1
79: -- And Lock the whole JTM_CON_REQUEST Table.
80: -- When Apply patch to add new FREQUENCY, it shouldn't do any UPDATE.
81: x_return_status := FND_API.G_RET_STS_SUCCESS;
82:
83: -- Initalize the Apps Context
84:
85: UPDATE JTM_CON_REQUEST_INTERVALS