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.113.2 - 1.113.2

Owned by Ginesys Knowledge Team
Last updated: Feb 14, 2017
8 min read


Control

Release Date


HO Version11.113.2
POS Version1.113.2
Web Database Compatibility Version1.6
Features & Enhancements03
Bug Fixes05
Navigation


Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
120228GIN-I-283

20228 Customer credit verification rules have changed and credit restrictions can now be applied if overdue documents are present

Module:

Sales and Distribution – Setup – Customer – Sales(tab)
Sales and Distribution – Outright – Sales Invoice
Sales and Distribution – Delivery – Delivery Challan [Against Order]
Sales and Distribution – Delivery – Delivery Challan [Adhoc]
Procurement – Setup – Supplier – Sales(tab)
Finance – Voucher – AP Voucher
Finance – Voucher – AP Workbench

Enhancement Summary:

Earlier the credit verification of a customer was only based on credit limit but there was no concept of restricting further credit if there was any overdue document of the customer. Now there will be a credit limit as well as some overdue document validations which are customer wise configurable. Moreover, some tolerance option for credit limit is now available for flexibility.

IMPORTANT

Note: Details of each rule is provided in the section below.

The new fields are –

  1. Credit Rule - User will now be able to select the rule, which needs to be applied.
     
  2. Tolerance Percentage - Previously, there was an option only to provide the credit limit. Due to which operations, would stop even when the value crossed marginally. By providing tolerance percentage, user will now be able to create a buffer value to the provided credit limit. For example, Credit limit is defined as 5 lakhs, and tolerance is 10%. The applicable credit limit will now become 5 lakhs and 50 thousand.  
     
  3. Max Overdue Days - Number of days beyond which if payment of any document is due for a customer, further delivery/sale process to be restricted for the customer. For example, Max overdue days is specified as 10 days and current date is 20th October. If there is any sales invoice which became due for payment before 10th of October, then user will be restricted to create any further delivery or sale document. 
     
  4. Overdue Amount - Buffer amount to be allowed even beyond overdue days. Suppose overdue days is specified as 2 days and overdue amount is 10000. If there are only two documents of Rs. 4000 each, which became due 3 days back. Even then DC or Invoice creation would not be barred. But if the overdue amount went beyond, like if there would have been 3 documents of Rs. 4000 each which became due 3 days back, then DC creation and Invoice creation would be barred for that customer.

    Note: In aforesaid example, profile setting for credit verification is considered to be set as ‘Stop’.

The rights to add and modify these details will now be controlled by the “Credit Verification Failure Alert Method” user profile setting.

In case of violation of any of the validations proper messages will be displayed and further DC / Invoice / AP Voucher creations will be allowed with warning or completely stopped based on the user’s profile setting.

Please note the following important points:

  1. For Credit Rule - Credit Limit Only

    The Credit limit amount and the Tolerance percentage will be checked for validation. In case of AP vouchers, only this Credit Rule is applicable. When this rule is applied Credit Limit field will become a mandatory field, but tolerance will remain as non-mandatory field. Only the Credit limit amount and the Tolerance percentage will be checked for validation. In case of AP vouchers, only this Credit Rule is applicable.

    Note: Even if overdue days or overdue amount is specified, same will not be considered for validation purpose.

  2. For Credit Rule - Overdue

    When this rule is applied Overdue days field will become a mandatory field, but Overdue amount will remain as non-mandatory field. Max Overdue days and Overdue amount will be checked for validation.

    Note: Even if Credit limit or tolerance is specified, same will not be considered for validation purpose.

  3. For Credit Rule - Credit Limit and Overdue

    Both of the above-mentioned rules will be applied for validation purpose. The Credit limit amount, the Tolerance percentage, Max Overdue days and Overdue amount will be checked for validation. However, in this particular credit rule, violation of any of the validations (Credit Limit or Max Overdue days) will cause further related actions to be continued with warning or be suspended.

4. For Credit Rule – None

No validations will be applied, when none is selected as the rule.

In case of violation of any of the validations proper messages will be displayed and further DC / Invoice / AP Voucher creations will be allowed with warning or completely stopped based on the user’s profile setting. The user profile setting to be checked: “Credit Verification Failure Alert Method”.

Note:

• The fields can be imported through excel in the relevant forms.

• The reflection of the information captured in Sales and Distribution > Setup > Customer > Sales(tab) will be reflected in all forms which display credit information of customers.

• Credit information of suppliers will also be reflected in the same manner in appropriate forms.

Assumptions:

  1. No impact for Auto Delivery Challan: Currently, auto delivery challan is done without checking the credit limit/overdue days. The same shall be applicable now as well. Henceforth after this development, the user shall get restricted in Sales Invoice.

  2. If user takes the system date to backdate while saving any document, the "Overdue" check might misfire, i.e., may not get validated.

  3. All overdue documents will be taken into account irrespective of being Posted or not.

  4. No check/validation has been provided in transfer out. The validation will be applicable in Delivery Challan itself for Consignment customers.

  5. No credit validation applicable for own stores/branches (MS-OO-CM, OS-OO-CM).

  6. Overdue check to be applicable for Sales Invoice documents only.

7. No overdue check to be applicable in "AP Voucher". Only Limit check will be applicable there.

Migration Logic: If credit limit had already been assigned to any customer / supplier before update; the credit rule for those customer / supplier will be automatically set to Credit Limit on updating the software. Otherwise the credit rule will be assigned the None value after update.

Scenario:

N.A.

221084GIN-I-611

21084 Sales Order Hold option provided to temporarily block the dispatch

Module:

Sales and Distribution – Order management – Sales Order

Sales and Distribution – Order management – Sales Order Wizard

Sales and Distribution – Order management – Transfer Order

Sales and Distribution – Order management – Transfer Order Wizard

Sales and Distribution – Delivery Challan – Delivery Challan[Against Order]

Sales and Distribution – Order Management - Order Cancellation

Sales & Distribution - Order Management - POS Order Distribution

Sales & Distribution - Approval - Authorize Order

Sales & Distribution - Order Management - Order Analysis - Order Delivery Status

Sales & Distribution - Order Management - Order Analysis - Sales Order Planning

Sales & Distribution - Order Management - Order Analysis - Pending Order Status


Enhancement Summary:

Sometimes there is a need to put authorized Sales Orders or Transfer Orders on hold which are either in Non Transferred or Partially Transferred state. Now those Sales Orders or Transfer Orders can be held for further processes until the issue of contention is resolved.

Please note following important points:

  1. Creation of new Delivery Challan [Against Order] for held orders will be suspended. Whether it is Advance mode or FIFO or Alternate or Alternate FIFO mode -operations will be similar.

  2. Orders (both sales and transfer) once authorized may be cancelled but cannot be deleted at all. By corollary, since only authorized orders can be held; held orders are automatically non delete-able.

  3. During order cancellation, orders can be filtered based on their hold status - Held or Un-held.

  4. While re-distributing orders from the POS Order distribution module, the new orders will be created with the same hold status as the original orders.

  5. Multiple orders may be held or un-held from the authorization form at once.

  6. Order Analysis reports now have a checkbox to allow/restrict the inclusion of information about held orders. In Order Delivery Status report each held order will have an asterisk sign before the Order Number. Similar changes have been made for the Sales Order Planning report and Pending order Status reports.

  7. Unauthorized orders may be deleted but cannot be cancelled.

  8. Orders once cancelled (fully or partially) cannot be un-authorized again.

  9. Hold information will now show in Order Analysis OLAP report

  10. Sales Order OLAP report will reflect details of only un-held orders.

Assumptions :

  1. User will be allowed to modify and cancel held orders.

  2. Held Orders will be available in POS Order Distribution.

  3. Previously created DC of a Held order can be modified.

Scenario:

N.A.

