https://blogs.oracle.com/ptian/entry/oracle_application_r12_12_1
Thursday, 20 February 2014
Wednesday, 12 February 2014
When BI Publisher desent works in Office 2010
Finally figured out what is the root cause of this issue is. This is caused by one of the Microsoft's windows security update that installs VBA runtime file, which is supposed to fix a VBA vulnerability but caused third party softwares (plug-in) stop working! Yes, this third party software in this case is the Template Builder.
Here is the detail of the MSFT update patch.
Here is the detail of the MSFT update patch.
http://support.microsoft.com/
Basically what we need to do is to delete '.exd' files, which have been invalidated by the update, then refresh them by restarting the Word again. In my case, I found one file under C:\Documents and Settings\Administrator\
Sunday, 5 January 2014
Running a SQL Loader as a concurrent program
There are few steps to register a control file in Oracle Applications R12.
Step I:
Step I:
Place the test.ctl script under the “bin” directory in application top directory e.g“$FND_TOP/bin”.
Also place the data.csv file on the server and give the complete path of csv in ctl file. e-g: /opt/oracle/FND_TOP/bin/data.csv
Step II:
Login to Oracle Application > System Administrator responsibility
Navigate Concurrent > Program > Executable and enter a new one:
Executable: test
Short Name: test
Application: Application Object Library (or if you place it in any other top then give its name)
Description: SQL Loader
Execution Method: SQL*Loader
Execution File Name: test
Navigate Concurrent > Program > Executable and enter a new one:
Executable: test
Short Name: test
Application: Application Object Library (or if you place it in any other top then give its name)
Description: SQL Loader
Execution Method: SQL*Loader
Execution File Name: test
Step III:
Navigate to: Concurrent > Program > Define and enter a new one:
Program: SQL Loader Program
Short Name: test
Application: Application Object Library
Description: SQL Loader
Name: test
Method: SQL*Loader
Short Name: test
Application: Application Object Library
Description: SQL Loader
Name: test
Method: SQL*Loader
Output Format: Text
Step IV:
Navigate Security > Responsibility > Request
Query for Group: System Administrator Reports and add one request
Type: Program, Name: SQL Loader program
Query for Group: System Administrator Reports and add one request
Type: Program, Name: SQL Loader program
Thursday, 26 December 2013
How to change port in Oracle Apps R12
Also bounce the server after that, sometimes after running Autoconfig even its displays message Unable to authenticate session or unavailable.
REP-1401: 'cf_nameformula0007': Fatal PL/SQL error occurred. ORA-06502: PL/SQL: numeric or value error
Reasons
i.
Return data type of formula column is a Number and you
are returning character data type
ii.
If both are of same data type then length of
characters returning are exceeding from the declared variable in formula column
or formula column itself.
Solution
Make sure data types are same and length is enough.
REP-1259 group has no break columns
You will have to keep at least one database column in group.
I think in the group you are setting BREAK ORDER for formula column is not
having any database column. Or it is having then try to make Break Order
Ascending for any database field in that group.
Tuesday, 24 December 2013
ORA-06508: PL/SQL could not find program unit being called in Package ONT_HEADER_Def_Hdlr procedure Default_Record
When we open sale order or quote entry forms in Order Management error appears and form doesn't open. Error screen shot displayed is also uploaded.
Temporary Solution: Run adautocfg scripts at database node or bounce the server.
Permanent Solution:
Open Sales Order Screen Generates Error ORA-06508 PL/SQL Could Not Find Program Unit Being Called (Doc ID 841870.1)
The problem is due to shared memory reasons.
The memory can be checked through bde_chk_cbo.sql script, or it can also be checked by following query.
select * from v$parameter
where name like 'shared_pool%'
Then increase by changes in $ORACLE_HOME/dbs/init<SID>.ora.
Changes can be make according to Oracle Document Section 9 (Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1))
You have to bounce the database after changes in init<SID>.ora file.
Error screenshot
Subscribe to:
Posts (Atom)
