Release Date

Jul 7, 2016 

HO Version

11.110.0

POS Version

1.110.0

Web Database Compatibility Version

1.5

Features & Enhancements

17

Bug Fixes

28

Navigation

1

17923

  BO-I-132

BO-I-132 Miscellaneous changes incorporated in TDS deduction of Service providers

Module:

Finance - Voucher - AP Voucher
Finance - TDS - TDS Journal
Finance - Approval - Release Document
Procurement - Invoicing - Service Invoice [Adhoc]
Procurement - Invoicing - Service Invoice [Against Document]

Enhancement Summary:

TDS (Tax Deducted at Source) is an instrument of Income Tax Department to collect taxes due for any particular payment. Earlier TDS on Advance Payment was manually computed in GINESYS HO. Now an option of automatic calculation of TDS for Advance Payment is being provided to the users.

Moreover, certain changes have been incorporated in GINESYS to ensure that there is no miscalculation of TDS due to Advance Payment. In GINESYS, two steps have been taken to ensure that calculating TDS is made easier -
• GINESYS is not considering the TDS exception limit during Advance Payment
• Total TDS applicable amount for any supplier in a particular financial year where all the records are made available for tagging in service invoice

The appearance of the AP voucher has undergone some changes as shown in the Notes section below.

Fig. 1 – If the AP Voucher is not being created for Advance Payment, then no changes are visible. Adjustment amount is entered manually and calculations are done based on that.

Fig. 2 – If the AP Voucher is being created for Advance Payment, then the appearance changes. The Adjust button does not exist anymore, in its place a new button – TDS Calc appears. If the Sub ledger tagged is “TDS applicable”, then the default value in the Deduct TDS field is “Yes”. Now it is up on the user if he wishes to deduct TDS on the advance payment or not. If “No” is selected, then the TDS Calc button is disabled. Then the user can decide to deduct TDS at the time of creating the Invoices or TDS Journal.

Scenario:

N.A.

2

17906

GIN-I-530

GIN-I-530 Price modification using ‘Edit Item’ can now be restricted through user profile

Module:

CHANGES IN USER PROFILE

Admin - Security Settings - User Profile - Procurement

IMPLEMENTATION IN TRANSACTIONS

Procurement - Order Management - Purchase Order
Procurement - Order Management - Goods Receive Challan - Against Order
Procurement - Goods Receive Challan

Enhancement Summary:

Currently when any operator is provided with access to modify the item using “F6=Edit Item” option, he was able to modify all Item properties. Since price is a sensitive property of an Item, modification of the same shouldn’t be allowed to all the operators on security grounds.

GINESYS has introduced various access permissions for editing Item Master from Purchase Order and GRC. List of those access permissions are given below:
• Allowed (All Item properties)
• Allowed (Price change restricted)
• Not Allowed

Scenario:

N.A.

3

17623

GIN-I-787

GIN-I-787 Service order cancellation remarks can now be provided while cancelling Items

Module:

Procurement - Order Management - Cancel Service Order
Procurement - Order Management - Purchase Service Order
OLAP reports

Enhancement Summary:

Service orders may be cancelled for many reasons; for the purposes of better management it is necessary to capture and monitor these reasons. GINESYS has added a Remarks field in the Cancel Service Order form module for the purpose of manual capture of the cancellation reason.

The remarks provided during cancellation shall also be reflected in the Service Order module.

Moreover, the cancellation remarks will also be reflected in the relevant OLAP report, Service Order Analysis, as well.

Scenario:

N.A.

4

17716

GIN-I-799

GIN-I-799 Item barcode import using Excel for Promotion Assortment

Module:

Retail - Admin - Utilities - Data Import

Enhancement Summary:

Now users have an option to quickly import a list of barcodes in the assortment's include or exclude block so that the promotions in the store can be managed properly.

The operator will have to provide a behavior to perform while importing the barcodes,
• ‘Add to existing’: This will add the barcodes to the existing list of barcodes in the assortment.
• ‘Remove existing then Add’: This will first remove the existing barcodes in the assortment and then add the imported barcodes.

The validation of items has been made optional so that the brand's barcode list can be imported directly. If the validation process has been selected and valid barcodes are found, they shall be added in the assortment. Otherwise, the import of barcodes will be restricted. For example, if suppose a brand has sent a generic barcode list for promotion applicability which has 2000 items. But out of 2000 only 1200 Items has been transacted/purchased from the brand. So while including the items:
• If “Avoid Item Validation” is set to ‘Yes’, then system will ignore the rest 800 items and import the 1200 items.
• If “Avoid Item Validation” is set to ‘No, then system will restrict the import process until those 800 items are either not removed from excel or not created in GINESYS.

