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 199: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false

195: , x_msg_count OUT NOCOPY NUMBER
196: , x_msg_data OUT NOCOPY VARCHAR2
197: , x_label_status OUT NOCOPY VARCHAR2
198: , p_api_version IN NUMBER
199: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
200: , p_commit IN VARCHAR2 := fnd_api.g_false
201: , p_print_mode IN NUMBER
202: , p_business_flow_code IN NUMBER DEFAULT NULL
203: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec

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

196: , x_msg_data OUT NOCOPY VARCHAR2
197: , x_label_status OUT NOCOPY VARCHAR2
198: , p_api_version IN NUMBER
199: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
200: , p_commit IN VARCHAR2 := fnd_api.g_false
201: , p_print_mode IN NUMBER
202: , p_business_flow_code IN NUMBER DEFAULT NULL
203: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec
204: , p_input_param_rec IN input_parameter_rec_type default input_param_null_rec

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

243: , x_msg_data OUT NOCOPY VARCHAR2
244: , x_label_status OUT NOCOPY VARCHAR2
245: , x_label_request_id OUT NOCOPY NUMBER -- fabdi, new para
246: , p_api_version IN NUMBER
247: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
248: , p_commit IN VARCHAR2 := fnd_api.g_false
249: , p_print_mode IN NUMBER
250: , p_business_flow_code IN NUMBER DEFAULT NULL
251: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec

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

244: , x_label_status OUT NOCOPY VARCHAR2
245: , x_label_request_id OUT NOCOPY NUMBER -- fabdi, new para
246: , p_api_version IN NUMBER
247: , p_init_msg_list IN VARCHAR2 := fnd_api.g_false
248: , p_commit IN VARCHAR2 := fnd_api.g_false
249: , p_print_mode IN NUMBER
250: , p_business_flow_code IN NUMBER DEFAULT NULL
251: , p_transaction_id IN transaction_id_rec_type default txn_id_null_rec
252: , p_input_param_rec IN input_parameter_rec_type default input_param_null_rec

Line 288: * 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

284: * business flow code can be provided for those transactions that do not have
285: * transaction records, such as Serial Generation, Cost Group Update, etc.
286: *
287: * @param x_return_status Return status of the procedure. If the procedure
288: * 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
289: * error, the value will be fnd_api.g_ret_sts_unexp_error;
290: * @ paraminfo {@rep:required}
291: * @ param x_msg_count if there is one or more errors, the number of error
292: * messages in the buffer

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

285: * transaction records, such as Serial Generation, Cost Group Update, etc.
286: *
287: * @param x_return_status Return status of the procedure. If the procedure
288: * 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
289: * error, the value will be fnd_api.g_ret_sts_unexp_error;
290: * @ paraminfo {@rep:required}
291: * @ param x_msg_count if there is one or more errors, the number of error
292: * messages in the buffer
293: * @ paraminfo {@rep:required}