web
You’re offline. This is a read only version of the page.
close
  • loyalty fields should be available as placeholders in Commerce related emails

    Currently, the placeholders do not include loyalty programs in commerce related emails. Customer needs to have loyalty fields - Loyalty card, balance, earned / redeemed values on order confirmation. These fileds should be included in the standard email placeholders.

  • B2B customer hierarchy in POS should authorize payment methods for customers

    Current design does not provide solution to authorize certain payment methods for each customer on the POS.

    Example - Customer A can pay exclusively in cash and credit card and all other payment methods will be prohibited. Customer B can use all the payment methods offered in the POS.

    Customer A and Customer B can be in the same organization and on the same billing account but must have different payment authorizations.


    Expected scenario:

    The customer hierarchy should allow user to manage several payment method authorizations per customer.

  • Salesperson field data is not visible on aged balances page in credit and collections module

    At customer level the "Aged balances" page > related information does not display the expected employee name or email address.


    However, on invoice level after going to the "collections" page of any customer > related information, user can see the name, but email address is still not visible. User has to manually take extra steps to see the email under"communicate" tab > transaction to salesperson.


    The related information is a fasttab and cannot be opened for each customer's collection page to see if the salesperson data is present. The details should be present on the Aged balances > related data form itself.

  • Inventory closing date should reflect the date on which inventory closing is performed instead of date of last transaction posted

    Current scenario: When inventory close is performed, the system shows date of last transaction posted instead of inventory closing UPTO date provided by user.


    Expected scenario: The system should reflect inventory closing date for all transactions irrespective of their last posted transaction date.

  • Allocation of stock into a blocked location - WMS app does not consider blocked location

    When a user blocks location by providing the cause of block under "input block" and tries to move the stock to blocked location, the warehouse management app does not prevent the movement of stock and allows a user to complete work. There is no warning/error populated by the app and it is pain for used as each user has to remember what locations are blocked for stock input.

  • When creating 2 or more purchase requisition (PR) lines and adding a new delivery address the default legal entity delivery address pulls through to the PO header

    Current scenario: Creating 2 or more purchase requisition (PR) lines with a new delivery address added by user in line details address section (this being a different address from default legal entity delivery address). When the PR is released to Purchase Order (PO) the new address appears in the line details on the PO, but the default legal entity delivery address pulls through to the PO header (and therefore legal entity address is printed on PO document).

     

    Expected scenario: The system should allow the user to manually override the default legal entity address on PO header with a new delivery address in the line details address section. 

  • User should be able to Change Item Tracking Dimension Group for Released Products

    Customer has many released products with wrong tracking dimension group that need to be updated. The physical inventory has been reduced to zero and user ran inventory closing > change the tracking dimension group > Get error: The new dimension group cannot be assigned. Other financial dimensions apply, while inventory transactions exist.


    There are some scenarios e.g., customer wants to record cost of good sold etc and for that they need to change the financial dimensions. There should be a flexibility for users to change the dimensions.

  • Multi level explosion of SFG does not work as expected

    System should have an option for the multi level cost analysis on SFG for two sites under same legal entity. When there are site A and site B. Instead of exploding/multi level analysis for SFGs that are transferred from site A to either site B or site C, system should show total cost of the SFG at least to be recognised as a cost in the multi level BOM in site B.

  • Cannnot assign Project ID to Purchase order line or header if user forget to add the same at the time of creating Purchase order

    When a user does not assign related Project ID while creating a purchase order, system disable the fields after the order is created and user cannot assign the same either on line or header level.


    It is frustrating as the user has to delete the PO and recreate the same to assign the Project ID. Current design checks if there is a project ID assigned and if false, system does not allow to edit.

    This functionality should be fixed to manage time consumption and minimize inconvenience.

  • Approved vendor functionality not working on purchase requisitions

    A vendor is approved for an item and visible on the approved vendor list on item master. When a purchase requisition is created with respective item, it is expected that approved vendor associated to item gets selected on PR line.

    However, when user click on dropdown button and select approved vendor from list, they receive warning as -"Vendor 1003 is not allowed for the selected purchase requisition line. Vendor must be either primary vendor or qualify for the best price."

    The functionality does not work in above scenario. It is expected to get the approved vendor list on Purchase requisition line when user does not provide single vendor on primary field.