Skip to Content Information Center
Lexmark T650

Lexmark T650

Incorrect and Unreadable Maxicode Barcodes in SAP (Oct. '11)

What you will see

Incorrect print output and the inability to read SAP-generated Maxicode bar codes:

plus some type of ASCII, i.e., 04951<GS>GSUN<GS>06X610

...

Or:

What happens

When you try to modify the output character set of the device type, you redefine the output code of a special character with non-printable information that is notapplicable to the required hexadecimal code.

Hence, extra characters in the non-printable ASCII range are printed due to SAP filtering by the SAP kernel.


NOTE:
This is only possible if the redefined character does not occur as "normal" printable text during the output of the bar code label or form. Should this be the case, the character will not be issued correctly after the modification.

Suggested Remedy

SAP AG recommends the following solution in an effort to output the hexadecimal code in a bar code contained within a SAP script.

Example using the '#' character

with the font "ÿ" (

dieresis*)

(0x1D [29 in decimal format])

* ( ¨ ) placed over the second of two adjacent vowels or over a vowel at then end of a word to indicate the vowel should be sounded out, e.g., naïve or Brontë.

Device type usedOutput character set of LB_UBI
LB_UBI 1117

Possible solutions

  1. The SAP character "ydieresis" ("ÿ"), SAP number 365, has the hexadecimal code FF in code page 1117. It does not occur as normal text in the form and can, therefore, be redefined.

  2. Up to Basis Release 4.6D:

  • In transaction SPAD: Copy code page 1117 to code page 9117.

As of Basis Release 6.10:

  • In transaction SCP: Copy code page 1117 to code page 9117.
  1. Up to Basis Release 4.6D:

  • In transaction SPAD: Edit code page 9117, change the hexadecimal code for SAP character 365 (ydieresis) from FF to 1D. Save the code page.

As of Basis Release 6.10:

  • In transaction SCP: Edit code page 9117, change the hexadecimal code for character "U+00FF" from FF to 1D. Save the code page.
  1. In transaction SPAD: Copy the LB_UBI device type toZLB_UBI. Edit ZLB_UBI, replace the three entries of code page 1117 with the entries in code page 9117, and then save the device type.

  2. In transaction SPAD: For the output device used (that is, the printer on which the bar code is printed), replace the LB_UBI device type with the ZLB_UBI device type that you have just created.

  3. In transaction SE71: In the SAPscript form, enter the special character ydieresis ("ÿ") at the position in the bar code data where the value 0x1D is to be output. To enter special characters, you may use the "Include-Characters-Printable characters" function in the SAPscript editor.

S

till Need Help?

If you require additional assistance, please contact SAP or see Contact information below.
NOTE:
When calling for support, you will need your printer model/machine type and serial number (SN).

Please be near the products described in this article to expedite the support process and reduce call-back situations.

LEGACY ID: SO6848

Was this article helpful?
Top