Problem: When running catpatch.sql as part of Oracle Database 9.2.0.8 upgrade, the following errors occur:
ORA-29832: cannot drop or replace an indextype with dependent indexes ORA-29844: duplicate operator name specified
Solution: These errors can be ignored.
Reference: Ora-29832 And Ora-29844 Errors Running Catpatch.sql [ID 781203.1]
Problem: I built a new Windows 2003 environment and restored a backup of E-Business Suite 11i. However, instead of going through the post-clone process, I attempted to change the hostname using the MOS document “How to change hostname for E-Business Suite Release 12 on single node” (Doc ID 1277556.1). However, when running AutoConfig on the apps tier, the following error occurred:
D:\ORACLE\MFGP\mfgpappl\admin>ECHO OFF Cannot find HOME_COUNTER under SOFTWARE\ORACLE\ALL_HOMES. Error when running adgenhomenum.exe d:\oracle\MFGP\mfgpora\8.0.6 ERROR: Running d:\oracle\MFGP\mfgpappl\ad\11.5.0\bin\adgethnum.cmd failed D:\ORACLE\MFGP\mfgpappl\admin>ECHO OFF
Solution:
Create HOME_COUNTER string key in registry under SOFTWARE\ORACLE\ALL_HOMES and set to 1.
Error Encountered
When AutoConfig was rerun, it completed with errors.
Solution:
Run the AutoConfig/adconfig.cmd command twice on apps tier! (Verified!)
Problem: When running the Payments batches process in Oracle, the following error occurs.
ORACLE error 20100 in FDPSTP
Cause: FDPSTP failed due to ORA-20100: File o}|#{|.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
ORA-06512: at "APPS.FND_FILE", line 396 ORA-06512.
Solution: Free disk space.
The drive on which temp files were created (pointed to by %TEMP% or %TMP%) ran out of space. Clear some disk space, and then rerun the Payments batches process.
Step 1: Navigate to Security > Responsibility > Request. Enter a new record with a new Group, Application, and Code. Then enter a new Request type.
Step 2: Next, navigate to Application > Function. Press F11 and search for CS%FND%. Locate CS_FNDRSRUN. Click the Form tab. Copy and paste the Parameters value to text file.
Step 3: Insert a new record in Form Functions named MFGL_FNDRSRUN. Paste the copied value into the Parameters field and modify the APPL_SHORT_NAME.
Step 4: Get menu name: GL_SUPERUSER
Navigate to Security > Responsibility > Define. Search for the custom responsibility by pressing F11 and entering the searching string, then press Ctrl+F11.
Step 5: Navigate to Application > Menu. We want to modify the Import Journals and review data Menu. Pull up GL_SUPERUSER menu and click View Tree. Navigate to Journals, then Import. Right-click and choose Properties. Alternatively, search for GL%IMPORT%.
Step 6: The GL_SU_J_IMPORT menu appears. Insert a new menu line together with its Prompt and Function Name. Then Save.
This documents the process of running a custom report in ADI.
Step 1: Log on to ADI (ILLUMINAT/******@TEST)
Step 2: Submit Ledger Process > Report
Step 3: Existing Report: MGFL%
Step 4: “MGFL Unaudited Revenue Stmt”
Step 5: Period: MAR-06
Step 6: Click Publishing Button
Step 7: Spreadsheet, New Workbook
Step 8: Publish To:
Step 9: Report Type: Financial Statement
Step 10: Green button: Submit and Clear the Form
Step 11: Then click Publish Report
This documentation covers locating the latest version of ADI on Metalink, downloading it, installing it on the client machine and configuring it to access an Oracle Applications instance.
Step 1: Log on to Oracle Metalink using your logon information (email address and password).
Step 2: Search for and read “Application Desktop Integrator (ADI) – FAQ” (Doc ID: Note:106667.1) to obtain instructions to download the latest version of ADI.
(Adapted from the FAQ):
QUESTION: Where can I download ADI from?
Download ADI from Metalink
Log on to http://metalink.oracle.com Click the Patches & Updates tab. On the Patches & Updates page, click Advanced Search. Enter: Product or Product Family: Click the Torchlight icon to search for Applications Desktop Integrator (adi). Release: ADI 7.2 Platform or Language: Microsoft Windows (32-bit) Client Patch Type: Any Press Go and the 7.2 base release will be available for download.
Step 3: The results of the search are returned at the bottom of the page.
Click the link ‘3966101’ to locate the patchset.
Step 4: You may be required to enter a username and password to access the file. Enter the email address and password that you used to log onto Metalink.
Step 5: Details about the patchset are displayed on screen.
Click Download to begin downloading the file. Note that the download size is 71MB.
Step 6: Click Save in the File Download dialog box, and then choose a location to save the file.
Step 7: After downloading, execute the patchset by double-clicking on it.
Step 8: Enter a location to unzip the files to, and then click Unzip.
Step 9: Ensure that all files were unzipped correctly (you should see ‘5179 file(s) unzipped successfully’), and then click Ok.
Then click Close to close the WinZip Self-Extractor program.
Step 10: In the folder that ADI was unzipped to, read the README.TXT file. It points the user to the ADI Installation Guide (ADI.PDF), which should be read before proceeding.
Step 11: After reading the installation guide, double-click Setupadi.exe to begin installation.
Caution: Remove headphones while installing this product since it uses a lot of extremely annoying sound effects.
Step 12: The Oracle ADI Installer loads.
Click Oracle Applications Desktop Integrator for Excel 2000/XP/2003.
Step 13: Click Yes to begin installation.
Step 14: The Oracle Installer Settings form is displayed. In the Company Name field, enter the name of the company. Then click Ok.
Step 15: The Software Asset Manager appears.
Install all of the products listed under Available Products. The products can be installed individually (one at a time), or all products can be selected and installed.
Note: The ADI Online Help will require you to choose a language to install.
Step 16: After installing the products, click Exit to exit the installer. You will be required to reboot the machine after exiting the installer.
Step 17: After the computer restarts, load Applications Desktop Integrator by clicking on the Start button, All Programs, Oracle ADI, and finally Applications Desktop Integrator.
Note: Let the client log on to the machine so that you can configure ADI under the user’s id. This is necessary since signon details are not shared between users.
Step 18: When the application is first loaded, a message appears informing the user to select an Applications database.
Step 19: After reading the message by the Office Assistant, click on the Signon button.
Step 20: The Signon form appears. Since there are no predefined databases, click Define Databases to define a new Applications database.
Step 21: The Select Database form appears. Click Add to add a database.
Step 22: Fill out the fields in the Add Database Details form, and then click OK.
Copy sqlnet.ora and tnsnames.ora from the “806 NET80” directory in the Project Folder to c:orantnet80admin and c:orantnetworkadmin. Note that these files contain configuration information for the production instance only.
In addition, each instance has a unique server ID. To obtain the server ID for the production instance, navigate to the Project Folder, and then open the file “Server ID.txt”. Copy the hexadecimal string under MFGP and paste it into the Server ID field in the Add Database Details form.
Step 23: After setting up the database details, save the information and log on to ADI using an Oracle Applications username:
After logging on, perform the following:
The job is submitted and completes within a few minutes. It will automatically open in Excel on completion.
Error Message: “No Listener”
Solution: Either instance on server does not exist or entry in TNSNAMES.ORA is incorrect. If TNS entry in the local TNSNAMES.ORA file is correct, then listener or database is not started on the server.
Error Message: “ORA-12571: TNS Packet Writer Failure”
Solution: Cannot send packets to the server. A firewall is blocking packets on the client machine.
Error Message: “ORA-12154: TNS: could not resolve service name”
Solution: Ensure that the service name is in c:orantnet80admintnsnames.ora
Check that c:orantnet80adminsqlnet.ora has names.default_domain and name.default_zone commented off.
Check %WINDIR%system32driversetchosts file has hostname and ip address.
Error Message: “An error occurred while attempting to establish an Applications File Server connection. There may be a network configuration problem, or the TNS listener may not be running. Nodename : ORACLESRV”
Solution: Incorrect FNDFS entry is in the TNSNAMES.ORA file. Recopy sqlnet.ora and tnsnames.ora from server onto client machine.
Subject: Tns Packet Writer Failure When Trying To Connect To ADI Ora-12571 (Doc ID: Note:264952.1)
Subject: Unable To Start ADI ORA-12571:TNS:Packet Writer Failure (Doc ID: Note:351088.1)
Subject: Troubleshooting the “Error Occurred While Attempting to Establish an Applications File Server Connection” (Doc ID: Note:117012.1)
[amazon asin=0071779728&template=iframe image&chan=default] [amazon asin=1849680620&template=iframe image&chan=default] [amazon asin=0071622292&template=iframe image&chan=default]
Problem: A database link must be created in the Target instance to pull (transfer) FSG information to the production instance from the test instance.
Solution: Use Define Database Links in Oracle Applications.
To define a database link in General Ledger perform the following steps
on the Target instance (the one you are copying to):
Step 1: Log on as sysadmin user and select a GL responsibility.
Step 2: Navigate to Setup > System > Database Links.
There are six fields that have to be entered:
Step 3: In the source database, enter the following SQL query:
SELECT value FROM v$parameter WHERE UPPER(name) = 'DB_NAME'; VALUE -------------- PROD
This value is to be entered in the ‘Database Name’ field in Oracle Applications.
Step 4: In the source database, enter the following SQL query:
SELECT value FROM v$parameter WHERE UPPER(name) = 'DB_DOMAIN'; VALUE ---------------------
This value must be entered into the ‘Domain Name’ field in the form. If it is null, any value can be entered into this field (e.g. WORLD).
Step 5: On the target database, grant privilege to apps user (log on as system user):
grant create database link to apps;
Step 6: Ensure the two hosts are in the hosts file on each host.
127.0.0.1 localhost 128.x.x.x oracleserver.domainname oracleserver 128.x.x.x oraclesrv.domainname oraclesrv
Step 7: Update the TNSNAMES.ORA file on each server with the entry for both instances:
PROD= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=ORACLESERVER.domainname) (PORT=1525)) (CONNECT_DATA= (SID=PROD) ) ) MFGP= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=ORACLESRV.domainname) (PORT=1527)) (CONNECT_DATA= (SID=MFGP) ) )
Step 8: Ensure that the TNSNAMES.ORA was set up correctly using tnsping to ping the remote instance.
Step 9: Ensure that SQL Restriction is turned off
Step 10: Bounce the 920 TNS listener on each node.
Step 11: Ensure that you can log on the other instance using SQL*Plus.
Step 12: Enter the following values into the form:
| Field | Value |
| Database Name | PROD |
| Description | Test Database |
| Connect String | PROD |
| Domain Name | WORLD (since it is null, any value can be entered) |
| APPS Username | apps |
| APPS Password | apps |
In the SQLNET.ORA file, I had to comment out the line: sqlnet.authentication_services= (NTS)
# sqlnet.authentication_services= (NTS)
Refer to Metalink Documents:
Doc ID 161635.1: (FSG Transfer Troubleshooting Guide)
Doc ID: Note:1057188.6 (WHERE DO YOU DEFINE DATABASE LINKS FOR FSG’S?)
[amazon asin=0070077290&template=iframe image&chan=default] [amazon asin=1453742735&template=iframe image&chan=default] [amazon asin=0615238440&template=iframe image&chan=default]
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).
This documentation shows how to load journals that were loaded into the GL_INTERFACE table.
Step 1: Log on as a user with access to the GL responsibility and select the General Ledger Manager responsibility.
Step 2: Navigate to Journals > Import > Run.
Step 3: Enter the Source and Group ID. Select Without Validation.
Step 4: Click Import.
Step 5: To delete imported journals, navigate to Journals > Import > Delete.
Step 6: Enter the Source, Request ID and Group ID.
The Request ID is that of the request used to import the journals (check View Requests to determine this ID).
We had some problems with loading the data because one of the fields, address_line3 was omitted from the data file. Verify the data file against the control file.
You must log on to the correct responsibility in order to import the data.
| Company | Org_id |
| Company A | 123 |
| Company B | 141 |
| Company C | 142 |
After the data is loaded, two concurrent programs must be run to import the data:
Data is loaded into:
Data is imported into:
Change VENDOR_SITE_CODE to ‘PRIMARY’.
For manual entry of vendor numbers, change the settings in the application and populate the SEGMENT1 field.
Valid TERMS_DATE: ‘Net 30 Days’
VENDOR_INTERFACE_ID must be in both tables. Insert it into the data file if necessary.
Recent Comments