Although it is not likely to make big changes in financial management, it might be necessary to create G/L entries in a new posting routine.
In the previous chapter, we already pointed out briefly that during posting transactions in Microsoft Dynamics NAV, the actual records are never really inserted in the database. They are used as temporary containers to hold the data during posting. Doing an actual
INSERT would require defining a journal template name, journal batch name, and line no. and could cause locking in the database.
Let's create a new Codeunit that would create a G/L transaction.
After creating the Codeunit, we need to set up the three variables that are the minimum requirement ...