Wednesday, 20 June 2018

Sales Invoice Creation thorough Jobs and resources.

Sales Invoice Process

Create Masters

Job Card

To create New Job, click on Financial ManagementàJob ( Click on New Button)

Job Card

Mandatory Fields on Job card
  • ·         No.
  • ·         Description
  • ·         Bill-to Customer No. (Bill- to Name, Bill -to Address should flow from Customer Card)
  • ·         Invoicing Type = FMB
  • ·         Job Posting Group = REV-ON

Attach 16 Dimensions on Job Card

We attach 16 Dimensions on Job card so that they can flow on Sales Invoice.
To attach 16 Dimensions, click on Dimensions button available under Navigate section of Job header.

Job Card

Dimension Card

Create Job Tasks

If there are multiple sub contracts available under Main contract, we create multiple Job tasks (per one subcontract). In NTI case, we need to create only one Job task per job.
  • To create Job task, click on Job Task Lines button under Home section

Job Task Create
Job Task Lines
Mandatory fields on Job Task Lines
  • ·         Job Task No: = Job No
  • ·         Description = Project Name

Create Resources

To Create New Resource, click on Resources à New Button
Resource Card
Mandatory Fields on Resource card
  • ·         No: = Work type code
  • ·         Name: = Work type Name
  • ·         Type: = Person
  • ·         Base Unit of Measure: = PH
  • ·         Gen. Prod. Posting Group: = ( as per nature of resource)

Transactional Details

Create Job Journal Lines

For each line of invoice, we need to post separate Job Journal Line.
To create Job journal lines, click on Departments àJobs àTasks àJob Journals
Job Journal
Job Journal Lines

Mandatory Fields on Job Journal Line (Please arrange fields on below sequence for your convenience)
  • ·            Line Type: = Contract
  • ·         Posting Date: = Sales Invoice Date
  • ·         Document No: = Auto Populate
  • ·         Job No.: = Project Code
  • ·         Job Task No.: = Project Code
  • ·         Type: = Resource
  • ·         No.: = Work type Code
  • ·         Description: = Work Type Name
  • ·         Description2: = (You can keep it blank)
  • ·         Unit of Measure: = PH
  • ·         Quantity: = (As per detail)
  • ·         Unit Price: = (As per detail)
  • ·         Line Amount: = Auto populate
  • ·         Gen. Bus Posting Group: = Gen
  • ·         Gen. Prod Posting Group: =  ( Auto populate from Resource card)
  • ·         Sub Contract: = (should be unchecked)
  • ·               Task type: = Main Task
   If there are 3 lines for a invoice, you need to create 3 lines in one go, select 3 lines and post them together.

      Create Sales Invoice through Job Planning Lines
        
          The lines which are posted from Job Journals will be stored in Job planning lines
          To open Job planning lines, click on Job à Job Task Lines

Jobs
       
     Select a Job task and click on Job Planning Lines
Job Planning Lines
     Click on OK.
Sales Invoice
      Note: Sales invoice is generated by above process, you can find generated sales invoice in list.
      16 Dimensions have been assigned on the invoice by Navision.


Tuesday, 22 May 2018

Installation of Dynamics NAV 2016

How to Install Dynamics NAV 2016 Client 

This guide will show you how to install the Dynamics NAV 2016 Client with or without the Development Environment.


1. Navigate to the installer, right click and select “Run as Administrator”.

2. Click “Next >”.

3. Click “I accept >”.

4. Click “Choose an installation option”.

5. Click on “Customize …” below the “Client” option.

6. If you just want the Client installing, click “Next >” and go to step 7.
If you want the Development Environment as well, carry on to step 6a
.

6a. Expand the Client option >> click on the dropdown for “Development Environment (C/SIDE)” >> click “Run from My Computer” >> click “Next >”.

7. Here you can select what service Dynamics NAV 2016 will connect to. If you want to skip this step if you already have it set up, by filling in: Server Name, Service Name & Client Services Port. If you have Help Server connections details as well, carry on to step 7a. If not, click “Apply” and skip to step 8.

7a. Scroll down and enter the Server and Port for your help server. Then click “Apply”.

8. Installing.

Note: A command prompt screen may pop up for a brief moment. No action is needed.

9. The Installation will then be complete and you can click “Close”.


Tuesday, 6 March 2018

Navision Objects

Navision Object

Basic Objects in MS Dynamics NAV

   There are seven objects in Navision. which is used by developers, as a developer you can edit existing objects and create new objects that is based on that are already in the system.

Seven objects in NAV are:
  1. Table: It describes how data is stored in the database and how it is retrieved. table is the most important object because most objects types are depend on them.
  2. Page: It enable user to view, add, change or delete record in a table.
  3. Report: It display and print summarize information. Use report to print documents such as invoice.
  4. Codeunit: It is an organized block of programming code, it manage by single process. Codeunits are similar to containers for code. it can hold functions that are repeatedly used throughout large application projects. 
  5. Query: It Defines relational data model for efficient querying of underlying Microsoft SQL Server database.
  6. XMLPort: XMLport object that can use to export data from or import data into Microsoft Dynamics NAV 2016. XMLport can manipulate the data in XML format or text format.
  7. Menusuits: MenuSuites contain menus that enable users to navigate and perform actions in the Microsoft Dynamics NAV Windows client.
