Printer

Basic Information on PrintingVia the Application,
A user will submit a request to run a report. This is most commonly done from the Submit Request Form (shortname =FNDRSRUN).The request is written into the concurrent queue/request table(s) (e.g.,FND_CONCURRENT_REQUESTS). The concurrent manager who eventually picks up the request will read the request and its definition from the queue. From there, the concurrent manager will kick off Oracle Reports. As Oracle Reports begins to run, it will look at a setting for how many copies you want. If copies = 0, then Oracle Reports will look at the Print Style definition for which SRW file to use. If copies > 0, then Oracle Reports will look at the Print Driver definition for which SRW file to use. In either case, Oracle Reports will look at the Print Style to determine the rows and columns that are contained in the report. The Print Style rows and columns overrides both the Print Style and Print Driver SRW files (which contain rows and columns as well). After the file has been generated using the appropriate SRW file and row/columns settings, the Concurrent Manager will pre-pend the initialization string and append the reset string to the output. As a general rule, the first component of the initialization string should be the reset string. You should not assume that the printer has been properly reset. It is the responsibility of the System Administrator to properly configure the initialization and reset strings. All of the seed data provided in Oracle Applications is for a DEC LN03 printer. This seed data is provided as example only. Chances are very good that your printers do not adhere to the DEC LN03 standards. There are numerous page description languages that are used to communicate with printers. The Big 3 are HP's PCL 5, Adobe's Postscript, and Microsoft's Windows GDI (Graphical Device Interface). Additionally, here are some other page descriptions languages.