@hjosephdcm Shipping is a piece of the quick process and by default it will use the Business Date (to the left of your login name) as the shipment date. What process are you using to import? The Quick Process action is an option under import scenarios and then using <Dialog Answer>, the shipment date can be controlled by setting the ShipDateMode to Custom and loading the original ship date. Tagging @BenjaminCrisman so he can confirm.Quick Process Dialog
@vkumar , @Naveen Boga , @leonchau80 I was searching for the same answer to the original question. I found one other setting that affects the Editable Unit Cost field in some cases. If the Vendor has Allow AP Bills Before Receipt checked, then the unit cost is not editable on the Purchase Order Receipt for some items.
I have added parameters to the GI posted above and posted the XML below. Would anyone be willing to run the GI in their environment and report back on the results? I greatly appreciate your consideration and efforts in the community! @Naveen Boga, @kandybeatty49, @Dana Moffat, @aaghaei
Hi @kandybeatty49 Thank you for taking time to take a look at this! I created an SO with mark for PO checked and then used the Create Purchase Order Screen to create the PO.
@kandybeatty49 If you look at the help, the way that I read it, by QTY is the default and that seems to be what comes from when you create a PO from an SO. Default, yes, when creating a new item. Create Purchase Orders ignoring the item setup is not correct and seriously and negatively impacting a standard business process. Any suggestions from Acumatica or the Community?
@Chris Hackett LOL, I did not know what to make of their post - thanks for the explanation.
Thanks @Dana Moffat I just received the case number and I will message it to you. Thanks for your reply!
Follow up: we tried a few more setting changes and ultimately reset the phone, reinstalled Acumatica, and then the app worked.
@Dana Moffat Thank you!
@Laura02 , @enhee0702 Thanks for adding to the thread! Here is the critical issue when refactoring to use the ARAdjust table:If so, how did you handle ARStatementAdjust fields that drive critical calculations in the Customer Statement report, that do not exist in the ARAdjust table? Personally, I think a customization to populate the ARStatementAdjust table for Statement Type = “Open Item” is the better solution.I am guessing it must not be a common request to show adjusting documents on Customer Statements, no matter the statement type. Best,Dan Concannon
@Mle45 There are caveats here. If you use work groups for other purposes, I recommend against this :)I assigned people that should have access to all records to workgroup. I did a cross join to the specific work group and added an or condition that <@me was within the group>.I could not use restriction groups so this was a workaround
23R1 Build 108 was released over the weekend. This is listed as a Fix under Project & Construction in the release notes: AC-276143: On the Journal Transactions (GL301000) form, if a purchase price variance appeared for a project related purchase order and its bill, the journal transaction line corresponding to the PPV amount had no project code, and the system did not create a project transaction.
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.