DBA Data[Home] [Help]

APPS.CZ_CONFIG_API_PVT dependencies on STANDARD

Line 35: -- IN: p_api_version (required), standard pl/sql api in parameter

31: ,p_new_name IN VARCHAR2 := NULL
32: ,p_force_new_inst_rev IN VARCHAR2 := NULL
33: );
34: -- Parameters:
35: -- IN: p_api_version (required), standard pl/sql api in parameter
36: -- p_config_hdr_id (required), header id of source config to be copied
37: -- p_config_rev_nbr (required), revision of source config to be copied
38: -- p_copy_mode (required), flag to specify whether creating a config having
39: -- new header id or new revision, has one of the following values.

Line 51: -- x_return_status, standard OUT NOCOPY parameter (FND_API.G_RET_STS_SUCCESS,

47: -- OUT: x_config_hdr_id, new config_hdr_id of the new config
48: -- x_config_rev_nbr, config_rev_nbr of the new config
49: -- x_orig_item_id_tbl, table of config_item_ids from the source config
50: -- x_new_item_id_tbl, table of config_item_ids from the new config
51: -- x_return_status, standard OUT NOCOPY parameter (FND_API.G_RET_STS_SUCCESS,
52: -- FND_API.G_RET_STS_ERROR, or FND_API.G_RET_STS_UNEXP_ERROR)
53: -- x_msg_count, standard OUT NOCOPY parameter
54: -- x_msg_data, standard OUT NOCOPY parameter
55:

Line 53: -- x_msg_count, standard OUT NOCOPY parameter

49: -- x_orig_item_id_tbl, table of config_item_ids from the source config
50: -- x_new_item_id_tbl, table of config_item_ids from the new config
51: -- x_return_status, standard OUT NOCOPY parameter (FND_API.G_RET_STS_SUCCESS,
52: -- FND_API.G_RET_STS_ERROR, or FND_API.G_RET_STS_UNEXP_ERROR)
53: -- x_msg_count, standard OUT NOCOPY parameter
54: -- x_msg_data, standard OUT NOCOPY parameter
55:
56: -- Validation:
57: -- p_config_hdr_id/p_config_rev_nbr: config exists in cz schema and is a network container

Line 54: -- x_msg_data, standard OUT NOCOPY parameter

50: -- x_new_item_id_tbl, table of config_item_ids from the new config
51: -- x_return_status, standard OUT NOCOPY parameter (FND_API.G_RET_STS_SUCCESS,
52: -- FND_API.G_RET_STS_ERROR, or FND_API.G_RET_STS_UNEXP_ERROR)
53: -- x_msg_count, standard OUT NOCOPY parameter
54: -- x_msg_data, standard OUT NOCOPY parameter
55:
56: -- Validation:
57: -- p_config_hdr_id/p_config_rev_nbr: config exists in cz schema and is a network container
58: -- config or a non-network config, i.e, component_instance_type is 'R'

Line 109: -- IN: p_api_version (required), standard pl/sql api in parameter

105: ,x_msg_data OUT NOCOPY VARCHAR2
106: );
107:
108: -- Parameters:
109: -- IN: p_api_version (required), standard pl/sql api in parameter
110: -- p_config_hdr_id (required), header id of config to be verified
111: -- p_config_rev_nbr (required), revision of config to be verified
112:
113: -- OUT: x_exists_flag FND_API.G_TRUE if config_hdr_id and config_rev_nbr describe a saved configuration,

Line 119: -- x_return_status, standard OUT parameter (FND_API.G_RET_STS_SUCCESS,

115: -- x_valid_flag FND_API.G_TRUE if configuration exists and is valid, FND_API.G_FALSE if the configuration
116: -- exists and is invalid, NULL if configuration does not exist.
117: -- x_complete_flag FND_API.G_TRUE if configuration exists and is complete, FND_API.G_FALSE if the
118: -- configuration exists and is incomplete, NULL if configuration does not exist.
119: -- x_return_status, standard OUT parameter (FND_API.G_RET_STS_SUCCESS,
120: -- FND_API.G_RET_STS_ERROR, or FND_API.G_RET_STS_UNEXP_ERROR)
121: -- x_msg_count, standard OUT parameter
122: -- x_msg_data, standard OUT parameter
123:

Line 121: -- x_msg_count, standard OUT parameter

117: -- x_complete_flag FND_API.G_TRUE if configuration exists and is complete, FND_API.G_FALSE if the
118: -- configuration exists and is incomplete, NULL if configuration does not exist.
119: -- x_return_status, standard OUT parameter (FND_API.G_RET_STS_SUCCESS,
120: -- FND_API.G_RET_STS_ERROR, or FND_API.G_RET_STS_UNEXP_ERROR)
121: -- x_msg_count, standard OUT parameter
122: -- x_msg_data, standard OUT parameter
123:
124: -- Validation:
125: -- p_config_hdr_id/p_config_rev_nbr: In 19 Configurator builds and later, the API validates that the configuration header

Line 122: -- x_msg_data, standard OUT parameter

118: -- configuration exists and is incomplete, NULL if configuration does not exist.
119: -- x_return_status, standard OUT parameter (FND_API.G_RET_STS_SUCCESS,
120: -- FND_API.G_RET_STS_ERROR, or FND_API.G_RET_STS_UNEXP_ERROR)
121: -- x_msg_count, standard OUT parameter
122: -- x_msg_data, standard OUT parameter
123:
124: -- Validation:
125: -- p_config_hdr_id/p_config_rev_nbr: In 19 Configurator builds and later, the API validates that the configuration header
126: -- identified by config_hdr_id and config_rev_nbr is a session (not instance) header. If not, x_return_status will be