Release Notes 11.137.0 - 1.137.0


Control

Release Date

3 May, 2018

HO Version11.137.0
POS Version1.137.0
Web Database Compatibility Version1.12
Features & Enhancements18
Bug Fixes03
Navigation


Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
138829 BO-I-47

38829 Auto Posting of Store Settlement data at Head-office

Module:

Ginesys Launchpad - POS Settlement

Enhancement Summary:

The following features have been enabled for settlement of POS data at HO - 

  • Automatic reflection of settlement data in inventory & financial books as soon as a settlement is done at store end. A new state for POS Settlement data, Unposted, has been introduced. Data in this state will reflect in inventory & financial reports without any restriction on reverting it if required. A scheduled background job will run every 15 minutes updating the settlement data from POS.
  • Performance improvement of settlement posting process.
  • Quick unsettled sale derivation for sharing with e-commerce aggregators.

Note

  1. Revert of Settlement can be done only if data is in Unposted state.
  2. The previous logic that Posted/Released settlements cannot be reverted remains as it is.
237820GIN-I-1367

37820 Item wise accounting introduced

Module(s):

  • Purchase Invoice
  • Consignment Invoice
  • Purchase Debit Note
  • Purchase Credit Note
  • Purchase Return
  • Sales Invoice
  • Sales Return
  • Sales Debit Note
  • Sales Credit Note
  • Transfer Out
  • Transfer In
  • Retail Sales (from HO)
  • POS Sales
  • Goods Receive at Store
  • Goods Return from Store

Enhancement Summary:

In Ginesys, it is now possible to maintain Item wise accounts. Tagging of items to general-ledger and sub-ledgers has been allowed. Once this process is done, for those items in which ledgers are tagged, all purchase to sale transactions will be impacted in those ledgers itself.

For the items in which General Ledger is tagged, the amount will be posted separately. However, for the items in which ledger is not tagged, the amount will be posted in the transaction GL itself. Few sample accounting entries:

Important Notes

  1. Item creation/modification from Ginesys Desktop has been removed.
  2. If you have any third party application integrated with Ginesys HO, you might need to upgrade your integration as this feature has made core structural changes. Please get in touch with your account manager for the details.
337820GIN-I-1367

37820 Transfer Rates for Non-Inventory Items can now be picked up from the Delivery Challan itself

Module(s) Affected:

Sales & Distribution - Consignment - Transfer Out
Sales & Distribution - Delivery - Delivery Challan (Adhoc or Against Order) - Auto Transfer Out

Enhancement Summary:

Previously, whenever any transfer used to be done, the rates for such transfers were always picked up from the Price List in Transfer Out irrespective of what was provided in Delivery Challan. However, in case of non-inventory items, the transfer rate cannot be fixed in Price List always. So for non-inventory items,the rates shall be picked up from the Delivery Challan itself.

Case Study: Procurement & transferring non-trading items to stores/other organization sites

  • Process
    1. Create a non-inventory Item with Ledger defined in it.
    2. Procure the same using GRC - Purchase Invoice.
    3. Move the goods to stores using DC - Transfer Out process.
  • Output
    • Ledger (item) wise detail will be available for in-out transactions.
    • No impact on the inventory.
437820GIN-I-1367

37820 GST ITC Eligibility introduced for Items in Procurement Flow

Module(s) Affected:

Procurement - Invoicing - Purchase Invoice
Procurement - Invoicing - Consignment Invoice
Procurement - Invoicing - Purchase Return
Procurement - Invoicing - Purchase Debit Note
Procurement - Invoicing - Purchase Credit Note

Enhancement Summary:

Similar to services, we have introduced GST Input Tax credit eligibility at Item level to allow the select input eligibility while doing a purchase transaction. In case, for any Item Input eligibility is set to 'Not applicable' for the item, then instead of posting the GST charges in input account, the system will post the same to the Purchase Account.

Scenario: A purchase invoice needs to be posted for purchase done from ABC Traders Pvt. Ltd. with the following Items:

  1. Item A with ledger:  Rs.1000
  2. Item B without ledger: Rs. 200


