Release Notes 11.134.0 - 1.134.0

12 February, 2018

34870 Session tracking enabled for all types of bills in POS

Modules:

Ginesys POS - POS - F5 (Tasks) - Take Deposit
Ginesys POS - Back Office - Transactions - Deposit / Refund Bill
Ginesys POS - Back Office - Transactions - Gift Voucher Issue
Ginesys POS - Back Office - Transactions - Petty Cash

Enhancement Summary:

Prior to this version, session tracking for all transactions from where cash was impacted was not available. For instance, suppose a cashier created a POS bill of Rs. 100 in cash as well as Deposit bill of Rs. 50 in cash. Now at the end of the day, if the cashier wanted to tally total cash, system used to show cash of the session of Rs. 100 only and not Rs. 150 which led to operational problems and cashier had to manually calculate total cash by adding cash received from Deposit bills. The same case was repeated with Gift Voucher Issue, Petty Cash bill and Refund bill. We have now introduced session tracking for all such transactions.

Session Manager in Back office introduced

36620 Closing amount will now be entered for Cash, Vouchers & Gift Vouchers

Module:

Ginesys POS - POS - F5 (Tasks) - Enter Closing Amount
Ginesys POS - Back office - POS Control - Session Manager - Enter Closing Amount

Enhancement Summary:

Closing can now be entered for Cash, Voucher, Gift Voucher type Mode of Payments enabling cashiers to enter all the modes which is physically reconciled by the manager during reconciliation. The details of the entered (actual) closing is compared with projected closing and shown in the Cash Drawer Summary report under Closing Summary section with difference (if any) shown separately.

Count based concept introduced
A new option has been added called Allow count based payment drop & closing in MOP master at head office. If this is enabled, while inputting closing amount, the user will have to enter denomination & count for each such MOP. System will automatically calculate the total amount of that MOP as per the count details provided by the cashier.

35543 Pay In / Out introduced for better Session Management

During the session, cashiers do need to make certain cash in and outs from drawer due to various reasons like change given to other terminal, giving cash for petty expenses, receiving cash from any other terminal, etc. All these transactions if not recorded in the system makes reconciliation process, at the day end, very tedious and cashier has to recall each and every such transaction while presenting the closing cash to the manager. To facilitate this, pay in and pay out options has been introduced.

Following menus are provided to manage Pay In / Out:

• Ginesys POS - POS - F5 (Tasks) - Pay In & Pay Out:
  • Depends on operation privilege allowed to the user.
  • Using this option, transactions can only be recorded.
• Ginesys POS - Back Office - POS Control - Pay In / Out:
  • Depends on menu & operation privilege allowed to the user.
  • Using this menu, transactions can be recorded as well as modified.
  • Only the transactions belonging to the current active session of the terminal will be shown in the list.
    Reason: This restriction has been put in place to ensure, that another cashier from a different terminal cannot modify any transaction which is not of his concern. The analytic report can be used for viewing all the transactions of the day across the terminals, .

Important Note: Delete option is not provided for this type of entry. If required by the cashier, he can create a reversal entry, i.e., if Pay In done wrongly, then pass a rectification Pay Out and vice versa.

Implementing Pay In / Out:

1. Create a new numbering scheme with Applies to Menu givenas 'Pay In / Out'.
2. Assign this numbering scheme to stores using Allocation Group.
3. In store Terminal master, tag this numbering scheme in Pay In / Out Numbering Scheme field for the terminal from where these entries can be done.
4. Give Pay In / Out operation privilege for POS or Back office menu privilege (as per the requirement) to the user. Now user will be allowed to make such entries.
5. Optional - Reason can be configured using reason master in head-office if you want pre-defined set of operations where the cashier should use this entry.

Printing Pay In / Out entries:

• On creating any entry, system will prompt the cashier asking to print the entry. If user selects yes, a default thermal report will get printed.
• In case, the cashier wants to reprint the same, then he can reprint using the Backoffice menu.
• Customization -
  • The report can be customized as per the requirement and can be allocated from Head Office using Allocation Group.
  • Once allocated, it can be tagged to the Pay In / Out option in the Reports tab of the Terminal master.
• Report Header & Footer can also be added for Pay In / Out report type in Allocation Group.

Reporting:

• Analytic report added, you can import the same using Import option in POS Analytics at Head Office.
• In Cash Drawer Summary, all in / out shall be shown under 'Pay In / Out Summary' section.

Important Notes:

• Modification of entries are allowed only till session is active, once session is closed, entries cannot be modified.

• For making any entry, atleast one out of remarks and reason needs to be provided, else system won't allow the cashier to save.

36620 Payment Drop introduced for better Session Management

During the session, when alot of cash gets accumulated in the cash drawer, cashiers do need to send the cash to the safe / handover to manager to avoid any mishandling of cash. These transactions if not recorded in the system makes reconciliation process at the day end very tedious and cashier has to recall each and every such transaction while presenting the closing cash to the manager. To facilitate this, payment drop option has been introduced.

Following menus are provided to manage Payment Drop:

• Ginesys POS - POS - F5 (Tasks) - Payment Drop:
  • Depends on operation privilege allowed to the user.
  • Using this option, transactions can only be recorded.
