Back Office >Reports > Custom Batch Report Scripts
Description
This feature provides the opportunity to create Custom Batch Report Scripts in the form of SQL Stored Procedures (.SQL). Once created, or provided by SwiftPOS, these can then be executed using Microsoft SQL Server Management Studio. Once executed they will appear as one of the Custom Batch Report Scripts in the Reports menu in SwiftPOS Back Office.
To Be Considered
- Note : There is no FREE support or assistance available for those customers that choose to develop their own Custom Batch Report Scripts.
Custom Development of Gadgets. Any reports developed would need to be tested against a 10G database to make sure they do not effect performance of SwiftPOS. Any support work created are a result of third party development would also be chargeable. - All Custom Batch Report Scripts created must be named with the prefix "BR_".
- All Custom Batch Report Scripts must NOT include a . in the name of the Stored Procedure.
- The Custom Batch Report Scripts can take full advantage of the Report Filter screen as long as the user names the Parameters in the stored procedure correctly. For example, @FROMDATE.
- When creating Stored Procedures (scripts) to generate Custom Batch Report Scripts, it is important to use the WITH(NOLOCK) argument on each Table in the FROM section of the Stored Procedure (.SQL). This is recommended to ensure that Tables used are not locked while the Stored Procedure (.SQL) is executing. This will avoid a deadlock situation from occurring and thus have no adverse impacts on the day to day operations of the site while the Stored Procedure (.SQL) is executing.
- If required. feel free to contact SwiftPOS for a quote to cover the consulting and development of Custom Batch Report Scripts.
Setup
- For Stored Procedure (.SQL) files provided by SwiftPOS to generate a Custom Batch Report Script, follow the steps below:
- Unzip the Stored Procedure (.SQL) to a directory on your PC.
- Double click the Stored Procedure (.SQL). This should open Microsoft SQL Server Management Studio.
- In Microsoft SQL Server Management Studio ensure the correct database is selected and a connection established. This should be the database (eg. SwiftPOS) against which the Stored Procedure (.SQL) is to be executed.
- Click the ???! Execute??? button to execute the Stored Procedure (.SQL). This will add it to the selected database.
- Ensure that the new custom batch report permission is set in Back Office>Clerks>Clerk Security Groups>Clerk Group Reports> Custom Batch Report Scripts.
- In SwiftPOS Back Office > Administration > Batch Reports - Select the New button to open the Batch Report Full Edit screen.
- Select the Select Report button to open the Reports screen below and expand the Custom Batch Report Scripts menu item. This should list all BR_ prefixed Custom Batch Report Scripts created as Stored Procedures (scripts).
- Select the Custom Batch Report Script created above and then select the Select button in the bottom left hand corner of the Reports screen.
- Back in the Batch Report Full Edit screen specify the Report Frequency, Destination and File Properties.
- Select Save to save the Batch Report Settings.
- Select Run Now to test. If File was selected as the Destination, then the file created can be found in the path specified in the Batch Report Full Edit screen.
Reports
|
Custom Batch Report Scripts
Report Name |
ID |
Sample |
Description |
SQL002 |
Exports Cash Draw Declarations. Exports Location, Terminal, Reconcile From/To Dates, Media , Expected Value, Counted Value ,Variance, Drawer, Clerk, Clerk Name , Clerk Media Expected. |
||
SQL003 |
Exports sales Data (excluding Rounding). |
||
SQL004 |
Exports Event Session sales related data. |
||
SQL005 |
|
To be continued ... |
|
SQL006 |
|
Exports Data for Flow Control liquor reporting. |
|
SQL007 |
Exports sales Data specific for Fuel sites. |
||
SQL008 |
Exports sales Data. Exports Transaction #, Terminal, Location, Receipt Date/Time, Product, Product Group, Default Price, Cost, Price Level, Qty sold, Tax, Sales Value and Member. |
||
SQL009 |
Exports Discount Summary information per Location. |
||
SQL010 |
|
To be continued ... |
|
SQL011 |
|
Reports on Member Fees by Linked Classifications |
|
SQL012 |
|
Data export for My Local Foodie |
|
SQL013 |
Exports Member data for those Members whose Membership has not expired. Lists the Member Join date, Surname, First Name and Member Number. |
||
SQL014 |
Exports Product data for MyFoodLink by Location. |
||
SQL015 |
Export sales related data grouped by Location and then Product Group. Lists the Location, Product Group, Qty sold, Sales amount, Sales Exc amount, Cost, Tax, GP Value and GP Percent. |
||
SQL016 |
|
To be continued ... |
|
SQL017 |
|
To be continued ... |
|
SQL018 |
|
To be continued ... |
|
SQL019 |
Exports Product data. Exports PLU as PLU_Number, Product Code as Inventory_Code, Product as Description, Case Qty as StockSize, Category ID as Dept#, Category as Department, Product Group ID as Group #, Product Group as Group, Master Group ID as Master Group #, Master Group, Supplier ID as Supplier #, Supplier Name, Manufacturer Name. |
||
SQL020 |
|
To be continued ... |
|
SQL021 |
|
To be continued ... |
|
SQL022 |
Exports sales data. Exports Transaction Date, Location, Department, Shift, Forecast Sales, Actual Sales, Actual Sales Ex. |
||
SQL023 |
Exports sales data. |
||
SQL024 |
Exports Stock on Hand (SOH) information by Bin number. Exports Product Code, PLU, Bin #, SOH, Qty, Order and Picked. Note : The Location(s) selected must be a Warehouse type Location. |
||
SQL025 |
Exports Product data. Note : The export file generated will need to be named Products.csv in order for it to be processed by Summit. This also, applies to when it is included as a Batch Report. Be sure to give it the Products.csv name here as well. |
||
SQL026 |
Exports Location data. Note : The export file generated will need to be named Stores.csv in order for it to be processed by Summit. This also, applies to when it is included as a Batch Report. Be sure to give it the Stores.csv name here as well. |
||
SQL027 |
Exports Transaction data. Note : The export file generated will need to be named Transactions.csv in order for it to be processed by Summit. This also, applies to when it is included as a Batch Report. Be sure to give it the Transactions.csv name here as well. |
||
SQL028 |
|
To be continued ... |
|
SQL029 |
Exports Supplier Rebate related data. Note : The DISC column will be populated with the Rebate Description. |
Commonly Used Parameters
@FromDate DATETIME
@ToDate DATETIME
@FromMember INT
@ToMember INT
@FromType SMALLINT
@ToType SMALLINT
@FromClerk INT
@ToClerk INT
@FromClerkGroup INT
@ToClerkGroup INT
@FromTerminal INT
@ToTerminal INT
@FromReceipt INT
@ToReceipt INT
@FromTable INT
@ToTable INT
@FromMedia INT
@ToMedia INT
@FromLocation INT
@ToLocation INT
@LocationGroup NVARCHAR(100)
@LocFilter1 NVARCHAR(1)
@LocFilter2 NVARCHAR(1)
@LocFilter3 NVARCHAR(1)
@LocFilter4 NVARCHAR(1)
@ProductFamily INT
@ProductFilter NVARCHAR(16)
@MasterGroups INT
@FromMasterGroup SMALLINT
@ToMasterGroup SMALLINT
@FromGroup REAL
@ToGroup REAL
@FromCategory SMALLINT
@ToCategory SMALLINT
@FromPLU INT
@ToPLU INT
@FromProduct NVARCHAR(13)
@ToProduct NVARCHAR(13)
@FromSupplier NVARCHAR(10)
@ToSupplier NVARCHAR(10)
@Discontinued INT
@NilInventory INT
@Inactive INT
@ShowSalesInc INT
@ShowStockAsCasesUnits INT
@ShowDetail INT
Related Topics