539012GIN-I-1680

39012 'Bill-to, Ship-to' concept added for Sales & Distribution process

Module:

Sales & Distribution - Setup - Customers - Un-managed Sites
Retail Management - Setup - Site: Location/Contact Information

Enhancement Summary:

Government has given a provision to ease out goods movements, i.e., marking separate bill to / ship to locations on a Tax Invoice. For example, A is the seller, B being the Buyer, however, B instructing to deliver directly to C. After this update, this possibility would be adequately mapped, i.e., the 'B' and 'C' do not have to be the same.

While you create sites against outright customers, you will have the option to select different shipping address. Note: For consignment stores this process is not applicable.

Scenario:

Consider the following scenarios - 

  • Agent Model - Agent asks the seller to deliver directly to the buyer but provide the bill to the Agent only. The Agent, in turn, would issue another Tax Invoice to the buyer.
  • One party multiple Sites - The party might want the invoices to be issued in a single location whereas the goods movement to be done directly to the multiple stores.
638836GIN-I-687

38836 Now image of item can be seen in POS as per Policy

Module(s):

POS - Normal POS - Item (Menu) - Search Item (option) > View Image (button)
POS - Collection Centre - Item (Menu) - Search Item (option) > View Image (button)
POS - Normal POS - Scan Item > View Image (button in Billing Area)
POS - Back Office - HO Control (Menu) - Item Master (option)  > View Image (button)

Enhancement Summary:

Item Image at store end is required specially in designer chains to address certain scenarios like when there is no stock available, the cashier/manager can refer to the image for reference and communications to the customer.

How to enable the same in Retail Management?

You will find a new System Policy setting, i.e., "Display Item Image at POS based on".

  • None - On clicking on the Image option, the user will be shown a message to contact the administrator for enabling this option.
  • Local - Image will be shown directly from the application folder at store end. Images should be saved manually to store server.
  • HOAPI - Based on the API configuration done for accessing Head Office, system will automatically show the image from Head Office.
    Note: In case no image is available for the Item or Image convention is not set for the Item, system will show "No Image found" by default.

For more details on configuring Web API or how to store image at store, you need to follow the details specified here: Setting Up the Web API

738768GIN-I-1527

38768 Accounting Year/Inventory Month / Finance Month - have separate Open and Close permission for more flexibility in usage

Module:

Admin - Organization - Periods - Accounting Year
Admin - Organization - Periods - Inventory Month
Admin - Organization - Periods - Finance Month

Enhancement Summary:

Open & Close functionality in Accounting YearInventory month & Finance Month modules in Ginesys web application has been done to ensure user is able to access the options depending upon the roles being assigned. It is a security check to ensure sanctity of financial data.

In Accounting Year, we have also introduced separate operations for "Transfer Ledger Balance" and "Edit".

Migration

We have given access for all new operations to the all the roles who earlier had the privilege to "Manage".

838763GIN-I-1329

38763 User defined fields introduced for Goods Return from Store

Module:

Ginesys Web - Admin - Utilities - Manage - User Defined Field (UDF)
Ginesys POS - Back Office - Transactions - Goods Return

Enhancement Summary:

User defined fields have been introduced for goods return documents getting generated from the store. The same can be configured in head-office and allocated to stores as per the requirement.

At the store, while preparing goods return transactions, the system shall allow the user to input any UDF if it has been enabled and assigned from Head-Office. If any UDF is made mandatory at HO, the user will have to mandatorily input the same while doing such entry.

NoteThe UDF information has been made available in the "Goods Return" analytic report.

938760GIN-I-1292

38760 Configurable user wise option for Policy driven GRT Advice behavior for Settlement post expiry now available

Module:

POS - Back Office - Transactions - Settlement

Enhancement Summary:

A new user policy has been introduced, i.e., "Settle with expired GRT Advice" with Allow, Warn and Stop options.

Scenario:

Currently the settlement is restricted, if any incomplete but expired GRT advice exists. Now, consider a scenario where the goods are packed in the store as per the goods return advice; but, it cannot be moved towards the destination - the logistics company being unable to pick up the same. In such situation, the user is unable to do settlement. In turn this leads to the billing process being stopped.

