Skip to main content

#msdyn365bc - Copy journal function on Posted General Journals.

Hi Readers,

The 2020 release wave 2 delivers a set of features which are requested by customers and Partners. In this article we will discuss about one of such feature which was added in Business Central based on Idea summited.

In this article we will discuss about that feature as a process and technically. 

After this article I hope you will be able to use and also understand how to technically handle customs with respect to General Journal.
This has been one of the most common requirement to see history of Journal Entries. With this feature will enable to have an history of General Journal like we have for documents in business central like posted purchase or sales documents.

Let's Understand the process first - 

1. To Enable this feature open General Journal Batch and enable - Copy to Posted Jnl. Lines In General Batch in batches.



2. Lets create journal lines.



3. Now Lets Post Journal Lines.


4. After Posting is successful open Posted General Journal and you will be able to see Posted Entries.



5. You can use Find Entries to see related entries after posting of General Journal. 


6. In Posted General Journal, You can choose action to Copy Selected Lines to Journal on selected entries. This action will  create a copy of a general journal line or a batch with same or opposite signs (a reversing journal), a different posting date or document number. 


7. You can see Copied Entries as shown below.


8. In Posted General Journal, You can also choose action to Copy G/L Register to Journal. This action will  create a copy of all general journal line in Selected Register to a Template, Batch with same or opposite signs (a reversing journal), a different posting date or document number. 


9. You can see Copied Entries as shown below.



Why this feature?
  • This feature will help you if you mistakenly posted incorrect General Journal Lines.
  • This feature will allow you to see history of what was posted in General Journals.
  • You can enable that to a selected or all General Journal Batch. 

Technically new objects are added to support this feature (in Base App) - 
  • Table 181 - Posted Gen. Journal Line.
  • Table 182 - Posted Gen. Journal Batch.
  • Page 182  - Posted General Journal.
  • Page 185  - Posted General Journal Batch.
  • Codeunit 181 - Copy Gen. Journal Mgt.
With respect to coding, During Copy system uses Transferfields. Any time you add a field using Table Extension then make sure to add that field in posted tables with same id for keeping history of that field.

Hope you like the feature. Let me know your views as comment to this article.

Regards,
Saurav Dhyani

https://www.sauravdhyani.com/

Comments

Post a Comment

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.