Share
Report
410Dear Experts,
I’m encountering an error when using the Landed Cost module for a transfer order scenario. I believe I understand the root cause, and it does not appear to be related to the “Allow zero costs” parameter.
Scenario:
- Item A is tracked financially by batch/serial number.
- Batch/serial numbers are not specified until the transfer order is shipped.
- The cost line apportionment method is set to “Amount.”
Behavior Observed:
There are two ways to assign batch/serial numbers on the transfer order line:
- The system allows adding cost lines and allocating by amount without error.
- However, this requires users to split the TO line by batch/serial manually.
Using “Pick” or similar functionality (which I typically use):
- Regardless of whether the TO is newly created, shipped, or received, adding a cost line and allocating by amount always triggers an error.
- Even if the cost line is added after shipping, the system prevents receiving due to the same error.
My Understanding:
Since the apportionment method is “Amount,” the system expects a non-zero total amount. In method (2), because batch/serial numbers are not assigned at the time of TO line creation, the system cannot retrieve the unit cost, resulting in a zero total amount and triggering the error.
However, after shipping, the batch/serial numbers are known, and the transaction displays the correct cost amount. Yet, adding a new cost line still results in the same error.
My Question:
Is this behavior due to incorrect usage, or is it a system limitation/bug?
In practice, users typically do not know which batch/serial will be transferred until the shipment stage. It’s also impractical to split TO lines manually for each batch/serial of the same item.
While switching to “Quantity” apportionment avoids the error, what if users still prefer to allocate costs based on value (Amount)?
All responses (
Answers (
