Release Notes 11.118.0 - 1.118.0

Configurable rounding modes with rounding multiple have been introduced in POS bill rounding operation.

Module:

Retail Management - Setup - Manage - Master Policy
POS Mode - Normal POS
POS Mode - Collection Center

Enhancement Summary:

Contrary to the existing rounding behavior in POS bill, where bill value is either rounded or not rounded, new rounding configurations have been introduced where the POS bill rounding behavior would depend upon the selection of rounding modes.

The existing system policy ‘Allow bill value rounding’ has been replaced with a new system policy ‘Rounding behavior in POS bill’. The policy would have the following 4 new rounding modes:

• Upper [Will always round the value to the next higher integer value.]
• Lower [Will always round the value to the previous lower integer value.]
• Round [Standard rounding behavior. Same as existing.]
• None [No rounding.]

Another new system policy “Rounding limit in POS bill” has been introduced to define the rounding limit.

Rounding Example –

• Item price - Rs.99.35
• Rounding Limit - 3
• Rounding Mode - Upper
• Rounding process (Steps) -
  • (Item Price) / (Rounding Limit) = 33.11
  • Round the value as per rounding mode (Rounding mode being ‘Upper’, the value 33.11 would be changed to 34)
  • Final Rounded Value - [34 * (Rounding Limit)] = Rs.102/-

Notes -

• On version upgrade, the rounding mode would be ‘Round’
• The default rounding limit would be ‘1’.
• Value ‘0’ or negative values as rounding limit would not be allowed.

Scenario:

N.A.

24132 Customer’s balance information is available for display in the POS bill window

Module:

POS Mode - Normal POS
POS Mode - Collection Center

Enhancement Summary:

After customer tagging in POS bill, the tagged customer’s balance details would be displayed from the customer detail window in POS bill. Depending upon the following customer’s balance conditions, the customer detail window would display the following -

• (+ve) Balance – Software would display ‘<Balance> receivable from customer’
• (-ve) Balance - Software would display ‘<Balance> due to customer’

Similar functionality is already available in POS order window. The same has been provided in POS bill window’s customer details section

Scenario:

N.A.

GIN-I-1205

26883 ‘Search by Name (With Stock)’ option has been introduced in multiple POS transaction windows

Module:

POS - Back Office - Transaction - Packet
POS - Back Office - Transaction - Stock Audit - Cycle Count
POS - Back Office - Transaction - Stock Point Transfer

Enhancement Summary:

‘Search By Name (With Stock)’ option which was earlier only available in POS bill window, is now available in Packet window, Cycle Count window and Stock Point Transfer window. The keyboard shortcut for this search option in all the 3 transaction window is ‘N’. 

Scenario:

N.A.

26817 ‘Religion’ column addition in customer list view

Module:

POS - Back Office - Store Control - Customer

Enhancement Summary:

Customer’s ‘Religion’ column has been added in the customer list view. Users would now be able to filter customers on the basis of religion and provide special offers at the time of religious festivals.

Scenario:

N.A.

26761 ‘Allow Credit Sale’ option in the customer creation window can be changed from POS stores

Module:

POS Mode - Normal POS
POS Mode - Collection Center
POS - Back Office - Transaction - Deposit/Refund Bill
POS - Back Office - Transaction - POS Order
POS - Back Office - Transaction - Gift Voucher Issue

Enhancement Summary:

The previous restriction on enabling the ‘Allow Credit Sale’ option from POS stores in customer creation window has been lifted. Now any user from POS store, can enable/disable ‘Allow Credit Sale’ option from the POS store itself.

Scenario:

N.A.

23620 Policy driven behavior after abnormal POS application shutdown

Module:

POS Application

Enhancement Summary:

New system policy has been introduced to determine the behavior of POS application after an instance of abnormal shutdown. Post abnormal shutdown, the policy value would be validated at the time of POS login, POS database backup and at the time of POS data synchronization.

The system policy has the following two values, each having different significances -

• Basic -
  • The last backup needs to be restored to resume normal POS operations.
  • 100% data integrity not assured.
• Restrict -
  • The last differential backup should be restored to resume POS operations.

Scenario:

N.A.

‘To Pay’ will automatically be set to ‘No’ if freight details are not provided

Module:

Inventory - Logistics - Incoming - LR

Inventory - Logistics - Outgoing - LR

Enhancement Summary:

In Incoming and Outgoing LR, by default ‘To Pay’ remain set as ‘Yes’. User either had to provide charges or had to manually change the value of ‘To Pay’ field to ‘No’.  

