Release Notes 11.135.1


Control

Release Date

23 March 2018

HO Version11.135.1
POS Version1.135.0
Web Database Compatibility Version1.11
Features & Enhancements01
Bug Fixes27
Navigation

 Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
132061GIN-I-1364

32061 Cost of Goods Sold (COGS) revamped with new logic.

Module:

Admin (Desktop Application) > Utilities > Application Tools > Recalculate COGS

All Inventory Valuation Reporting

Enhancement Summary:

Impacts & Benefits of new revamped COGS on Ginesys operation –

  • Ginesys will now provide more effective Stock Valuation, as it will consider only non-transit stock point inwards instead all stock point inwards, including transit inwards.
  • Reports are expected to be refreshed faster.
  • Once Inventory Value is finalized, no new entry would be possible unless the month or year is opened.
  • Once Inventory Value is finalized, even if later a report is refreshed at any point of time, the values will remain the same for a particular date.
  • Considering the item’s Last-In Rate is more effective for cost calculation as it is stored site wise.
  • Before COGS is run tentative Gross Profit will be calculated based on that point of time Last-In rate instead of FIFO rate. This will be overwritten during COGS with proper FIFO Rate.

Definitions of terminology used in Rate Picking Logic in COGS:

In-Pool

All stock inward entries in any non-transit stock points for particular site is considered as in-pool

In Pool Entries = All +ve stock entries by inter site stock movement (only non-transit stock point entries) + First Time inward into system

Last-In Rate

The entries by which an item comes into the system first time will be considered for capturing Last-In Rate. At any point of time, whenever any of the following entries happens this will be captured in a separate table for each item and site. For same site and item, only one rate will be available at one point of time as each record updates the previous one.

  • Opening Stock
  • Goods Receive
  • Conversion - Bundle/Split/Production
  • Production Receipts (PC)
  • Miscellaneous Receipt

[These are the entries which provide the first time entry of the items into system]

Process flow of COGS

 

COGS Process Rate Picking Logic

At any point of time, to calculate cost value of available inventory will be calculated based on the following rates depending on certain conditions mentioned in the flowchart below.

  • Cost Rate of the available item’s items’ in-pools entries based on FIFO
  • Latest In-pool Rate of the Item at that point of time
  • Latest In-pool Rate of the Item in other site under same OU
  • Last-In Rate of the Item in that Site [May be later date]
  • Last-In Rate of the Item in other Site [May be later date]
  • Item Standard Rate

Change in Reporting

Optimization of Reports: Since, Ginesys will store any existing difference value, reports are expected to be faster as no complex calculation at report level is required to achieve FIFO value.

Transit Value in Reporting: In the Stock Movement Cube Report, Closing Stock will not display the Transit Amount. Transit Movement within the Period will be shown separately in Stock Book Report. Due to earlier logic; for any item, if transit quantity is zero but value exists; then that value will be shown in Transit Difference once pending Transit Quantity reaches zero.

Reporting in Between Month: Difference Value is posted in the last day of the month hence reports in between period will give provisional report only even if COGS status is Final.

Aging Report Value Calculation Method: To achieve the stock value of different aging period, average cost of total stock as on the value in the ‘Date to’ column of the cube will have multiplied by available quantity of the stock at the aging period. Thus avg. cost of stock for any aging period will be same.

Modification in Reporting Sources:

OLAP Cube - Following Old Cubes under Inventory will be shifted to Inventory Defunct Module. No other restriction is imposed.

  1. Stock Valuation OU [CUBE$STKVALOU]
  2. Stock Movement [CUBE$STKMOVE]
  3. Stock Valuation [CUBE$STKVAL]
  4. Stock Movement GP [CUBE$STKMOVEGP]

Registered Report - Following Reports will be removed.

  1. Inventory Movement (Amt)
  2. Inventory Aging Analysis
  3. Inventory Summary (Group Wise)

Web Report - Following New Reports will be introduced
[location: Inventory > Status > Stock Book]

  1. Site Wise Qty
  2. Site wise Qty and Amount
  3. Item Group wise Qty
  4. Item Group wise Qty & Amount
  5. Item wise Qty
  6. Item wise Qty & Amount
  7. Item Costing
  8. Gross Profit Margin
  9. Stock On Hand

