Could someone explain under which conditions these postings are created? We have some trouble understanding the mathematics of these postings and I have tried to provoke the system to produce them in a test environment. But so far I have failed. My test cases are built upon serial tracked parts with Weighted Average, Cost per Part or Cost per Condition, and Distribution Orders between sites in the same company. NB that the same parts and sites have resulted both in INTORDTR transactions with ORDTREVAL postings and without such postings.
Page 1 / 1
Hi Kenneth!
I do have the same issue for a customer. According to them it started after upgrading to 24R1. On which version are your customer?
Hi Fredrik,
Nice to see you here! According to my notes, this was an issue that was corrected in 24.1.7. And I also noted some comments from the code (in inventory transaction history if I remember it right), these were removed in later releases:
-- SCDEV-42869, start
-- Movement between sites within the same company.
-- The value_factor_ compensates for the fact that there can be a one-to-many relation between source transaction and destination transaction.
-- Since there can be several serial numbers and/or handling units ID's on one delivery transaction due to transaction aggregation, we need to
-- deal with the fact that the destination transactions will be created that all refers back to the same source transaction.
After the upgrade to 24.1.7, we did not have the same issue, so we concluded this was the correction.
/ Kenneth
Thanks, my customer is running 24.1.4 so it make sense 😊
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.