We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
Release Notes 11.104.0 - 1.104.0
Control
Release Date |
|
HO Version | 11.104.0 |
POS Version | 1.104.0 |
Web Database Compatibility Version | 1.3.0 |
Features & Enhancements | 19 |
Bug Fixes | 14 |
Navigation |
Features & Enhancements
Serial | Description |
---|---|
1 | Promotion Sample Testing has been migrated to GINESYS WebModule: GINESYS Web - Retail Management - Promotion - Manage - Sample Testing Enhancement Summary: The sample testing utility for testing promotions would now be available in web. The function of sample testing has been enhanced. The previous logic of promotion resolution has been changed and promotion is now being resolved as per the latest promotions available in POS. Note: Only Item level promotions gets resolved in this testing module. Scenario: N.A. |
2 | Successive resolution of promotions on an Item based on priorityModule: POS - Normal POS Enhancement Summary: GINESYS is now providing an option to apply multiple promotions on a single item successively based upon its priority. Previously, if a promotional item was scanned in a POS bill, depending upon the condition for promotion applicability, only the promotion with highest priority was resolved. Now since the concept of successive resolution of multiple promotions has been introduced, the promotions would be applied in a cyclic order depending upon its priority. That means after the promotion with highest priority is resolved, promotion with second highest priority will be applied on remaining item qty. Hence, single barcode/item will resolve multiple promotions simultaneously but single quantity of an item will be considered in one promotion only. Scenario: Suppose there are two assortments -
Promotions running currently, from priority high to low -
Items scanned in the POS bill are -
Since promotion P1 has higher priority, it would be resolved first on item I1001, out of 3 qty of I1001, 2 qty of I001 would be clubbed and 50% discount would be applied. Next, promotion P2 which is in lower priority would be applied on the remaining 1 qty of I1001 & I1003, flat 10% promotional discount would be applied. Note: The web version of Sample Testing is also compatible with this feature. |
3 | Multi buy assortments can now be provided in Promotion definitionModule: Retail - Sales Promotion - Define Promos Enhancement Summary: GINESYS has enhanced the assortment selection process in promotion definition. Along with the presently available option where only single BUY type assortment can be provided, the new enhancement would enable users to provide multiple BUY type assortments while defining a promotion. This enhancement has been made available for the following promotion types:
Scenario: Previously, if suppose 2 assortments were required as buy assortment of a promotion, the operator had to first create a new assortment copying both existing assortments and then use it as buy assortment in the promotion definition. With this release, now multiple assortments will be allowed in buy condition and system will automatically consider it as a single assortment/buy condition. Note: The web version of Sample Testing is also compatible with this feature. |
4 | Promotion definition of BUY assortments with ratio of item quantity is now availableModule: Retail - Sales Promotion - Define Promos Enhancement Summary: The concept of ‘Item ratio’ wise promotion is yet another new promotion type that is highly popular in the retail industry. This unique promotion type is only available in the Item Level Quantity Based Simple Benefit promotion. With the two existing BUY condition, ‘Item Ratio’ has been added as the third type of BUY condition. Using this BUY condition, users can define such promotions where on purchase of 1 item from T-Shirts assortment, 1 item from Denim assortment and 1 item from Formal Shirt assortment, the customer would get a flat discount%. Scenario: Suppose there are 3 BUY type assortments tagged to a single promotion -
Promotion defined - Buy any 1 quantity from assortment A, 1 quantity from assortment B and 1 quantity from assortment C and GET 50% FLAT Discount on the bought items.
When promotion is resolved on pressing F8 in POS Bill window, software would resolve 1 unit each from assortments A, B and C (T1001, T1004 and T1005) and get 50% Flat Discount on all the three items. And 1 unit of T1001 will be billed at MRP. Note: The web version of Sample Testing is also compatible with this feature. |
5 | Expired PO information can now be viewed while creating GRC from wizardModule: Procurement - Goods Receive Challan (Wizard) Enhancement Summary: Previously, at the time of creating GRC from GRC wizard module, there was no option to check if the item is available in pending expired PO. Same information will now be available to the operator. While creating GRC, once the items have been scanned, items which are available only in pending expired PO will be reflected with an asterisk mark beside. Along with this GINESYS is also providing an option to view details of all the pending expired PO Item wise. Operator will be able to view details and also will be able to export the information in CSV format. Note: Expiry will be considered only after adding buffer days to the expiry date. Scenario: Suppose GRC is to be created with item I001 for 20 qty. The same item is available in valid PO for 5 qty., and 10 quantity of same item is pending to be received in an expired PO. The item will be marked as “having pending expired PO” and the details of the order will also be shown there. This will help the operator to ask the higher authority to update the expired order’s validity if required so that set-off can be done. |
6 | Service Order Cancellation module has now been introducedModule: Procurement - Order Management - Cancel Service Order Enhancement Summary: Presently, service order can be cancelled using service order form itself, by providing cancelled quantity/amount. In order to do the cancellation operator was also getting privilege to do any other modifications in the document. In order to enhance the security, separate cancellation module has been provided. Scenario: Suppose a service order was created on 10-Nov-15 and user lock days specified for a user is 2 days, then on 15-Nov-15 operator was not allowed to cancel that service order. For cancelling that order user lock days had to be increased to 6 days. With the addition of new Service Order cancellation module, the operator will be allowed to cancel those orders without the need of extension of user lock days. |
7 | POS Order Cancellation reason option has been introducedModule: Retail Management - Setup - Reason Enhancement Summary: POS Order cancellation reason can now be defined at HO, and the same can be tagged in POS Order at the time of cancellation. A new user policy has been introduced using which the cancellation reason tagging at the time of POS Order cancellation can be made optional or mandatory. Note: Remarks is different. Reason and remarks will remain independent. Scenario: During the peak sale time, operator is unable to enter appropriate reason to cancel the POS order. GINESYS has now provided an option to create a master for POS cancellation reasons. Operator can now select reason for order cancellation from the master. And along with this, reason for order cancellation is important for reporting and analysis purpose. Entering of order cancellation reason can now be made mandatory, operator will be restricted to save the document without doing so. |
8 | Item rate can now be modified while creating POS orders.Module: POS - Back Office - Transactions - POS Order Enhancement Summary: Previously, there was no option to modify the rate of item in POS Order. The same has now been provided. If price modification is allowed in item master for the item and if “Allow price overwrite” policy is ticked in the policy, the operator would be able to modify item rate in POS Order. Scenario: N.A. |
9 | All Transfer transaction dates will now be reflected in register reports.Module: Sales & Distribution - Consignment - Register - Transfer Out Register Enhancement Summary: GINESYS has now provided an option to check receive date of all the transactions made to its various stores across multiple cities. And along with this, date on which returns were made from the stores will also be reflected. Previously, there was no option to view this data. Scenario: Suppose transfer out was created on 15th February, 2016 and the same was received at store on 20th February, 2016. The receive date will now be reflected in transfer out register report. Similarly, date on which goods return was done from store will be reflected in transfer in register report. |
10 | Modification of PTC records now allowed till day is settledModule: POS - Back Office - Transactions - Petty Cash Enhancement Summary: Previously, only reference details and remarks could be modified after Petty cash creation. Operator will now be able to modify other information like, petty cash head, petty cash type and amount but it will be allowed until the day is settled. Scenario: Suppose by mistake at the time of creating a petty cash document, operator selected wrong petty cash head or entered an extra number while entering amount. Previously there was not option to rectify this mistake, the same information can now be modified. |
11 | Head wise summary of PTC provided in daily summary reportModule: POS - Back Office - Report - Daily Summary - Petty Cash Bill Enhancement Summary: Previously, only transaction wise details of PTC were provided. Now, along with transaction details petty cash head wise summary will also be provided in daily summary report. Scenario: In daily summary, petty cash transactions are reflected, but there was no way to check summarized detail of the same. Operator will now be able to check total payment and receipts made against each head. |
12 | Sub-ledger details are now reflected in Cost Center register reportModule: Finance - Register - Cost Center Enhancement Summary: Previously, sub-ledger details were not reflected in Cost Center register report. GINESYS has now provided an option to view sub-ledger details in cost center register report. Along with this sub-ledger filter option has also been provided. Operator will now be able to view report for certain selected sub-ledgers only, if required. Scenario: N.A. |
13 | Authorization date time and authorizer’s name will be reflected in Order documents from Procurement and Sales & Distribution upon retrieval.Module: Procurement - Order Management - Purchase Order Enhancement Summary: As and when aforesaid documents will be authorized, authorization date time will be reflected on retrieval of the document along with the authorizer’s name. Scenario: N.A. |
14 | Destination site selection now available in Sales & Distribution documentsModule: Sales & Distribution - Order Management - Order Analysis - Pending Order Status Enhancement Summary: Previously destination site selection option was not available, the same has now been provided. Operator will now be able to filter report data on the basis of selected site. Scenario: N.A. |
15 | Option to filter report data on the basis of state now availableModule: Sales & Distribution - Consignment - Register - Transfer Out Register Enhancement Summary: Previously, there was no option to filter report data on the basis of state. State filter has now been provided. Operator will now be able to view details of one state at a time. Scenario: N.A. |
16 | Tax summary can now be printed in goods return document reportModule: POS - Back Office - Transactions - Goods Return Enhancement Summary: Previously, tax summary could not be printed in goods return document report. Tax name wise Tax summary can now be printed in the Goods Return Document report. Scenario: N.A. |
17 | Due date tagging can now be made mandatory using profile settingModule: POS - Back Office - Transactions - POS Order Enhancement Summary: Previously due date tagging was optional, the same can now be made mandatory using profile setting. Operator will not be allowed to save the POS order without tagging due date. Scenario: N.A. |
18 | System will now reflect multiple item information as last scan informationModule: POS - Back Office - Transactions - Packets Enhancement Summary: Previously, while scanning an item, only item name was reflected as last scan information. Along with item name, system will now reflect information like "Barcode", "ItemId", "MRP" and "RSP" as last scan information. Scenario: N.A. |
19 | Customer details, coupon details and redemption details can now be printed in the POS BillModule: POS - Normal POS Enhancement Summary: Customer details, coupon details and redemption details can now be printed while printing a POS bill document. IMPORTANT Note: Applicable only for Capillary Scenario: N.A. |
Bug Fixes
Serial | Description |
---|---|
1 | Delivery challan was getting saved even when no item was selectedModule: Sales & Distribution - Delivery - Delivery Challan(Adhoc) Reported Version: 11.103.0 Scenario: N.A. |
2 | An error was getting generated when same item was tagged with multiple pricesModule: Sales & Distribution - Delivery - Delivery Challan (Against Order) Reported Version: 11.103.0 Scenario: N.A. |
3 | At the time of providing Cash Discount for a document, adjustment amount was not getting rounded offModule: Finance - Voucher - AP Voucher Reported Version: 11.103.0 Scenario: N.A. |
4 | At some cases, modifications made to an item was not getting saved in the item modification logModule: Inventory - Item Definition - Modify/Manage Item Reported Version: 11.103.0 Scenario: N.A. |
5 | At the time of recalculation of charges, an error was getting generatedModule: Procurement - Order Management - Purchase Order Reported Version: 11.103.0 Scenario: N.A. |
6 | At some cases, return document of store was not getting tagged in transfer In documentModule: Sales & Distribution - Consignment - Transfer In (Against Transfer Out) Reported Version: 11.103.0 Scenario: N.A. |
7 | When Purchase Invoice or Purchase Return Debit Note is created automatically from GRC/GRT document, taxable charges were not getting calculatedModule: Procurement - Invoicing - Purchase Invoice Reported Version: 11.103.0 Scenario: N.A. |
8 | At some cases, Petty Cash summary was not being reflected in Settlement Summary ReportModule: POS - Back Office - Reports - Settlement Summary Reported Version: 11.103.0 Scenario: N.A. |
9 | Item Set was getting deleted even when the same was tagged in a purchase OrderModule: Inventory - Item Definition - Item Sets Reported Version: 11.103.0 Scenario: N.A. |
10 | Supplier Alias was not getting updated with change in Supplier name using global change optionModule: Inventory - Item Definition - Modify/Manage Item Reported Version: 11.103.0 Scenario: N.A. |
11 | At some cases, “Finish” button was getting enabled even when stock update has not been completedModule: Inventory - Stock Audit - Verify/Update stock Reported Version: 11.103.0 Scenario: N.A. |
12 | Previously, there was no option to provide item remarks while creating or modifying items using import excel optionModule: Inventory - Item Definition - Item Creation Reported Version: 11.103.0 Scenario: N.A. |
13 | Previously, on receiving of changes made in the policy (site or master), the role policy settings were getting removed in case of ‘Centralized user management’Module: POS - Data Sync Reported Version: 11.103.0 Scenario: N.A. |
14 | In some cases, while downloading Items using Item Download option, items were not getting searched due to case sensitivity issueModule: POS - Normal POS Reported Version: 11.103.0 Scenario: N.A. |