Oracle Applications Config

Written by Michael
Friday, 09 November 2007
I've decided to start pasting any information I've found handy whilst configuring Oracle Applications. Just snips of code, and other information which I have had trouble finding myself. Like the following, which is the list of parameters for the FNDRSRUN form when called from a menu function. Complete List of All Submit Request Paramters Below is the comprehensive list of parameters supported by the ”Run Requests” 'FNDRSRUN' SRS form and additional information about their usage. • REQUEST_GROUP_CODE • REQUEST_GROUP_APPL_SHORT_NAME (used with REQUEST_GROUP_CODE) • CONCURRENT_PROGRAM_NAME Managing Concurrent Programs and Reports 6 – 21 • PROGRAM_APPL_SHORT_NAME (used with CONCURRENT_PROGRAM_NAME) • REQUEST_SET_NAME • SET_APPL_SHORT_NAME (used with REQUEST_SET_NAME) • SUBMIT_ONCE (default ’N’). SUBMIT_ONCE can be set to either Y or N ( N is the default). SUBMIT_ONCE is used in conjunction with CONCURRENT_PROGRAM_NAME or REQUEST_SET_NAME. If SUBMIT_ONCE is set to Y, then the form will exit after the Submit button is clicked. • TITLE • LOOKUP (default ’N’) • USE_ORG, ORG_ID, ORG_NAME, ORG_CODE, CHART_OF_ACCOUNTS_ID (five parameters) If USE_ORG is set to ’Y’ (default is ’N’) then the Submit Requests form checks to see if the other ORG parameters are set. If the parameters are not set, then it attempts to populate the parameters from the globals (GLOBAL.FND_ORG_ID, GLOBA L.FND_ORG_NAME, etc.). If the globals have not yet been set, the an ORG LOV shows, and both the parameters and the globals are populated from the LOV. Values sets should always reference the parameters, not the globals. • CHAR1, CHAR2, CHAR3, CHAR4, CHAR5 • DATE1, DATE2, DATE3, DATE4, DATE5 • NUMBER1, NUMBER2, NUMBER3, NUMBER4, NUMBER5 In your value sets, refer to these parameters as: :PARAMETER.CHAR1, :PARAMETER.DATE1, :PARAMETER.NUMBER1 etc.
Last Updated ( Friday, 25 April 2008 )

Next >

[ Back ]