Control
Release Date |
|
HO Version | 11.112.0 |
POS Version | 1.112.0 |
Web Database Compatibility Version | 1.5 |
Features & Enhancements | 15 |
Bug Fixes | 24 |
Navigation |
Features & Enhancements
Serial | Dev ID | Idea Tracker | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 17557 | GIN-I-532 | POS settlement data will now be checked at HO end before final postingModule: POS - Back Office – Transactions – Settlement Enhancement Summary: Sometimes due to application bugs or even erroneous data rectification there used to be a mismatch between POS settlement data and the data finally posted in HO. This caused major alterations in reports and caused their data to become questionable. Now, there is an alert mechanism in place. After sync when the POS Settlement data will be finally posted in HO, it will perform a data sanity check. It will be comparing the number of transactions in the synced physical data detail with the data count that was also synced from the POS, for that date. If the counts match, settlement will be done, otherwise it will display an error message. This will ensure that all the relevant data - i.e. no. of POS bills, PTC bills, Deposit/ Refund bills, Gift Voucher bills, Packets and GRC and GRTs etc. – are correctly synced to HO before Settlement can be posted. In case there is a mismatch in the data, Settlement Posting will be stopped till the data mismatch is rectified. So now the data reflected in reports will be accurate and complete. There will be a link in red in the Settlement form in HO which when clicked will open a list to show erroneous settlement data document level count. Scenario: N.A. | ||||||||||||||||||||||
2 | 13744 | GIN-I-313 | New system parameters introduced for Planning ModuleModule: GINESYS Launchpad – GINESYS Planning - Settings Enhancement Summary: Apart from the existing system parameters, the GINESYS Planning module will now have the following parameters which can be included for generating more comprehensive planning output. PENDING AUTHORIZE PO There are other system parameters too. The exhaustive list of new as well as earlier system parameters can be visible in the following location in Planning : Parameters > Manage System Parameter There is modification of Warehouse Stock [where packet stock is now not included] and POS sales [earlier only POS sales were considered but now sales from different site types are also considered] Scenario: N.A. | ||||||||||||||||||||||
3 | 17351 | GIN-I-372 | Now automated Customized database operation can be done after normal flow of Planning with the new hooking option called ‘Manage Post Run’Module: GINESYS Launchpad – GINESYS Planning Enhancement Summary: Customized database procedure can now be run to address customized requirement after the normal process of Planning. . But this customized procedure can only be configured by GINESYS Support and Implementation staff. Scenario: N.A. | ||||||||||||||||||||||
4 | 18380 18533 | N.A. | Unmanaged customer owned outright mode track secondary sites are now available for selection in the Planning moduleModule: GINESYS Launchpad – GINESYS Planning Enhancement Summary: Unmanaged customer owned outright mode track secondary sites are now available for selection in various menus and submenus of the Planning module. The real stock situation of these sites will now be effectively reflected in the Planning module. Scenario: N.A. | ||||||||||||||||||||||
5 | 17523 | GIN-I-371 | New User Role Privilege for different operations within Planning Module has been introducedModule: GINESYS Launchpad – GINESYS Planning Enhancement Summary: Earlier there were no role privileges involved in the management of the Planning Module. Anyone could log in and work with full access of all features. But since this is neither safe nor required, User Role Privileges have been introduced for different operations in the Planning Module. Now users may have right to add and save with no right to edit. A user can also edit and save and not be given the right to delete. There may also be users who can delete data. On upgrading to this version all existing users need to provide the privilege for using the Planning. Scenario: N.A. | ||||||||||||||||||||||
6 | 15508 | GIN-I-248 | Privilege to make transactions on last date of any open accounting year has been providedModule: Admin – Security Settings - Users Enhancement Summary: Earlier users could only operate on back date as allowed by the user lock days – i.e. if the user lock days in the profile of a user was 2 days; then he could only operate till two days before the system date. But now irrespective of the assigned lock days; users can operate on the last date of any open accounting year. The privilege to do so is provided through a check box in the Users form in Security Settings, called Ignore lock days on last date of any open accounting year(only for financial documents). As the name suggests, the option added will only allow the user to make financial transactions, like purchase/sales invoices and all financial documents. IMPORTANT Feature is only for the last date of the open accounting years – 31st March of each open accounting year only. Scenario: N.A. | ||||||||||||||||||||||
7 | 18468 | GIN-I-304 | Speed Search for Select Item has been providedModule: Wherever there is Select Item button / option (Speed search) Enhancement Summary: Presently in Select Item, user can search item on the basis of Barcode or Product Attributes but that is time consuming and depend heavily on the users’ abilities to remember the details. But now, a new option – Speed Search – has been included with a radio button beside barcode scanning option. When selected this opens a search box which allows the user to provide the following inputs related to an item and the LOV will be populated with a global search of the characters typed in. The search strings accepted by the Speed search option: • Division So now not only will it be faster and more efficient, but it will also allow the user to have the peace of mind when preparing documents under pressure because he will not need to remember item details anymore. Scenario: N.A. | ||||||||||||||||||||||
8 | 18595 | GIN-I-229 | Site tagging option now available in Incoming LRModule: Inventory – Logistics – Incoming – LR Enhancement Summary: Previously Incoming LRs could not be tagged to a site for consignors who are tagged to multiple sites. Often LRs created for one site was sent to another causing possible data mismatch and data corruption. While creating an Incoming LR/Gate Entry, site of the selected consignor can now be tagged. Accordingly, LOV for the LR in Sales Return/Transfer IN documents or Sales Return document will show those LRs which were created for the particular site of the particular consignee along with those LRs which have not been tagged to any site. Follow the tables below for more clarity. When LR is applicable
When only GE is applicable
Site selection option has been provided in search criteria of both Incoming and Outgoing Logistics tab of Print barcode label form. Operator will now be able to print Incoming & Outgoing Logistics label site wise.
Important information Note: This field shall only be visible if the LR Type is S&D: Sales Return/Transfer In Scenario: N.A. | ||||||||||||||||||||||
9 | 18596 | BO-I-88 | ‘Station From’ and ‘Station To’ will now be populated by default based on LR typeModule: Inventory - Logistics - Incoming - LR Enhancement Summary: Earlier station population logic was same for all LR types. Now, default population of station to be made as per the LR type in-order to make it more user friendly. Follow the table given below for more clarity: For Incoming LRs Station From
Station To For Outgoing LRs Station To
Station From If connected site’s city has been defined, it will be auto-populated. Otherwise the Organization Unit’s city or the Company’s city will be populated.
Important information Note: The auto populated city will get cleared on change of LR type. Scenario: N.A. | ||||||||||||||||||||||
10 | 18594 | BO-I-16 | Modification of freight in LR has been restrictedModule: Inventory - Logistics - Incoming - LR Enhancement Summary: Earlier if the freight charges were to be paid, then in both Incoming and Outgoing LR – It allowed the manual manipulation of the freight charges despite providing the Chargeable Weight and the Rate. Now, if the freight charges are to be paid, then in both Incoming and Outgoing LR – The freight charge is a calculated display field (calculated as a product of Charged weight and Rate) and does not allow manual manipulation. Total Freight amount can then be calculated by adding up with other charges. And in case rate and charged weight information is unavailable, entire amount can be placed as other charges. Same logic has been applied in Shipment Tracking Logistics. Scenario: N.A. | ||||||||||||||||||||||
11 | 18602 | BO-I-38 | The form amount can now be captured in the Purchase Form and a new quick assignment function added in both Sales Form entry & Purchase Form entry for Form AmountModule: Procurement - Invoicing - Purchase Form Register Report OLAP Reports - Procurement Sales & Distribution - Outright - Sales Form Entry Register Report OLAP Reports – Sales and Distribution Enhancement Summary: Previously there was only Form Number and Form Date in the Purchase Form Entry, now Form Amount will also be captured just like in the Sales Form Entry.
Important information Note: Overwriting existing values are not possible through the Assign button. Scenario: N.A. | ||||||||||||||||||||||
12 | 19089 | N.A. | Sub Ledger ID will now be displayed with Sub Ledger Name in Payment adviceModule: Finance - Documents - Payment advice Enhancement Summary: Now Sub Ledger ID will be displayed with Sub Ledger Name in Payment advice allowing report to be generated easily. Scenario: N.A. | ||||||||||||||||||||||
13 | 18574 | GIN-I-764 | Import Excel option has been added to Process MasterModule: GINESYS Web - Admin – Securities – Roles Enhancement Summary: Item wise - Jobber wise - Process wise Import Excel Option has been added in Process Master. Option has also been provided to update pending Job Orders and Job receipts with the item rate through Import Excel. Important information Note : Pending Job Orders are those job orders in which all ordered items have not been received yet. Scenario: N.A. | ||||||||||||||||||||||
14 | 19217 | N.A. | Route Group will now be shown against items while cancelling Job OrderModule: Production - Job Order Cancel Enhancement Summary: Route Group name will now be shown against items while cancelling Job Orders. Scenario: N.A. | ||||||||||||||||||||||
15 | 19272 | N.A. | Negative quantity of item is now allowed in "Opening Stock"Module: Inventory - Setup - Opening Stock Enhancement Summary: During migration of stock from other software to GINESYS, if any negative quantity of item was existent in the previous software; it can now be entered as "Opening Stock" to enable reflection of actual stock scenario vis-à-vis the business. Application of this feature has also been enabled through import Excel. Important information Note: Scenario: N.A. |
Bug Fixes
Serial | Dev ID | Issue Tracker | Description |
---|---|---|---|
1 | 18162 | N.A. | More than 14 records could not be created in the Organization Owned Site tab in the Customer master of the Sales and Distribution moduleModule: Sales and Distribution – Setup – Customer – Organization Owned Site tab Reported Version: 11.109.0 Scenario:
|
2 | 18207 | N.A. | PO status was not updated from back end procedure and error was getting generated but error was not showing at front end and document was successfully being savedModule: Procurement - Order Management - Goods Receive Challan -Agst Order Reported Version: 11.109.0 Scenario:
|
3 | 18319 | N.A. | Sorting option was not working properly in the Site tab at Customer masterModule: Sales and Distribution - Setup - Customer Master - Site tab - Sorting Tool (Right click on site) Reported Version: 11.109.0 Scenario:
|
4 | 18415 | N.A. | In Sales Order Cancellation, the filtration of last year documents was not working properly, the current year's documents were also showing along with last year's documentsModule: Sales and Distribution - Order Management - Consignment - Order Cancellation - Sales Order details Reported Version: 11.109.0 Scenario:
|
5 | 18480 | N.A. | Cheque Number was showing status 'New' in Cheque book although the cheque was already tagged with General VoucherModule: Finance – Cheque – Cheque Book Reported Version: 11.109.0 Scenario:
|
6 | 18534 | N.A. | User was unable to make a sales return due to error displayed by the system while selecting itemsModule: Sales and Distribution – Outright – Sales Return – Add Item Reported Version: 11.109.0 Scenario:
|
7 | 18567 | N.A. | Line level charge amount was not flowing from Service Order document to Service InvoiceModule: Procurement – Order Management – Purchase Service Order Reported Version: 11.109.0 Scenario:
|
8 | 18975 | N.A. | Quantity above 5 digit including 3 decimal places could not be edited and inserted in goods return challanModule: Procurement – Goods Return Challan – Goods Return Challan - Adhoc Reported Version: 11.109.0 Scenario: After creating a Goods Return Challan; it was observed that - during goods return when an item is selected from item selection and populated thereafter user was unable to edit the quantity and make it 6 digit including 3 places of decimal. Let's say instead of 100.00 the user wants to make the quantity 1285.357 but the system was only accepting till 1285.3 in the quantity field.
|
9 | 19017 | N.A. | "Available to Forward" column was not getting updated on clearing the WIP Clearance EntryModule: Production - WIP Clearance Reported Version: 11.110.0 Scenario: Available to forward column was not getting updated on clearing the WIP Clearance Entry in the report, Planning Master.
|
10 | 19243 | N.A. | In Select item module; item quantity in the set was not populating correctly as defined in Item Set masterModule: Inventory Reported Version: 11.109.0 Scenario:
|
11 | 19335 | N.A. | In the secondary sales form gross amount was showing wrongModule: Sales and Distribution – Outright – Secondary Sales Reported Version: 11.108.1 Scenario:
|
12 | 19344 | N.A. | In BOM master, by default BOM versions were not displayed in descending orderModule: Production - Setup - Bills of Material Reported Version: 11.110.0 Scenario: In BOM master, by default BOM versions were not displayed in descending order.
|
13 | 19347 | N.A. | Populated items in Job Order could not be deleted even before entry was saved, if user's role privileges were defined as Save OnlyModule: Production – Job Order Reported Version: 11.110.0 Scenario: Populated items could not be deleted even before entry was saved, if user's role privileges were defined as Save Only
|
14 | 19349 | N.A. | In the item details grid of Job receipts Consolidate Mode, item's were not populating based on item's Category nameModule: Production – Job Receipts – Consolidate Mode Reported Version: 11.110.1 Scenario:
|
15 | 19353 | N.A. | While adding intermediate process into the Working plan,supply type wrongly showing as 'Push' for the new processModule: Production – Working Plan Reported Version: 11.110.1 Scenario:
|
16 | 19396 | N.A. | Authorized Orders are not showing documents in the expected date wise descending, as well as document no. wise descendingModule: Procurement - Approval - Authorize Order Reported Version: 11.110.0 Scenario:
|
17 | 19576 | N.A. | The loyalty point card number is missing for some of the membersModule: Customer Masters in both HO and POS Reported Version: 1.109.0 Scenario: A customer is created with the name 'C' without the loyalty point card information and synced to HO. Then in the store the client updates the customer's name to 'Rajni' and tags a loyalty point card. During the next sync cycle from the HO it updates the customer information in the store with its previous sync’s state as available in the HO. So now, the customer name again shows as ‘C’ and shows no loyalty card tagged to it. |
18 | 19643 | N.A. | Error shown while sync at HO – “Column 'Isdenoapplicable' does not belong to table POSBillMOP”Module: POS – Administration – Data Exchange Reported Version: 1.111.0 Scenario: Error shown while sync if the event contains Petty Cash Bill
|
19 | 18360 | N.A. | At HO in bill detail analytical report, extra tax amount is showing correctly but the same report is showing 0 in all the fields at store endModule: POS Analytical Report Reported Version: 1.109.0 Scenario: At HO in bill detail analytical report, "Extra Tax" amount is showing correctly but the same report is showing '0' value for all the fields at store end.
|
20 | 19658 | N.A. | If no record is exists in Sales Person Assignment list then the Manage button was disabledModule: GINESYS Web – Retail Management – Security – Process – Sales Person Assignments Reported Version: 11.111.0 Scenario: If no record is exists in Sales Person Assignment list then the Manage button was disabled
|
21 | 18848 | N.A. | In some cases, user was unable to define Route Group MasterModule: Production – Setup – Route Group Master Reported Version: 11.109.0 Scenario:
|
22 | 19432 | N.A. | Selection of Alternate Component item was also populating its standard componentModule: Production - Job Order Reported Version: 11.110.0 Scenario: Saving of Job Order populated BOM for assembly items with both Standard or Alternate Components. This is required coz, selecting of alternate component against standard component was repopulating the standard component again resulting generation of double components. |
23 | 19405 | N.A. | User was unable to change the jobber and stock point while modifying Job ReceiptsModule: Production - Job Receipts Reported Version: 11.110.1 Scenario:
|