An alert has now been provided with the help of which user will now be able to save the document without entering charges and ‘To Pay’ will be set as ‘No’ automatically.

Scenario:

N.A.

Instrument number and amount wise a new LOV has been provided in all Accounting Voucher forms

Module:

Finance - Voucher - AP Vouchers

Finance - Voucher - AR Vouchers

Finance - Voucher - Contra Vouchers

Finance - Voucher - General Vouchers

Enhancement Summary:

Previously, there was no provision to retrieve any document with its instrument number. A new LOV has now been added with instrument details. Instrument information provided in the LOV are:

• Instrument No.

• Instrument Date.

• Amount

• Payment mode.

Scenario:

N.A.

Interface based UDF Configuration in various forms of Ginesys S&D Module

Module:

S&D - Outright - Sales Invoice

S&D - Consignment - Transfer OUT

S&D - Outright - Sales Return

S&D - Consignment - Transfer IN Adhoc

S&D - Consignment - Transfer IN Against Transfer OUT

Enhancement Summary:

Interface based UDF configuration option has been introduced for Invoice and Return forms of S&D module. The configuration option is head office driven.

The invoice and return transactions in the S&D module are available in the UDF module LOV.

Once the UDF is configured for any S&D form, users would be able to open an UDF window form the transaction window and select appropriate user defined fields. Following transactions have UDF availability -

• Sales Invoice

• Sales Return

• Transfer OUT

• Transfer IN

Scenario:

N.A.

Item criteria can now be specified in Promotion Assortment while creating the same using Import Excel option

Module:

Web - Admin - Utilities - Data Import - Promotion Assortment - Item Addition

Enhancement Summary:

Previously, through excel import we could only add items, barcode wise in an existing  active promo-assortment. Providing item criteria was only restricted to assortment window.

With this new enhancement, users would be allowed to provide other assortment criteria like Division, Section, Department, Article, Cat1-6, Desc1-6, price range basis, price range, creation date etc. to add items in an existing active assortment with excel import mode.

Scenario:

N.A.

Set Barcode can now be scanned using quick scan option in Sales and Transfer Orders

Module:

Sales and Distribution  - Order Management - Sales Order

Sales and Distribution  - Order Management - Transfer Order

Sales and Distribution - Delivery - Delivery Challan (Against Order)

Enhancement Summary:

Previously in Sales and Transfer Order forms users were not allowed to scan ‘Set Barcodes’ through F7=Quick Scan option. Now users will be allowed to scan the Set Barcode.

Delivery challan changes: Previously, while scanning set barcodes entire pending quantity of the order used to get populated. Now, quantity will be populated as per scan unit of the set.

Scenario:

N.A.

Site short name has now been made unique similar to site name

Module:

Organization Hierarchy - Organization Unit - Organization Site

Sales and Distribution - Setup - Customer

Enhancement Summary:

Previously, only Site Name was unique whereas site’s short name could be kept same for multiple site. Same has now been restricted, site short name will now accept only unique values.

Scenario:

N.A.

Column Description now updated to "Site short name for GV allocation" for 'ALLOCATED_SITE' column of Gift Voucher Creation and Gift Voucher Allocation import excel classes.

Module:

Ginesys Web - Admin - Utilities - Data Import - GV Creation

Ginesys Web - Admin - Utilities - Data Import - GV Allocation

Enhancement Summary:

Previously, in Gift Voucher Creation and Gift Voucher Allocation import excel classes, description of 'ALLOCATED_SITE" column was creating ambiguity. With the help of new description, user will now know that site’s short name needs to be provided, at the time of import and not site name.

Scenario:

N.A.

Reference Number of Web Transactions will now be displayed in Document Adjustment form

Module:

Finance - Journal - Document Adjustment

Ginesys Web - Sales & Distribution - Retail Sale - Store - Owned

Ginesys Web - Sales & Distribution - Retail Sale - Store - Franchise (Consignment)

Ginesys Web - Sales & Distribution - Retail Sale - E-Commerce - Fulfilled by Marketplace

Ginesys Web - Sales & Distribution - Retail Sale - E-Commerce - Fulfilled by Seller

Enhancement Summary:

Reference number provided in web transactions will now be displayed at the time of making adjustments from document adjustment form.

Scenario:

N.A.

Local Purchase is now be done for Secondary Franchisee Sites

Module:

Procurement - Goods Receive Challan