Object Designer 




See more: Navision Objects 


Monday, 19 February 2018

#1 Dynamics NAV - Table Object

Table Object In NAV 2013 R2

Table Overview

         Tables are the most fundamental objects in Microsoft Dynamics NAV. They store records that are collected through pages. for example customers, sales, and inventories. These records are then presented to users through pages and reports.

About Table
       Records in Microsoft Dynamics NAV databases are stored in tables. A table can be visualized as a two-dimensional matrix, consisting of columns and rows. Each row is a single record, and each column is a field in that record.
    A table consists of table data and the table description. The table data contains the actual records and their fields. The table description specifies the layout and properties of the table and the fields.
     The table description is not directly visible to the user. When a developer creates a table, he or she assigns the table name, ID number, and fields. This establishes the table description.
      Field characteristics, such as field name, ID number, data type, and initial value together with the primary and secondary keys (used to sequence data) are also part of the table description.

    The table description contains properties, triggers, fields, and keys. The “Table Components and Their Relation” figure shows components of the table description and how they are related.
Table Description


Properties of Table

  Field No, Name, Caption, CaptionML, Datatype, Field Class, Min-Max Value, Table Relation, EDT(Extended data type), Width, etc
  this are important properties to work on table object.

Data Type

BLOB, Boolean, Code, Date, Decimal, Integer, Option, RecordID, Text, TableFilter, etc.

How to create Table in Object designer:

Steps:
  1. Go-to tool menu: > Click Object Designer> Click table object> New table
  2. In table window appears has fields that enters data in fields i.e
               1) Field No.
               2) field Name 
               3) Data Type & Length
               4) Description 
   and Save Table ID & Table Name.

Customer Table in Table Designer

Customer table and its Property 

Save the ID of table in between 50,000 to 90,000 any where save. this are customize tables & other table ID's are standard tables i.e parent level tables OR predefined tables.

Save the table and run it(Ctrl+R)


Saturday, 10 February 2018

Its all About Navision !

About Microsoft Dynamics NAV...

Defination: NAV is an ERP software suit for midsize organization, The NAV system offers specialized functionality for manufacturing, Distribution, Government, Retail, & other industries.

Versions of Navision:
  • Dynamics NAV 2009: 2009, 2009 R2
  • Dynamics NAV 2013: 2013, 2013 R2
  • Dynamics NAV 2015: 2015
  • Dynamics NAV 2016: 2016
  • Dynamics NAV 2017: 2017
  • Dynamics NAV 2018: 2018

NAV 3- Tier Architecture:

1) Roletailored Client: RTC is the client tier, which includes a NAV windows client and web client.
2) Nav Server: Nav Server is the middle or server tier, which managing all bussiness logic and communication.
3) SQL Server: SQL server is the R2 database components, is the data tier. the database tier consists of an application database.

NAS (Navision Application Server)
   NAS is a .net-based windows service application that manages communication between NAV Client & NAV database is SQL Server.

C/SIDE and C/AL:
  C/SIDE - Client/Server Integrated Development Environment
        C/AL is the programming language that used within the development environment for Microsoft Dynamics NAV, and the development environment is called as C/SIDE.  
  C/AL - Client/Server Application Language 
        C/AL is a database specific programming language and it primarily used to retrieve, insert, and modify the records in the dynamics NAV Database.

Object Designer 

       Object designer area which contains 7 objects through development and access to all the application object.
There are 7 object in NAV
        1. Table                                          
        2. Page                                           
        3. Report                                       
        4. Codeunit
        5. Query
        6. XMLport
        7. Menusuit

RoilTailored Center | RTC Client Side 

Object Designer










Tuesday, 6 February 2018

Microsoft Dynamics NAV installation & Configuration

MS Dynamics NAV Installation & Configuration 

Installation Of NAV

few steps of NAV installation before that pre-requisite Software & Hardware 
Pre-Requisite of NAV 
  • Supported OS: Windows server 2008 R2, Server 2012, Windows 7 service pack-1, Windows Ultimate, Windows 8 & 8.1, Windows 10 Professional.
  • Hardware Resources: 1 GB- RAM & 30GB Hard disk.
  • Report: RDLC, MS Visual Studio, SQL Server Builder for Creating & editing RDLC reports layouts, Word 2013 to create word report layouts. 
Installation Steps:
  1. Verify that computer system H/W and S/W requirement.
  2. Locate the NAV 2013 R3 setup.exe file in computer and double click on it.
  3. Choose Next
  4. Then to accept the License terms.
  5. Choose an installation Options (Client, Server, Developer & Custom).
  6. Choose Customize the installation.( Verify the errors & fix them, Click Next)
  7. Choose Next to open the specify parameters page in this any field that has an asterisk(*) it is required parameter. after that click - OK.
  8. Installing Dynamics NAV is in process.
  9. When setup is finished, click Finish & close.
