Print log journal
This procedure is used to print and approve log journals. When the journal is approved, it will be recorded in the accounting. The journals are available as different list types. It is also possible to approve the journals without printing them. This is done by clicking Load and then clicking the button Approve. In connection with approval of the journals, the transactions will be recorded in the accounting. To automate approval of journals, you can also schedule this in the procedure Posting of logs.
At the very bottom of the Selection tab, you can see information regarding how many transactions are available to approve per log. It is also possible to see how many transactions contain incorrect posting. These transactions are not shown in the journal but under the Warnings tab.
If you have transactions in more than one accounting period, the system will automatically separate these journals per accounting period.

Each journal type is recorded in a separate voucher number series. A setting for this is configured in the Voucher number series/Journals procedure. The journal contains a detailed journal showing posting per transaction, and it also contains a total accounting order which totals the entire journal per account/dimension/transaction type/order number/specification. It is the total accounting order which forms the voucher in the accounting.

Records which cannot be posted (where posting method is missing for the transaction) are shown under the Warnings tab. The error code informs about the primary cause of why the transaction could not be posted. What causes the warning is shown in red text.
The following warnings can be issued:
Warning | When does this warning appear? | Action |
---|---|---|
1. Transaction type is missing in posting method | This is shown when there is a transaction where posting method for this transaction type is not registered. | Register a posting method for this Transaction type in the procedure Register posting method. |
2. Part type is missing in posting method | This is shown when transaction type exists for the posting method, but there is no posting method with the part type concerned by the transaction. | Check which part type the transaction concerns and check if there is a posting method that handles this part type in the Part type field in the Register posting method procedure. If the part on the other hand has got an incorrect part type, you correct this in the Part register. |
3. Control method is missing | This is shown when transaction type and part type exist for the posting method, but there is no posting method containing the control method for the M-part which the transaction concerns. | Check which control method the M-part transaction concerns, and check that there are posting methods which handle this control method in the field Control method M-part. |
4. Setting for packaging part is missing | This is shown when transaction type, part type, and control method, exist for the posting method, but there is no posting method which handles the setting Include packaging. | Check if the transaction concerns packaging. If so, the existing posting methods must be changed so they also handle packaging. This is done by selecting Yes for the setting Include packaging. If packaging should be separately posted, you have to register a separate posting method for packaging and choose Only packaging in the setting Include packaging. |
5. Event type is missing in posting method | This is shown when transaction type, part type, control method, and include packaging, exist for the posting method, but there is no posting method which handles the event type which is concerned by the transaction. | Check which event type the transaction concerns, for example stock increase or stock decrease. Check the posting method for the transaction type in question. Perhaps you have by mistake unchecked the setting Reverse posting on reversed event type? |
6. Manufacturing order is not posted in full | This is shown when transaction type, part type, control method, include packaging, and event type, exist for the posting method, but the manufacturing order has not been posted regarding stock transaction log, manufacturing order log, and/or price change log. | Make sure the posting of stock transaction log, manufacturing order log, and price change log, has been posted regarding the manufacturing order in question. Otherwise it is not possible to calculate the calculation difference. |
7. Other term is missing in posting method | This is shown when transaction type, part type, control method, include packaging, and event type, exists for the posting method. Manufacturing order has posting concerning stock transaction log, manufacturing order log, and/or price change log, but there is no posting method which handles what has been entered as Other terms for the posting method. | The transaction has a term which does not exist among the terms you have entered in the posting method for the transaction type in question under Other terms. Complement the posting method so the terms is included in the Other term. It might also be an incorrect product group etc. for a part which needs to be corrected in the Part register. |
Tip!
When you have attended to the warnings, you need to do a new posting of logs before it will affect the journal.

In the column Suggested posting method, the system shows which posting method is "best match" to post the transaction. This information can be useful if you want to find incorrect settings for posting methods. It is also possible to go to Register posting method via link, to check how the posting method is registered. Maybe you need to adjust this posting method or register a similar posting method which takes care of the record which did not become posted.
Please note! You can add more columns under the Warnings tab via the button More info, for example Product group, Part code, and Part category. This can provide you with additional help to for example find the cause of warnings which have to do with other terms that do not match.
Do not post
By marking the Do not post setting and saving, the transaction will not be recorded. This function should be used with caution since incorrect use of the Do not post setting, can cause differences between logs and balances in the accounting.