mO SharemO Share

Release Note 11.147.8


Control

Release Date

25 July 2019

HO Version11.147.8
POS Version1.147.0
Web Database Compatibility Version1.16
Features & Enhancements

01

Bug Fixes15
Navigation

Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
117860GIN-1112

17860 HO Backup - Data pump utility incorporation will speed up backup in HO

Module:

Ginesys Launchpad - Data Backup

Enhancement Summary:

HO Database Backup utility has been upgraded to use Oracle Data Pump utility for speeding up the backup process substantially.

Scenario:

Please note the following behaviors under different deployment scenarios

Case 1: Database Server and Application Server are same and both are running Windows OS

Backup utility works normally.

Case 2: Database Server and Application Server are different and both are running Windows OS

Backup utility works normally.

Case 3: Database Server and Application Server are different and Database Server is running Linux OS

Backup utility currently will not work in this scenario. This scenario will be addressed in a future release.

How To: Backup your files in HO may be seen for more information.

Bug Fixes

Serial

Dev IDIssue TrackerDescription
123980N.A.

23980 Cannot save record: Reason: Record updated by another user.Error message showing while editing Shipment In Transit

Module:

Ginesys Web - Shipment Tracking - Logistic - Manage - Shipment In Transit

Reported Version:

11.147.5             

Scenario:

  1. Go to Ginesys Web > Shipment Tracking > Logistic > Manage > Shipment In Transit

  2. Edit something in Shipment In Transit

  3. Observe that the following error is showing: Cannot save record: Reason: Record updated by another user. at MAIN.T_INVLGTNOTE_DATAVERSION", line 15 error during execution of trigger MAIN.T_INVLGTNOTE_DATAVERSION'

223947N.A.

23947 Item Description search is not working properly while creating or editing Assortment

Module:

Retail Management - Promotion - Manage - Assortment 

Reported Version:

11.147.5             

Scenario:

  1. Go to Retail Management > Promotion > Manage > Assortment.
  2. Create a new Assortment or modify an existing Assortment.
  3. Add a new row.
  4. Search any item Description from the drop-down.
  5. Observe that all the descriptions in that group (Description 1 or Description 2 etc.) are showing without filtering.
323854N.A.

23854 In GRC, on scanning item present in Purchase Order, a new row is being created instead of increasing that item's quantity

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts 

Reported Version:

11.147.4             

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts
  2. Give all value in mandatory fields
  3. Click on Select Order Items and select a PO.
  4. Then click on Show Items
  5. All items in order will be shown in the list
  6. Scan a Barcode which is present in the Purchase Order.
  7. Observe that the scanned Item is creating another row and not increasing number of existing item.
  8. Also observe that again on scanning the item again then it is increasing number of existing item.
423826N.A.

23826 Purchase Order cannot be selected in GRC if transporter name in Purchase Order is different from the transporter in LR

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts 

Reported Version:

11.147.4              

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts.
  2. Give all mandatory field values.
  3. In Item Details section, click on 'Select order Items'.
  4. Then observe that Purchase Order is not showing in PO list.
522992 N.A.

22992 Issue in item population at the time of GRC Against Order

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.4               

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts
  2. Try to create a GRC against order.
  3. Click on Select Order Item mode.
  4. Select Purchase Order and scan one item.
  5. Then scan another item.
  6. Observe that the second item is replacing the first Item.
622865N.A.

22865 Cannot read record: Reason: An internal error occurred... - Error message is shown while Calculating Charge in GRC Against Order if the Rate has NULL value in Purchase Order

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.4              

Scenario:

  1. Create a Purchase Order with an item having Rate of NULL value.

  2. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts.
  3. Create a GRC against that Purchase Order.
  4. Calculate Charge.
  5. Observe that an error message is showing: Cannot read record: Reason: An internal error occurred during your request!
722823N.A.

22823 Definition of Promotion is not showing properly in Sample Testing 

Module:

Retail Management - Promotion - Sample Testing

Reported Version:

11.147.4              

Scenario:

  1. Create a Promotion Definition.
  2. Go to Retail Management > promotion > Sample Testing.
  3. Perform Sample Testing of the created promotion.
  4. Observe that Sample Testing is not working properly.