Configuring Microsoft Dynamics NAV Server in Setup: 
  You can configure Microsoft Dynamics NAV Server when running Microsoft Dynamics NAV 2009 Setup. You must first select Microsoft Dynamics NAV Server as a component to install. To do this, select one of the following Installation Options that includes Microsoft Dynamics NAV Server.
  • Server Option installs Microsoft Dynamics NAV Server without any other components.
  • Developer Environment Option installs Microsoft Dynamics NAV Server with other components that are used for developing client applications.

After you specify an installation option or customize your component list, the Specify parameters page is displayed. Click Server to open the Installation Parameters page. The underscore indicates that this component is configurable. 

Settings
The parameter list that you see in the Specify parameters pane depends on which components you have selected for configuration. The following parameters pertain to Microsoft Dynamics NAV Server.
ParameterDescription
Server Name
The computer running Microsoft Dynamics NAV Server.
Server Port
The listening TCP port for Microsoft Dynamics NAV Server, which becomes part of the server's URL.
Default value: 7046
Valid range: 1-65535
SQL Server
The computer running SQL Server.
SQL Database
The SQL Server database.
Web Service Port
The listening HTTP port for Microsoft Dynamics NAV Web services.
Default value: 7047
Valid range: 1-65535
Click Apply when you have finished entering values to return to the Specify parameters page in Setup.
After you finish running Setup, you can modify Microsoft Dynamics NAV Server settings by editing the CustomSettings.config file.

Configuring Microsoft Dynamics NAV Server After Installation
Settings in the CustomSettings.config File
The CustomSettings.config file is an .xml file that you can edit with any text editor. It contains the following settings. Quotation marks are required for all values.
SettingDescription
NetType
The network protocol used to access the database.
Default value: Default
Valid values: Default, NamedPipes, Sockets
DatabaseServer
The computer running SQL Server.
DatabaseInstance
The name of the SQL Server database instance to connect to.
DatabaseName
The name of the SQL Server database.
ServerInstance
A name that identifies the instance of Microsoft Dynamics NAV Server.
Default: DynamicsNAV
You may need to modify this value if you have more than one Microsoft Dynamics NAV Server instance installed on a single server computer. For more information, see Walkthrough: Accessing Multiple Microsoft Dynamics NAV Databases from a Single Microsoft Dynamics NAV Server Computer.
ServerPort
The listening TCP port for Microsoft Dynamics NAV Server, which becomes part of the server URL.
Default value: 7046
Valid range: 1 - 65535
WebServicePort
The listening HTTP port for Microsoft Dynamics NAV Web services.
Default value: 7047
Valid range: 1 - 65535
WebServiceSSLEnabled
The parameter for whether SSL (https) is enabled for the Web service port.
Default value: false
Values: truefalse

Tuesday, 30 January 2018

In-House ERP Implementation

In-house Implementation Pros and Cons.


     Naturally, as a software development company that operates solely within the logistics market, we believe that in most cases the most common sense and logical action is to purchase “off the shelf”. 
      You may well think, “Well, they would say that wouldn’t they”, but if you do read the document in its entirety, I believe that you will find it to be well balanced in its views.
    A company usually develops in-house where the issue to be addressed is trivial or where their requirement is ‘seen’ internally as complex or unusual – the ‘we do things differently’ comment, or where the IT department is seen as a fixed or sunk cost to the business and therefore a ‘cheaper’ option.
    If we ignore the first and move on to the complex or unusual, the realisation of software project ranges from the totally in-house development through to the totally off-the-shelf commercial offering.  
   With the totally in-house development, the requirement is defined, analyzed, programmed, maintained and developed using the firm’s own resources, while in the case of the totally off the-shelf commercial offering, you buy and effectively have to work with the package as it comes out of the box. In reality the least likely total solutions for logistic software are in those extreme positions. 

Further developing the system with new, even minor changes, can be slow and costly to deliver.

In house development pro’s:
  1. The company has full ownership of the final product as well as its source code and the knowledge gained while developing it.
  2. Fits exactly to the business requirements of the company
  3. There is a relationship between the development team and the user base which helps in communication and expectation delivery. 
  4. It gives you full control over the system and its functionality
  5. Allows you to differentiate from your competitors (as the system is developed for your specific needs).
  6. Can provide the business with a greater competitive advantage that a bought solution.

In house development cons: 
  1. Spending valuable money on developing a system from scratch is like ‘re-inventing the wheel’. Clearly defining the project and specifications is an involving task.
  2. Both operational and technical staff need to be involved, using up valuable man hours.
  3. Tight deadlines and time constraints could mean that time is not on your side  
  4. It requires more IT personnel which in turn lead to High overhead cost.
  5. High switching costs: it is more expensive to change to newer technology.
  6. It is time consuming to develop an in-house IT system as opposed to buying it