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

Line 20: or override the standard logic for determining Retirement Cost Type, based on their own

16: Cost Type can either be 'COR' for Costs of Removal or 'POS' for Proceeds of Sale. This
17: function must return one of those two values, or downstream processing errors will result.
18:
19: The intended use of this extension is to provide clients with the ability to modify
20: or override the standard logic for determining Retirement Cost Type, based on their own
21: business rules. The standard application logic, located in this function, checks to see
22: if the expenditure type of the EI exists in the PROCEEDS_OF_SALE_EXP_TYPES
23: Lookup Set. If so, the function will return 'POS', otherwise it will return 'COR'.
24:

Line 21: business rules. The standard application logic, located in this function, checks to see

17: function must return one of those two values, or downstream processing errors will result.
18:
19: The intended use of this extension is to provide clients with the ability to modify
20: or override the standard logic for determining Retirement Cost Type, based on their own
21: business rules. The standard application logic, located in this function, checks to see
22: if the expenditure type of the EI exists in the PROCEEDS_OF_SALE_EXP_TYPES
23: Lookup Set. If so, the function will return 'POS', otherwise it will return 'COR'.
24:
25: One example of a customer business rule may be to derive the Retirement Cost Type based