mO SharemO Share

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.107.0 - 1.107.0


Control

Release Date

 

HO Version11.107.0
POS Version1.107.0
Web Database Compatibility Version1.4
Features & Enhancements09
Bug Fixes23
Navigation


Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
115262GIN-I-621

GIN-I-621 List type User Defined Fields (UDFs) are now available in POS Bill and Deposit / Refund Bill

Module:

POS Mode - Normal POS
POS Mode - POS as Collection Centre
POS Back office - Transaction - Deposit / Refund

Enhancement Summary:

  • Prior to this version, only Text type UDFs were available, where the user had to enter the values in text boxes. In case the HO wanted to restrict the user to selecting the some pre-determined values from a list, no such option was available. A list based UDF helps in reducing erroneous entries by users and thereby maintains standard values across all POS installations.
  • Earlier, only 5 UDFs could be configured for use in POS Bill. Now 10 fields have been provisioned for UDFs in POS Bill.


  • Only 5 UDFs were there in Deposit/Refund Bill. Now 10 fields have been provisioned for UDF in Deposit/Refund Bill.


NOTE: UDF configuration module is still not available from the application. You need to get in touch with GINESYS helpdesk in case you need to use UDFs in GINESYS POS

Scenario:

N.A.

214664OFFPOS-I-57

OFFPOS-I-57 HO can now control errors in POS Goods Receive entries through packet value tolerance policy

Module:

GINESYS Web - Retail Management - Setup - Manage - Master Policy
POS Back office - Transaction - Goods Receive

Enhancement Summary:

When items are transferred to POS stores from their replenishment sites, sometimes the following can happen due to human errors (during data entry or packing) –

  1. Items physically shipped are more than the transfer document qty (excess delivery)
  2. Items physically shipped are less than the transfer document qty (short delivery)

Organizations which follow proper delivery processes like to put a check against human errors in POS GRC entry by putting a tolerance limit (%) against the packet value.


Why is the tolerance limit not defined at quantity level?
The transferred items are in many cases in large quantities, so it becomes difficult and often irrational to manage the tolerance limit at item quantity level. E.g. a tolerance level of 10% at item quantity level does not make any sense for an item that has been sent as 1 qty (assuming that the sale factor of that item = 1, user cannot receive 0.9 or 1.1. quantities of the item). Hence, organizations find it easier to manage deviations at a packet value level.


How is the tolerance level defined?
The tolerance limits can be configured through two new policy settings “Short Goods Receive Tolerance %” and “Excess Goods Receive Tolerance %” available in Master Policy. Both of these are User Settings which means they can be allocated at Site Policy or Role Policy. When assigned at Role Policy, it means that there can be more than one user at POS with different levels of tolerance limit. E.g. the Store Manager may have a tolerance limit of 25% while the general user will have a limit of 10%.

How does tolerance level control errors?
If tolerance limit is defined, then short/excess amount can only be booked in accordance to the tolerance factor preventing any human error. In case an error has happened (either in physical shipment or in document quantity) beyond the tolerance limit, the store has to get in touch with a local user (e.g. The Store Manager) who has a higher tolerance limit to get the entry done. In case the deviation went beyond the limits of all POS users then HO has to intervene.
The intervention allows a higher authority to verify what went wrong. Inventory posting will not be allowed for a GRC where such packets exist.

Scenario:

Let's assume that the tolerance factors for short as well excess amount bookings are defined as 5% in the Master/Site Policy. Now in a GRC there is a packet where Sent Amount (Sent Qty x Rate) = Rs. 10,000. This packet can be received in POS as long as the Received Amount {(Received Qty + Damaged Qty) x Rate} of the packet is within Rs. 9,500 (5% short limit) to Rs. 10,500 (5% excess limit).

315506GIN-I-267

GIN-I-267 3.1 Corporate Identification Number (CIN) for Organization, Suppliers and Customers can now be captured in their respective setups and are available for reporting.
3.2 Service Tax Number for the Organization can now be captured in Organization setup and is available for reporting.


NOTE: Service Tax Number capturing for Suppliers and Customers are already available

Module:

Admin - Organization Hierarchy - Organization Procurement - Setup - Supplier Master – Statutory tab
Sales & Distribution - Setup - Customer Master – Statutory tab

Enhancement Summary:

