Tuesday 19 January 2021

Setting the Custom Font for XML Publisher Report as a PDF Output.

Recently while we have working on XML Publisher came across a requirement from the client. The requirement was to have a specific font for the PDF Report Output i.e. print Barcode on PDF Format.

We need first to download & Install the required custom Font file from the Internet; this file is not free and need a license to possess it. But we can surely go with the trial one to start with.

Once you have download & Install the Font File, all installed font goes to “C:\Windows\Fonts” directory after that we start the setup you can use standard font path or use optional path for the .ttf file. We have placed the .ttf file under the custom path i.e. “C:\idautomationhc39m”.

The next step would be to configure and so the “xdo.cfg” should be updated to map to the new font as below Generally the .cfg file is found in the path “C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config”. in my case:

Initially xdo.cfg doesn’t exist. Well it does, it’s just called xdo_example.cfg and you can easily rename it to xdo.cfg. Open it up with your editor of choice and this line at the bottom:

     <font family="IDAutomationHC39M" style="normal" weight="normal">

      <truetype path="C:\idautomationhc39m\IDAutomationHC39M.ttf" />

      </font>

The “family” is the same as “Base Font” and the “path” is the directory where you have your font file (.ttf) located.

Note: For the exact File Name of .ttf file, Right click the font file and go to properties. Copy the .ttf file name Font family is the name that you see in Word under Fonts

This would complete the local setups and now if you have a RTF file just load the .xml file and have the tag mapped to the desired font and run, you would be able to see the desired font output if you run it as PDF.

Moving to the setups required for setting the Fonts in the Oracle Application.

Navigate to the XML Publisher Administrator Responsibility è Administration









Move to Font Files Tab and Click on Create Font File

 


Give a desired Font Name say “IDAutomationHC39M” and map the IDAutomationHC39M.ttf file from your local system. The font file would be uploaded and saved to the server.

 


Next we need to create the Font Mapping, Move to Font Mappings Tab and Click on Create Font Mapping Set






Feed the details for the Mapping Name, Mapping Code and Type as FO To PDF and click on APPLY


 





Now click on Create Font Mapping

 



Feed in the details for Font Family as IDAutomationHC39M the name that you see in Word under Fonts, Style and Weight would be Normal and Font Type would be TrueType then click on CONTINUE

 


Next map the Font Mapping with the Font File that was created in the above step and click on APPLY.

 






Here is the final screen, now the Font File is mapped with the Font Mapping.

 






Next and the final step would to configure it, move to the Configuration Tab







Under FO Processing map the Font Mapping Set created in the above step and SAVE.








This completes the setting up the new Font with the XML Publisher.

Now when we run our RTF file from the Application the output would be as desired say as below, my requirement was to have the same is shown as below. 


 


This completed the complete information on setting up the desired font for our custom XML Publisher Report an RTF File.

Thanks You!!!

Thursday 14 January 2021

Form Builder Errors On Startup FRM-10102: Cannot attach PL/SQL library APPCORE

Errors: 

Unable to open Template.fmb. Getting following error

FRM-10102: Cannot attach PL/SQL library APPCORE. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library APPDAYPK. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library GLOBE. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library FNDSQF. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library JA. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library JE. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library JL. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library VERT. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library GHR. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library PQH_GEN. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library PSAC. This library attachment will be lost if the module is saved.

Cause:

FORMS_PATH was not set
 
FORMS_PATH should include location of pll and fmb files

Solution:

On windows7

=========

1. Open the System Properties control panel applet.
Note: To do this
Start Menu => Control Panel => System
2. Click on the Advanced tab.
3. Click on the Environment Variables button
4.Add the FORMS_PATH variable to the set of User Variables .
5. Click on the New button and enter the Variable Name and Variable Value
a). Variable Name = FORMS_PATH
b)Variable Value = full path to your pll and fmb files

Example

C:\DevSuiteHome_1\cgenf61\admin;C:\DevSuiteHome_1\forms

Optinal

6.Copy the above pll from your Unix environment i.e. ($AU_TOP/resource) to the location pointed by FORMS_PATH in the Windows machine i.e.(C:\DevSuiteHome_1\cgenf61\admin).


Wednesday 13 January 2021

APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM, because the environment variable &BASEPATH is not set for the application to which the concurrent program executable &EXECUTABLE belongs.

APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM

Error:
=====
APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM, because the environment variable &BASEPATH is not set for the application to which the concurrent program executable &EXECUTABLE belongs.

Shut down the concurrent managers. Set the basepath environment variable for the application. Restart the concurrent managers. (VARIABLE=)

Routine AFPEOT cannot construct the name of an executable file for your concurrent request 5194371.

Check that the file name components are correct and valid on your system. Check that the environment for the person who started the concurrent manager

Scenario:
=======
There is a Custom Top registered and that top is not set in the ENV while starting the conc.

Request Name:  Project Balance Head Exp

Query to Check whether the Env is set for the Particular request: 

===============================================
select variable name, value from fnd_env_context e, fnd_concurrent_processes p ,fnd_concurrent_requests r where p.concurrent_process_id =p.concurrent_process_id and p.concurrent_process_id = r.controlling_manager and e.variable_name like '%CUSTOM_TOP%' and r.request_id = &request_id;

Solution:
=======

 Ø  Make the new custom environment file in $APPL_TOP.

    i.e. $APPL_TOP/customTEST_erptestappldb.env

   Doing below entry in above make custom environment file in $APPL_TOP

   export XXCUSTOM_TOP=/testappl/apps/apps_st/appl/XXCUSTOM/12.0.0

 Ø  Add the respective Top in env file.

   $APPL_TOP/admin/adovars.env

   so that while running autoconfig it won’t remove every time.

   export XXCUSTOM_TOP=/testappl/apps/apps_st/appl/XXCUSTOM/12.0.0