<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Print MICR Font from SAP Script Using PostScript Printer Driver on Xerox DocuPrint 180 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/print-micr-font-from-sap-script-using-postscript-printer-driver-on-xerox/m-p/687320#M30825</link>
    <description>&lt;P&gt;Dear All,&lt;/P&gt;
  &lt;P&gt;We have a requirement to print a check using SAPScript on a Xerox Docuprint 180 Printer from ECC. The standard Printer Device Type DP180 is outdated and no longer available; we have created a custom device type to print the MICR Font.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;We tried using PCL Driver Type to print the MICR.&lt;/P&gt;
  &lt;P&gt;1. We defined MICR_E font on the custom Device Type &lt;/P&gt;
  &lt;P&gt;2. Added the PCL escape sequence for MICR Font from the Xerox Printer Manual into Print Control 450 for the font. (&amp;lt;ESC&amp;gt;(0U&amp;lt;ESC&amp;gt;(s0p8.00h9.00v0s0b0T)&lt;/P&gt;
  &lt;P&gt;The MICR works fine. However, this is messing up the rest of the layout as the original layout was designed using a POST2 Device Type and a PS Driver.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Now we are trying to use a PostScript Driver to trigger the MICR. Herein lies the problem.&lt;/P&gt;
  &lt;P&gt;I am simply unable to figure out what the Print Control Character Sequence should be to trigger the MICR for PostScript. Any kind of help will be greatly appreciated. This is a critical issue now.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Thank you.&lt;/P&gt;
  &lt;P&gt;Johnson&lt;/P&gt;</description>
    <pubDate>Fri, 03 Aug 2018 03:43:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2018-08-03T03:43:13Z</dc:date>
    <item>
      <title>Print MICR Font from SAP Script Using PostScript Printer Driver on Xerox DocuPrint 180</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/print-micr-font-from-sap-script-using-postscript-printer-driver-on-xerox/m-p/687320#M30825</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;
  &lt;P&gt;We have a requirement to print a check using SAPScript on a Xerox Docuprint 180 Printer from ECC. The standard Printer Device Type DP180 is outdated and no longer available; we have created a custom device type to print the MICR Font.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;We tried using PCL Driver Type to print the MICR.&lt;/P&gt;
  &lt;P&gt;1. We defined MICR_E font on the custom Device Type &lt;/P&gt;
  &lt;P&gt;2. Added the PCL escape sequence for MICR Font from the Xerox Printer Manual into Print Control 450 for the font. (&amp;lt;ESC&amp;gt;(0U&amp;lt;ESC&amp;gt;(s0p8.00h9.00v0s0b0T)&lt;/P&gt;
  &lt;P&gt;The MICR works fine. However, this is messing up the rest of the layout as the original layout was designed using a POST2 Device Type and a PS Driver.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Now we are trying to use a PostScript Driver to trigger the MICR. Herein lies the problem.&lt;/P&gt;
  &lt;P&gt;I am simply unable to figure out what the Print Control Character Sequence should be to trigger the MICR for PostScript. Any kind of help will be greatly appreciated. This is a critical issue now.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Thank you.&lt;/P&gt;
  &lt;P&gt;Johnson&lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 03:43:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/print-micr-font-from-sap-script-using-postscript-printer-driver-on-xerox/m-p/687320#M30825</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-08-03T03:43:13Z</dc:date>
    </item>
  </channel>
</rss>