The statutory organizational information - Corporate Identification Number (CIN) and Service Tax Number has to be mandatorily displayed in certain documents in some states of India. Now both these details will be captured in the Organization setup in the provisioned fields. The Suppliers’ CIN and Customers’ CIN will be captured in Procurement and Sales & Distribution respectively. The information can now be printed in both HO and POS documents. Please contact GINESYS support to include the same in your report layouts. 

NOTE: Changing the report layouts may be charged based on your Service Level Agreement (SLA)

Scenario:

N.A.

414709BO-I-131

BO-I-131 Revert option for posted General Journal entries now available

Module:

Finance - Journal - General Journal

Enhancement Summary:

Reverting option for posted journal entries was available in all other type of journals allowing users to modify and correct inadvertent mistakes identified after posting of the journal. From this version onwards, the option to modify incorrect General Journal entries by reverting and bringing it to the “unposted” state will be available. However, please note that the reversal option is still available.

Scenario:

N.A.

5

Item image now available in Auto Email report services of Purchase Order

Module:

SMTP Mailer - PO Events

Enhancement Summary:

Purchase Order Reports sent from the GINESYS Auto Email Application can now incorporate images of the ordered items if they are available for tagging. However, if image is not enabled for the item's department or image is not tagged, then the default 'No image available' image shall be shown.

NOTE: Please contact GINESYS support to include the same in your report layouts. Changing the report layouts may be charged based on your Service Level Agreement (SLA)

Scenario:

N.A.

615509BO-I-94

BO-I-94 Incoming and Outgoing Logistics Labels can now be printed to track the products being sent and received by the organization

Module:

Procurement – Print Barcode Label – Incoming Logistics

Procurement – Print Barcode Label – Outgoing Logistics

Inventory – Logistics – Incoming - LR

Inventory – Logistics – Outgoing - LR 

Enhancement Summary:

Earlier only the barcode label of an outgoing logistic document was printed. Now the print barcode label module has been provided with two new tabs, Incoming Logistics and Outgoing Logistics, for printing the barcode labels of outgoing and incoming documents. In both Incoming LR and Outgoing LR, one check box (Online LR barcode printing) each has been provided. If you check this box in Incoming LR then it will take you directly to the Incoming Logistics tab in Print Barcode Label to allow direct printing. Checking this box in Outgoing – LR takes you directly to Outgoing Logistics tab in Print Barcode Label to print the barcode labels immediately.

Scenario:

N.A.

714973

14973 In GRC adhoc and GRC against order, quantity total and amount total is seen while entering item details

Module:

Procurement - Goods Receive Challan

Procurement - Order Management - Goods Receive Challan - Agst Order

Enhancement Summary:

 While entering item details, in Goods Receive Challan adhoc and Goods Receive Challan against order, the total quantity and total amount can now be seen under the quantity and amount columns respectively.

Scenario:

N.A.

8 15511

15511 Manual Permit Numbers can now be generated in Permit Master

Module:

Inventory - Logistics - Incoming - Permit Inventory - Logistics - Outgoing - Permit 

Enhancement Summary:

Earlier, in GINESYS, permits could only be issued series wise and that made it a hassle to enter Permit Numbers which are provided by the Permit authorities. So now, it will be possible to enter permit numbers manually, making it easier to capture the Permit Numbers.

Scenario:

N.A.

9 14710 GIN-I-535

GIN-I-535 TDS Agency was showing in Supplier LOV although it cannot be tagged to complete the process

Module:

Inventory - Item Definition - Article Creation
Inventory - Item Definition - Item Creation
Inventory - Item Definition – Modify / Manage Article
Inventory - Item Definition – Modify / Manage Item
Procurement – GRC (Adhoc)
Procurement – Order Management – Purchase Order
Procurement – Order Management – Purchase Order Status
Procurement – Order Management –Delivery Analysis
Procurement – Setup – Margin Rule - Allocation
Procurement - Register-Vendor Master
Procurement - Register-Goods Receive Register
Procurement - Register-Good Return Register
Procurement - Register-Purchase Register
Procurement - Register-Order Cancellation Register
Procurement - Register-Purchase Return Register
Procurement - Register-Open Good Receive
Procurement - Register-Open Goods Return
Procurement - Register-Open Invoice
Procurement - Register-Pending Purchase Form

Enhancement Summary:

TDS Agency should not be a part of the Supplier LOV as it cannot be tagged to complete the supplier related processes in Inventory and Procurement forms and reports. However, this class is necessary in the Finance module. Now, TDS Agency will not be a part of the Supplier LOV in Inventory and Procurement modules but will reflect in the Finance module. 

Scenario:

N.A.

