mO SharemO Share

Release Notes 11.110.0 - 1.110.0


Control

Release Date

 

HO Version11.110.0
POS Version1.110.0
Web Database Compatibility Version1.5
Features & Enhancements17
Bug Fixes28
Navigation


Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
117923  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.

Important information

Note:

  • If auto-posting is allowed in the user’s profile, TDS document will be auto-posted after creation of voucher.
  • In case of Service Invoices, with or without document, it will be possible to tag all the TDS journals at once; it will ensure transparency in TDS calculation.
  • Reports, of both document and OLAP types, will reflect the TDS deduction done.
  • In Advance payment AP voucher, TDS calculation will not take into account the TDS exception limit. The consideration of exception limit will be handled at TDS Journal or Invoicing level.


Scenario:

N.A.

217906GIN-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

Important information

Note: The access permissions have to be defined under User Profile and Users belongs to that profile will inherit those access permissions

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.

Important information

Note: There is a single remark option for cancellation, i.e., if a particular service has been cancelled multiple times, due to multiple reasons, then the operator will have to provide remarks comma separated.

Scenario:

N.A.

417716GIN-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.

Important information

Note: Assortment master won’t get created automatically. It shall be created first and then barcodes can be imported.

Scenario:

N.A.

517908GIN-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.

Important information

Note: Reporting Changes have been made in POS Document Reports, POS Analytic and HO OLAP reports


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 –


Site nameCityState
Site 1PuneMaharashtra
Site 2MumbaiMaharashtra
Site 3KolkataWest Bengal
Site 4AhmedabadGujrat
Site 5SuratGujrat


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

Important information

Note: If no city defined for any site, that site's document won't be shown in this list.

1017630GIN-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.

1117909BO-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.

1217886GIN-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.

1318374N.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.

1417626GIN-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.

Important information

Note: GINESYS cannot migrate any term, so it might happen that in existing records, this problem might persist


Scenario:

N.A.

1518445N.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.

 1615486OFFPOS-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:

VariableDescription
SITE_NAMEStore’s Name
SITE_SHORTNAMEStore’s Short Name
SITE_CP_MOBILEStore’s Mobile No.
SETTLEMENT_BYSettled by user’s name
SETTLEMENT_FORSettlement date
FOOTFALL

Footfall on the settled date

POSBILLNET_COUNTNo. of POS bills (net of return)
POSBILLNET_VALUENet value of POS bills (net of return)
POSSALE_COUNTNo. of POS bills (positive bill value)
POSSALE_VALUEValue of POS bills (positive bill value)
POSRETURN_COUNTNo. of POS bills (negative bill value)
POSRETURN_VALUEValue of POS bills (negative bill value)
DEPOSITBILL_COUNTNo. of Deposit bills
DEPOSITBILL_VALUEValue of Deposit bills
REFUNDBILL_COUNTNo. of Refund bills
REFUNDBILL_VALUEValue of Refund bills
GVBILL_COUNTNo. of Gift Voucher bills
GVBILL_VALUEValue of Gift Voucher bills

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.

IMPORTANT

Note: After updating this patch, on any modification in existing document numbering scheme, the user will be prompted to provide literals (as per the reset interval) if not provided.

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’.


Bug Fixes


Serial

Dev IDIssue TrackerDescription
116873 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

217911N.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.

317910N.A.

17910 The doc no.'s LOV sequencing needed modification

Module:

Finance-Documents-Payment Advice
Finance-Documents-Money Receipt

Reported Version:

11.109.0

Scenario:

Document number LOV was being reflected Document number wise in descending order, due to this when document numbering is done on monthly basis, records of past months were reflected before current records; making users go through a lot of hassles.

Doc No. LOV will now be sorted Doc Date wise descending and then doc no. wise descending.

418230N.A.

18230 The items  excluded from the assortment in a coupon offer were not getting synced to store during coupon offer allocation and coupon offer change

Module:

POS – Administration - Data Exchange
Retail - Coupon - Coupon Management - Redemption Site Specification
Retail - Coupon - Coupon Management - Assortment Specification

Reported Version:

11.107.1

Scenario:

