Using Dynamics GP Report Writer with the POS Standard Receipt

Article ID: 80468

Understanding the Standard Receipt

How to customize the Retail Point of Sale standard receipt within GP Report Writer: 1) From within GP, go to Tools>Customize>Report Writer. 2) Select Retail Point of Sale from the drop down list & click OK. 3) Click the Reports button. 4) Scroll through the list on the right to select POS_StdReceipt and click Insert. 5) Highlight the report on the right side of the window, then click Open. 6) From the Report Definition window, click Layout. Understanding the Report Sections: Report Header 1) Company name 2) Company address 3) Company phone number 4) Legend #11 Header 1 This section repeats (whenever the POS Line Type changes but doesn't print if item description is blank). 1) Item Description 2) Item Number 3) Quantity 4) Unit Price 5) About Price Body Section repeats. 1) Item Number 2) POS Payment String 3) Amount Paid Footer 3 This section repeats for all the comments for markdowns or item comments. 1) Comment 1 2) Comment 2 3) Comment 3 4) Comment 4 Footer 2 This section repeats for all items printed in Header 1. 1) Markdown percent (blank if zero) 2) Text "Markdown" if markdown amount is not zero 3) Markdown amount. Footer 1 Repeats for all lines. 1) Payment number Report Footer 1) Document number 2) Bar-coded document number 3) Store Location (legend #1) 4) Workstation (legend #2) 5) Operator (legend #3) 6) Salesperson (legend #4) 7) Date (legend #5) 8) Time (legend #6) 9) Customer number (legend #12) 10) Legend #7 11) Legend #8 12) Legend #9 13) Legend #10 What are Legends? Legends are fields that contain "hard-coded" data from POS. A legend's contents might be different under certain circumstances. Here's how POS uses the legends: 1) POS Location 2) Workstation ID where it was modified (from the transaction) 3) User ID who modified (from the transaction) 4) Salesperson ID 5) Date Modified (from transaction) 6) Time Modified (from transaction) 7) POS Receipt Comment 1 8) POS Receipt Comment 2 9) Signature line 1 (if credit card, contains a line, otherwise blank). 10) Signature line 2 (if credit card, then ****** CUSTOMER SIGNATURE ******** otherwise blank.) 11) Return Title (if a return document, then ****** RETURN ***** otherwise blank.) 12) Customer number. What's in the POS Standard Receipt Table? The table is a temporary file created right before printing the receipt. It contains the following fields: User ID: user who printed the receipt. Used to restrict which receipt to print because all requests sit in table. SOP Type: document type. SOP Number: document number. Line Item Sequence: sequence number from the SOP_LINE_WORK or a sequential number we generate to keep the body lines in the correct order. POS Line Type: designates the type of data in the record, which controls where it prints. For each item purchased this will be a different numeric value (which cases header 1 to repeat for each item before the body even prints once), for all other lines = B. Item Number: Item number for each item purchased. For the subtotal line this will hold the total number of items sold; all others are blank. Quantity: Used only for the items purchased records. Unit of Measure: Used only for the items purchased records. Unit Price: Unit price of the item but blank if printing a gift receipt. Used only for the items purchased records. Markdown Percent: percent of markdown given for an item; used only for the items purchased records. Markdown Amount: markdown given for an item; used only for the items purchased records. POS Payment String: see below. Payment Number: see below (flags--MC or C would be for the previous line in the table). Amount Paid: Amount. Location ID: address ID from the POS Location Setup. Company ID: company ID. Component Sequence: Decimal Places QTY: Decimal Places Currency: Types of lines that need to print: 1) Items purchased with or without markdowns 2) Serial or Lot numbers 3) Subtotal 4) Trade Discount 5) Freight 6) Miscellaneous 7) Taxes 8) Document Amount 9) Payments (including on account, change given, & change due) Types of lines Item Number Item Description Payment String Payment Number POS Line Type Items Item Number Description MC or C or blank 0001, 0002, etc. Serial or lots Serial or lot number preceded by some text MC or C or blank Continued from above numbering Subtotal Item count “Items Subtotal” MC or C or blank B Trade Discount Trade discount percentage “Discount” Blank B Freight “Freight” Blank B Miscellaneous “Miscellaneous” Blank B Taxes Tax detail ID B Balance of taxes “Tax” B Document Amount “Total” B Payments Checks “Check” Check # B Credit Card Card name Credit card # (masked or unmasked) B Certificate “Certificate” Certificate # B On Account “On Account” B Change Given “Change Given” B Cash “Cash” B Change Due “Change Due” B

Can I configure POS to disallow a user to sell an item below the quantity available?

Article ID: 65157

Dex.ini switch

Yes, you can--but only for users that have not been granted POS Manager Access. There's a Dex.ini switch available for this. Go to your Dex.ini file (typically located at the root of your Dynamics GP folder) and add the following line:

CompassPreventOverSell=TRUE.

Adding this line will prevent a non-manager user from tabbing past the quantity field on line items where the quantity sold is greater than the quantity available.

How to establish multiple dex.ini environments in Citrix or Terminal Services environment for GP.

Article ID: 79867

Create Multiple dex.ini for users logging into a Citrix or Terminal Services environment.

1. On the Terminal Services or Citrix server create multiple dex.ini an place them in separate folders on the hard drive. 2. For each user's profile create a dynamics.exe shortcut with a target that points to their specific dex.ini. The target line in the shortcut should look something like this. C:\GP10\Dynamics.exe Dynamics.set C:\windows\dex.ini 3. When a user logs in under their profile they will use their specific shortcut to login to Dynamics GP.

Are there any Retail Point of Sale features controlled by Dex.ini settings?

Article ID: 11661

Question: Are there any Retail Point of Sale features controlled by Dex.ini settings?

Answer: Yes. The following is a list of Dex.ini switches that affect POS.

EditSalesperson=TRUE (makes the salesperson ID field editable in the Line Details window).

POSManualPromotions=TRUE (does not search for and apply promos automatically. Clerk must manually enter promotion ID).

CompassUseCustomerLookup=TRUE (the Great Plains customer lookup will open rather than the default POS mailist lookup window (new in version 8)).

CompassPreventOverSell=TRUE (Adding this line will prevent a non-POS-manager user from tabbing past the quantity field on line items where the quantity sold is greater than the quantity available).


NoPrintDialogs=TRUE (this will prohibit the print dialog from opening each time a receipt or report is submitted for printing. Stopping the print dialog expedites transaction processing, but once set, doesn't give the user a choice of where to print.)