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

Line 8: * p_commit commit after successful processing? pass fnd_api.g_true or fnd_api.g_false

4: /* This version process a single row *only*. If no rows are passed or more
5: * than one is tied to the associated transaction_header_id this procedure will error.
6: * parameters: p_txnIntID The transaction_interface_id of the MTI row. As noted above,
7: * this should be the only row tied to its associated transaction_header_id.
8: * p_commit commit after successful processing? pass fnd_api.g_true or fnd_api.g_false
9: * x_returnStatus fnd_api.g_ret_sts_success on successful processing of the transaction.
10: * x_errorMsg contains the error message on failure. null on success.
11: */
12: procedure processInterface(p_txnIntID IN NUMBER,

Line 9: * x_returnStatus fnd_api.g_ret_sts_success on successful processing of the transaction.

5: * than one is tied to the associated transaction_header_id this procedure will error.
6: * parameters: p_txnIntID The transaction_interface_id of the MTI row. As noted above,
7: * this should be the only row tied to its associated transaction_header_id.
8: * p_commit commit after successful processing? pass fnd_api.g_true or fnd_api.g_false
9: * x_returnStatus fnd_api.g_ret_sts_success on successful processing of the transaction.
10: * x_errorMsg contains the error message on failure. null on success.
11: */
12: procedure processInterface(p_txnIntID IN NUMBER,
13: p_commit IN VARCHAR2 := fnd_api.g_false,

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

9: * x_returnStatus fnd_api.g_ret_sts_success on successful processing of the transaction.
10: * x_errorMsg contains the error message on failure. null on success.
11: */
12: procedure processInterface(p_txnIntID IN NUMBER,
13: p_commit IN VARCHAR2 := fnd_api.g_false,
14: x_returnStatus OUT NOCOPY VARCHAR2,
15: x_errorMsg OUT NOCOPY VARCHAR2);
16:
17: /* This version process multiple rows in MTI. All the rows tied to the header id should be WIP transactions.

Line 19: * + fnd_api.g_ret_sts_success if all rows processed successfully

15: x_errorMsg OUT NOCOPY VARCHAR2);
16:
17: /* This version process multiple rows in MTI. All the rows tied to the header id should be WIP transactions.
18: * The return status will be:
19: * + fnd_api.g_ret_sts_success if all rows processed successfully
20: * + fnd_api.g_ret_sts_error if one or more rows failed processing
21: * + fnd_api.g_ret_sts_unexp_error if an unexpected exception occurred(e.g. a package was invalid)
22: *
23: * If the return status is not success, the caller should query the error_explanation column of the MTI rows to

Line 20: * + fnd_api.g_ret_sts_error if one or more rows failed processing

16:
17: /* This version process multiple rows in MTI. All the rows tied to the header id should be WIP transactions.
18: * The return status will be:
19: * + fnd_api.g_ret_sts_success if all rows processed successfully
20: * + fnd_api.g_ret_sts_error if one or more rows failed processing
21: * + fnd_api.g_ret_sts_unexp_error if an unexpected exception occurred(e.g. a package was invalid)
22: *
23: * If the return status is not success, the caller should query the error_explanation column of the MTI rows to
24: * find out which rows errored and for what reason.

Line 21: * + fnd_api.g_ret_sts_unexp_error if an unexpected exception occurred(e.g. a package was invalid)

17: /* This version process multiple rows in MTI. All the rows tied to the header id should be WIP transactions.
18: * The return status will be:
19: * + fnd_api.g_ret_sts_success if all rows processed successfully
20: * + fnd_api.g_ret_sts_error if one or more rows failed processing
21: * + fnd_api.g_ret_sts_unexp_error if an unexpected exception occurred(e.g. a package was invalid)
22: *
23: * If the return status is not success, the caller should query the error_explanation column of the MTI rows to
24: * find out which rows errored and for what reason.
25: *

Line 28: * p_commit commit after successful processing? pass fnd_api.g_true or fnd_api.g_false

24: * find out which rows errored and for what reason.
25: *
26: * parameters: p_txnHdrID The transaction_interface_id of the MTI row. As noted above,
27: * this should be the only row tied to its associated transaction_header_id.
28: * p_commit commit after successful processing? pass fnd_api.g_true or fnd_api.g_false
29: * x_returnStatus fnd_api.g_ret_sts_success if all rows were processed successfully. See note
30: * above for more details.
31: */
32: procedure processInterface(p_txnHdrID IN NUMBER,

Line 29: * x_returnStatus fnd_api.g_ret_sts_success if all rows were processed successfully. See note

25: *
26: * parameters: p_txnHdrID The transaction_interface_id of the MTI row. As noted above,
27: * this should be the only row tied to its associated transaction_header_id.
28: * p_commit commit after successful processing? pass fnd_api.g_true or fnd_api.g_false
29: * x_returnStatus fnd_api.g_ret_sts_success if all rows were processed successfully. See note
30: * above for more details.
31: */
32: procedure processInterface(p_txnHdrID IN NUMBER,
33: p_commit IN VARCHAR2 := fnd_api.g_false,

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

29: * x_returnStatus fnd_api.g_ret_sts_success if all rows were processed successfully. See note
30: * above for more details.
31: */
32: procedure processInterface(p_txnHdrID IN NUMBER,
33: p_commit IN VARCHAR2 := fnd_api.g_false,
34: x_returnStatus OUT NOCOPY VARCHAR2);
35: end wip_mtlInterfaceProc_pub;