Oracle Reports For Dot Matrix Printers to Print output on Stationary

I would like to share my experience on developing the reports which output should print on the preformed stationary using the dot matrix printers.

If we have to print the output on dot matrix printer it would be better if we should generate the report which  gives the output in normal plain text format.
We can generate the text output reports either by using oracle RDF reports or XSL-FO text output bi publisher report.
Before starting the development  we need to ensure the below points.

  • we should have the exact hard copy of stationary (or photo copy of it) on which data should print.
  • If we get photo copy then it should have the same dimensions like length and width of the original stationary.
  • Has to fix or load the stationary in dot matrix printer as per the printer guidelines always. 
  • Identify the number of lines should feed for each copy of the print so that we can make sure in the report should generate same number of lines for each copy.
  • Identify for each section of information starting line ,starting character position and ending character positions in that line.
  • In case if we are building an RDF report, has to place one line filler at end to make sure that it should generate required space to get starting position of the next copy of stationary in the printer correct position.
  • To have this filler we may need to print at least one dot for each line.
  • Some times this RDF report will render a form feed (enter) for each main repeating frame i.e after printing one copy which will cause issues while output gets printed on running stationary.
  • To make sure report won't give form feed we have to adjust existing SRW driver or have to create a new Report drivers as explained in below section.
Creating a new SRW  Driver for text ouput:


If Pasta is not already at the latest version of 3.0.4, install the latest released Pasta Patch 3325651. Use the following command to determine the current version of Pasta: FNDPSTAX -v

Copy the default Pasta configuration file in order to create a configuration files that support non-Postscript printers (any name can be used *.cfg): 

cp $FND_TOP/resource/pasta.cfg pasta_epson.cfg 

Edit the pasta_epson.cfg file and change the “outputFormat” parameter to text and/or a character set that the printer supports, as follows: 

i.e. outputFormat=text.WE8ISO8859P1 or outputFormat=text 

SRW Drivers will be read by the oracle reports server while generating the RDF report output. Reports server will look into SRW driver files which located in the location $FND_TOP/$APPLREP these files will be having extension of .prt.

By reading these .prt files report server will set the page breaks and other control characters to format as bold or underlined in the final output. Sample .prt file looks like below

In this prt file seventh line linefeed ...
causes the report server to enter page break at the end of each copy(i.e for each repeating frame prints). If we remove this then we won't get page break and has to use this driver files in the printer setup.





Printer setup:

è         Driver
Navigation                                  : System Administrator –Printer-Driver
Driver Name                      : "PASTA_LANDWIDE" -- For dot matrix printers
User Driver                        : "Pasta driver for Landwide"
Description                        : "Pasta universal PS driver for Landwide style "
SRW Driver                        : "PD"
Driver Method                  : "Program” (Select as program)
Driver Method Parameters:
Spool File                           : "Yes" (Check the Check mark)
Program Name                 : "FNDPSTAX"
Arguments                        : "-pn$PROFILES$.PRINTER -c$PROFILES$CONC_COPIES -f$PROFILES$.FILENAME –l -Fpasta_epson.cfg"














è  Printer Type
Navigation          : System Administrator –Printer-Types
Type                     : "—Pasta Printer Type"
Description         : "The printer type that can support many printers and languages"
Style                     : "LANDWIDE"
Driver Name       : "PASTA_LANDWIDE"





è  Register Printer
Printer                 : “XXTEST”
Type                     : "—Pasta       Printer Type"
Description         : "XXTEST Dot Matrix "



Comments

Post a Comment

Popular posts from this blog

Queries For Oracle Interface Errors Records.

Below are the queries to get the error records information while processing interface data. AP Invoices:   SELECT    airl.last_update_date process_date,    HU.NAME,   nvl(ail.invoice_line_id,aii.invoice_id) process_id,   'AP' module,   'Import AP Invoice' interface_name,   aii.source source,   NVL(SUBSTR( ail.dist_code_concatenated,1,instr(ail.dist_code_concatenated,'.',1,1)-1),'ALL') company,   'ERROR' status,   ail.line_type_lookup_code ,   airl.parent_table ,   ail.description ,   NVL(ail.distribution_set_name,dist_code_concatenated) ,   pvsa.vendor_site_code ,   listagg(NVL(airl.reject_lookup_code,'AP_INV_ERROR') ,';') within group (order by NVL(airl.reject_lookup_code,'AP_INV_ERROR')) error_code,   listagg(flv.meaning,';')  within group (order by NVL(flv.meaning,'AP_INV_ERROR'))error_summary,   NULL error_details,   pv.vendor_name ,   pv.segment1 ,   aii.invoice_amount,   aii.i
Read more

Customising PO Output For Communication Report in Oracle Purchasing

Image
PO Print PDF Report: Oracle EBS provided  a standard functionality to print the PO report directly from the PO form itself by clicking tools menu and view PDF option. Once we select that option output will be rendered in PDF format in the browser instantly. Internally it will run the concurrent program 'PO Output For Communication'. This concurrent program is of JAVA type which will uses the seeded package  'PO_COMMUNICATION_PVT'  for generating the XML data and later this XML data will be processed and formatted by using the XSL template of data definition 'Standard Purchase Order Data Source' in case of standard PO's. Oracle by default will provide one standard BI publisher template for this. In case if we want to have custom layout for this report we can build a new template for the same data definition and this template has to be used while doing the setup for PO Document types. Creating Custom Template and Setup this for PO Document type: To c
Read more

Oracle APPS Useful Queries

                       ACCOUNT PAYABLES Payable Open Interface Rejection:   SELECT ail.* FROM AP_INVOICES_INTERFACE ai ,   ap_invoice_lines_interface ail ,   ap_interface_rejections AIR WHERE ai.GROUP_ID='EO_AUG-13_010813_443' AND ai.status    ='REJECTED' AND ai.invoice_id=ail.invoice_id   --and ail.dist_code_concatenated='66810-00-999-00000000-00000000-00000-FI100' AND air.parent_id = DECODE(air.parent_table,'AP_INVOICES_INTERFACE',AI.INVOICE_ID,'AP_INVOICE_LINES_INTERFACE',ail.invoice_line_id,NULL) ORDER BY 2; AP Invoices Query: /*+INDEX (AP_INVOICES_ALL [XXDG_TEST]) */ SELECT  apia.invoice_id,        alc.displayed_field "Invoice Type",        apia.invoice_num "Invoice Number",        apia.invoice_date "Invoice Date",        apia.gl_date   "Invoice GL Date",        nvl(apia.VOUCHER_NUM,doc_sequence_value)"Voucher Number",        apia.description inv_Description,  
Read more