1038843GIN-I-1426

38843 Now reason can be provided for voiding Deposit / Refund Bill

Module:

Retail Management - Setup - Configure - Reason
Retail Management - Setup - Manage - Master Policy
Retail Management - Setup - Manage - Site Policy

Enhancement Summary:

Now the head-office user can configure the applicability of void reason for deposit & refund bills so that the cashier is forced to enter a reason while voiding the Deposit / Refund bill. The name of the policy applied - Void Deposit bill reason entry required & Void Refund bill reason entry required.

Deposit / Refund Bill Analysis Analytic Report

  1. Void Deposit & Refund bills were not available in this analytic report earlier. This will now be available with ISVOID column as 'Yes'.
  2. The void reason & remarks information has been made available in this report.
1138873GIN-I-1038

38873 Customer addition and tagging have been made easier

Module:

POS - Normal POS
POS - POS as Collection Centre

Enhancement Summary:

Customer addition and tagging have been made easier by auto population of some of the data. The customer will now be auto-tagged after selecting the return bill then the customer need not be manually selected, reducing the time spent on each bill. 

Also, customers can be directly created from the search customer window so that the mobile number of the customer need not be asked again. The scenarios given below are handled by this enhancement.

Scenario:

  • When the cashier is searching for a customer by his mobile number and the customer is not found, then he needs to add the customer. However, for doing that, he needs to go to the add window and retype the details. Due to this, the customer might be irritated with the cashier.
  • When the cashier is selecting a bill against a customer, then the customer and card details are not auto-populating. But while pressing F8, the cashier is mandatorily asked to tag the customer to whom this bill was done.
1238844GIN-I-1495

38844 Now the GSTIN of NRI (non resident Indian) customers can be captured in Ginesys

Module:

POS - Normal POS
POS - POS as Collection Centre
Retail Management - Setup - POS Customer
Ginesys Web - Data Import

Enhancement Summary:

At the time of creating or editing customers (whether normal add/edit or on the fly creation through the (plus) sign) at POS or HO - now the UIN for NRI customers can be captured. For certain categories, like UN bodies, embassies, etc., the format is different as they don't have any PAN No.; as per GST law, it is called UIN (Unique Identification No.).

Sample No. - 0717AUS12345UN1

  • First 2 digit state code
  • Next 2 digit year (YY format)
  • Next 3 country code
  • Next 5 Serial Number
  • Next 3 alphanumerics (including checksum)

Changes Retail Sale Data Import

GSTIN details & GST State of the billing customer were missing in data imports for retail sale which has been added.
Note: In case you are posting inter-state sale, please map GST state as well for the billing customer so that actual "Place of Supply" can be synced to EasemyGST.

1338821GIN-I-1681

38821 Reprint bills will be printed as single copy only

Module:

Normal POS - POS (module) - Bill (menu) - Reprint (option)
Normal POS - POS (module) - Bill (menu) - Reprint Last Bill (option)
Normal POS - POS (module) - POS Taskpad - Bill Reprint (option)
POS as Collection Centre - Collection Centre (module) - Bill (menu) - Reprint (option)
POS as Collection Centre - Collection Centre (module) - Bill (menu) - Reprint Last Bill (option)
POS as Collection Centre - Collection Centre (module) - Collection Centre Taskpad - Bill Reprint (option)
POS as Delivery Slip - Delivery Slip (module) - Slip (menu) - Reprint (option)
POS as Delivery Slip - Delivery Slip (module) - Tasks (menu) - Reprint Last Slip (option)
POS as Delivery Slip - Delivery Slip (module) - Delivery Slip Taskpad - Slip Reprint (option)

Enhancement Summary:

Previously, on reprinting any bill, the system used to reprint the no. of copies specified in the policy to print. However, reprint is required rarely and study suggests that reprint is ideally required only for a single copy. So, now at the time of bill reprint only a single copy will get printed. The number of copies of Sale or return bill Bill at the time of creation and save, provided in the Master policy, will not be considered here.