The items in the excluded list of an assortment were not being synced to store during coupon offer allocation and coupon offer change, which meant that all items in the particular assortment were getting tagged with the coupons without taking into account the excluded items.
Suppose an assortment has items from I001 through I010. But when tagged in a particular coupon offer some items were excluded - items I003 and I005 were excluded from the offer. But in the POS, even I003 and I005 were also getting tagged for the offer.

518064N.A.

18064 MOP modification not being allowed in POS Bill / GV Bill / Deposit Bill after disabling Denomination Based Payment options

Module:

POS – Normal POS
POS – POS as Collection Center

Reported Version:

11.109.0

Scenario:

  1. Make voucher payment with multiple denominations
  2. Disable the 'Denomination based payment' option from MOP master
  3. Now attempt to modify the MOP details.
  4. System does not allow modifications
618233N.A.

18233 At the time of adding raw materials items through Notepad, component items were not populating into the main window

Module:

Production – Setup – Bills of Materials

Reported Version:

11.109.0

Scenario:

  1. Open BOM master.
  2. Click on F4 and scan FG/SG items.
  3. Add Component.
  4. Click on select Items window for adding raw materials.
  5. Add component from notepad.
  6. Check that the component items are not populating in the main window.
718036N.A.

18036 All Route Group names were not displaying in Job Order selection LOV

Module:

Production – Job Order

Reported Version:

11.109.0

Scenario:

  1. Go to Production > Job Order
  2. In the Default Stock Point, The Route Group selection LOV was not showing all “non-extinct” Route group
818082N.A.

18082 The document reports Goods Received Document (Listed MRP) and Goods Received Note Without MRP were not showing correct 'Item Tax Group Name'

Module:

Procurement – Goods Receive Challan

Reported Version:

11.103.0

Scenario:

  1. Define KOLKATA as 'TAX region ‘at Connected Site.
  2. Define DELHI as ‘Tax Region' in Supplier Master.
  3. Define Tax rate master with same trade group, tax group and form name with different Tax region as 'Kolkata' and 'Delhi'
  4. Create a Goods Received document with tax group item.
  5. Execute the document report - 'Goods Received Document (Listed MRP)' and 'Goods Received Note without MRP'.
  6. The above report is not showing proper Item tax group name.
917662N.A.

17662 Stock Point field was disabled, once the GRC document was selected, while making GRT Adhoc and GRT against document

Module:

Procurement - Goods Return Challan - Goods Return Challan - Adhoc
Procurement - Goods Return Challan - Goods Return Challan - Agst Good Receive

Reported Version:

11.108.0

Scenario:

  1. In Goods Return Challan – Adhoc, scan an item or in Goods Return Challan - Agst Good Receive, select a GRC.
  2. See that the stock point field is getting disabled.
1017744N.A.

17744 Despite users’ role privilege being set to level 2,  users were unable to save the "Transfer form entry" for Transfer out

Module:

Sales and Distribution - Consignment - Transfer form entry

Reported Version:

11.105.0

Scenario:

  1. Go to Admin and Role privilege
  2. Set Privilege as 2, Privilege Level 2 means "View and Save" rights only
  3. Now go to Sales & Distribution > Consignment >Transfer out
  4. Now open Transfer form entry and try to save it with role privilege "2"
  5. The system does not allow you to save the document.
1117849N.A.

17849 In some cases, Excise charge was not being calculated in Sales invoice module

Module:

Sales and Distribution - Outright - Sales Invoice

Reported Version:

11.107.2

Scenario:

  1. Select document scheme number for Excise.
  2. Select excise applicable item.
  3. Calculate the charge.
  4. Save the document.
  5. Excise was not calculated properly in database.
12

17896

N.A.

17896 In 'Job Order Component Item (Production)'document type, for Job order item selection, Document No. Lookup was not showing entry

Module:

Any module - Item details – (F4) Select Items – Advance Search – Document tab

Reported Version:

11.109.0

Scenario:

  1. Create Job Order with Component Item.
  2. Now create any document Like GRC or any module.
  3. Using Select Item for Item picking.
  4. Now going to Advance Search > Document Tab
  5. Select document type 'Job Order Component Item (Production)'.
  6. Document No. Lookup is not showing Entry no. for document type 'Job Order Component Item (Production)
1317747N.A.

17747 In case of manual definition of an activation date of a Stock Audit Plan by a user, an error was generating

Module:

Inventory - Stock Audit - Plan  Stock Audit

