Scenario
A user observed that Purchase Order line sequencing no longer matched the originating Purchase Requisition line sequence when creating Purchase Orders through the Order Requisitions page in NetSuite.
The business process involved creating one Purchase Order for each Purchase Requisition, including situations where the same expense was split across multiple requisition lines. Prior to a recent system update, the generated Purchase Order lines consistently followed the same sequence as the originating Purchase Requisition lines.
After the update, the Purchase Order lines were reordered during creation, causing inconsistencies between the Purchase Requisition and Purchase Order line sequences. The user wanted to determine whether there was a way to ensure that the Purchase Order line sequence exactly matched the originating Purchase Requisition.
Solution
Currently, NetSuite does not provide a native configuration that guarantees Purchase Order line sequencing will exactly match the originating Purchase Requisition line sequence when Purchase Orders are created through the Order Requisitions page.
The requisition to Purchase Order generation process may internally reorder or regroup transaction lines during Purchase Order creation, especially following system updates or optimization changes to requisition processing logic.
Available Workarounds
The following alternatives may help reduce line sequence differences:
- Create the Purchase Order directly from the Purchase Requisition record instead of using the bulk Order Requisitions page.
- Use a custom field to manually track the original requisition line numbering and carry that information through to the Purchase Order.
Customization Considerations
Although customization may help store reference values, NetSuite does not fully support maintaining fixed line sequencing across related transactions due to the complexity of transaction relationships.
This becomes more challenging when additional processes are involved, including:
- Item Receipts
- Vendor Bills
- Three way matching
- Consolidated billing
Because transaction lines can split, merge, or reorder throughout the procurement process, maintaining permanent synchronized line numbering across all related records is not supported through standard functionality.
As a result, exact Purchase Requisition to Purchase Order line sequence matching is not currently guaranteed within NetSuite.
-----
If you find this information useful, let us know by reacting or commenting on this post!