New Cube Introduction under Inventory Module

  1. Stock Book: This a new OLAP cube introduced under Inventory Module
  2. Stock Aging Analysis

Following Reports will be Modified

  1. Inventory Status (Radio Button: Costing)
  2. Inventory Valuation (FIFO): Only FIFO option to be changed to Cost Rate

Item Costing Web Report will help to understand - whether outward transaction for an item is done on the basis of ‘as per the expected rate’ defined in the COGS logic defined above.

NOTE: All Ginesys Web Reports except Item Costing and Stock On Hand will be based on Stock Movement New Cube

COGS Process Highlights

  • COGS Status: COGS can be run at any point of time even if Inventory Month is not closed. In that case status of the COGS will be ‘Provisional’. When Inventory Month is Closed then the status of would be ‘Final’
  • Non-Transit Inwards: Calculation will be done based on movement of items across different sites. Inward Movement in COGS is considered only in non-transit location for a site.
  • Transit In /Out Value: All Transit Inward and Outward Cost Value will be same for consignment sites as all inward and corresponding outward will be updated with same source value.
    NOTE: Transaction Value will be as it is, no changes in that respect but Cost Value will be updated by COGS
  • Same Day Inward on Priority: If within a same day any inward entry is done after doing the sale of that item; then at the time of COGS calculation, will consider all inward entries of that day will be considered first.
  • Transaction considered in COGS: Based the calculation logic, cost rate for all the outward transaction’s transactions cost rate will be updated by FIFO / other alternative Rates. In some cases, inward transactions will may also be calculated in FIFO due to non-availability of Cost Rate.
  • Intra Site Transactions: In COGS Rate Picking Logic, no Intra site transactions is being considered
  • Cost Difference Value: If no in-pool entries are found for an item then some of the alternative rates, as mentioned in Flowchart given below, will be considered as mentioned in Flowchart. Due to this, a ‘Difference’ amount will be posted in stock on each month’s last date with a different entry type. Due to this difference value will return provisional value of stock, if any report runs for a period which is not covering complete month. will return provisional value of stock.

UI Changes

  • Front end process of running COGS will be same as it was earlier. However, after this update, Production Cost will be calculated automatically, no choice will be offered at the front end.
  • There is a window added which can be opened by clicking ‘New COGS Migration’ button in this user form. This new window, Stock Value Migration, can be used to match closing stock value of an inventory month (calculated based on old COGS calculation logic) with the opening stock value of the next month (to be calculated based on the new Revamped COGS logic). Migration means earlier Stock Value (of Cost Rate non-transit stock point) calculated in any closed inventory month should be shown as opening value in the next inventory month.


    Follow the guidelines for the same:
  1. Select The Year & Inventory Month for which the Stock Value has to be Freezed.
  2. There are two options either CSV import or Cube selection. [Only Stock Valuation & Stock Valuation GP cube type is permissible]
  3. Now Upload, the data.
  4. After uploading, it will freeze the stock value (click on the Freeze Inventory button), based on the available stock value given by Cube / CSV file.
  5. Once freezed, no manipulation of data can be done. Even to Clear Data from the grid, you would need to click on Un-Freeze Inventory.

Note: The Migration of Stock Value is mandatory if user used to view stock reports based on old FIFO rate logic.

Other Areas of Changes

Price List:

  • In Price List, FIFO Rate option will not be there.
  • Existing ‘Effective Rate’ will consider rate from the Last-In Rate Table for each site and item combination at the time of entry instead of considering the item master Last-In rate.

Real Time Cost Rate update for Outward Transactions:

  • Currently a schedule job updates real-time cost rate before COGS is run, this process will be changed and the rates from the Last-In Rate table will be considered and this will be overwritten by COGS process later by FIFO/Relevant rate as per process flow.

Real Time Cost Rate update for Production Transaction:

  • Currently a schedule Job updates real-time cost rate of Production Process before COGS is run, this process will be changed and component cost will be considered from the Last-In Rate table to calculate the production cost and this will be overwritten by COGS process later by FIFO/Relevant rate as per process flow.

Limitation in Production Cost Calculation:

  • Raw Material cost can be considered till fourth level from Finished Goods.

Finished Goods < Semi Finished Goods < Semi Finished Goods < Raw Material

Bug Fixes

Serial

Dev IDIssue TrackerDescription
130187 N.A.

30187 Release Document module not working properly if user lock days define in User master

Module:

Finance- Approval - Release Document

Reported Version:

11.118.6

Scenario:

  1. Define the lock days of a user as zero (0).
  2. Let the above user, take any random back-dated document and try to release it.
  3. Observe that the user is able to do it.
236391N.A.

36391 Supplier could not be imported from Excel if same city name was provided in both upper and lower case

Module:

Ginesys Web - Admin- Utilities - Data Import

Reported Version:

11.133.5 

Scenario:

  1. Prepare an Excel for suppliers with same city name provided in both upper and lower case.
  2. Try  to import the above.
  3. Observe that the Excel is not imported.
335948N.A.

35948 While importing same unmanged site validation error is getting generated

Module:

Ginesys Web - Admin - Utilities - Data Imports(Unmanaged Site)

Reported Version:

11.133.3 

Scenario:

  1. Create two identical rows in Excel sheet for unmanaged site. 
  2. Try to import that Excel sheet, it will show error type with description.
  3. Observe that the correct line no. is not showing with the error.
437301N.A.

37301 A new Sub Assembly Item is getting inserted at last process, from Copy option at BOM master

Module:

Production - Setup - BOM Master

Reported Version:

11.133.1 

Scenario:

1. Create a new assembly item.
2. Tag this item into a Route Group.
3. Now define BOM for that item with Duplicate option.
4. Select a sub-assembly item of different route from LOV.
5. Populate it.
6. Select that item and press Edit button.
7. Add a new process and select a new sub-assembly item.
8. Delete old sub-assembly item.
9. Press OK and Save.
537603

37603 Duplicate item exists - Message incorrectly displayed while saving new stock audit plan in both create and edit mode

Module:

Inventory - Stock Audit - Plan Stock Audit

Reported Version:

11.133.10

Scenario:

1. Go to Inventory > Stock Audit > Plan Stock Audit.
2. Make a new plan.
3. Try to save the new plan.
4. Observe that the message - Duplicate item exists - appears on saving.
5. It also appears when saving a new plan in Edit mode.
637716

37716 Cannot find Menu Item - Invalid ID - Message is incorrectly shown if user clicks on UDF button when no UDFs are defined

Module:

Sales and Distribution - Outright - Sales Return Wizard

Reported Version:

11.133.7 

Scenario:

  1. Open sales return wizard and ensure that there are no user defined fields. 
  2. Now press on User Defined Field button on the opening page. 
  3. Scan item from Select Item and populate. 
  4. Click Next. 
  5. Now the following error is generated - Cannot find Menu Item - Invalid ID
737951

37951 The option for finding ledgers in Opening Ledger not working

Module:

Finance - Setup - Opening Ledger

Reported Version:

11.134.0 

Scenario:

  1. Go to Opening Ledger.
  2. Define opening balance for some ledgers.
  3. Now try to use the F3 button to find the ledger.
  4. Observe that the ledger cannot be found and the message -  Invalid value for field Find - is seen.
838317

38317 Sub-ledger transactions for all or multiple organization units (OU), showing incorrect opening balance in Sub-ledger register report

Module:

Finance - Register - Sub Ledger Register (All Reports)

Reported Version:

11.133.9 

Scenario:

1. Create a Sub Ledger.
2. Make Transaction to this Sub ledger in Multiple OU. 
   e.g.  In OU1  on 30/09/2017 made a Financial Transaction and
          In  OU2  on 26/09/2017 made a Financial Transaction. 
3. Open  Sub  Ledger Register. Date Range given 01/10/2017 to 31/10/2017 
4. Obseve that the opening balance is displayed wrong. It includes all OUs Transactions made to a particular Sub-ledger.
938384

38384 BOMs with multiple Assembly Items cannot be edited properly

Module:

Production - Setup - BOM Master

Reported Version:

11.134.0

Scenario:

1. Take Two Item which have 5 process (Cutting+Embroidery+Ironing+Stitching+Finishing)
2. Make BOM for above items (take 3 component in Cutting process)
3. Save it.
4. Re-open the above
items and select them.
5. Press Edit Component button.
6. Put 4 at operation seq and Stitching in Process Name.
7. Select one Component in Component Item window.
8. Press OK button.
9. Now Cutting component not get copied in new version.  
1038389