Reported Version:

11.107.0

Scenario:

  1. Create Plan definition.
  2. Provide the activation date.
  3. It is generating an error.

Updated scenario

• If user has permission for "back dated activation of Physical Stock Audit" in his user profile then user will have the option to manually provide an Activation Date.

• Manually provided Activation Date should be always be a date previous to the system date. User will not have permission to manually provide future date in the activation date.

• Once the user has provided any logical value in the Activation Date; the user will only be able to save after right clicking and activating the plan. User can only activate any plan with the right clicking of the plan. After activation, the save button has to be clicked to save all the changes, otherwise all the changes done by activation will not be stored permanently.

• During Activation, if no date is available in the activation date field then system date has to be considered for activation.

• For the purpose of Back date Activation it is not required to log-in to previous date, even if user logs in to previous date then also system date is to be considered as activation date unless a manually provided activation date is available in the said field.

• Plans which are created in the previous year will be shown only by logging in the previous year and user has to manually provide the activation date. System date will not to be considered automatically in that case. If any Activated plan is reverted back to "New" state then make the activation date NULL.

• If any Updated or Completed Audit Plan exist after that (manually provided) Activation date for the given item / assortment it should not allow to input or activate the said plan for the same stock point. A message to be shown 'There are Plan(s) already completed / updated in future date as compare with the activation date of the current plan which is covering same item(s)/assortment. Thus it is not possible to Activate in backdate to ensure data sanctity of the previously completed Plans.'

• Activation Date should be in open state as per DAY BOOK Calendar.

• While activating a plan in back date the software will check if there is any open activated plan for that item / assortment. This validation was there in current activation but will now work back dated activation also.

1418120N.A.

18120 The documents were not opening when the user is attempting to retrieve the data

Module:

Procurement - Invoicing - Purchase Service Invoice

Reported Version:

11.105.0

Scenario:

  1. Save a Purchase Service Invoice
  2. Attempt to retrieve the document.

Database is being updated with negative values for the Purchase Service Invoice, due to loss of database connection.

1514566N.A.

14566 Blank report is being mailed to recipients when the sub ledger balance is zero (0) for Bill wise outstanding

Module:

GINESYS Launchpad - Mail Notification

Reported Version:

11.103.0

Scenario:

  1. Create a sub ledger with balance zero (0)
  2. Attempt to send a mail for Bill wise Outstanding
  3. Blank mail is sent
16 16806 N.A.

16806 Margin Monitor was populating wrong proposed item rate for Net of Vat margin rule

Module:

Procurement - Order Management - Purchase Order - Margin Monitor

Reported Version:

11.107.0

Scenario:

  1. Go to Procurement > Setup > Margin rule
  2. Define margin rule with Net of Vat.
  3. Set margin rule and article in supplier master.
  4. Set user profile for margin rule alert.
  5. Make purchase order - select the item of that article.
  6. Set the item rate which is not maintained the as per the defined margin.
  7. On saving the purchase order - margin monitor alert will come.
  8. Please check the item proposed rate which is not correct.

This rectification was done to correct the calculation of margin rule as well picking off tax rate based on Tax region.

17 18269 N.A.

18269 Tax slab was being given zero (0) value and tax was not being calculated in several modules

Module:

Inventory – Product Definition – Tax Definition – Tax Rate 

Reported Version:

11.109.0

Scenario:

Tax was not being calculated when tax slab was defined with zero (0) value.

Updated Scenario

The user has been restricted from defining tax slab with zero value. Old data will be migrated with all zero (0) values being replaced by 0.01

1817968  N.A.

17968 Margin Monitor was not picking proper tax rate if multiple Tax Region was defined for single Tax Group

Module:

Procurement - Goods Received Challan
Procurement - Order Management - Purchase Order
Procurement - Order management - Goods Received Challan - Agst Order

Reported Version:

11.109.0

Scenario:

  1. Create Tax rate master for multiple tax regions.
  2. Define tax region in supplier master.
  3. Set margin rule for supplier on Net of vat.
  4. Take item which is picking a tax rate and violates the margin rule.
  5. It will show wrong proposed rate.
19 18179 N.A.

18179 Sorting of document numbers was not properly executed when running reports on Money Receipts

Module:

Finance - Document - Money Receipts 

Reported Version:

