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.WSH_ROUTING_RESPONSE_PKG dependencies on STANDARD

Line 359: -- actid - Standard WF attribute to represent the activity ID inside the process

355: -- Parameters
356: -- itemtype - represents the WF item type. In this case, it is FTERRESP
357: -- itemKey - identifies the unique item Key. In this case, it is the transaction_id
358: -- from wsh_inbound_txn_history
359: -- actid - Standard WF attribute to represent the activity ID inside the process
360: -- funcmode - Standard WF attribute representing the function execution mode
361: -- resultout - Standard WF attribute that represents the return status of this API
362: --
363: -- Purpose : This is a API that is called as part of the actual routing response WF.

Line 360: -- funcmode - Standard WF attribute representing the function execution mode

356: -- itemtype - represents the WF item type. In this case, it is FTERRESP
357: -- itemKey - identifies the unique item Key. In this case, it is the transaction_id
358: -- from wsh_inbound_txn_history
359: -- actid - Standard WF attribute to represent the activity ID inside the process
360: -- funcmode - Standard WF attribute representing the function execution mode
361: -- resultout - Standard WF attribute that represents the return status of this API
362: --
363: -- Purpose : This is a API that is called as part of the actual routing response WF.
364: -- This API performs some additional checks prior to actually

Line 361: -- resultout - Standard WF attribute that represents the return status of this API

357: -- itemKey - identifies the unique item Key. In this case, it is the transaction_id
358: -- from wsh_inbound_txn_history
359: -- actid - Standard WF attribute to represent the activity ID inside the process
360: -- funcmode - Standard WF attribute representing the function execution mode
361: -- resultout - Standard WF attribute that represents the return status of this API
362: --
363: -- Purpose : This is a API that is called as part of the actual routing response WF.
364: -- This API performs some additional checks prior to actually
365: -- firing the notification. The following logic is implemented in this API

Line 797: -- actid - Standard WF attribute to represent the activity ID inside the process

793: -- Parameters
794: -- itemtype - represents the WF item type. In this case, it is FTERRESP
795: -- itemKey - identifies the unique item Key. In this case, it is the transaction_id
796: -- from wsh_inbound_txn_history
797: -- actid - Standard WF attribute to represent the activity ID inside the process
798: -- funcmode - Standard WF attribute representing the fuction execution mode.
799: -- resultout - Standard WF attribute that represents the return status of this API
800: --
801: -- Purpose : This is the API that is called as part of the actual routing response WF.

Line 798: -- funcmode - Standard WF attribute representing the fuction execution mode.

794: -- itemtype - represents the WF item type. In this case, it is FTERRESP
795: -- itemKey - identifies the unique item Key. In this case, it is the transaction_id
796: -- from wsh_inbound_txn_history
797: -- actid - Standard WF attribute to represent the activity ID inside the process
798: -- funcmode - Standard WF attribute representing the fuction execution mode.
799: -- resultout - Standard WF attribute that represents the return status of this API
800: --
801: -- Purpose : This is the API that is called as part of the actual routing response WF.
802: -- Control would be transferred to this API after the actual notification

Line 799: -- resultout - Standard WF attribute that represents the return status of this API

795: -- itemKey - identifies the unique item Key. In this case, it is the transaction_id
796: -- from wsh_inbound_txn_history
797: -- actid - Standard WF attribute to represent the activity ID inside the process
798: -- funcmode - Standard WF attribute representing the fuction execution mode.
799: -- resultout - Standard WF attribute that represents the return status of this API
800: --
801: -- Purpose : This is the API that is called as part of the actual routing response WF.
802: -- Control would be transferred to this API after the actual notification
803: -- has been fired. This API in turn calls procedure UpdateTxnHistory to

Line 2102: -- actid - Standard WF attribute to represent the activity ID inside the process

2098: -- Parameters
2099: -- itemtype - represents the WF item type. Here it is FTERRESP
2100: -- itemKey - identifies the unique item Key. Here it is the transaction_id
2101: -- from wsh_inbound_txn_history
2102: -- actid - Standard WF attribute to represent the activity ID inside the process
2103: -- funcmode - Standard WF attribute representing the fuction execution mode.
2104: -- resultout - Standard WF attribute that represents the return status of this API
2105: --
2106: -- Purpose : This is a selector/callback function to initialize data for each

Line 2103: -- funcmode - Standard WF attribute representing the fuction execution mode.

2099: -- itemtype - represents the WF item type. Here it is FTERRESP
2100: -- itemKey - identifies the unique item Key. Here it is the transaction_id
2101: -- from wsh_inbound_txn_history
2102: -- actid - Standard WF attribute to represent the activity ID inside the process
2103: -- funcmode - Standard WF attribute representing the fuction execution mode.
2104: -- resultout - Standard WF attribute that represents the return status of this API
2105: --
2106: -- Purpose : This is a selector/callback function to initialize data for each
2107: -- routing response process instance. In particular, this procedure

Line 2104: -- resultout - Standard WF attribute that represents the return status of this API

2100: -- itemKey - identifies the unique item Key. Here it is the transaction_id
2101: -- from wsh_inbound_txn_history
2102: -- actid - Standard WF attribute to represent the activity ID inside the process
2103: -- funcmode - Standard WF attribute representing the fuction execution mode.
2104: -- resultout - Standard WF attribute that represents the return status of this API
2105: --
2106: -- Purpose : This is a selector/callback function to initialize data for each
2107: -- routing response process instance. In particular, this procedure
2108: -- set the apps context for the WF item type. It can be used in the foll.