Sales Report for particular product group was appear blank

Sales Report for particular product group was appear blank

Product Version:

iVend 6.6 integrated with SAPB1


Problem statement:

Sales Report for particular product group was appear blank


Symptoms:

NA


Resolution/Work Around:

Check product group id if found comma on id removed the comma from product group code through SAP.


Recommendations/Suggestion:

Suggested to not use commas on product group id.


    • Related Articles

    • Error while creating a new product group with Business Central

      Environment: iVend 6.6 Patch 7989 Problem Statement: Loyalty plans were created correctly but adding the products involved in the discount does NOT allow us to create a new group of products. Scenario: Client created loyalty plans in iVend system but ...
    • Blank CSV file while exporting Sales Report

      Environment: iVend 6.6 Problem statement: When trying to export from the Sales Report to CSV, the system producing a blank CSV file. Symptoms: The process appears to work on all other reports and also works like on Excel Export. Steps: 1. select ...
    • iVend Stock transfer Code field appear blank

      Product Version: 6.6 integrated with Sap B1 Problem Statement: Customer generated stock transfer from General warehouse to retail warehouse on SAP however at the time of receiving stock transfer on store code field appears blank. Proposed Solution: ...
    • Sales Reports between items for a particular date range.

      Environment : iVend 6.6 with SAPB1 Problem Statement : Generate Sales Reports between items for a particular date range. Resolution/Work Around : Sales reports can be generated from the Management Console. Management Console >>Reports >>Sales>> Sales ...
    • Inventory Audit report showing Blank After Store Re-initialization

      Problem Statement Inventory Audit report showing Blank After Store Re-initialization Investigation Upon reviewing the issue, it was found that the inventory log data was missing in the respective SQL table. After further inspection, we identified ...