For transactions that include serials or handling units, there are some scenarios where those transactions will be aggregated so that there will be one transaction with part and quantity, and then the details regarding serials and handling units are shown on a sub-level of the transaction.
The main reason for aggregating transactions in this way is that it will improve performance so that for example a material requisition issue that previously created 1000 transactions (and at least 2000 posting lines) when issuing 1000 serials, will now be one transaction with a quantity of 1000 and the minimum number of posting lines is 2. There are also further performance improvements related to transferring transactions to finance, Rerun Erroneous Transactions, Aggregate per Statistic Periods, etc.
As mentioned above, the serial tracking or handling unit details are visible for an aggregated transaction as a sub-level of the transactions. In the detailed Inventory Transaction History page these details are found in the Logistics Detail tab. On the list page for Inventory Transactions History, detailed information is available via a list in a list for each transaction. There is also an expanded view that shows the full list of serial numbers and handling units called Inventory Transactions History Details – this listing page can be used to search and track all transactions for a certain serial number of a part.
The aggregation of serials and handling units have been added to the following flows:
The issue of material requisition that includes serials or handling units will be aggregated into one transaction.
Delivery of customer order that includes serials or handling units will be aggregated into one transaction. The aggregation will happen for all delivery approaches e.g. with shipment, without shipment, with load list, with pre-ship delivery note, etc. The sub-sequent functional processes will still be one transaction per serial and handling unit e.g.:
Creates double transactions for in and out move
for parts on Handling Unit between different locations.
There is a limited number of scenarios where triggering move of handling
units will make aggregate inventory transactions for serials and handling
units:
Note that when moving a handling unit to transit, it will only be the issue transactions, moving to transit, that will be aggregated for serials or handling units. The Receive from Transit will still create one inventory transaction per inventory part in stock record in transit.
Aggregation will only happen when performing Move Handling Unit from Picking, Floor Stock, or Production Line locations.
Further scenarios for aggregation could be added in future releases.
Note that reverse transactions like unissue for the mentioned scenarios will not be aggregated. Such reversal scenarios will require additional development to use aggregated transactions for serials or Handling Units.
There are some scenarios where aggregation of inventory transactions for serials and handling units will not be applied even though they are done in one of the above scenarios. This has to do with the level applied for the inventory value of the part and which cost that needs to be used on the inventory transaction and postings. So, inventory transaction aggregation will not apply if the Inventory Part Cost Level is set to any of the following values:
Then the following values used on the inventory transactions need to be the same for aggregation to happen:
For the aggregated inventory transaction the following information is displayed as details of the inventory transaction: