TTX Setting Definitions

Transaction Code:

The TTX code is made up of codes found in three separate tables in the Central Table Database; Tasting Room Master (TRM), Tasting Room Transaction (TRT), and Tasting Room Transaction Category (TTC). To create a TTX code the first character is pulled from the TRM table, the second two from the TRT table and the final two from the TTC table.

Description:

The description is used when running reports that show transaction code and for reference when creating general ledger mappings. 

Sort Code:

The sort code field is ordinarily blank.  Sort codes allow you to have reports including this table in the SHOW statement to sort on that value, rather than the actual code itself.

Default Ship Location:

This is the default inventory location for this transaction code.

Default PS bill to customer number:

The default customer for retail carryout type sales (example shown in the Example TTX codes below).  For instance, you may have a single “generic customer” (see Point of Sale Customer Management manual) that represents carry-out sales to people not in your database.

Post to OE customer number:

IT IS VERY IMPORTANT TO SET THIS CORRECTLY.   This helps determine how this kind of sale posts to the General Ledger for accounting.  Mistakes here are difficult to correct.  This OE customer (set up in menu ARCSM, option CCC) supplies the Customer Financial Code used in setting up the G/L cross reference.

In addition, this is the customer that is used in AMS Sales reporting database.  There are two sets of customers here: tasting room customers (you may have tens of thousands of these), and wholesale customers (usually a lot fewer).  The Sales reporting database has to post your tasting room sales to one or more customers in the wholesale database.  Usually these are “generic” tasting-room customers.  Thus sales reports run from menu SA will show all tasting room sales as being to this customer.  Sales reports run from menu PSRPM will use your tasting room customers.

Carryout/Ship

This flag determines if this transaction code will be a Carry out or Ship Sale.

OE Post to Customer Number Source

A single transaction cannot be both. However, there can be several different kinds of transactions in one sale.  (For instance, a customer may carry out a bottle of wine and ask for a case to be shipped to his home. This would be one sale with two different transactions.)

• If this flag is “T”, then any OE customer attached to a tasting room customer is ignored, and the OE customer attached to the transaction is always used.
• If it is “C”, then the OE customer attached to the transaction is ignored, and the OE customer attached to the tasting room customer is always used. (OE customer is optional on tasting room customers.  If you have a transaction that requires an OE customer on a tasting room customer, and try to make a sale with that transaction using a tasting room customer without an OE customer, the register will indicate that it is not allowed.)
• If this flag is blank, then the OE customer from the tasting room customer will be used if it exists, otherwise the OE customer from the transaction code will be used.

Require clerk information input

Often used to prompt the clerk to enter the name of the recipient of a no-charge, or the reason for a return.

Clerk information prompt/rpt desc

This is used in conjunction with the above setting. The left field is what the cash register program will use to prompt the sales clerk for a reason, the right is what will appear on reports to the left of whatever the clerk enters.  This might be the reason for a return, or the recipient of a sample.

Inventory transaction code

All movements of inventory (sales, returns, receives, etc.) have an associated inventory transaction code.  These are set up in central table Inventory Transaction Code Table (ITC).

Sales type Code

Sales types are used for reporting purposes.  For instance, you may want different sales types for each kind of no-charge you support.  Sales types are set up in central table SAT.

Notify if not in batch

Usually used to remind clerks to enter pours at the end of the day.  If this flag is “Y”, the clerk will be notified when “cashing out” the register if transactions of this type were not included in the batch.

Futures only

Y/N flag - Futures must have their own unique transaction codes, as they are accounted for differently.

Require Event Code

Event codes are defined in table Event Code (TRE).

Ship date entry mode

Shipment orders require entry of a ship-date. 

• If this flag is “T”, then today’s date (current date of sale) is filled in automatically (it can be overridden). 
• If it is “E”, then the clerk will be prompted to enter the date for each such transaction. 
• If it is “R”, the clerk will be prompted for the first such transaction in a batch, and the register will “R”epeat that date in subsequent such transactions (again, it can be overridden).  Quick-ship transactions always use the current batch date for ship date.
  

Override shipping code

Shipping codes (which include calculation of shipping charges). When a shipment transaction is entered, the shipping code will be filled in from the customer, unless an override is entered here. In either case, the clerk can manually override at the time the order is entered.

Allow 'quick' shipping

If this flag is “Y”, inventory is relieved in the system as soon as a sale is completed (using the current batch date as ship date).  In this case, no further steps are required to complete inventory update.  Alternatively, if you leave this flag blank, you can leave orders unshipped after tendering.  In either case, you can later print packing documents, create export files for UPS, etc.  See Point of Sale Shipping manual for details

Inactive Flag

If this trans code is no longer in use and you want to avoid clerks from accessing it you will mark it inactive. Please do not ever delete a code that has been used, this can cause posting errors to the GL and reporting errors that cannot be fixed without adding the code back.

Force on-hand check for products

There are 3 levels of inventory checking. First is the PS Tasting Room Master (TRM), if this is set to YES it overrides all other checks and inventory WILL always be checked on Point Of Sale Transactions. If the TRM is set to NO, the next check is this flag. This flag pertains to inventory checking of the location defined above as "default ship location". If this flag is set to "Y" then all transactions that use this TTX code WILL check inventory. If this flag is set to "N" then inventory stock checking will be bypassed and you can run the risk of overselling product.

Return transaction type/cat codes

In the PS system when the "RETURN" button is used on an order, it will do a reversal of the product and dollars, BUT it will bring the goods back in based on the defaults indicated here.

On-site Sale?

When the default is Y = On-Site Sale. An On-site transaction code is used when the customer is physically in your tasting room making the purchase. Transaction codes flagged as CARRY OUT should be considered On-Site. The default when left blank is “N” (not ON-site, therefore, considered an OFF-site sale). These are your wine club orders, web orders, and mail/phone/fax orders. The customer is not at your facility when placing the order. You can also have a S=Ship order marked as on-site for those guests who are in your tasting room but shipping wine home.

One line persistence

This should be turned on when this TTX code should not be automatically used for subsequent lines, and the touchscreen should go back to the defined default TTX code for that register after an item is entered. Default TTX codes for registers are set on the Maintain Register Master File (MRM).

Reservations only

Only to be used in conjunction with Event Management and Reservations System (EVM).

Print to Aux Printer

Typically set BLANK or N to use a regular receipt printer. If anything else is needed please contact the AMS Helpdesk.