Product documentation
Business Rules adds functionality in several Microsoft Dynamics 365 for Finance and Operations modules in order to maintain a work flow status to a record.
E.g., when a new supplier is entered in the system, first the bank account number should be checked, then a copy of the ISO9000 certificate must be stored, etc. These steps can be parts of a business work flow.
The basic structure of the business rules can be found in Common > Setup > Business rules.
Rules with different statuses can be defined for:
The user can define the different statuses that a business rule may have, and the conditional transition from one status to another.
Note that business rules can not be applied to order lines.
Business rules can be used with or without blocking reasons.
Important
Blocking Reasons adds functionality in several Microsoft Dynamics 365 for Finance and Operations modules.
Standard Microsoft Dynamics 365 for Finance and Operations has very limited functionality to differentiate between the allowed use of e.g. a vendor, a customer or an item. In most cases the choice between all or nothing does not comply with the requirements.
Blocking reasons are like a matrix with process steps and blocking levels. The blocking reason specifies in which step in the process a warning signal should pop up, or a block should be triggered, or both.
A blocking reason can be specified per:
Note that blocking reasons can also be applied to order lines.
Blocking reasons can be used with or without business rules.
For both Business Rules as for Blocking reasons it is possible to activate a Business event.
Business events provide a mechanism that lets external systems (like PowerAutomate or LogicApps) to receive notifications from Microsoft Dynamics 365 for Finance and Operations applications. In this way, the systems can perform business actions in response to the business events.
For more general information about Business event please visit: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/business-events/home-page.
The configuration keys Business rules and Blocking reasons add functionality in several Microsoft Dynamics 365 for Finance and Operations modules in order to:
The functionality behind the license configuration keys is displayed below:
| Field | Description | Remark |
| Blocking reasons |
Signal or block for: Order (line) entry, Print confirmation, Product receipt, Picklist + registration (WMS I), Packing slip (WMS I), Invoice |
|
Blocking reasons and business rules WHS |
||
|
Business rules |
||
|
Business rules for supply chain |
Blocking reasons on items and customers can be set automatically when an item or customer proceeds to a different business rule status. Example: when the user decides to release an item only for prepacking, the user applies a new business rule status “Prepacking” or similar to this item, and this will automatically set the blocking reason on the item from Blocked for delivery to Blocked for shipment confirmation. Now all open sales lines for this item can be released to warehouse at once, but shipment confirmation is not possible yet.
With the configuration key Blocking reasons and business rules WHS functionality is added to use business rules and blocking reasons in the logistical processes.
Important
Processes:
In general, the most important decision moment is release to warehouse. Basically, once the order is released to the warehouse, no check should be necessary, but in emergencies and non-standard outbound logistics, it is important to controll the process in more detail. In specific cases, the products must be picked but should not be delivered at the customer yet.
The automatic blocking and warning during the packing, shipment confirmation and packing slip, support different scenarios, e.g.:
Note