321441BO-I-21

21441 Mark Down option has been provided for price calculations of "on the fly" item creation

Module:

Procurement - GRC - Item Details - Definition

Procurement - Order Management – Purchase Order - Item Details - Definition

Inventory - Setup - Opening Stock - Add/Edit Item - Definition

Inventory - Conversion - Bundle - Create Item

Inventory - Conversion - Production - Create Item


Enhancement Summary:

Previously the RSP and WSP prices for “On The Fly” Item creation in GINESYS ERP was calculated from its Rate or Standard Rate through the Mark Up approach and both positive and negative value was accepted as Margin %.

Now a Mark Down approach for price calculation is being implemented for the same functionality (on the fly item creation). So a different input parameter for price calculation is being provided.

The user is being provided an option to select either the Mark Up or the Mark Down approaches before getting into the price calculation process in the Price Population window within Item Details.

Mark Down calculation formula:
Rate(After Discount) / (1 - (Margin%/100))

Important information

Note: Default margin values provided in Customer or Supplier master is applicable only for Mark up approach.

Scenario:

Rate: 5000

Discount%: 10

RSP Margin%: 20

Round Off: 0

RSP will be calculated as follows:

Discounted rate = [5000-(5000*10%)] = 4500

RSP = 4500 / [1-(20/100) = 5625


Bug Fixes

Serial

Dev IDIssue TrackerDescription
121664 N.A.

21664 Negative Stock is not getting counted for a specific scenario

Module:

POS – Back Office – Transactions – Packets

Reported Version:

11.113.1

Scenario:

  1. Suppose there is 1 quantity of an item in stock and the negative alert option is set to 'STOP'.
  2. Create a packet with the above item and save it in Open state without posting.
  3. Retrieve the packet record and update the quantity with 3.
  4. It will stop the user from saving the new record and post the document with negative stock alert but show presence of 2 quantity of the item in the stock whereas there is actually only 1 quantity in the stock.
  5. Update the quantity with 2 and post it. It is allowing the posting of the document instead of restricting with negative stock alert although the stock is still 1 quantity.
221665N.A.

21665 Saving customer in edit mode is removing card information

Module:

GINESYS Web – Retail Management – Setup – Manage – POS Customer – Loyalty Information (tab)

Reported Version:

11.113.1

Scenario:

  1. Create a customer tagging a Loyalty Point Card.
  2. Retrieve the same customer record and go to the Loyalty Information tab.
  3. Observe that the card information is not getting displayed.
  4. Now if the record is saved again, the customer is saved without the card information.
321294N.A.

21294 Allow Credit Sale information cannot be incorporated in Customer Master Import Excel  

Module:

GINESYS Web – Admin – Utilities – Manage – Data Import

Reported Version:

11.113.0

Scenario:

  1. Go to GINESYS Web > Admin > Utilities > Manage > Data Import.
  2. Attempt to import customer information where there is a column related to allowing credit sale to the customer.
  3. Observe the information about allowing credit sale is not imported.
421242N.A.

21242 Auto email reports did not have a prefix of the document type and the document number while saving to .pdf file

Module:

GINESYS Launchpad – Mail Notification

Reported Version:

11.113.1

Scenario:

  1. During generation of auto mail reports, the document naming should be like the example as below:
    -- If the document number is 00000006_16_17 and it is a sale invoice  then the .pdf file should be named as SalesInvoice_SAL_00000006_16_17
  2. It was not happening.
519423N.A.

19423 Record is getting inserted in for wrong cost centre for Sale Invoice entry

Module:

Sales and Distribution - Outright - Sales Invoice

Reported Version:

11.113.1

Scenario:

Create Sale Invoice with charge value.
Retrieve the invoice.
Now change the Sales main ledger with sub ledger value.
It will prompt for term. Provide the term but do not press the calculate button.
Save the document. First it shows data validation error.
Again save the document. Document will save successfully.
Retrieve the document and check the Cost Centre.