10.15506GIN-I-267

15506 3.1 Corporate Identification Number (CIN) for Organization, Suppliers and Customers can now
be captured in their respective setups and are available for reporting.
3.2 Service Tax Number for the Organization can now be captured in Organization setup and is
available for reporting.

Module:

Admin - Organization Hierarchy - Organization
Procurement - Setup - Supplier Master – Statutory tab
Sales & Distribution - Setup - Customer Master – Statutory tab

Enhancement Summary:

 The statutory organizational information - Corporate Identification Number (CIN) and Service Tax Number has to be mandatorily displayed in certain documents in some states of India. Now both these details will be captured in the Organization setup in the provisioned fields. The Suppliers’ CIN and Customers’ CIN will be captured in Procurement and Sales & Distribution respectively. The information can now be printed in both HO and POS documents. Please contact GINESYS support to include the same in your report layouts.

Important information

Note: Changing the report layouts may be charged based on your Service Level Agreement (SLA).

  Service Tax Number capturing for Suppliers and Customers are already available.

Scenario:

N.A.



Bug Fixes

Serial

Dev IDIssue TrackerDescription
116023 N.A.

16023 Last Backup information was not getting displayed in the Backup UI although Backup was getting created successfully

Module:

POS - Administration - Database

Reported Version:

1.103.0

Scenario:

  1. Open the Backup application and create backup.
  2. After completion of the backup, close the same form.
    Note: Backup is created successfully in respective path.  
  3. Now again open the Backup application.
  4. See that in the 'Last Full backup taken on:' section and red alert is displayed as 'Full backup is not found in backup location' even if the backup is present physically in the backup location.
216039N.A.

16039 HO Auto updater did not recognize .SQL file if SQL extension was written in CAPS.

Module:

HO Auto Update

Reported Version:

11.104.1

Scenario:

  1. Go to 'Custom Patch' tab.
  2. Select a custom patch named XXX.SQL (sql written in upper case).
  3. Apply the patch.
  4. The error message - 'The patch cannot be executed......' was shown and execution of the patch was restricted.
315903N.A.

15903 Wrong data was being imported if user changed sheet name from default sheet name (Sheet1, Sheet2) to any other name.

Module:

GINESYS Web - Admin - Utilities - Data Import

Reported Version:

11.105.0

Scenario:

  1. Suppose an Excel has sheet1 named as A2 and the sheet2 as A1.
  2. But while importing the data from excel application, sheet number = 1 was taking the A1 named sheet and importing sheet number = 2 was taking the A2 named sheet.
416080N.A.

16080 On remote login, the remote terminal is also updated as a server. Thus the planning process is getting stopped as multiple servers are not supported by GINESYS.

Module:

GINESYS Launchpad - Planning

Reported Version:

11.105.0

Scenario:

  1. Login from Remote terminal where the Planning service is installed and in the remote terminal the planning service is not installed.
  2. Planning process is not working as Planning service is installed in multiple terminals.
516074N.A.

16074 Cancellation of ordered item was not being allowed, when due date of the item was less than the system date.

Module:

POS-Back office - Transactions - POS Order

Reported Version:

1.105.0

Scenario:

  1. Create a POS Order on Date XX with Due date as YY.
  2. At System date is Date ZZ and user tried to cancel the order items; where ZZ>XX.
  3. An error message “User cannot cancel order items whose due date is less than the current date” is shown.
6 13913 N.A.

13913 When a global credit note was scanned /entered in POS for adjustment, the credit note was locked by the system to prevent duplicate adjustments. In case the bill against which it was being adjusted, had to be cleared for some reason, the credit note remained locked under some circumstances, mostly due to a broken internet connection at the time of saving. The credit note could not be re-scanned and adjusted again.

Module:

POS - Normal Mode
POS - POS as Collection Center
POS - Back office - Transaction - Deposit / Refund
POS - Back office - Transaction - Gift Voucher Bills

Reported Version:

1.100.0

Scenario:

  1. Start creating a POS Bill / GV Bill / Deposit Bill / Refund Bill.
  2. Tag one or more global credit note to any of the above bills.
  3. Now for some reason, the bill is cleared.
  4. Just at the time of clearing the bill, Web database connection is failed due to network issues.
  5. Start creating a fresh bill.
  6. Attempt to tag the same credit note as previous adjustment was not successful. 
  7. Error message is shown – “The credit note is locked by <LOCKEDBY> on <LOCKEDON>. Cannot proceed.” and the credit note cannot be adjusted.