11.109.0 

Scenario:

  1. Go to Finance > Document > Money Receipts
  2. Run the report
  3. Check that the Money Receipt numbers are not appearing in order.
20 18331 N.A.

18331 Delivery Challan Quantity was not getting printed through "Print Delivery Challan" module if Site city name was more than 30 characters

Module:

Procurement - Print Barcode - Delivery Challan

Reported Version:

11.109.0 

Scenario:

  1. Create city name more than 30 character.
  2. Tag the above city name in site master for Managed Site.
  3. Create Delivery Challan with some item.
  4. Go to print Barcode module.
  5. Open the Delivery Challan tab.
  6. Select the above delivery Challan no.
  7. Attempt to print the Barcode after selecting the default Barcode Control file
21 18334 N.A.

18334 Modify / Manage Item form was getting hanged when item was being imported through "Browse" option

Module:

Inventory – Item Definition – Modify/Manage Item

Reported Version:

11.109.0

Scenario:

  1. Check that a large number of items are present in the database.
  2. Try to modify more than 100 items through browsing from a Notepad or .txt file.
  3. Form gets hanged.
2218363 N.A.

18363 Negative stock check was getting violated for BOM items at the time of receiving alternate items

Module:

Production – Job Receipt 

Reported Version:

11.109.0 

Scenario:

  1. Open Job Receipts
  2. Click alternate items window
  3. Add alternate item
  4. Return/Issue window will open; same items were being issued and returned for alternate and order item.
  5. Negative stock checking constraint getting violated.
23 18367 N.A.

18367 Sub assembly were not getting auto populated in BOM as sub component item for the respective process on saving of BOM

Module:

Production - Setup - BOM 

Reported Version:

11.102.0 

Scenario:

While making BOM for Sub assembly item, if a particular sub assembly item is used in more than one process then, that sub assembly item will get auto populated as sub component item for the consecutive process on saving of BOM.

24 18370 N.A.

18370 PO is getting un-authorized when it is shipped from shipment module

Module:

Procurement – Approval – Authorize Order
GINESYS Web – Shipment Tracking – Manage – Purchase Order

Reported Version:

11.109.0 

Scenario:

  1. PO is created from Purchase Order module.
  2. Authorized the PO from Authorized Order Module.
  3. Created a Shipment request for Authorized Order from Shipment module.
  4. Now search the authorized PO.
  5. UN-authorized the authorized PO.
  6. PO is getting un-authorised

Updated Scenario

Now the document authorization will be checked gain before shipping

25 18427 N.A.

18427 Error in running split item register report

Module:

Inventory - Register - Split Item Register 

Reported Version:

11.109.0 

Scenario:

  1. Open Split item register from Inventory
  2. Select respective Date range to generate report
  3. Select the Process
  4. Select Site name(Site should be manage site)
  5. Select Stock point(Warehouse)
  6. Run the report.
  7. Error is displayed.
 26 18448 N.A.

 18448 Gate entry date was taking value less than that of logistic date in time of modification

Module:

Inventory – Logistics – Incoming - LR
Inventory – Logistics – Incoming – Gate Entry

Reported Version:

 11.109.0

Scenario:

  1. Create LR (Incoming).
  2. Create Gate entry to the corresponding LR.
  3. It was observed that after gate entry generation, modification of the date field accepted a date less than the corresponding LR.
 27 18436 N.A.

18436 Sub Assembly items not populating at the time of making duplicate BOM

Module:

Production – Bills of Material 

Reported Version:

11.109.0

Scenario:

  1. Select with F4 finish Goods/Semi finish goods type of items which have multiple types of sub assembly into the first process. Like the Cutting process being divided into cutting of Front, Back and Hand portions
  2. Create a duplicate BOM from Duplicate (Copy) option. Select Items either from LOV or through Category matching.
  3. In both cases, Sub assembly items are not populating into the new BOM.
2817893N.A

17893 Refresh item is not working while 'Entire Store' plan is used in audit journal

Module

POS - Back Office - Transactions - Physical Stock Audit - Audit Journal

Reported Version

1.108.0

Scenario

  1. Create a journal with 'Entire Store' plan and active it.
  2. Now in create some new items in HO and send to the store through datasync.
  3. Now open the journal and try to include the new items in the journal.
  4. the items are not getting included.