-
Create a workflow in Advance warehouse management similar to inventory counting workflow
Adding a workflow for stock cycle counting in advance warehouse management which is similar to the counting workflow in inventory management in order to make the process of cycle counting similar to counting journal.
-
Excluding the parent PO line from calculations when calculating the sum of the splitted children PO lines when using delivery schedule functionality.
Excluding the parent PO line from calculations when calculating the sum of the splitted children PO lines when using delivery schedule functionality.
For example: If I am to split a PO line containing a quantity of 150 into 5 separate lines each containing a specific quantity using delivery schedule functionality and then calculate the sum, I want to have the sum of the 5 lines added as the total quantity of the order in the footer section not the total sum of all 6 records.
-
Full blocking is required in a WMS3 enabled warehouse which is enabled for quality order for warehouse processes.
I do want to use WMS quality order processes when my quality order is validated, that is why my warehouse is enabled for quality order for warehouse processes, but I always get this error "Full blocking is not supported here".
My incoming goods should be full blocked with an item sampling of less than 100% and can be put all on a quality location.
So, I need to implement this feature in the WMS because it is logical to have a full blocking feature similar to that of the inventory management module.
-
Creating a direct relation between Commission and discount percentage in sales order line.
The scenario is: the % of commission for sales agent depends on the discount applied in the sales order.
For example:
- If no discount is applied for all items, the commission % is=10%.
- If the discount is between 1 and 10%, the commission % becomes 8%
- For discounts greater than 10% commission becomes 2%.
The % of commission is applied on net price.
-
Posting invoice for product receipts for items which are quality cleared.
- We have a PO which contains a line that I'm using to split its quantities using the registration option from the update line tab.
- Whenever we post the product receipt for a specific part of the total quantity in that line, a quality order is created.
- We've different quality orders and all of them are closed after the item passes the validation tests.
- We only have one quality order which is pending (open).
- However, if we tried to invoice any other quantity related to a previous product receipt, we receive an error stating message "Error: The update has been blocked because the item is in inspection or because there is a conflict between a parameter setup and a policy in a quality association.".
- I receive this error even though the quantity being invoiced is related to a quality order which is closed.
- This issue is causing impact to the business process as the quality inspections takes time in real life, so closing every quality order related to the item just for invoicing a quantity which is already quality cleared seems to be un-realistic.
-
Adding a validation process to prevent duplicate Customer name creation
- Customer name is getting duplicated. System allowing to create new customer with same customer name. So, need to prevent the customer duplicate records.
- If the records are edited and the name field is changed, even if the name already exists or used, the system will allow it.
- This also applies if the records are imported using data entity.
- Can we add a validation process like the one used with the account name to notify the user that the record name already exists to prevent future duplications due to human error while entering the records.
-
Adding security diagnostics before printing reports
- The user wants to know if we can add a security diagnostics option like the one available in any form page to allow specific users to view or print the reports in reference to their security role.
- The reports are for example (Customer/item statistics report).
-
Displaying the variant name in the production orders instead of the description name of the product master.
The All production orders form page as well as the pop-up menu doesn't display released product variant name, but instead the normal description of the product master is used.
The users need to see the variant name displayed in the product name field and needs to make sure that if they changed the inventory dimensions and chose another variant, the system will automatically retrieve the related name not the product master name.
-
Allowing the acceptance of count for Cycle count pending review when the journal name is connected to an approval workflow.
- Is a cycle count supervisor – Set this option to Yes to make the worker a cycle count supervisor. In this case, all cycle counts that the worker performs on the warehouse app will be immediately approved. The Maximum percentage limit, Maximum quantity limit, and Maximum value limit fields aren't considered for workers that this option is set to Yes for.
- Maximum percentage limit – Enter the highest percentage limit that a cycle count can vary from the expected count without requiring approval by a cycle count supervisor.
- Maximum quantity limit – Enter the total quantity that the entered quantity can differ from the expected quantity (in units) without requiring approval by a cycle count supervisor.
- Maximum value limit – Enter the maximum amount that the cost of the inventory can differ from the expected cost without requiring approval by a cycle count supervisor.
-
Adding implementation to the Purchase inquiry report.
The customer is asking if we can add specific fields to the purchase inquiry report.
Additional to the quantity, item number and description, can we add the approver signature and the net amount of the order as well.