822820N.A.

22820 Issue in Charge calculation

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.4              

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts
  2. Proceed to create a GRC.
  3. Select a Term which has more than two Charge amount.
  4. Modify the amount of first charge.
  5. Observe that the charge amount is adding or subtracting by 0.01.
  6. Also Observe that after modification of the second charge amount, the first charge amount is getting changed.
922753N.A.

22753 Cannot Save record: Reason: maximum number... - Error is shown while populating Purchase Order with more than 1000 data in GRC

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.4          

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts
  2. Try to create a GRC against order.
  3. Populate Purchase Order with more than 1000 data.
  4. Observe that an error message is shown - Cannot Save record: Reason: maximum number of expressions in a list is 1000.
1022446N.A.

22446 Cannot Save record: Reason: ORA-12899: value too large for column "MAIN"...Error showing while importing "Assign Organization Site - Vendor/Customer" with Site Name more than 25 characters

Module:

Ginesys Web - Admin - Utilities - Manage - Data Import

Reported Version:

11.147.2           

Scenario:

  1. Go to Ginesys Web > Admin > Utilities > Manage > Data Import
  2. Select Class "Assign Organization Site - Vendor/Customer"
  3. Import with Site Name >25 characters
  4. Observe that the following error is showing: Cannot Save record: Reason: ORA-12899: value too large for column "MAIN"."INT$STG_FINSLOUTAG"."ORG_SITE_SHORTNAME" (actual: 100, maximum: 25). Error Source : Ginesys.Application
1122422N.A.

22422 The charge is not getting calculated during GRC creation in Trade Group selected in Purchase Order is Export/Import

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.2           

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts.
  2. Give value in all mandatory fields.
  3. Click on select order items.
  4. Select a PO in which selected Trade group is EXPORT/IMPORT.
  5. Populate items from this PO.
  6. Then click on Calculate Charge.
  7. Observe that charge is not getting calculated properly.
1222418N.A.

22418"8080:8080" is an invalid integer. Press OK... - Error is shown while printing barcode in GRC if Ginesys Web is running on custom port 

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.1             

Scenario:

  1. Run Ginesys Web on custom port 8080.
  2. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts.
  3. Open a GRC.
  4. Click on Print Barcode.
  5. Observe that an error message is shown - "8080:8080" is an invalid integer. Press OK to ignore and risk data corruption. Press Cancel to kill the program.
1322324N.A.

22324 Reference Site is not populating automatically at  the time of Auto Purchase Invoice creation

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.147.1             

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts.
  2. Create a GRC when 'Allow auto creation of Purchase Invoice and Purchase Return' is enabled in the user profile.
  3. The system will ask you - 'Do you want to generate Purchase Invoice against this Receipt?'.
  4. Click on Yes.
  5. Observe that Reference Site is not populating automatically.
1418228N.A.

18228 New item is not getting created in new purchase rate even if it is defined to create new item for new rate in user profile

Module:

Ginesys Web - Procurement - Operations - Goods In/Out - Receipts

Reported Version:

11.145.11          

Scenario:

  1. Go to Ginesys Web > Procurement > Operations > Goods In/Out > Receipts.
  2. Click on Add button.
  3. Put in the value into all mandatory fields.
  4. Select Create Item option and create an Item with Rate, std Rate, MRP, RSP, WSP.
  5. Then again click on Create Item option.
  6. Create another item with all the same value but only with different change in Rate value.
  7. Click on Create Item button.
  8. Observe that the new item is not created and showing a message - Item already exist.
153746N.A.

3746 ORA-01843: not a valid month... - Error message is shown while saving Recurrence type SMS notification where Date/Time format is MM/DD/YYYY

Module:

SMS Notification

Reported Version:

11.138.4               

Scenario:

  1. Set Date/Time format as MM/DD/YYYY.
  2. Now, go to SMS notification.
  3. Go to, Ginesys Events > Retail > Daily POS Sale.
  4. Try to save the Task.
  5. Observe that an error message is showing - ORA-01843: not a valid month ORA-06512: at "TTLT.DB_PKG_NOTIFICATION", line 236 ORA-06512: at line 1.