When the count is rejected that might be considered a delete, your role would need Full permissions in order to delete.

@Danny Carter Yes, I agree that assigning Full permission allows the user to update and resubmit the rejected Inventory Count. However, what I don't understand is the logic behind NetSuite treating a rejected Inventory Count as if it were a deleted one from a permission perspective. A rejected count is not deleted—it is simply sent back for correction. Since the transaction returns to the Started status, I would expect the same user to be able to update the count with the correct details and resubmit it, just as they were able to do the first time.

@Vaibhav Patil I agree with you 100% that the full permission should not be needed and according to this documentation what you described should be the native process. Seems that some native actions are coded to require Full even though the action itself is only changing status and rebuilding related count data. docs.oracle.com/en/cloud/…/section_N2299731.html?…