38389 Financial Year cannot be closed

Module:

Ginesys Web - Admin - Organization - Period - Accounting Year

Reported Version:

11.134.0 

Scenario:

  1. Go to Admin > Organization > Period.
  2. Close Inventory Months and Financial Months.
  3. Try to close Accounting Year.
  4. Observe that the Accounting Year cannot be closed.
1138484

38484 Unable to delete item from Item block although user has Level - 3 (modification) privilege

Module:

Production - Job Receipt

Reported Version:

11.134.2 

Scenario:

1. Ensure that the user has Level - 3 privilege.
2. Make an Adhoc Job Order with 4 items.
3. Make Job Receipt and save.
4. Re-open that Job Receipt and try to delete 1 item from item block.
5. Observe that the item cannot be deleted.
1238502

38502 Charge block format was showing incorrectly in Service Invoice [ Adhoc ] report

Module:

Procurement - Invoice - Service Invoice [ Adhoc ]

Reported Version:

11.134.2

Scenario:

1. Go to Service Invoice [ Adhoc ].
2. Retrieve old data.
3. Run Service Bill GST document report.
4. Observe that the charge block is not showing correctly.
1338525

38525 In Job Receipts detail- after tagging Job Order, cursor goes to first row of item information block

Module:

Production - Job Receipt

Reported Version:

11.134.0 

Scenario:

1. Modify some items in the Tag Job Order window.
2. Observe that the cursor goes on first row on after each modification, irrespective of row modified.

1438581

38581 Auto TDS entry from AP voucher is getting insert in default OU despite other OU being provided

Module:

Finance -Voucher - AP Voucher

Reported Version:

11.134.2 

Scenario:

  1. User has two Organization Units. - Kolkata OU and Delhi OU.
  2. Create AP Voucher in Delhi-OU and deduct AUTO TDS from this entry.
  3. Observe that the TDS journal is not showing the entry in Delhi -OU because the TDS entry is getting inserted in Kolkata OU.
1539026

39026 Auto Debit/Credit Note entry for Managed Organization Owned Consignment stores cannot be done

Module:

Procurement - Invoicing - Purchase Debit Note
Procurement - Invoicing - Purchase Credit Note
Procurement - Invoicing - Vendor Debit / Credit Note Reconciliation

Reported Version:

11.133.12 

Scenario:

1. Login to  Managed Organization Owned Consignment store (MS-OO-CM) site.
2. Generate a PI with Auto Debit or Credit Note and save the entry.
3. Go to above modules and try to open the Auto generated entry.
4. Observe that the entry cannot be opened.
1639112

39112 In Incoming Logistic Entry, GRC No. is not showing in Bales Summary tab

Module:

Inventory - Logistics - Incoming - LR

Reported Version:

11.133.10 

Scenario:

Scenario 1:

1. Create a Incoming Logistics entry with Bale details.
2. Tag this Logistics entry into a Incoming Gate Entry.
3. Go to Goods Received Challan Against Order module, Create a entry with gate entry and tag the Bale detail.
4. Re-open the above entry.
5. Now untag the Bales Entry, 
6. Provide the Gate Quantity manually and try to save.
7. Go to the print Barcode button.
8. Exit from Print barcode module and save the GRC Entry.
9. Bales detail has been untagged from above GRC entry.

Scenario 2:

1. Go to Goods Received Challan Against Order module, Create a entry with gate entry and tagged the Bales detail.
2. Re-open the above Entry.
3. Press the delete action.
4. Cancel the delete action.
5. Save the Entry again.
6. Bales detail has been untagged from above GRC entry.
1739303

39303 Menu buttons "Save" and "Delete" getting enabled for posted entries if one click on UDF button

Module:

Sales and Distribution - Consignment - Transfer Out

Sales and Distribution - Outright - Sales Invoice

Reported Version:

11.133.12

Scenario:

  1. Create a Sales Invoice or Transfer Out. 
  2. Post it. 
  3. Now open the posted document and click on UDF button. 
  4. Now close the UDF form. 
  5. Observe that the menu buttons are getting enabled.
1835993

35993 Miscellaneous Issue - GST Document Report is showing blank for Managed Site

Module:

Inventory - Requisition - Miscellaneous Issue

Reported Version:

