TriniDBA

This documentation covers how to create a custom application, program and executable in Oracle Applications. The custom application will load data from feeder systems into Oracle Application’s interface tables.

A custom application needs to be set up only once. The custom program executable will then need to be set up and the program defined. Finally, the program must be added to a request group, so that it appears in a user’s responsibility.

Step 1:        Create a new application: Log on as the SYSADMIN user. Select the System Administrator responsibility, then navigate to Application, and then Register.

Step 2:        Click the New button to insert a new row.

Insert a new application, Maryland Financial Group Limited. The Short Name chosen is MFGL and Basepath is MFGL_TOP. Save the record.

Step 3:        Create a directory d:PRODprodapplmfgl on oracleserver. Under mfgl, create a directory ‘11.5.0. Under this directory, create the directories: bin, data, log, out, reports, and sql.

The d:PRODprodapplmfgl11.5.0 directory will be set to the environment variable MFGL_TOP.

Step 4:        Under Windows, Oracle Applications stores the application top folders in the registry. Update the registry on oracleserver to add the MFGL_TOP base path:

[HKEY_LOCAL_MACHINESOFTWAREORACLEAPPLICATIONS11.5.0 PROD_oracleserver]

MFGL_TOP=”d:PRODprodapplmfgl11.5.0″

Step 5:        To add MFGL_TOP as an environment variable, create customPROD_oracleserver.cmd in the d:PRODprodappl directory and put the following path into this file.

set MFGL_TOP=d:PRODprodapplmfgl11.5.0

Step 6:        Navigate to Security, then ORACLE and finally DataGroup.

Insert a new record. Select the Maryland Financial Group Limited application, add APPS as Oracle ID and enter an optional description. Click Save.

Note that steps 1 to 6 only need to be done once. Since these steps have already been done, there is no need to go do them again.

Step 7:        The data will be loaded via SQL*Loader. Create the control file GLMLAS400.ctl file and place the SQL*Loader command in it. Place the control file in the d:PRODprodapplmfgl11.5.0bin folder.

Step 8:        Set up the concurrent program executable: Navigate to Concurrent, then Program and finally Executable.

Insert a new executable program. Ensure that the Execution Method is SQL*Loader, since selecting Host causes Oracle Application to look for an executable (“.EXE”) program rather than a “.CMD” program on Windows. Click Save.

Step 9:        Define the concurrent program: Navigate to Concurrent, then Program and finally Define.

Insert a new record and fill in the fields to add the new program. Click Save.

Step 10:   Click the Incompatibilities button. Insert a new incompatible program ‘Maryland – Load AS/400 GL Journals’. This will prevent another instance of this program from running if it is running already.

Step 11:    The program must now be set up so that it can be submitted from Standard Request Submission. To submit the program from the General Ledger Manager, the request group for the responsibility must be found. Navigate to Security, then Responsibility, and finally Define.

Search for the ‘General Ledger Manager’ responsibility. Note the name of the Request Group.

Step 12:   Add the new program to the Request Group. To do so, navigate to Security, then Responsibility and finally Request.

Search for the group noted in the previous step (in this case, ‘GL Concurrent Program Group’). Insert a new record for ‘Maryland – Load AS/400 GL Journals’.

Step 13:   Before running the concurrent request, place the data file in the d:PRODprodapplmfgl11.5.0data directory, under the name GLMLAS400GL.dat. If this file already exists in the directory, it can be overwritten.

Step 14:   Choose the General Ledger Manager responsibility. Submit a new request, ‘Maryland – Load AS/400 GL Journals’.

No parameters need to be entered for this request. The request will automatically search for the data file and load it if present. If not, the request completes in error and the log will have to be checked to determine the cause of the error.

For additional information on setting up a custom application, refer to Metalink Doc ID: Note:105127.1, Subject: FAQ (Customization).