Microsoft Dynamics NAV - C/SIDE Solution Development -

Microsoft Dynamics NAV – C/SIDE Solution Development

Locus IT ServicesMicrosoft Dynamics NAV – C/SIDE Solution Development

Lesson 2: Posting Seminar Registrations

Posting Seminar Registrations

Posting Seminar Registrations : In this section the client’s functional requirements are analyzed and a solution is designed and implemented.

Solution Design

The CRONUS International Ltd. functional requirements outline that when a seminar is completed, users must be able to move the seminar registration information into the transaction history, and disable any further modification of this information. This requirement indicates that there must be a posting process that is involved with seminar registrations. When you apply the customer’s language to the terminology of Microsoft Dynamics NAV 2013, this requirement states that users must be able to post the seminar registration information.

Another requirement further clarifies the customer’s business need for a transaction history for seminars that must include the following:

  • Details of participants, instructors, and rooms that are utilized during the seminars
  • Information about additional charges

This information will be the basis for seminar cost analytical and statistical reporting. This indicates that the detailed information about posted transactions must include all the information that is contained in the seminar registration document. Microsoft Dynamics NAV terminology calls these transactions the Ledger Entries.

The final requirement details how the seminar registration information must integrate with the availability planning functionality for instructors and rooms. It also must provide the basis for automatic invoicing of customers.

When seminar registration is posted, the resource ledger entries should be generated for the instructor and room resources. The solution must provide the registration posting functionality that creates transaction data from which users can view history, analyze statistics, and create invoices.

When you introduce posting functionality, you must follow Microsoft Dynamics NAV 2013 standard conceptual, data model, and user interface principles. This means that you must provide at least the journal posting infrastructure that consists of the following:

  • Journal tables
  • Ledger tables
  • Register tables
  • Journal posting codeunits

Depending on the complexity of the processes that you must support, you may have to extend the functionality to also include the following features:

  • Posted document tables
  • Document posting codeunits

The “Data Flow in Seminar Registration Posting” figure shows the entities that are involved in the seminar registration posting process and the data flow between them.

Locus IT Project Management Office
What’s it?