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:
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

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
   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



Thursday, 26 December 2013

How to change port in Oracle Apps R12



How to change the Web Listener Port number in Oracle E-Business Suite Release 12? [ID 760590.1]

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

Tuesday, 17 December 2013

Auto invoice import program: Unable to derive gl date for your transaction

Description:

Lets take an example to understand this issue.

The orders booked and shipped in OCT and return were made in NOV and OCT period was closed.
This is happening because of the GL date which is derived by Autoinvoice. As per the Autoinvoice interface data and the Autoinvoice setup, the GL date of the AR transaction to be created for the sales return order derived as "31-Aug-2012". However, the "Aug-2012" period is closed. As a result, the Autoinvoice is not able to create the AR transaction. The same thing is happening for the sales return order.

Temporary Solution:
Update the transaction gl date in the ar interface lines form manually in current open period and run Autoinvoice.

Permanent Solution:

This requires a little change in your current setup to avoid this problem in future.

1) Switch to the "Receivables Manager" responsibility.
2) Navigate to "Setup : Transactions : Sources".
3) Query with the required source :

Name : ABC_AUTO_INVOICE

4) Go to the "Autoinvoice Options" tab.
5) Set the "GL Date in a Closed Period" option to "Adjust".
6) Save the change.
7) Now check the issue.

Adjust will automatically adjust the General Ledger date to the first GL date of the next Open or Future enterable period.

For more information kindly review

Oracle® Receivables User Guide
Adjusting General Ledger Dates

Moreover, Doc ID 1080995.1 : Troubleshooting AutoAccounting in AutoInvoice is also very useful.