Hi Naren,There is no direct disconnecting method as the demand has already created a PO. However this is possible with the following workaround steps.Create a new demand line from the second activity and connect it to the same PO Now cancel the first PO line from the PO side Go to activity 1 demand line and cancel the demand (Cancel project supply request) Now you have the demand and PO line created only for the second activity.This may not be the ideal solution but I hope you can work around with this. Please check and let me know if that works. RegardsSusith
A severity 2 patch 157008 has been created to address the issue mentioned by @ntaylor :)
Hi,I’m afraid there is no such undo button to recall the deleted records. Also you need to keep in mind that even though it removed order details from customer order window it will still keep inventory transaction records in place RegardsSusith
Hi Simon,Unfortunately there is no other way of checking this information. And I also feel there should have been a track of the business leads came in.Anyhow i will raise this concern with the R&D team and see what they have to offer.RegardsSusith
Agrees with Fredrik on the above option. This can be done
Hi,I think this is possible. Just make sure you remove the record first from SFPPThen go to Part window and remove it from bottom table first, then remove from top table.Try this and let me know if it works RegardsSusith
Hi Alan,As far as I know you cannot invoice individual lines of a customer order separately unless you have connected them to different shipments and then process Shipment invoices OR process each line separately (reserve one and invoice and then move to the next line) . RegardsSusith
The reason for this problem is, when receiving serials, we execute the full receipt process (through PURCH, INVENT, MPCCOM and PARTCA) from A to Z for each serial, including the creation of one inventory transaction and its related postings for each serial. In that case, for each transaction history record there will be at least one record in InventoryTransactionCost and at least two records in MpccomAccounting. Apart from that, if “Weighted Average (WA)” is chosen as the valuation method, then there will also be one WA recalculation done for each serial. This WA recalculation involves finding out about the total company owned stock for the involved part number on the site. Therefore, as a result, it takes longer time to receive 3000 serials through purchase order arrival registration. However, a solution to solve the issue would be to create just one InventoryTransactionHist record for each transaction code involved (instead of creating for each serial), and the minimum possible numbe
Already have an account? Login
No account yet? Create an account
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.