Share This Post

NAV Updates

Dynamics NAV Batch Posting Creation

In this Article, we are going to discuss the Dynamics NAV Batch Posting creation and its Sales & Purchase Batch Posting Issue.

Microsoft Dynamics NAV 2018 introduces a new method for NAV Batch Posting for multiple invoices at one time. Simply go to your list view and then hold down the Ctrl key and select the invoices you want to post and then from the ribbon at the top of the screen, select ‘Post’.

This works for orders, invoices, and credit memos.

NAV Batch Posting

works for orders, invoices, and credit memos.

A pop-up message will show how many invoices will attempt to post and ask you to confirm.

pop up message

pop up message

If all invoices can post, then you will see the following message:

All invoices post popup

All invoices post popup

If any of the invoices can’t post, then you will see an error.

The same process works on the purchase side.

purchase side

Here is an example of an error message: There was one Purchase Invoice where no ‘Vendor Invoice No.’ was entered.

error message

error message

Click ‘OK’ and a page will open to tell you more about an error(s) encountered.

more about the error(s) encountered

more about the error(s) encountered

Batch Post Production Consumption

If the flushing method is Manual, you must post the components manually, using the consumption journal.

To post-consumption for one or many production order lines

  1. Enter the Consumption Journal, and then choose the related link.

2. Fill in the fields with the production order data and the consumption data. Select a field to read a short description of the field or link to more information.

The warehouse location is that where the components are stored is set up to use bins but does not require pick processing, assign a bin code to the journal line to specify where the items should be taken from in the warehouse.

3. Choose the Post action to post the consumption. The related item ledger entries are reduced.

Batch Post Output and Run Times

The output quantity represents the work progress in the form of finished quantity.

To post output quantities for one or many production order lines

  1. Enter the Output Journal, and then choose the related link.

2. Fill in the fields with the production order data and the output data. Choose the field to read a short description of the field or link to more information.

3. If the operation has been completed, select the Finished field.

If the warehouse location is that where the items should be put away uses bins but does not require put-away processing, assign a bin code to the journal line to specify where the items should be placed in a warehouse.

4. Choose the Post auto post the operations. The output quantity will be posted. The item is now available for shipping.

To post runtimes for one or more production order lines

The runtime represents the work progress in the form of the necessary working time.

  1. Enter the Output Journal, and then choose the related link.

2. Fill in the fields with the production order data and the output data.

3. If the operation is completed, select the Finished field.

4. Choose the Post action to post the time spent per operation. Capacity ledger entries are updated for the used work or for machine centers.

Sales & Purchase NAV Batch Posting Issue

Example

1. The Batch Processing Parameter Map already exist. Identification Fields and the values: Record ID= Sales Header: Order,”

2. When I try and post the batch, nothing happens. Also, if I try and invoice of an individual order, it always posts to a fixed date.

Microsoft object Impact for the fix is code units – 1371|1372|1380.

These core units have been referred in two code units – 88|98

Object Impact for fix issue – 88|98|1371|1372|1380

Codeunit

88             Sales Post via Job Queue
89             Purchase Post via Job Queue
1371         Sales Batch Post Mgt.
1372         Purchase Batch Post Mgt.
1380         Batch Processing Mgt.

If these objects are not modified in the customer database, we can replace these objects from CU09 database otherwise compare the listed objects to merge changes.

This actually does not fix the problems as legacy data exist which will be required to be cleared.

Additionally – User have to delete data from table 52 & 53.

These tables are used to store information that stores batch processing parameter and Map.

Table 52 – Batch Processing Parameter & the Table 53 – Batch Processing Parameter Map

Conclusion

In this Article, we dealt with Dynamics NAV Batch Posting Creation in various fields and its sales and purchase Batch posting issue resolved with an example.

Share This Post

Leave a Reply

avatar
  Subscribe  
Notify of
Skip to toolbar