• Ginesys POS - Back Office - POS Control - Payment Drop:
  • Depends on menu & operation privilege allowed to the user.
  • Using this menu, transactions can be recorded as well as modified.
  • Only those transactions will be shown in the list which are of current active session of the terminal.
    Reason: This restriction is to ensure that any other cashier of different terminal doesn't modify any transaction which is not of his concern. If required to view all the transactions of the day across the terminals, analytic report can be used.

Important Note: Delete option is not provided for this type of entry. If any mistake is done, either user can modify the same or do a Pay In entry for making any correction.

Implementing Payment Drop:

1. Create a new numbering scheme with Applies to Menu as 'Payment Drop'.
2. Assign this numbering scheme to stores using Allocation Group.
3. In store Terminal master, tag this numbering scheme in Payment Drop Numbering Scheme field for the terminal from where these entries can be done.
4. Give Payment Drop operation privilege for POS or Back office menu privilege (as per the requirement) to the user. Now user will be allowed to make such entries.

Printing Payment Drop entries:

• On creating any entry, system will prompt the cashier asking to print the entry. If user selects yes, a default thermal report will get printed.
• In case, the cashier wants to reprint the same, then he can reprint using the Backoffice menu.
• Customization -
  • The report can be customized as per the requirement and can be allocated from Head Office using Allocation Group.
  • Once allocated, it can be tagged to the Payment Drop option in the Reports tab of the Terminal master.
• Report Header & Footer can also be added for Payment Drop report type in Allocation Group.

Reporting:

• Analytic report added, you can import the same using Import option in POS Analytics at Head Office.
• In Cash Drawer Summary, all payment drop shall be shown under 'Payment Drop Summary' section.

Important Note:

• Modification of entries are allowed only till session is active, once session is closed, entries cannot be modified.
• Currently, Payment Drop is enabled only for Cash (in base currency).
• If for the Cash MOP, "Allow count based payment drop and closing" is enabled, the cashier will have to enter denomination & count.

36620 Cash Drawer Limit can now be defined at Head Office

Module:

Ginesys POS - Normal POS / Collection Center
Ginesys Web - Retail Management - Setup - Master Policy

Enhancement Summary:

A new system policy has been introduced using which head-office can now define a limit for cash drawers at stores which shall be applicable for all the terminals of the store. The cashier will be asked to drop the cash if the total cash value in the drawer is equal to or more than the provided value in the policy.

The cashier will be prompted as soon as the bill is saved. If the cashier ignores the same and proceed with next bill, the system will again restrict the cashier on F8 if the drawer balance is exceeding the limit set in the policy setting.

Note: It is currently applicable only for POS Bill transaction.

Scenario:

Suppose cash balance = 98000, current bill value with cash payment = 2000, and if the policy value is provided as -

• 99000 : User will be allowed to save this bill and as soon as the bill is saved, user will be prompted to drop cash.
• 99999 : User will be allowed to save this bill and as soon as the bill is saved, user will be prompted to drop cash.
• 100000 : User will be allowed to save this bill and as soon as the bill is saved, user will be prompted to drop cash.
• 100001 : User will be allowed to save this bill but will NOT be prompted to drop cash.
• Not Provided : User will never get prompted to drop cash.

35708 Ginesys Web Reports will now work with only compatible Ginesys versions

Module:

Ginesys Web - Reports

Enhancement Summary:

Now Ginesys Web Reports will only work with compatible Ginesys versions. When you update to the Ginesys version 11.134.0 - 1.134.0, your Ginesys Web Reports will stop working until you update to the proper version. The various scenarios you may face are given below, follow the message and do the needful to get your Ginesys Web Reports working again.

Scenario:

Scenario 1

GINESYS Version = 11.133.12
Web Reports Compatibility version = 2017.2
Web Reports Kit Version = Null (This case will occur after this patch update only)
Web Report Home & Server page will not open, the following message will display on the screen: Please process SYNC from Report Repository to start browsing reports.

Scenario 2

GINESYS Version = 11.133.12
Web Reports Compatibility version = 2017.2
Web Reports Kit Version = 2016.3.0 (Lower than compatible version)
Web Report Home & Server page will not open, the following message will display on the screen: Current Web Report version (2016.3) is not compatible with current GINESYS Version (11.133.2). Please Update web report version up to 2017.1 and process SYNC from Report Repository to start browsing Web reports.

Scenario 3

GINESYS Version = 11.133.2
Web Reports Compatibility version = 2017.1
Web ReportsVersion = 2017.2.0 (Higher than Compatible version)
Web Report Home & Server page will not open, the following message will display on the screen: Current Web Report version (2017.2) is not compatible with current GINESYS Version (11.133.2). Please Update web report version up to 2017.1 and process SYNC from Report Repository to start browsing Web reports.

Scenario 4

GINESYS Version = 11.133.2
Web Reports Compatibility version = 2017.1
Web Reports Version = 2017.1.0 (Same as Compatible version)
Resolution: Web Report Home & Server will always open.

37548 Vendor and Jobber Capacity can now be planned

Modules:

