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

Line 176: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false

172: , x_msg_count OUT NOCOPY NUMBER
173: , x_msg_data OUT NOCOPY VARCHAR2
174: , x_label_status OUT NOCOPY VARCHAR2
175: , p_api_version IN NUMBER
176: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
177: , p_commit IN VARCHAR2 := fnd_api.g_false
178: , p_print_mode IN NUMBER
179: , p_business_flow_code IN NUMBER DEFAULT NULL
180: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec

Line 177: , p_commit IN VARCHAR2 := fnd_api.g_false

173: , x_msg_data OUT NOCOPY VARCHAR2
174: , x_label_status OUT NOCOPY VARCHAR2
175: , p_api_version IN NUMBER
176: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
177: , p_commit IN VARCHAR2 := fnd_api.g_false
178: , p_print_mode IN NUMBER
179: , p_business_flow_code IN NUMBER DEFAULT NULL
180: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec
181: , p_input_param_rec IN input_parameter_rec_type default input_param_null_rec

Line 224: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false

220: , x_msg_data OUT NOCOPY VARCHAR2
221: , x_label_status OUT NOCOPY VARCHAR2
222: , x_label_request_id OUT NOCOPY NUMBER -- fabdi, new para
223: , p_api_version IN NUMBER
224: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
225: , p_commit IN VARCHAR2 := fnd_api.g_false
226: , p_print_mode IN NUMBER
227: , p_business_flow_code IN NUMBER DEFAULT NULL
228: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec

Line 225: , p_commit IN VARCHAR2 := fnd_api.g_false

221: , x_label_status OUT NOCOPY VARCHAR2
222: , x_label_request_id OUT NOCOPY NUMBER -- fabdi, new para
223: , p_api_version IN NUMBER
224: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
225: , p_commit IN VARCHAR2 := fnd_api.g_false
226: , p_print_mode IN NUMBER
227: , p_business_flow_code IN NUMBER DEFAULT NULL
228: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec
229: , p_input_param_rec IN input_parameter_rec_type default input_param_null_rec

Line 265: * succeeds, the value will be fnd_api.g_ret_sts_success; if there is an expected * error, the value will be fnd_api.g_ret_sts_error; if there is an unexpected

261: * business flow code can be provided for those transactions that do not have
262: * transaction records, such as Serial Generation, Cost Group Update, etc.
263: *
264: * @param x_return_status Return status of the procedure. If the procedure
265: * succeeds, the value will be fnd_api.g_ret_sts_success; if there is an expected * error, the value will be fnd_api.g_ret_sts_error; if there is an unexpected
266: * error, the value will be fnd_api.g_ret_sts_unexp_error;
267: * @ paraminfo {@rep:required}
268: * @ param x_msg_count if there is one or more errors, the number of error
269: * messages in the buffer

Line 266: * error, the value will be fnd_api.g_ret_sts_unexp_error;

262: * transaction records, such as Serial Generation, Cost Group Update, etc.
263: *
264: * @param x_return_status Return status of the procedure. If the procedure
265: * succeeds, the value will be fnd_api.g_ret_sts_success; if there is an expected * error, the value will be fnd_api.g_ret_sts_error; if there is an unexpected
266: * error, the value will be fnd_api.g_ret_sts_unexp_error;
267: * @ paraminfo {@rep:required}
268: * @ param x_msg_count if there is one or more errors, the number of error
269: * messages in the buffer
270: * @ paraminfo {@rep:required}