Module 1: DATA AND PROCESS MODEL
Module 2: MASTER TABLES AND PAGES
Module 3: DOCUMENTS
Module 4: POSTING
Module 5: FEATURE INTEGRATION
Module 6: REPORTING
Module 7: STATISTICS
Module 8: DIMENSIONS
Module 9: ROLE TAILORING
Module 10: INTERFACES
Module 11: WEB SERVICES
Module 12: TESTING AND DEBUGGING
Module 13: SQL SERVER OPTIMIZATION
- Lesson 1: SQL Server for Microsoft Dynamics NAV
- Lesson 2: Representation of NAV Tables and Indexes in SQL Server
- Lesson 3: Collation Options
- Lesson 4: SQL Server Query Optimizer
- Lesson 5: SQL Server Query Optimizer
- Lesson 6: Data Access Redesign
- Lesson 7: C/AL Database Functions and Performance on SQL Server
- Lesson 8: Bulk Inserts
- Lesson 9: Locking, Blocking, and Deadlocks
- Lesson 10: SIFT Data Storage in SQL Server
- Lesson 11: SQL Server Profiler
Lesson 1: Prerequisite Knowledge
Prerequisite Knowledge : Before you begin to work on posting, it is important to know about journal tables, ledger tables, and some of the elements that are involved in posting.
Journal, Ledger and Register Tables and Pages
Journal tables, ledger tables, and posting code units are at the core of every posting process in Microsoft Dynamics NAV 2013.
A journal is a temporary work area for the user. Users can insert, change, and delete all records in journals. A journal consists of three tables.
|Journal Template||Journal templates represent transaction types, such as sales, cash receipt, inventory, or reclassification. There is typically only one journal template per transaction type, but users may decide to define more.|
|Journal Batch||Batches may represent various logical subtypes of the same transaction type. For example, users may have different cash receipt batches for different bank accounts or customer groups, or different inventory batches for different locations or item types. Sometimes, batches represent different users who use them to physically separate transactions that are entered by different users.|
|Journal Line||Journal line tables store the information about the transaction itself.|
Lines belong to batches, and batches belong to templates. The “Journal Structure” figure shows how journal tables are related to one another.
The Journal Page
The primary page to enter information into journals is called by the transaction type, and followed by the word Journal, for example: Sales Journal, Cash Receipt Journal, Resource Journal, or Consumption Journal. The page is of type worksheet, and uses Journal Line as its source table.
The primary key of a Journal Line table is a composite key, and consists of the Journal Template Name, Journal Batch Name and Line No. fields. The user never enters information into any of these fields directly. Instead, the Journal page sets the field according to the following rules:
- The Journal page that the user accesses sets the Journal Template Name If there are more templates for the same Journal page, then users must select the template when they start the Journal page. They cannot change the template unless they close and then reopen the Journal page.
- The journal page also sets the Journal Batch Name However, the user may change the Batch Name field at the top of the page.
- The Line No. field keeps each record in the same template and batch unique. The batch page sets the Line No. field automatically through the AutoSplitKey property.
The Journal page lets users enter and edit the journal lines that will later be posted into ledger tables. As long as the lines are in the journal, users can freely change or delete them, and they have no effect until the user posts the journal. Users can even leave the lines in the journal table indefinitely.