Ginesys Web - Admin - Utilities - Security - Users - User Profile
Ginesys Web - Procurement - Setup - Vendors - Vendor
Ginesys Web - Sales & Distribution - Setup - Customers - Customer
Ginesys Web - Admin - Utilities - Manage - Data Import
Ginesys Desktop - Procurement - Order Management - Purchase Order 
Ginesysy Desktop - Inventory - Setup - Process Master 
Ginesys Desktop - Production - Setup - Process Master
Ginesys Desktop - Production - Job Order

Enhancement Summary:

If we give excess order to any vendor or jobber, there is a chance that the vendor or jobber will not be able to fulfill the requirement. When we come to know about his limitations and still not implement any restriction while issuing the orders might lead to failure in meeting the demands of the customers. So now, with this feature, you will be allowed to define the vendor and jobber capacity and accordingly system shall restrict the user while preparing/modifying any order with capacity planned for him.

Vendor Capacity (Amount only):

• At vendor level, you will be allowed to define the capacity of the vendor. A new field called 'Purchase Order Limit (in amount)' has been added in the procurement tab of the Vendor master. 

  Note: Vendor import excel option is also made compatible with this new field.

• At user profile level, 'Purchase Order Limit Alert Method' profile in Procurement tab has been added with options of Ignore/Warn/Stop.
  
  
• While issuing a purchase order, if any capacity is defined for the vendor then system will calculate the pending order amount of the vendor and check against the capacity/limit provided. If the current order's value is exceeding the limit defined, then system will prompt the user as per the limit method defined in the user profile.
  
  
• Pending Order Amount Calculation: Rate * Pending Qty of all the orders of that vendor (irrespective of organization site, operating unit, authorization status).

Note: Charges are not considered in the limit calculation, only rate * qty. is done for deriving pending order value as well as current order value.

Jobber Capacity (Qty or Amount):

• At process level where we define jobber wise rate, you will be allowed to define the capacity of the jobber with choice of basis, i.e., quantity or service amount. Two new fields called 'Order Limit' and 'Limit basis' (quantity or service amount) has been added.
  
  
• At user profile level, 'Job Order Limit Alert Method' profile in Production tab has been added with options of Ignore/Warn/Stop.
  
  
• While issuing a job order, if any capacity is defined for the jobber for that process then system will calculate the pending order amount/qty of the jobber for that process and check against the capacity/limit provided. If the current order is exceeding the limit defined, then system will prompt the user as per the limit method defined in the user profile.
  
  
• Pending Order Calculation:
  
  
  • Basis = 'Qty.' then Pending Qty. of all the orders of that jobber for that process (irrespective of organization site, operating unit).
  • Basis = 'Service Amount' then Job Order Rate * Pending Qty. of all the orders of that jobber for that process (irrespective of organization site, operating unit).

36419 Re-issuing of Purchase Order from cancellation document is now a click away

Module:

Procurement - Order Management - Order Cancellation

Enhancement Summary:

A new option called 'Save and Re-issue Order' has been added in the aforesaid module. This option will help the user to quickly re-issue the order to a new supplier. On clicking on this option, the system will first save the cancellation document (to ensure any change done is accounted) and open up a small window asking few inputs like:

• Numbering Scheme: The scheme using which new order no. will be generated.
• Supplier: The supplier to whom you want to issue the cancelled order items.
• Reference No.: Optional reference no. field.
• Item Due Date Basis: There will be two options for this, i.e., as per the master (default) or as per the old order. The user will be allowed to change this only if he has 'Allow to change Item Due date in Purchase Order' privilege in his profile.

Important Notes:

1. Rate will be picked up as per latest master configuration.
2. For using this option, user must have create privilege of purchase order document.

37075 All inventory item based web reports will now have Item Category Dynamic Grouping

Module:

Ginesys Web - Reports

Enhancement Summary:

Now report data would be grouped and measures would show the aggregated values depending on which categories are combined as filters. Below an illustration is provided -

Example
Cat1(Design) . Cat2(Colour) . Cat3(Size)    Quantity
D-01 .                White                 32                  10
D-01 .                White                 34                  10
D-01 .                White                 36                  10
D-01 .                  Red                  32                  10
D-01 .                  Red                  34                  10
D-01 .                  Red                  36                  10

Case1: If user selects only Cat3 then following result would show

Cat3(Size)                                                   Quantity(summarized)
32                                                                            20
34                                                                            20
36                                                                            20

Case2: If user selects Cat1+Cat2 then following result would show

Cat1(Design) + Cat2(Colour)                       Quantity(summarized)
D-01 + White                                                           30
D-01 + Red                                                              30

Scenario:

N.A.

36348 A new button for 'Import Barcode' has been added in 'Item Reconciliation' window of Packets tab in the Goods Receive window for POS

Module:

Ginesys POS - Back Office - Transactions - Goods Receive (Add / Edit mode)

Enhancement Summary:

In POS - Back Office, a new button for 'Import Barcode' has been added in 'Item Reconciliation' window of Packets tab in the Goods Receive window. The new import barcode from text file feature will enable faster population of the item grid while receiving items at the store.

Scenario:

N.A.