Limiting the Processing of Transactions Based on the Organization Unit

Regardless of the transaction type, the rights to process a transaction can be limited based on the organization unit of the transaction. You can specify for each workflow step if the processor has to be a member of the transaction unit or either a member of the transaction unit or its sub-unit in the organization structure.

To enable the organization unit-specific limitation of processors on the Workflow Steps screen, set the Allowed Processors setting for the step to Members of the transaction's unit or Members of the transaction's unit and sub-units.

If an organization unit-specific limitation of processors is enabled for any of the workflow steps of a transaction, you have to select a unit for the transaction when you save it. The transaction cannot be saved without a unit. You can select a company as the unit for the transaction but in that case, unit-specific limitation of processors does not apply regardless of the workflow step settings.

Tip: A company can be selected as the unit for a transaction if the transaction cannot be assigned to the correct unit or if the transaction should be assigned to several units instead of just one unit.

Purchase invoices can be approved based on a contract or order regardless of an organization unit-specific limitation of processors even if the unit of the transaction is different from the unit of the contract or order associated with the transaction.

The default processors are assigned to transactions based on the valid settings. If the default processor assigned to a transaction does not meet the processing criteria of the unit that exists for the transaction, the processor will not be added as the processor of the transaction.