Label/Email Notice Configurator

Note:  if you are looking for information on shipping labels, please click here.

The control file for labels and email notices is a text file which contains configuration and detail information for the system.  To set the path to the Label Control file, go to EDIMNU--> Shipping/Handheld System Information--> Labels tab, and then enter the path to the directory on the server.  To enter the file name for the label control file, go to EDIMNU--> Cross-Reference Maintenance--> Label Cross Reference, and then enter the appropriate settings for a new label file (a text file ending with the 3-character file extension .lbl).

• Commands

• Token Attributes

• Numeric Value Tokens

• Command Token Replacement

• Special Tokens

• Direct File Interface

• Embedding SQL statements

Generic Types

Non-Shipping Labels and Emailing

The handheld solution can generate other labels as well as producing shipment emails.

Other labels the labeling system is capable of producing are as follows:

• Purchase Order Receipt Labels
• Job Receipt Labels
• Job Issue Labels
• Stock Code Labels
• Bin Labels

Unlike the shipping labels there are no predefined tokens.  The SYSPRO fields names for the tables are used to extract the data.  It is important to understand the tables available for a particular label are specific for the SYSPRO function.  For example Purchase Order Receipt labels would access the PORMasterHdr and PORMasterDetail tables. Additional tables are generally available based on information from the main tables for the function.  One instance of this extension of available tables is that the POMasterDetail table contains a StockCode which is used to provide access to the InvMaster table. 

As an example of the differences in tokens, for a shipping label the purchase order number would use the token <PONUM>. A purchase order receipt label would use the field name <PurchaseOrder>.

To find table field names using SQL use the SQL server management studio to  expand the database, find the table and look at the column names. To view column names within SYSPRO for CISAM users or users unfamiliar with SQL,  select Report Writer->Browse->Browse On Data Dictionary Columns.  The table name will be requested and then the columns displayed.

If the label contains the word "ERROR" in your label data the labeling system was unable to determine the column and/or table which was requested.  Either there is an error in the token or the token requested is not available as valid token.  Double check the column names in the table and correct the token name to match the field name.  If the word "NODATA"  or incorrect data is in the label output then the labling system understands the token, but does not know how to get to the data requested. Try using the fully qualified table/field name by adding the table name in front of the token in the form of <tablename.fieldname> (I.E. <PORMasterHdr.PurchaseOrder>). In some cases the more advanced data controls such as <START> and <READ> might be required.

The system provides a base set of information for the handheld solution. The information provided is summarized in the table below.  The system is able to print any information from a SYSPRO table that is able to be read based on the information provided.  For example a purchase order receipt  is able to print information from the stock code master based on the stock code of the line being received.

  Tokens

Tokens are anything within <> within the control file.  They are generally used within the [LABEL] area of the control file, but can be used within many of the commands also. The tokens for the generic labels/notices are taken from the SYSPRO SQL data field names. You may use the SYSPRO Data Dictionary Viewer from the Utilities menu for viewing the SQL Data names.

Custom form fields can be printed using a special token format of <CFF-{TYPE}-{NAME}> where {TYPE} is the custom form field type (STK, POR, etc.) and {NAME} is the custom form field name.

Special Tokens

• QUANTITY - Quantity provided to the labels/notices
• CYMD - Date as CCYYMMDD
• FDATE - Formatted date (See Token Attributes on how to format the date)
• DATE or YMD- Date as YYMMDD
• TIME - Current time as HHMMSS (Length attribute can be used to modify)

Note: If the system can not recognize the token the word "ERROR" will be printed. If the token is a recognized SQL data name, but the system can not locate the information based on the data provided "NODATA" will be printed.

Note: If the information received from a token is not what is expected, try specifying the table name in front of the token name followed by a period, for example:

• rather than simply using the <StockCode> token, try using <JobMaster.StockCode> token (where JobMaster is the table name for StockCode)

  Stock Take Tickets

These work the same as any other label in the handheld solution.  However, they also have an option to print the tickets directly from the handheld to the printer via a bluetooth connection (in theory a direct serial connection would work also).

Place a file "StockTake.lbl" (see sample below) in the Handheld Resources folder on the server. Update the resources on the handheld and this file will be copied to the handheld. This file works similar to a label control file but there are no [] commands and it has to be in the printers control language. The number of tokens it understands is also limited.

Enable the option "Direct printing...." on the direct stock take page.

Enter the port number of the serial connection under "Local printer...." on the RF tab

After doing a direct stock take it should send a label directly to the printer.

 Samples

To see sample label control files, click here.

To see a sample email notice control file, click here.

 To see a sample stock take ticket label control file, click here.