To answer succinctly, no, there is no mass renumber. The Rename ID function is specific to certain entities, not documents. The document transaction numbers are actually unique IDs since most allow alphanumeric characters, so they may not be sequentially numbered.

The document identifiers can generally be entered manually in most interfaces, but you cannot select the IDs for specific documents when those are involved in a generation process like shipment to invoice. To renumber any documents you would need to update multiple columns in multiple tables, and for that you would have to map, from new to old, all the document IDs. Renumbering can be done since the surrogate keys propagate through the various document and entity relationships, not the ID, but to do so requires a transform map and a developer versed in the 500 schema.

Curiosity about how this could happen with SQL aside, I wouldn't recommend a reentry of every document including so to shipment to invoice, etc. You should handle this like a migration or server crash which is to create the open documents representative of outstanding invoices, vouchers, orders where they are missing, or adjust the outstanding balances, if they exist. You would also have to establish or adjust inventory levels and values as well given the data you can reconstruct. Attempting to recreate all the sales order to shipment to invoice and various purchase order links might be a waste of resources.

To answer succinctly, no, there is no mass renumber. The Rename ID function is specific to certain entities, not documents. The document transaction numbers are actually unique IDs since most allow alphanumeric characters, so they may not be sequentially numbered.

The document identifiers can generally be entered manually in most interfaces, but you cannot select the IDs for specific documents when those are involved in a generation process like shipment to invoice. To renumber any documents you would need to update multiple columns in multiple tables, and for that you would have to map, from new to old, all the document IDs. Renumbering can be done since the surrogate keys propagate through the various document and entity relationships, not the ID, but to do so requires a transform map and a developer versed in the 500 schema.

Curiosity about how this could happen with SQL aside, I wouldn't recommend a reentry of every document including so to shipment to invoice, etc. You should handle this like a migration or server crash which is to create the open documents representative of outstanding invoices, vouchers, orders where they are missing, or adjust the outstanding balances, if they exist. You would also have to establish or adjust inventory levels and values as well given the data you can reconstruct. Attempting to recreate all the sales order to shipment to invoice and various purchase order links might be a waste of resources.