Resolution/Workaround:
Global credit notes are no more locked at the time of scanning. Though highly unlikely, multiple terminals/store can scan the same global credit note at the same time. However, at the time of saving, the system checks whether the credit note has already been adjusted
from any other terminal/store and blocks the user if it is found adjusted from any other terminal/store.
The bill is allowed to be saved only if the credit note can be successfully adjusted. Note that, to perform this check at the time of saving, availability of internet connection becomes mandatory at the time of bill saving.

IMPORTANT

NOTE: This resolution requires that internet connection is present at the time of saving a bill where any global credit note is tagged. Any bill with a global credit note tagged, will not be saved if internet connection fails at the time of saving.

7 16499 N.A.

 16499 GINESYS POS crashes when terminal is re-opened after text mode Held Bill is assigned to it

Module:

GINESYS POS - Administration - POS Terminals - Report

Reported Version:

11.100.0

Scenario:

  1. Go to POS>>Administration>>POS Terminals>>Report and assign the text mode Held Bill layout which has been synced from the HO.
  2. Attempt to re-login to the POS Server.
  3. POS fails to open.
  4. Even while printing the print option doesn't work for the text mode of the Held Bill report layout.

The text mode functionality for the Held bill report layout has been developed and a default Hold POS bill report has been created.

.

8 16203 N.A.

16203 Amount in words was displayed in default GRT report in POS; showing “Millions” and “Billions” instead of “Lakhs” and “Crores” in case of 7 digit or 9 digit values

Module:

GINESYS POS - Back office - Transactions - Goods Return - Print

Reported Version:

1.106.0

Scenario:

  1. Attempt to print a Goods Return report in POS Back Office
  2. Report showing “Millions” and “Billions” instead of “Lakhs” and “Crores” in case of 7 digit or 9 digit values in amount in words field.
9 15992 N.A.

 15992 Excise was getting wrongly calculated in Transfer Out.

Module:

Sales & Distribution – Consignment – Transfer Out

Reported Version:

11.105.0

Scenario:

  1. Ensure that type selection in excise tariff master is WSP.
  2. Create a Transfer Out where Excise is applicable.
  3. Attempt to calculate Excise Rate
  4. The Excise rate was not being calculated as defined i.e. on WSP.

    The Excise rate in the Tax Master will be calculated from the Transfer Out document.

10 12845 N.A.

12845 The report is not being able to print some special characters in site name, address and other organization details.

Module:

All modules that have document report

Reported Version:

11.105.0

Scenario:

  1. Use special characters in the site name or other details of the Organization Unit.
  2. No document report in HO was opening.
11 15995 N.A.

15995 If item received is more than ordered quantity while creating a GRC against order then the Applied On amount for Excise was not getting modified according to the modified and increased item quantity.

Module:

Procurement – Order Management – Goods Receive Challan – Agst Order

Reported Version:

11.105.0

Scenario:

  1. Attempt to create a Goods Receive Challan against order
  2. Change item quantity to a value greater than the ordered value.
  3. The value of Excise rate calculated in the Applied On field stays the same.
12 15950 N.A.

15950 Through the Goods Receive Challan – Wizard, GRC against Order is created without logistic quantity in some cases.

Module:

Procurement - Goods Receive Challan - Wizard

Reported Version:

11.105.0

Scenario:

  1. Fill all the required fields with logistic information.
  2. Scan the item for GRC creation.
  3. In the set off window, press the next button.
  4. Now if user goes back to first window then logistic information gets removed automatically.
  5. User can save GRC against Order without Logistic qty.
1313182 N.A.

13182 Split items cannot be created if stock of that particular item is negative or zero and value in user profile negative stock control field is “Stop”.

Module:

Inventory - Conversion - Split item

Reported Version:

11.105.0

Scenario:

  1. Attempt to create a split item where the user has negative stock alert method “Stop” in his profile for the above type of organization units.
  2. An error message is shown, “You cannot issue this item. It has a quantity of [negative quantity or zero]”.
1416052 N.A.

16052 The Sorting Order not coming properly in the Item Details window of GRC-Adhoc and GRC-Against Order.

Module:

Procurement – Goods Receive Challan
Procurement – Order Management - Goods Receive Challan – Agst Order

Reported Version:

11.105.0