Scenario:

N.A.

5

17908

GIN-I-476

GIN-I-476 Zero balance sub-ledgers/general ledgers now made optional in Register reports

Module:

Finance - Register - Sub Ledger
Finance - Register - General Ledger

Enhancement Summary:

Earlier sub-ledgers with zero balance were also reflected in sub-ledger & general ledger summary & monthly reports making the report unnecessarily lengthy. However, for the detail reports reflection of the same was optional.

Now the reflection of zero balance sub ledgers/general ledgers have been made optional for the summary & monthly reports as well.

Scenario:

N.A.

6

17889

 OFFPOS-I-67

OFFPOS-I-67 POS Return reason can now be provided while taking a return

Module:

POS Mode - Normal POS
POS Mode - POS as Collection Center
POS - Back Office - POS Control - Bill Modification

Enhancement Summary:

Previously, there was no provision to provide a reason for return of POS items, due to this, the return reason for each item, didn’t get captured. Reason to return an item may be different. For example, item I1001 is returned to store as it was damaged, item I1002 is returned as it was not of perfect fit. There can be various reasons for returning any item, and if these reasons are known then appropriate action can be taken to reduce return of goods. Like, item I1001 which was damaged needs quality check and more size options can be added for the item.

A new button has been added in the button panel of the POS Bill/Collection center window with the prompt 'Return Reason'. It is placed in the F7 (Return) button panel, below the 'Search Bill' button and is enabled only if user has 'Allow Return' privilege in Role Security.

On clicking on the 'Return Reason' button, if no item has been added for return the following message will be displayed - 'No return item has been added. Please add a return item to proceed.' If item has been added for return the Select Reason window will be opened to capture return reason.

Additionally, a new user policy, "POS Return Reason Entry Required", has been introduced to ensure that Return reason is mandatorily provided with each return.

Scenario:

N.A.

7

17907

 GIN-I-188

GIN-I-188 Sales return remarks can now be provided while returning Items

Module:

Sales & Distribution - Outright - Sales Return
Sales & Distribution - Consignment - Transfer In (Adhoc)
Sales & Distribution - Consignment - Transfer In (Against Transfer Out)

Enhancement Summary:

Sales return may happen due to many reasons - damaged item, not saleable item depending on time and place etc. GINESYS has now provided space to capture line level remarks in Sales Return, so that the return reason/remarks of each item gets recorded for future management study and actions.

For example, item I1001 is returned from store as it was received damaged, item I1002 is returned as it is not as per trend in store's location. There can be various reasons for returning any item, and if these reasons are known then appropriate action can be taken to reduce return of goods. Like, item I1001 which gets damaged needs quality check and along with that proper packaging of the item can be initiated to reduce the returns. And items like I1002 either needs to be advertised more near the store location so that the item is considered trendy in that particular location.

These remarks will be reflected in the reports too.

Scenario:

N.A.

8

 16940

 GIN-I-760

GIN-I-760 POS’s back-office transactions is now allowed despite of settlement threshold violation

Module:

POS - Back Office - Transaction (All)

Enhancement Summary:

Often when the operators either attempt to change a transaction document from open state to posted state or they attempt to settle a day, they fail to perform any of the tasks and it creates a deadlock situation. This happens because, day settlement cannot be done due to the presence of transaction documents in open state and when the operator tries to post an open transaction document, the software restricts the operator since the minimum threshold period for unsettled days have been crossed.

In order to avoid this scenario, a functional change has been made. From now onwards, even if the minimum threshold period for pending settlement day gets violated, software would allow the operator to post all open POS Back Office transaction documents. However, creation of POS transactions from all three POS modes Normal POS/Delivery Slip/Collection Center would be restricted.

Note: Henceforth, there is no settlement threshold check in back office transactions, i.e., the user will be allowed to create, modify, delete, post any back-office transactions. Only POS transactions will be restricted.

Scenario:

N.A.

9

 17625

 GIN-I-313

GIN-I-313 State filtration provided for F3 list of tagging documents in Outgoing Logistics

Module:

Inventory - Logistics - Outgoing – LR [only for document type S&D - Sales Invoice/Transfer Out]

Enhancement Summary:

Earlier, if site was not selected for the customer then documents of all the sites of the customer was available in the LOV for tagging with outgoing logistic. But for all practical purposes, clients receive only one state's permit and in a single LR, only a specific state's goods are sent or invoices can be tagged. Now, to make life easier for our users we have introduced the "State" filter as per the "Station To"(Destination) field in the LOV for selecting documents.

Scenario:

LR where Customer (consignee) has been selected with site: Only F2 LOV is present, displaying only the documents related to the consignee and the selected site. LR where ONLY Customer (consignee) has been selected: F2 and F3 LOVs are present, F2 displaying transfer documents of all states and F3 showing transfer documents within the same state. Suppose there is a customer, Customer 1,dealing with five(5) sites in the following way –

So for Customer1 on pressing F2 Transfer Documents of all states (i.e. Maharashtra, West Bengal and Gujarat) will show. F3 will show only documents of the state in which the selected city belongs (i.e. after application of the new “State” filter). So if the “Station To” is Pune then F3 will show all transfer documents from Maharashtra. LR where site is Organization Site Earlier F2 displayed all transfer documents of the selected organization site and it still works the same way. F3 previously showed transfer documents of all states related to that organization site; this feature will now be available on pressing F4. Presently F3 will only display transfer documents from the state in which the organization site belongs. If Pune is the city for the organization site, then • F2 will only display transfer documents for Pune organization site • F3 will only display transfer documents from Maharashtra (as Pune is a city in this state) • F4 will display transfer documents of that organization site related to all states

10

17630

GIN-I-478

GIN-I-478 Unadjusted Payment will now show separately in Bill wise Ageing Report

Module:

Finance - Financial Analysis - Bill Wise Ageing

Enhancement Summary:

Earlier the payment/receipt unadjusted amount was not shown separately in bill wise ageing report. Due to this, user was not able to understand which of the advance/unadjusted payments or receipt amounts were present in the "Total Pending Amount" being displayed. Now a new column, “Unadjusted Payments”, has been added to show these amounts. This will help the user to judge the ‘follow up’ process.

Scenario:

N.A.

11

17909

BO-I-18

BO-I-18 Stock point modification will now be allowed in Goods Receive even after Logistics tagging

Module:

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

Enhancement Summary:

Previously stock point modification was not allowed once LR or Gate Entry (whichever was applicable) had been tagged. But this caused an anomalous situation as GINESYS does allow modifications of all other information like item, rate, charge, etc. So an option to modify the same even after LR/Gate Entry is tagged has been provided.

Scenario:

N.A.

12

17886

GIN-I-807

GIN-I-807 Credit Card name and amount will now be shown in Card Detail window

Module:

POS - Normal POS / Collection Center - Take Deposit POS - Normal POS / Collection Center - Take Order - Deposit POS - Back Office - Transactions - Deposit / Refund - Deposit (Add/Edit) POS - Back Office - Transactions - Gift Voucher Issue (Add/Edit) POS - Back Office - Transactions - POS Order - Take Deposit

Enhancement Summary:

Earlier, once the user pressed F8 on the credit card MOP's amount field, he was taken into the card detail window where he entered the card number and expiry information or used Plutus to transact. However, in this process, two important informations went missing from the detail window, i.e., the MOP Amount and MOP Name. Especially people, who transact using Plutus, definitely need to see the amount in that window.

Scenario:

N.A.

13

18374

N.A.

18374 Route group name will now be displayed in Job related forms

Module:

Production – Job Order Production – Job Receipt

Enhancement Summary:

Route group name will now be displayed in the above named forms if defined in the Working plan

Scenario:

N.A.

14

17626

GIN-I-231

GIN-I-231 Term will now get saved in Procurement modules

Module:

Inventory Related Transactions Procurement - Goods Receive Challan Procurement - Goods Receive Challan - Wizard (For Adhoc GRC Created) Procurement - Goods Return Challan - Goods Return Challan (Adhoc) Procurement - Goods Return - Goods Return Challan - Wizard (For Adhoc GRT created) Procurement - Invoicing - Purchase Invoice (Including Auto Purchase Invoice) Procurement - Invoicing - Purchase Return Debit Note (Including Auto PRDN) Procurement - Invoicing - Consignment Invoice Service Related Transactions Procurement - Order Management - Purchase Service Order Procurement - Invoicing - Service Invoice (Adhoc) Procurement - Invoicing - Service Invoice (Against Document)

Enhancement Summary:

The new feature is meant to help users by saving the purchase terms for various Procurement modules – allowing them to recalculate charges if needed. Earlier when a user created a new GRC or Invoice then the system populated Purchase term as defined in the master, but once the respective document was saved, on retrieving the document the Purchase term was not being reflected in the charge window. Now the Purchase terms will appear in the charge window for the above saved documents in the Procurement module.

Scenario:

N.A.

15

18445

N.A.

18445 Supplier VAT/CST no. now available in Purchase Service Invoice Document Report below address block

Module:

Procurement - Invoicing - Purchase Service Invoice Document Report

Enhancement Summary:

Now the Supplier's VAT/CST no. is available in Purchase Service Invoice Document Report below address block if defined in Supplier master

Scenario:

N.A.

 16

15486

OFFPOS-I-59

OFFPOS-I-59 SMS can now be sent on Day Settlement at POS to concerned persons

Module:

POS - Back Office - Transactions - Settlement

GINESYS Launchpad - SMS Notification

Enhancement Summary:

The store or regional managers need certain basic updates about the day settlement like daily sale amount, number of bills that day etc. GINESYS POS now has an option of an SMS to the store manager or other managers at Day Settlement.

The configuration process is same as that of “POS Bill Save” or other POS SMS configuration, i.e., from Head-Office’s SMS notification module.

Following are the variables which shall be can be a part of the SMS configuration:

Scenario:

N.A.

17 

 17888

 OFFPOS-I-81

OFFPOS-I-81 Document numbering scheme for POS has been improved

i) New literals (MM) will now be available for use as suffix or prefix

ii) Literals have now been made mandatory based on reset interval

Module:

GINESYS Web - Retail Management – Setup – Configure – Document Numbering Scheme

Enhancement Summary:

i) New literal [MM] has been added which can be used in either prefix or suffix. The same will be replaced with digital representation of the document date's month. Like 01 for January, 10 for October, and so on.

ii) Presently, day, month or year may be provided as prefix or suffix in document numbering scheme, but the same is not mandatory. Due to this duplicate numbering scheme gets generated and at times it is very difficult to identify the reason for it.

The following scenarios described below explain the issue:

Case 1: (Prefix) BILL / (Running Number) 0001 / (Calendar Year) 2015 interval is monthly
POS Installation is done in the month of Jan for 2015
Thus the 1st bill generated would be as BILL/00001/2015
Now in the month of Feb the number would be again BILL/00001/2015

Case 2: (Prefix) BILL / (Running Number) 0001 / (Calendar Year) 2015 interval is yearly
POS Installation is done in the month of Jan for 2015
Thus the 1st bill generated would be as BILL/00001/2015
Now in the month of April the number would be again BILL/00001/2015

If reset interval is monthly or yearly - the user will mandatorily have to provide, in the prefix or suffix, the month literal, i.e. MM or MON AND the year literal, i.e. YY or YYYY.

Similarly, for the daily reset intervals - the mandatory literals, in the prefix or suffix, are date literal, i.e. DD; the month literal, i.e. MM or MON and the year literal, i.e. YY or YYYY.

Scenario:

Consider a scenario,
• A document numbering scheme for goods receive was defined as ‘GRC/’ as prefix.
• Last goods receive transaction at a store using that scheme is ‘GRC/10’.
• On modification in document scheme like name change or any other change, user will be restricted as per the interval, he will have to provide literals.
• He provided literal in suffix as ‘/[MM][YY]’.
• Now when this information is synced to store and another transaction is prepared at store using the same scheme, new number will be ‘GRC/11/0716’.

1

16873

 N.A.

16873 In OLAP reports, Stock Audit Verification report was not compatible with new audit process logic

Module:

Analytics - Oracle BI Tool

Reported Version:

11.107.2

Scenario:

Stock Audit Verification report is now compatible with new audit process logic

2

17911

N.A.

17911 Negative stock alert was not working in Advance mode of Delivery Challan [Against Order]

Module:

Sales & Distribution – Delivery – Delivery Challan (Against Order) – Advance Mode – Select Item

Reported Version:

11.109.0

Scenario:

When users scan any particular item to include it into the Delivery Challan it is obvious for the system to check the available stock of that item and in case of no stock or negative stock user must get an alert message in real time.
But here it was occurring after selection of all the items into the packet. In Advance Mode, at the time of saving the packet after populating pending items from a Sales Order, a negative stock popup was showing up. But then since the stock was negative, user is not able to do the transaction and save the document. Result was that he would have to find that item and take it out from the carton manually. This was practically impossible for the user.

Case study

Suppose there is an item (I001), which has been populated in a DC from a SO and has negative stock. I001 has been scanned and a packet has been created. Now the negative stock status comes forward and therefore not only can I001 complete this transaction but it has to be taken out from the carton manually. On the other hand, in the updated case I001 will show a negative stock, the moment it is tagged and scanned.

3

17910