Unable to receive more than 3000 serials-valuation method WA

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 number of records in InventoryTransactionCost and MpccomAccounting.

As a suggestion I would recommend to set the inventory part cost level to either "Cost per serial" or "Cost per lot/batch"

Have you considered using 'Receive' Option instead of 'Receive with Serials/Lots' when receiving your Purchase Order? This way you can Receive your Stock in to a 'Arrival' type Location and later Split the Stock in to Serials.

I've tried this myself with a 'Weighted Average Tracked' Serial Part (in APPS10 Regional TEST CMB. USER KANDLK, Part DW TP 200), it only took couple of Seconds to Complete the Receipt process, and about 1 Minutes to Split my 3000 PCS in to Serials.

Let me know if you need further help with this.

I checked with PD and according to them 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 number of records in InventoryTransactionCost and
MpccomAccounting. But, according to product architect it is not an easy task to
solve this in the standard product, because it requires a large-scale
restructuring of the whole process. Therefore it would have to redesign the
InventoryTransactionHist LU and add a new sub-LU to make it possible to create
an inventory transaction for a collection of serials instead of just one
serial. Then it would have to pass the collection of serials through the whole
process, something that will be quite challenging. Therefore, it is definitely
a development from the size and complexity perspective and would be suitable to
consider it in a core development project for a new release.
Therefore
their suggestion also to set the inventory part cost level to either "Cost
per serial" or "Cost per lot/batch"