Scenario:

  1. Open or create Goods Receive Challan (Adhoc) or Goods Receive Challan against order.
  2. Open Item Details.
  3. Select Items and populate in grid.
  4. Attempt to Sort them by right clicking the items and selecting “Sort” option from the drop down.
  5. In the Select columns to sort by window, some of the values (Barcode / Department / Article etc.) that should appear in the Available Columns list were missing. However some other columns from Available Columns for sorting from Price Population window were appearing in this Select columns to sort by window of Item Details.
1516065 N.A.

16065 Master plans from previous years could not be tagged in Working Plans of this year.

Module:

Production – Working Plan

Reported Version:

11.105.0

Scenario:

  1. Create a Master Plan entry in a previous year.
  2. The Working Plan is created in this year then Master Plan no. lookup is not showing previous year’s master plan.
1616077 N.A.

16077 The tax rate was not being correctly calculated during invoicing of service orders through Service Liability Workbench.

Module:

Procurement – Invoicing – Service Liability Workbench

Reported Version:

11.105.0

Scenario:

  1. Attempt to create invoice Service Orders through Service Liability Workbench.
  2. The tax is populated from the Purchase Service Order.
1716218 N.A.

16218 While selecting item in Bill of Materials or Working Plan the following error message was showing, “Variable GLOBAL.JOB_TYPE does not exist.”

Module:

Production – Working Plan
Production – Setup – Bill of Materials

Reported Version:

11.105.0

Scenario:

  1. Open either Working Plan or Bill of Materials.
  2. Attempt to Select Item or press F4.
  3. In the Production Select Item window, give the search criteria and press Search button.
  4. The following error message was showing, “Variable GLOBAL.JOB_TYPE does not exist.”
1814732 N.A.

14732 If a “Non Taxable” tax type was not defined in the Tax Master but the user was trying to create items through the Import Excel function using Item_serial class then it was showing an error message of integrity constraint violation.

Module:

Inventory – Item Definition – Create Item – Import Excel

Reported Version:

11.105.0

Scenario:

  1. Attempt to create item from Import Excel where item being created is Non Taxable but the Non Taxable head has not been defined in the Tax Master.
  2. Error message is shown when the create item button is pressed.
1914094 N.A.

14094 The changes made through the Global Change button in Description 2 field in items are reflecting within single quotes.

Module:

Inventory – Item Definition – Modify / Manage Item

Reported Version:

11.105.0

Scenario:

  1. Go to Inventory > modify\manage item
  2. Select an item having value in Description 2 field
  3. Click on Global Change
  4. Change Description 2
  5. Notice the changes coming with a single quote
2015462 N.A.

15462 Charges in GRC Against Order could not be modified when an item having same tax name with different rates was included in the applicable Purchase Order.

Module:

Procurement – Order Management – GRC-Agst Order

Reported Version:

11.105.0

Scenario:

  1. Open a GRC-Against Order where there is an item having same tax name with different rates included.
  2. Open the charge window.
  3. Edit the term.
  4. Attempt to save the changes.
  5. Then the following message is shown, “There must be one tax 'IS TAX' Charge in document with same source."
2114203 N.A.

14203 In consignment invoice the tax calculations was not picking the tax rate defined in the Tax Slab which has been tagged.

Module:

Procurement – Order Management – GRC-Agst Order

Reported Version:

11.105.0

Scenario:

  1. Create a consignment invoice with Tax Slab applicable item.
  2. Tax calculations are being calculated from tax master rates instead of the defined Tax Slab.
2215465 N.A.

15465 Simultaneous Stock Audit showing wrong prompts in forms and reports instead of “RSP” it was showing “MRP”.
Show modified items (if any) checkbox showing unchecked after modification to the Stock Verification Plan.

Module:

Inventory – Stock Audit – Verify / Update Stock

Reported Version:

11.105.0

Scenario:

  1. Open Stock Audit.
  2. All forms and reports have the wrong prompt where “RSP” is showing instead of “MRP”.
  3. Open Verify / Update Stock module.
  4. “Show Modified Items (if any)” check box was remaining unchecked when it should be checked by default.
2316264 N.A.

16264 Any change in Promotion Assortment is not getting uploaded for respective sites.

Module:

GINESYS Web - Retail Management - Utilities - Explore - Data Sync

Reported Version:

11.105.0

Scenario:

  1. Create a Promotion P1 with assortment A1 where I1 and I2 items exist.
  2. Allocate P1 to Site S1 and see that the promotion is getting resolved for I1 and I2.
  3. Now edit A1 include I3 item in it and save A1.
  4. Sync data in HO.
  5. The assortment change information is not getting uploaded for the allocated site/sites.