Transfer to the unposted purchasing documents
After the workflow system has released the purchasing document, it is transferred to the Breeze interface. A plausibility check is then performed in the interface. If the check is successful, an unposted purchasing document is created.
If the plausibility check failed, the document is set to the status "error" and the error message is appended to the respective position in the Json structure of the document. Now the document is again waiting to be picked up and corrected by the workflow.
The unposted purchase document is created with all data from the Json structure. If attachments from the process have been attached, these will also be transferred to the unposted document.
Responsibility center and VAT business posting group
If the document header contains responsibilityCenter (responsibility center) and vatBusPostingGroup (VAT business posting group), they are applied to the unposted purchasing document: both on invoices and credit memos, the VAT business posting group on purchase orders (purchase orders already took over the responsibility center). A blank value keeps the default Business Central sets from the vendor or the user setup. The VAT business posting group of the header is the default for the lines; a group given on a line takes precedence.
The plausibility check reports
- a responsibility center or VAT business posting group that does not exist in the system,
- a responsibility center that the user under which the Breeze Interface processes the document may not use on purchase documents according to the user setup (or the company information).
Order confirmations do not change either field on the existing order.