That’s awesome. Was looking into this and couldn’t find any support for this.
@cmoreland if you find a solution it would be great to share, I would image others could run into the same issue. For now could you create an inventory adjustment, if support is able to help then you could reverse the adjustment. My solution worked.
With this setting:Couldn’t you just complete the order? The status won’t ever change, but you should be able to finish the order.
As a Non-Stock item and uncheck the box that says require shipment possibly? You can’t add items to a shipment.
They used to show up on the Prepare Replenishment screen, but as of 23r1, they seem to be filtered out. My advice is to give them replenishment settings and they will show up.
Jumping in for visibility since yesterday I was asked to look at adding 30 more accounts and remembered this article.
Any word on the subitems and the potential replacement? Matrix Items is not a 1-1 replacement. Not to mention all of the data that is on Open SO’s PO’s as well as history. They whole idea behind it was the ability to not need to set up all the combinations of types.
Has this functioonality been removed? I do not see it in the User Profile anymore. Where would this be in 2023 R1? It’s still there
@cmoreland - I have reached out to your partner to see if they can help shed some light for you. Debbie Debbie, I already an open support case on this.
@maichinger Operations are sorted in sequence by Operation CD. But the lastoperationid is important on the AMProdItem record to indicate which is the last operationid. The LastOperationID value is set automatically when the user is making changes on production order details. The operation CD has no value in code other than sorting for the sequence of operations. I cannot tell from your last comment what the AMProdItem.LastOperationID value is. It must be value 5. Any other value is incorrect. My “last Operation” is 5, but since this was manually created, the last line entered was Operation 15 so it gave the Operation Id #6. It’s not doing any sort of re-numbering. If the Production Order was created from a BOM, it’s not an issue.Hope that helps
@maichinger what is the AMProdItem.LastOperationID for this order? This is the value used during move transaction to determine if the entry is for the last operation. In your case from your screen shot it should be value 5 If it is not 5, then how are the operations being generated on the production order? customization? manually using production order details? 5 is the last step but since the one qwith DBID #6 was added after, it gave it a higher DB#The only labor on the JOB was posted to Operation 20 with a quantityIt created a move transaction which, by definition, if the last step on a labor entry has a quantity and it fulfills the order, a “move” or Inventory Receipt would be created.The Production Order Details show this for each step:It completed all the steps prior to the one on Operation 20, which I would expect. Leaving 2 more to complete.But, since operation 15 has DBID of 6, it created the IN Receipt, and completed the Production Order. It appears that for one function,
I may be a little late to the party here, but why would one Avalara connector in Shopify recognize this and calculate the $.27 and the calculations coming from Avalara through Acumatica not recognize this? we can only ponder! we get rounding errors all the time too, which you’d think couldn’t be possible if both systems are using the same tax engine. All the time. Boggles my mind. What makes this more complex is that it’s per invoice. Not per order. So if you have multiple shipments, each one needs to be charged the $.27. No one seemed to catch that part of this tax. and it needs to be itemized.
On top of that, if the customer is exempt, the “fee” still needs to be charged as this isn’t a tax, it’s a fee per shipment from what I see, not per order. And if the customer is tax exempt, Avalara won’t recognize this either and not charge even the initial fee. This fee is regardless of a customer being tax exempt.
I may be a little late to the party here, but why would one Avalara connector in Shopify recognize this and calculate the $.27 and the calculations coming from Avalara through Acumatica not recognize this?
How about the help files get changed to look at the Prepare Purchase Orders screen as a start instead of the misleading verbiage in help.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.