GST is all set to swallow other indirect taxes in India and wipe off the unorganized warehouses. Here’s how the Goods and Service Tax gearing up for changes in taxation across the country.
Goods and Service Tax (GST) is an indirect tax collected by the government during the purchase or sale of goods but for you it can be a worthy taxation tool in short. How does one say whether it will help or not? It will replace the tax collected by the government as it is considered as the biggest reform in India’s indirect tax structure. Let’s figure out few facts about GST:
- GST is levied on manufacture, sale, consumption of goods and services in India.
- With the ratification of more than 50% of state legislatures, the Constitution Amendment Bill for Goods and Service Tax has been approved by the President of India in the Parliament.
- The endeavor is to replace all the indirect taxes imposed on goods and services by the Centre and States and implement GST by April, 2017.
IoT creates opportunities, evoking new business models in logistics and warehousing. With lot of potential, IoT is to revolutionize business processes across the entire value chain.
We all know that the internet has undergone numerous stages of development from its inception but wait, the revolution is yet to be realized. What is Internet of Things (IOT) and why it is need of an hour? First and foremost, you need to perceive the current scenario of today’s livelihood that is smeared with latest technologies and internet undoubtedly.
Today, a quintessential part of our living is covered by internet and it is considered indispensable for its omnipresence in our daily life. The accelerating influence of internet in our work and communication is as transparent as glass. But how did the internet get so large so quickly?
Today’s internet evolved from ARPANET, the first TCP/IP network. With this evolution, computers have also evolved remarkably from PCs to laptops, tablets, smartphones and more. The transition of internet and technologies has modified the system of send, receive and process to the devices.
Last time I mentioned in my blog “The only harm perhaps that synthetic keys cause is that they destroy the readability of your Data Model”. Some of the beginners did not quite understand this well enough and I realized this may need some elaboration.
My next exercise will just highlight the same.
In this exercise we will build on to the Data Model we had arrived on in Exercise 2, which is reproduced again below for the sake of continuity:
To the Data Model created in Exercise 2, add the following four tables. The tables are self-explanatory. You may note the following regarding the tables:
- Invoices table links to the Sales table.
- Similar to the Customer, SalesOrders and Invoices tables, for the incoming supply of goods the Suppliers, Purchases and Receipts tables have been added.
NPrinting is a product of Qlik to generate the reports from QlikView and Qlik Sense Applications. Reports can be created in various formats such as PDF, Excel, Word, PowerPoint and HTML and the distribution can be scheduled and automated. In this blog we shall cover the critical differences that exist in usage of filters and variables in NPrinting.
NPrinting Filter Fundamentals:
NPrinting supports three types of filters:
i) Task Level Filter –
This is a Global level filter and applies throughout the task for all recipients.
e.g.: If we have to generate a report for 100 recipients for a given Year-Month, then the Year-Month filter shall be defined as a Task Level filter.
ii) Recipient Level Filter –
This applies for a specific recipient only.
e.g.: for each Recipient, the customer name needs to be selected in the QlikView application so that relevant data of the given customer only gets sent to the respective recipient. The Customer filter will be set as Recipient Level Filter. Please note all recipients details will be maintained in an Excel file.
This is first in series of specific blogs that I will be writing explaining the fundamentals of Data Modelling in Qlik.
Data Model is the heart of your Qlik dashboard and can affect each of the following:
- Expression Complexity
- Reload Times
Link Table design and Star Schema are the most favoured data models and we shall be covering both of these in these blogs.
I plan to take the reader through a series of practical exercises that shall demonstrate the various concepts. The initial exercises shall be trivial since the blog is being written for the absolute newbie but as we proceed, I shall be bringing in more and more complexities.
In each of these exercises it is my recommendation that before looking at the solution provided by me, try to solve the same on your own.
Incidentally I am assuming that all readers are familiar with ETL scripting on Qlik. This blog does not cover any concepts related to ETL scripting.
The source system has the following three tables. Create a Data Model in QlikView for the same.