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.109.0 - 1.109.0
Control
Features & Enhancements
Serial | Dev ID | Idea Tracker | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 17019 | BO-I-48 | BO-I-48 New price type Basic Rate(Last Purchase Rate) introduced for Procurement work-flowModule: Procurement - Goods Receive Challan Enhancement Summary: Earlier our users were facing a particular issue for Adhoc returns. The return value of item was becoming greater than the transactional rate due to charge calculations. Now, a new price type has been introduced - Basic Rate (Last Purchase Rate) - which is the last transactional rate with charges excluded. If the calculation of the rate at which the item must be returned is based on the new price type Basic Rate (Last Purchase Rate); then all the applicable charge calculations will be based on Basic Rate only. This will provide more clarity and resolve anomalies like return rate being greater than the purchase rate. Scenario: Scenario in previous versions Suppose, Item's Transactional Rate (Basic Rate) - 100.00 Now suppose, if Item needs to be returned on ADHOC basis considering Effective Rate, following calculation takes place: So in this scenario, when Item is purchased in Rs. 102.60 but is returned 115.53, it is not unacceptable by the suppliers. Scenario in current version Now, Item’s Transactional Rate (Basic Rate) - 100.00 [Basic Rate (Last Purchase Rate)] will be used for adhoc returns and all calculations will be based on it. So returns can be done at the Last Purchased Rate. | ||||||||
2 | 15507 | GIN-I-541 | GIN-I-541 Price List's assortment resolution has been changedModule: Sales & Distribution - Setup - Price List Enhancement Summary: The resolution logic of Price list assortment order has been changed. Earlier, if an Item used to belong to two different assortments, the first assortment (in definition order) was getting considered for calculating the price. But now the second assortment will be considered. IMPORTANT Note: The lastly defined assortment will be considered in case of Item belonging to more than 2 assortments. Scenario: Suppose there is a price list’s assortments are defined in the following way: Earlier, if the Item was a shirt of “Solid” category1 as well, the factor was considered as 10% but now it will be considered as 15%. | ||||||||
3 | 17016 | GIN-I-775 | GIN-I-775 Item’s vendor applicability in Goods Return wizard has been enhancedModule: Procurement - Goods Return - Goods Return (Wizard) Enhancement Summary: Item population in the GRT Wizard for a particular vendor was happening based on GRC made against the last supplier from whom the item was procured irrespective of the connected site. Now, the changed logic has been changed as follows: Scenario: Case 1 | ||||||||
4 | 16939 | GIN-I-225 | GIN-I-225 Packet Item reconciliation goods receive method in POS has become policy drivenModule: Retail Management - Setup - Manage - Master Policy Enhancement Summary: Currently, there are two different processes to receive goods in POS stores: (1) Packet reconciliation (2) Packet Item reconciliation. But often, while booking Goods Receive in the system, the store users follow the 'Packet Reconciliation' process as a faster option. In 'Packet reconciliation' process, the entire 'Send Quantity' is converted to 'Received Quantity'. As a result, even if there is an actual shortage of packet items in the cartons, the GRC still gets updated with complete send quantity as received quantity, since item wise reconciliation is not performed while receiving. A new policy has been added for the POS users, where the user can be given the privilege of receiving goods through packet reconciliation. If the policy has not been implemented, on a default basis, each item in the packet will have to be individually reconciled to ensure whether there are any short or excess items in the packets. The policy is called, 'Allow packet reconciliation in Goods Receive'. IMPORTANT Note: If the privilege is not given to the POS site user, they have to use the Goods Receive form to scan items individually. Scenario: N.A. | ||||||||
5 | 17013 | GIN-I-250 | GIN-I-250 Options like Copy/Search/Sort assortment are now available in Price ListModule: Sales & Distribution - Setup - Price List Enhancement Summary: The former ‘Copy Assortment’ button has now become ‘Copy Selected Assortment’ button and ‘Copy Assortment from another Price List’ has been provided to copy selected assortments and tag to a price list. This enables faster and more efficient implementation of multiple price lists with similar assortments for different suppliers or customers. This functionality is only available in new price list creation mode. All the fields in Price List have been made searchable and sort-able; enabling right click Search-Sort option for all columns of assortment details block in a Price List has made it easier to find any assortment from a pool of assortment for a price List with high volume of assortments defined. Scenario: N.A. | ||||||||
6 | 14707 | BO-I-42 | BO-I-42 Ledger tagging option is now available in Tax Slab levelModule: Procurement - Invoicing - Purchase Invoice Enhancement Summary: Now there is an option of defining ledgers and sub-ledgers of Procurement (Purchase Ledger & Purchase Sub-ledger) and Sales and Distribution (Sales Ledger & Sales Sub-ledger) in the Tax slab definition. At the time of financial posting from the aforesaid transactions, the ledger shall be picked up from the slab level (if defined). If not defined at slab level, then the base ledgers shall be considered. Scenario: N.A. | ||||||||
7 | 16998 | GIN-I-451; GIN-I-662 | GIN-I-451; GIN-I-662 Some of the fields have been made mandatory in Customer/Supplier master and rupee has been made the default currencyModule: Sales & Distribution - Setup - Customer Enhancement Summary: 1. Some more fields have been made mandatory in defining customers and suppliers to ensure ethical practices in future and smoother operations for our users. Both the new and existing mandatory fields are the most useful information without which no business operation with the Customers or Suppliers can be executed. Following are the new fields which are made mandatory: 2. Another important change is “Rupees” will now be the Default currency for both new and existing parties but will be subject to manual modification by user. It will reduce our user's effort as most of our business belongs to India and it will also give calculative advantage. IMPORTANT Notes: Scenario: N.A. | ||||||||
8 | 14229 | GIN-I-315 | GIN-I-315 System will automatically restrict tax reversal after certain days as provided in Tax RegionModule: Inventory - Product Definition - Tax Definition - Tax Region Enhancement Summary: At the time of sales/purchase return, in some cases, the law does not allow reversal of tax amount after a pre-determined number of days. In other words, as per norms setup by Government, if sold items are returned the beyond time limit set for the tax region, then government would not return the tax amount charged at the time of invoice creation. The return period validity for tax calculation will now be based as per the tax region master and then would be applicable for PRDN (Purchase Return Debit Note) and Sales Return for Outright sales. IMPORTANT Notes: Scenario:
| ||||||||
9 | 17206 | GIN-I-714 | GIN-I-714 Purchase order’s “valid to” will now get updated as per Item’s due dateModule: Procurement - Order Management - Purchase Order Enhancement Summary: Although PO validity date is still being calculated from Supplier Master Due Date field; now, the PO “Valid to” will first take into account Item level validity. In other words, item validity gains precedence over Supplier Master due date value. However, still if the user wants to extend the validity of PO, he can manually change it. IMPORTANT Note: In case the Item validity date is not provided, then the PO “Valid to” remains unchanged. Scenario: Suppose there are 3 items scanned in the PO and the longest validity assigned to one of the items is 7 days; then the PO validity would be of 7 days, regardless of the value of the due date in Supplier Master. Similarly, if the Supplier Master Due Date is 15 days and items’ validity is greater than that, then the validity of the PO will be the maximum possible validity of the items. | ||||||||
10 | 17025 | BO-I-28 | BO-I-28 Balance can now be transferred even with unposted documents of last yearModule: Admin - Organization Hierarchy - Close Book Enhancement Summary: Earlier, ledger balances could not be transferred until following conditions had been met: • All documents had been posted Transfer balance is now allowed even with unposted documents but with confirmation from user, i.e., if any unposted record is found, user is asked for confirmation and when confirmed, only then transferring balance is allowed. Only posted balance is considered for transfer. The Profit & Loss account balance is updated as per the posted records itself, i.e., unposted balance will not be considered. Also, an option has been provided in transfer balance form for viewing unposted documents. In Trial balance and balance sheet, user is shown a difference message in bold red if the last year isn’t closed yet. IMPORTANT Note: User will not be allowed to Close Books with un-posted records and neither can he transfer the balance in presence of documents pending invoice. Scenario: N.A. | ||||||||
11 | 17480 | GIN-I-281 | GIN-I-281 Working Plan will now automatically include component items needed to be produced separately as per Assembly BOMModule: Production - Working Plan Enhancement Summary: Now if a semi finished goods is part of the BOM of a finished goods then the semi finished item will be considered as a component item of the assembly item and its production will be processed accordingly. If a dress set includes a scarf (individual SKU and it has a BOM defined), and the scarf is a component item of the dress set; then the scarf will be auto processed as part of the BOM of the dress set. IMPORTANT Note: The following conditions must be fulfilled for the above features to work: 1. The semi finished goods must be an individual SKU. Scenario: N.A. | ||||||||
12 | 17020 | GIN-I-519 | GIN-I-519 Default Population of Short/Excess Quantity has been restricted in Transfer In (Against Transfer Out)Module: Sales & Distribution - Consignment - Transfer In (Against Transfer Out) Enhancement Summary: Automatic population of Short/Excess Quantity during creation of Transfer In (Against Transfer Out) has been restricted now. Now it will only be populated if there is an actual shortage or excess during the receiving of items. The receive items column now has to be explicitly entered even if the received quantity for some item is zero (0). The Short/Excess field will be updated with the difference of the Send Quantity and Receive Quantity. Scenario: N.A. | ||||||||
13 | 11917 | N.A. | 11917 Quick scan (F7) option provided in Stock Entry formModule: Inventory - Stock Audit - Stock Entry Enhancement Summary: A quick scan option has been provided in Stock Entry form which can be activated by pressing F7 allowing users to enter the quantity right at the time of scanning the items. Scenario: N.A. | ||||||||
14 | 16915 | N.A. | 16915 Goods Forwarding Note now shows the 'Excise Registration No.'Module: Inventory - Logistics - Outgoing - Goods Forwarding Note Enhancement Summary: Now if the Excise Registration No. is provided in the Customer / Supplier master then it will be displayed in the Goods Forwarding Note report. Scenario: N.A. | ||||||||
15 | 17002 | GIN-I-759 | GIN-I-759 Selected Site’s filter added for Sales Return Adjust windowModule: Sales & Distribution - Outright - Sales Return Enhancement Summary: In the Adjustment window of the Sales Return form; F2 button will now display all Pending Documents of the site from which the Sales Return is being made - i.e. the Pending Documents list for the selected site. The F3 button has been assigned the former function of the F2 button - i.e. it will show the Pending Documents list for all sites. IMPORTANT Note: F4 button is still assigned its former role of listing Pending Documents grouped site-wise. Scenario: N.A. | ||||||||
16 | 16938 | OFFPOS-I-19 | OFFPOS-I-19 Web search for customer has been made default in POSModule: POS - Normal POS Enhancement Summary: Sometimes during rush hours it becomes tough for cashiers to check for the existence of customers in the Web. In such instances often duplicate customer entries get created. Now, the Web search for customers, not available in the local database, will become automatic. The Search in Web checkbox will be checked by default and even if the reset button is clicked. IMPORTANT Note: The checkbox can be unchecked for a “local database only” search. Scenario: N.A. | ||||||||
17 | 16333 | GIN-I-263 | GIN-I-263 Automated mailer report for 'Transfer Out' invoice is now availableModule: GINESYS Launchpad - Mail Notification Enhancement Summary: Now Transfer Out Invoice related Mail Notification can be configured in GINESYS. It will be issued once the Transfer Out is “posted”, from - Please call GINESYS Helpdesk for assistance in configuration of the above mail. Scenario: N.A. | ||||||||
18 | 17207 | N.A. | 17207 Delivery Challan Register report has been improved with more visual clarity and sorting options includedModule: Sales and Distribution - Registers - Delivery Challan Register Enhancement Summary: In the Delivery Challan, some improvements have been made which are listed below. 1. Delivery Challan number which was being displayed was not getting printed completely - The width of the field has been increased to handle the issue. Scenario: N.A. | ||||||||
19 | 16332 | GIN-I-709 | GIN-I-709 User and system details of POS Settlement in HO will now be available in reportModule: GINESYS Launchpad - POS Settlement Enhancement Summary: Now GINESYS can store and reflect in OLAP report the 'settlement date/time' and 'user information' of the user by whom settlement of POS store data in HO was done. IMPORTANT Note: The above information will be reflected in only OLAP cube for “POS Settlement Status”. Scenario: N.A. |
Bug Fixes
Serial | Dev ID | Issue Tracker | Description |
|---|---|---|---|
1 | 17270 | N.A. | 17270 Warehouse could not be tagged as replenishment source in Retail ManagementModule: GINESYS Web - Retail Management - Setup - Manage - Site - Replenishment Source Reported Version: 11.105.0 Scenario:
|
2 | 17119 | N.A. | 17119 Import Excel of GINESYS Web was generating error when opened in Internet ExplorerModule: GINESYS - Web - Admin - Data Import Reported Version: 11.108.0 Scenario:
|
3 | 16798 | N.A. | 16798 Modification of stock audit plans by HO was removing the plans from POS on sync of the modified plansModule: GINESYS Web - Retail Management – Operations – Process - Stock Audit Plans POS – Back Office – Physical Stock Audit – Audit Plan Reported Version: 11.107.0 Scenario:
|
4 | 17588 | N.A. | 17588 Site to site Goods Return Document was being revertedModule: |