Open sschuh opened 6 months ago
@sschuh all these methods seem to depend on one or more global variables to be set, making those methods as public increases the risk of those methods failing or returning undesired results. Can you please explain the use cases for better understanding?
Hi, sure.
We need some different logic on specific items. (called "Sales Display Items")
The user taps in "Quantity to Assemble" with value 10 in the Assembly header and start posting the document.
We now need to post the document 10 times with a "Quantity to Assemble" with value 1. (Serial Tracking) Th approach is, that we can match the assembled item and it's components in the item ledger entries.
If you disagree with this change, we need to search for another solution.
@sschuh sounds like an improvement that we should provide to the posting process. Can you give us more details about the issue you are trying to fix by us exposing those mentioned methods? This is what I have tried
@ChethanT Your examples work fine.
But here is our scenario: Assembly Item "Sales Display" (with Serial Tracking) Components: 10x Red Wine 10x White White
The assembly order has been posted with 2 serial items.
You can see two output lines. And the cumulated consumption of 20x Red Wine and 20x White Wine.
The cumulated consumption is our problem.
We need following result:
One Ledger Entry for the output item with serial no. SER00001280 One Ledger Entry with consumption of 10x Red wine One Ledger Entry with consumption of 10x White wine
We need this structure for tracking the components that belongs to SER00001280.
One Ledger Entry for the output item with serial no. SER00001279 One Ledger Entry with consumption of 10x Red wine One Ledger Entry with consumption of 10x White wine
We need this structure for tracking the components that belongs to SER00001279.
Describe the request
hi,
please make these functions accessable:
Additional context
We need this to do some extra stuff with Assembly Orders. Internal work item: AB#504093