Professional Documents
Culture Documents
Figure 1
Optio develops, implements and supports a suite of
Figure 1 is an example of a standard Oracle Purchase integrated output customization and delivery
Order. It is easy to see that the output is very generic solutions that facilitates the integration,
and does not meet the expectations and needs of individualization and delivery of information
customers. throughout the enterprise and beyond. The
technology provides an enterprise-wide foundation
for ongoing output management that enables users
STANDARD ORACLE INFORMATION to customize information, as business needs
change. The solution has been developed with a
• Lack of company identification and standards component-based open systems architecture,
• No visual images – logos, barcodes, lines, allowing easy, seamless integration with disparate
boxes, shaded areas, etc. information systems and Oracle Applications. The
technology provides a gateway between legacy and
• Limited line items client/server applications and their output
• Lack of document reformatting management. Users can import legacy data into
customized forms without reprogramming the
• Manual document process original application.
WORKING IN A CUSTOMIZED ORACLE
Input APPLICATIONS ENVIRONMENT
F Channel
OptioDCS (Document Customization Server)
U integrates seamlessly with Oracle Applications
N enabling users to take advantage of the
C sophisticated capabilities of both a best-of-breed
T document and output customization solution and
I world-class Oracle Applications. The integration
O Data between the products is achieved through setting
N Maps Format Devices up new printer definitions in the Oracle
S Applications. When an Oracle Applications user
executes a print routine, the Oracle Application will
pass the standard Oracle printer “spool file” or print
Output stream into the OptioDCS software. This process
Channel will take place whether the print job of spool file(s)
which contain print output for multiple transactions,
or if the print job contains output to be printed for a
single transaction. The process of capturing the
standard Oracle “spool file” or database print
Figure 2
stream and reformatting it and then sending it to
the desired print or output destination(s) is
Input Channel: Where data comes from: stdin, transparent to the end-user who originally launched
file, odbc the print job from the Oracle Applications and
requires no modifications to the Oracle
Set Dimensions: page size, rows, columns Applications.
Delimited Data Structure
Data Maps: Location of data, set data to variables
and regions
O ra c le D B