11.134.0

Scenario:

  1. Open the Miscellaneous Issue. 
  2. Press Change Document Site.  
  3. Execute the Report and it  is showing  blank.
1936761

36761 Track Secondary sites are not appearing in Add Delivery Challan's destination site LOV in Transfer Out in case of transit via sites

Module:

Sales and Distribution -  Consignment - Transfer out

Reported Version:

11.134.2

Scenario:

1. Suppose Site1 and Site 2 are Organization Sites.
2. Suppose Site 3 is a Track Secondary site for which replenishment site is Site 1 via Site 2.
3. Create Delivery Challan for Site 3.
4. Create Transfer Out from Site 1 for Site 2.
5. In the Add Delivery Challan window, To Site lookup is not showing Track Secondary site for which Delivery challan is created.

2037660

37660 In Inventory Valuation (Site wise) report, error is being displayed when input item is selected at Division level

Module:

Inventory - Analysis - Inventory Valuation (Site wise) report 

Reported Version:

11.133.9 

Scenario:

  1. Go to Inventory > Analysis > Inventory Valuation (Site wise) report.
  2. Observe that an error is displayed when its run with input item being selected at Division level.
2138548

38548 The system cannot find the file specifiedError is getting generated while creating database and objects in web database

Module:

Retail Management - Utilities - Web Database

Reported Version:

11.134.3

Scenario:

  1. Go to Retail Management - Utilities - Web Database
  2. Provide all mandatory details.
  3. Click on Create Database with Objects.
  4. Observe that the following error message is displayed:
    Could not load file or assembly 'Microsoft.SqlServer.BatchParserClient, Version=14.100.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2239245

39245 Cannot Save record: ... - incorrect error message displayed while executing Fulfilled by Seller transaction

Module:

Ginesys Web - Sales & Distribution - Retail Sale - Fulfilled by Seller  

Reported Version:

11.134.3 

Scenario:

  1. Open Fulfilled by Seller module.
  2. Input all mandatory fields with billing customer not having GST state and select trade group local or export.
  3. Select items and calculate tax then try to save the transaction.
  4. Observe that it shows a message:
    "Cannot Save record: 
    Reason: Invalid Trade Group. Please select Trade Group LOCAL.Billing customer is not selected or GST state is not provided in billing customer, so you can only select the following trade groups: Local & Export."
2339257

39257 ORA-00001: unique constraint (MOFI.PSITE_POSREPRINTBILLAUDIT_PK) violated - Error message was displayed during sync from HO when PosBill Reprint event is present

Module:

Ginesys Launchpad - Data Sync

Reported Version:

11.133.9 

Scenario:

  1. Go to Ginesys Launchpad - Data Sync.
  2. Attempt to sync with a POS which has uploaded a PosBill Reprint event data.
  3. Observe that the following error message is displayed - "ORA-00001: unique constraint (MOFI.PSITE_POSREPRINTBILLAUDIT_PK) violated"
2439275

39275 Filtering with date in advanced filter is not working in Goods Return from Site if the regional settings are modified 

Module:

Retail Management - Operations - Goods Return from Site 

Reported Version:

11.133.9 

Scenario:

  1. Modify the regional settings to some other country.
  2. Now, go to Goods Return from Site.
  3. Attempt to apply the date filter in the list view.
  4. Observe that it is not working correctly.
2526335

26335 Incorrect financial data being inserted in the database of invoices

Module:

All invoices 

Reported Version:

11.113.1

Scenario:

  1. Create two invoices in any invoice module.
  2. Re-open the invoices
  3. Observe that sometimes the data is becoming mismatched.
2639192

39192 Duplicate rows were being allowed in Plan Stock Audit

Module:

Inventory - Stock Audit - Plan Stock Audit

Reported Version:

11.131.4 

Scenario:

Sometimes due to various internal problems duplicate data used to appear but the issue has been rectified.

2739556

39556 PLS-00306: wrong number or types of arguments in call to 'P_PSITE_PACKET_VOID_UPD' - Error message displayed when syncing "Packet Void" event to HO

Module:

Ginesys Launchpad - Data Sync

Reported Version:

11.135.0

Scenario:

  1. Void a packet in a store.
  2. Sync to HO.
  3. Run Sunc from HO.
  4. Observe that the above error message is displayed.