If it is necessary to implement this workflow, it can be done by means of business event. It does not bring about additional load on the release process and adds flexibility and transparency Attached are components of this suggsted business events:1. -SOAllocatedPlandWithExistingOpenShipments GI which shows sales order line allocations created by Move transactions and having open shipment for other order lines2. MULT SHIPMENTS Import scenario . It takes the output of GI as input (the sheet should be renamed to Sheet1) and runs the ADD Order action on the corresponding shipments for corresponding order lines.
@willie98 , as far I see, there is another root cause which leads to the same outcome and is fixed in 21.114:See ‘Known Issues for 2021 R1’ (https://sso.acumatica.com/Main?ScreenId=KI2021R1&PageID=994d89e7-82a1-41eb-8465-9db854ab3c04) AC-203120: If a sales order was created for a customer on credit hold, then the status of the customer was changed from Credit Hold to Active, and then a user tried to create a shipment for the sales order on the Sales Orders (SO301000) form, the system displayed the following error: “Order does not contain items planned for shipment“.Workaround: On the Sales Orders form, put the sales order on hold and then assign it the Open status back. To identify documents affected by the issue, please perform the instructions of the knowledge base article.
See the response in the
@priekenberg40 , this cannot be done that straightforward.Filling of the "SOLineNbr", "SOOrderNbr", "SOOrderType" fields should be the result of the LinkProductionOrders method. Filling these fields through API does not trigger this methodThis might be addressed in future versions, but now you should implement all this logic yourself.You can use the following approach:Extend AMProdItem dac by adding unbound copies of the "SOLineNbr", "SOOrderNbr", "SOOrderType" fields marked as [PXUIField(DisplayName =<FieldName>, Enabled = true, Visible = false)] Add these fields to the .aspx page (they are not visible, so won’t appear in UI) See the attached customization which does (1), (2) Extend the MANUFACTURING endpoint and add these fields there (see MFGEndpointExtensionforLinkSalesOrder.png) Write the logic which calls the LinkProductionOrders method when these fields are filled through API, like this:public class AMProdMaintAPIExtension : PXGraphExtension<ProdMaint> {
@willie98 , I did not test this scenario, but it does not look as an obvious issue to meObviously, first customer status should be settled, then a sales order lines should be enteredIf it is done vice versa, order lines need to be ‘refreshed’ - i.e either have quantity retyped or the order should be put to and removed from hold
@dmzasdf , no the two-step inventory transfers do not create new inventory itemsThey are transfers of existing inventory items between warehouses
@bigil , here is the example of GI which shows the shipped not invoiced account per shipments (and periods) . It shows only shipments which were issued from inventory and not invoiced when the ‘Use Shipped Not Invoiced Account’ as checked in SO PreferencesYou can build a report based on this GI structure if necessary
@bigil , you can’t merge MRP and Purchase Requisitions to make them a single source of purchase orders creationMoreover, if you run MRP while there are open Purchase Requisitions, not only it splits purchase orders, it might lead to a double ordering, because MRP simply does not see these quantities as a potential supplyIf you absolutely need Purchase Requisitions, you can create a customization which ‘merges’ open purchase orders for the same vendor after they are created from different sources.
@roygao40 , please let me know if this is still an issue, If it is, we will create a support case to review
I suggest to check
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.