1438825GIN-I-1616

38825 Technical upgrades have been made to Paytm wallet for smooth functioning of the e-wallet feature

Module:

POS - All transactiosn with Mode of Payment

Enhancement Summary:

New technical upgrades have been made in Paytm e-wallet feature for smoother integrated functioning.

1538782GIN-I-844

38782 Technical upgrades have been made to ensure that Document Numbers do not skip in POS

Module:

POS - All transactions

Enhancement Summary:

Technical upgrades have been made to ensure that Document Numbers do not skip at POS.

Scenario:

In a few cases, we had observed that in POS stores (specially a multi-brand outlet), POS Bills would often skip a few document number and again start working. Suppose if the POS Bill document no. was defined as POSBL/<n>; sometimes the POS Bills would often have numbering like POSBL/1, POSBL/2, POSBL/3 etc. But the continuity would sometimes be broken at POSBL/16,  and instead of the next bill being  POSBL/17 it would take the numbering to be POSBL/18.

Although the scenario is explained with the example of a POS Invoice the same is perfectly applicable on all POS Transactions.

1638772GIN-I-1679

38772 User policy settings for stores has been regrouped for better visibility

Module:

Ginesys Web - Retail Management - Setup - Manage - Master Policy

Enhancement Summary:

New grouping has been added for organizing the user policies for stores.

  • Common
  • Delivery Slip & POS Bill
  • Other Bills
  • POS Order
  • Goods Receive & Return
1738775GIN-I-1682

38775 Data Sync Dashboard will allow filtration Event Data wise

Module:

Ginesys Launchpad - Data Sync

Enhancement Summary:

Currently, during the support process, if a particular event data's last receive status needs to be checked, the support executive has to open in descending order each and every record in the Sync list. Some quick filtration option was required for the same, it has been provided. 

A field called EVENTS has been introduced in the Send and Receive tabs, it will show distinct events that are packaged in the particular Send or Receive records. Grid column filters will operate on records having a particular kind of events.

1838837 GIN-I-1070

38837 A prefix for site identification is now available for site specific POS and HO Document Numbering Scheme

Module:

Retail Management - Setup - Configure - Document Numbering Scheme

Ginesys Web - Admin - Utilities - Document Numbering Scheme

Enhancement Summary:

At present to meet the requirement of site specific HO / POS Document Numbering Scheme, the user has to create individual document numbering scheme for each site separately, a tedious and time consuming job. However, after this update users will be able to create site specific document schemes by prefixing the site identification code while defining document numbering schemes for those documents.

Note: If  you wish to use site wise prefix in HO then the document Generation Basis has to be selected as Site.

Not applicable for unmanaged site documents

This new placeholder is not applicable for unmanaged sites as you are not allowed to enter Site Document Identification number for unmanaged sites. In case you do any transaction like "Miscellaneous Issue" for such sites with numbering scheme having this placeholder in prefix or suffix, then you won't be allowed to save the transaction and an error log/window will show up.


Bug Fixes

Serial

Dev IDIssue TrackerDescription
140533 N.A.

40533 Inventory Valuation Report showing wrong values

Module:

Inventory - Analysis - Inventory Valuation

Reported Version:

11.136.1                         

Scenario:

  1. Run the Inventory Valuation Report
  2. Observe that it is showing wrong values
240544N.A.

40544 COGS performance has been enhanced

Module:

Admin - Utilities - Application Tools - Recalculate COGS

Reported Version:

11.136.1                    

Scenario:

COGS internal logic has been altered to enhance performance.

338831N.A.

38831 Barcodes with preceding 0 (zero) can now be scanned in POS as Collection Centre and POS as Delivery Slip

Module:

POS as Collection Centre
POS as Delivery Slip

Reported Version:

1.136.1

Scenario:

Since Barcodes with preceding 0 (zero) are quite common in daily life; it has been made applicable for POS as Collection Centre and POS as Delivery Slip as it was already applicable in other modules.

Note: In Normal POS mode, barcodes with preceding 0 (zero) was already working fine.