Arabic in pdf reports

Arabic is not possible in 6i pdf reports. The two solutions which is possible are following :

1. Use xml publisher and develop all reports in xml.

2. Install Acrobat distiller software in ur PC (client machine). Develop report in 6i. And register that report output format as PostScript format. But in this you will have to install Acrobat Distiller on every users PC who is using this report.

arabic report coming as question marks ???????

The standard report was not coming with arabic data though character set supports Arabic :

There are two solutions :

1. Try set profile option FND: NATIVE CLIENT ENCODING to ARISO..... or ARWINS.....


OR


2. Use pasta viewer to view non english language :

login through sysadmin > install > viewer > add a new line
text apps/bidi pasta viewer


-----------------------------------------

search .prt file you are using with the help of below query --


SELECT PRINTER_DRIVER_NAME, USER_PRINTER_DRIVER_NAME, PRINTER_DRIVER_METHOD_CODE, SPOOL_FLAG, SRW_DRIVER, COMMAND_NAME, ARGUMENTS, INITIALIZATION, RESET
FROM FND_PRINTER_DRIVERS
WHERE PRINTER_DRIVER_NAME = (SELECT PRINTER_DRIVER
FROM FND_PRINTER_INFORMATION
WHERE PRINTER_STYLE = (SELECT PRINT_STYLE
FROM FND_CONCURRENT_REQUESTS
where request_id = <>) AND PRINTER_TYPE = (SELECT PRINTER_TYPE
FROM FND_PRINTER
WHERE PRINTER_NAME = (SELECT PRINTER FROM FND_CONCURRENT_REQUESTS where request_id = <>)))



insert these lines in .prt file at the end

----------------------------------------
nls locale "arabic"
nls datastorageorder "logical"
nls contextuallayout "no"
nls contextualshaping "yes"
-------------------------------------------


set this in system profile options :
Viewer: Application for Text = pasta viewer

OFA client error odbc32.dll or odbcnt.dll

While installing Oracle Financial Analyzer client software you get some error regarding odbc32.dll or odbcnt.dll

rename odbc32.dll and odbcnt.dll in c:/windows/system32

and press retry

default values in discoverer plus login page

If you want these values default on your discoverer 10g plus/Viewer login page.

Connect to :
Database :

Edit your URL as follows :

http://disc-host.disc-domain:disc-port/discoverer/viewer?connectionAccessType=APPS&Database=database-SID

http://disc-host.disc-domain:disc-port/discoverer/viewer?connectionAccessType=APPS&Database=database-SID


replace the original value for bold characters

arabic report imp doc ids

arabic Appears As Question Marks In Reports -----key link---- Doc ID: Note:199429.1 Type: PROBLEM

9iAS: Arabic Characters Displayed Question Marks Doc ID: Note:208901.1 Type: PROBLEM
Difference between AR8MSWIN1256 and AR8ISO8859P6 characterset Doc ID: Note:260023.1 Type: BULLETIN

Question Marks (?) in Diagrammers and RON when using Arabic NLS Doc ID: Note:108973.1 Type: PROBLEM

Printing and Previewing Arabic Reports using PASTA in Oracle Applications 11i Doc ID: Note:179801.1 Type: HOWTO

Subject: How To Print Arabic Reports in PDF Format? Doc ID: Note:430774.1 Type: HOWTO

cannot connect 11i using Discoverer/ADI/TOAD

Problem cannot login through applications user using ADI/Discoverer/TOAD :

the Oracle Applications Authentication mode is defined in the the Applications context file:
$APPL_TOP/admin/_.xml context file

Look for the following context variable: s_appserverid_authentication
By default, in E-Business Suite 11.5.10, this is set to SECURE. In previous E-Business Suite 11i versions, this was set to OFF.There are 3 Modes of authentication:

* ON : Partial
* SECURE : activates full server security (SECURE mode)
* OFF : deactivates server security

As a workaround, you may set this to OFF from the default of SECURE.Run Autoconfig to instantiate the changes.
Now you should be able to access E-Business Suite 11.5.10 databases using Discoverer/ADI/TOAD.

enable all disabled triggers in 11i

query to see how many trigger disabled

select count(*)from dba_triggerswhere status = 'DISABLED' and owner !='SYS';


run this script as trig.sql as sysdba

--------------------------------------------------


set serveroutput on size 1000000set verify offset serveroutput on
DECLAREsql_cmd varchar2(1024);
cursor cur_record isselect distinct OWNER,TRIGGER_NAMEfrom dba_triggerswhere status = 'DISABLED' and owner!='SYS';
trig_rec cur_record%ROWTYPE;
BEGINDBMS_OUTPUT.PUT_LINE('START OF PROGRAM');
FOR trig_rec IN cur_record LOOP
BEGINsql_cmd := 'alter trigger 'trig_rec.owner'."'trig_rec.trigger_name'" enable ';
EXECUTE IMMEDIATE sql_cmd;
DBMS_OUTPUT.PUT_LINE('Enabled : 'trig_rec.owner'.'trig_rec.trigger_name);
EXCEPTION WHEN others THENdbms_output.put_line('Error : 'trig_rec.owner'.'trig_rec.trigger_name);dbms_output.put_line(SQLERRM);END;
END LOOP;
DBMS_OUTPUT.PUT_LINE('END OF PROGRAM');
END;
/



------------------------------------------------------------------------------