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

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.

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.

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.

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

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.

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

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.

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.

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.

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.

17896

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)

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.

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.

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

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.

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

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.

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.

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

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.

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.

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.

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

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.

 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.

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.

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.