Procurement - Goods receive Challan (Wizard)

Procurement - Order Management - Goods Receive Challan (Against Order)

Procurement - Order Management - Purchase Order

Procurement - Goods Return Challan - Goods Return Challan (Adhoc)

Procurement - Goods Return Challan - Goods Return Challan (Wizard)

Procurement - Goods Return Challan - Goods Return Challan (Against Goods Receive)

Enhancement Summary:

Local procurement operation (purchase/return), which was earlier restricted only for organization owned POS stores, has been allowed for franchisee operated managed outright POS stores.

Similar to organization owned stores, in order to make a local purchase/return transaction, the store name for managed franchisee operated POS stores have to be selected from head office.

Scenario:

N.A.

Site Code can now be provided while creating DC against order using import excel option

Module:

GINESYS Web - Admin - Utilities - Data Import - DC Against Order

Enhancement Summary:

Previously, DC had to be created by providing site short name. User can now create DC(s) by providing site short name or site code, whichever is available to him.

Note: User need to provide either of the two, site short name or site code. DC creation would be restricted if both the values are provided.

Scenario:

N.A.

26718 Store Performance Report was not displaying properly

Module:

POS - Back Office - Analytics

Reported Version:

11.112.1

Scenario:

If the Store Performance Report was viewed the weekly/monthly/quarterly, the report could not be displayed in a date-wise ascending manner.

26809 Local Purchase and Local Purchase Return document missing from Sync process

Module:

Procurement - Goods Receive Challan

Procurement - Order Management - Goods Receive Challan - Agst Order

Procurement - Goods Return Challan -Adhoc

Procurement - Goods Return Challan - Agst Goods Receive

Reported Version:

11.116.1

Scenario:

In the scenario given below the Local Purchase and Local Purchase return document were getting missed out from sync process; if the occurs between two consequetive sync processes at HO:

1. Create local purchase / Local Purchase return for a particular POS site.
2. Authorize the same to the site.
3. After authorization, immediately revert the Local Purchase / the Local Purchase Return document.
4. Edit the same and then Authorize(Release).

26957 Item Stock was not reflecting the result of Local Purchase Revert and Local Purchase Return Revert event handling

Module:

Procurement - Goods Receive Challan

Procurement - Order Management - Goods Receive Challan - Agst Order

Procurement - Goods Return Challan -Adhoc

Procurement - Goods Return Challan - Agst Goods Receive

Reported Version:

11.115.2

Scenario:

After Local Purchase Revert or Local Purchase Return Revert event occurs there was no reflection of it in the item stock at the time of billing in the POS which prevented the negative stock check from operating.

26993 Vendor ID was not being saved during Planning for Procurement

Module:

GINESYS Launchpad - Planning

Reported Version:

1.117.1

Scenario:

The records for Procurement Planning were not being saved.

26994 Decimals were not allowed for both percentage(%) and Amount type of Benefit Factor in all types of Promotion

Module:

GINESYS Web - Retail Management - Promotion - Definition

Reported Version:

11.117.1

Scenario:

Decimals were not allowed for both percentage(%) and Amount type of Benefit Factor in all types of Promotion

27020 After any ledger was assigned to Petty Cash, Site master data was not being saved

Module:

GINESYS Web - Retail Management - Setup - Site - Petty Cash Heads (tab)

Reported Version:

11.116.1

Scenario:

In the Site master, assign ledgers to Petty Cash heads.

Attempt to save the record.

27062 Users' site assignment data was not being saved in some instances

Module:

GINESYS Web - Retail Management - Security - User

Reported Version:

11.117.0

Scenario:

27107 Charge factor of 3 decimal places was not being saved for both Purchase and Sales terms for Item and Document Charges

Module:

GINESYS Web - Procurement - Setup - Invoice Overheads - Terms

GINESYS Web - Sales and Distribution - Setup - Invoice Overheads - Terms

Reported Version:

11.117.1

Scenario:

1. Enter 2.222 as Factor in Terms of the above modules.
2. Press Tab button.
3. Observe that the value is changed to 2.22.

27109 Proper error message was not showing in when back-dated entry was being made in Packets

Module:

POS - Back Office - Transactions - Packets

Reported Version:

11.116.1

Scenario:

1. Attempt to save the record after making a back-dated entry in Packets.
2. Ambiguous error message comes up.

27233 Range Min-Max could not be imported in the planning module

Module:

GINESYS Launchpad - Planning

Reported Version:

11.117.1

Scenario: