Problem: How do I change the effective start date for an employee after it has been entered into EBS?
Solution: Use the hr_change_start_date_api.update_start_date procedure.
Problem: How do I change the effective start date for an employee after it has been entered into EBS?
Solution: Use the hr_change_start_date_api.update_start_date procedure.
Problem: While installing EBS R12.1 on Linux x86-64, the following error appears:
"Processing Disk1.... RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported. Please make sure you have UnZip 5.X in your path and try again... Cannot execute Install for database ORACLE_HOME RW-50010: Error: - script has returned an error: 1 RW-50004: Error code received when running external process. Check log file for details. Running Database Install Driver for TEST instance"
Solution: As root user, rename the default unzip (/usr/bin/unzip) to a temporary filename (e.g. /usr/bin/unzip-ver6), perform the installation, and then rename unzip-ver6 to the original name when complete.
# mv /usr/bin/unzip /usr/bin/unzip-ver6
Reference: R12 Rapid Install Failing With “RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.” (Doc ID 1455077.1)
Problem: How do I set Approval Analyzer Diagnostic so that it can be run as a concurrent request?
Solution: Refer to My Oracle Support article “R12: Approval Analyzer Diagnostic Script (Doc ID 1525670.1)”.
Problem: A number of cheques were printed and then spoilt as the wrong starting number was entered. AP tried to run the payment again, then realized that the invoices were not able to be pulled. The info on the payments showed that the cheques were still selected for payments.
Solution: Refer to R12 Generic Data Fix (GDF) Patch for Payment stuck when Invoices On “Spoiled Checks” remain in “Selected For Payment” Status (Doc ID 1367272.1). Apply patch 16216890, then run scripts $IBY_TOP/patch/115/sql/iby_splt_pmts_sel.sql and $IBY_TOP/patch/115/sql/iby_splt_pmts_fix.sql.
Problem: Running the PRC: Interface Supplier Costs completes in error. The output log shows the following error:
ORA-20003: import1_prog:ORA-00060: deadlock detected while waiting for resource ORA-06512: at "APPS.PA_TRX_IMPORT", line 11279 ORA-06512: at "APPS.PA_TRX_IMPORT", line 9201 ORA-01400: cannot insert NU
Solution: Refer to “PAAPIMP – PRC: Interface Supplier Costs fails with Error ORA-01400: cannot insert NULL into (“PA”.”PA_EXPENDITURE_ITEMS_ALL”.”BILLABLE_FLAG”) (Doc ID 1265338.1)”. This issue was caused by a data error. Open an SR to get a datafix for the issue.
Problem: How do I determine who is logged on to EBS?
Solution: There are two ways you can do this: check the Monitor Users form, or run the Signon Audit Users report.
Problem: The Cost Manager concurrent job stopped running a few weeks ago. It now remains on the Pending phase. The Actual Cost Worker, which usually runs every five minutes, has not run since.
Solution: An error occurred while the Actual Cost Worker was running (tablespace ran out of space) and so the process completed in error. The errored process must be resubmitted, so that it completes successfully. After this, the Cost Manager and Actual Cost Worker began running once more.
Problem: Users are getting ORA-01653 or ORA-01658 for tablespace APPS_TS_TX_DATA.
Solution: Add another datafile to the APPS_TS_TX_DATA tablespace using the alter tablespace add datafile command:
alter tablespace APPS_TS_TX_DATA add datafile '/path/to/data/files/db/apps_st/data/a_txn_data0x.dbf' size 1950M;
Problem: I want to create a custom concurrent program based on a SQL script, but do not know how to pass date parameters to the concurrent program.
Solution: Use ‘&1’, ‘&2’ etc. and format it using ‘yyyy-mm-dd hh24:mi:ss’ in the SQL program (i.e. to_date(‘&1’, ‘yyyy-mm-dd hh24:mi:ss’). In the Concurrent Program parameter setup, set the Value Set as FND_STANDARD_DATE.
Problem: After incorrect PPR (Payment Process Request) is terminated, the invoices cannot be selected for payment.
Solution:
Refer to R12: Generic Data Fix (GDF) patch for “stuck” invoices after PPR is terminated or completed (Doc ID 874862.1). Apply patch 19717441, then run the scripts $AP_TOP/patch/115/sql/ap_Rel_Inv_frm_TermPPR_sel.sql and ap_Rel_Inv_frm_TermPPR_fix.sql.
Recent Comments