Richa garg invited you to ClearTax !

Hello,

Richa garg finished Tax filing using ClearTax, and invited you to file your tax return. 

Accept the invitation and complete your e-filing.

 
Accept Invitation
 

Why your friend, and over 15 Lakh Indians love ClearTax:

• ClearTax is completely free and 100 times simpler to use than any other website
• You can finish E-Filing your tax return in 7 minutes
• If you have Form-16 PDF, upload it on ClearTax and E-File in one-click.

Best,
Team ClearTax

PS: The Economic Times rates ClearTax as #1 E-filing portal. You are in good hands :)

To stop receiving all emails from ClearTax click here. Please note that once you unsubscribe, it cannot be changed.

Data Model Relations in SYNON

The Synon data model explicitly declares relationships between files, and files and fields. These statements are known as Data Relations. There are Nine Data Relations in the Synon/2E product. We will focus our attention on All of those relations at this time.The Data Relations we will use are the Defined As, Known By, Has, Owned By , Refers To,  Extended By ,Denoted by , Includes ,Qualified By.

1. Defined As - The Defined As data relation declares or defines a file to the Synon Data Model. When ever you enter data relations into a file the Defined As relation is a relation you need not remember to enter, it Created automatically. As compaired to other Synon Data Relations, the Defined As relation does not appear on the screen. We have to requesting that to appear . To see Defined As relations, position the cursor in one of the selection or position field called Relation Level (Rel lvl) and enter "ALL" or "DFN" and Press ENTER. All files currently defined in the data
model will be displayed.

NOTE:

If  any file is deleted from the model make sure to you delete Defined as relation after deleting Functions,fields, Access Paths and in last Defined as Relation.

2. Known By - The Known By relation defines a field as a key field in a file. It is usually a Primary Key field. This is a File-to-Field relation.

3. Has - The Has relation defines a field  as a non-key or data attribute field in a file. This is a File-to-Field relation.

4. Owned By - The Owned By relation causes the key fields of the owning file to be included among the key entries of the owned file as major keys. For example, if the Employee file is owned by the Company file, then the key field(s) of the Company file would be included as keys on the Employee file. The key fields of the Company file will appear before the key fields of the Employee file, making them the major keys. This is a File-to- File relation.

5. Refers To - The Refers To relation causes the key fields of the referenced file to be included as non-key fields on the referring file. For example, if the Employee file Refers To Job Master file, the keys of Job Master file will be included as non-key fields on the Employee file. This is a File-to-File relation.

6. Denoted by - The 'Denoted by'   relation  specifies that A CA 2E file may be defined  by a special unique identifier:  'a surrogate'.  A surrogate is a system  wide number (of a specified size) that uniquely identifies each record in  the  system. For instance you might use a surrogate in an application  where  the  normal  identifiers are subject to repeated change (in effect  a  customer  number is a limited application of this idea).                                                                 
        
7. Extended by - The 'Extended by'  relation  declares  A CA 2E file to be an extension of  another  CA 2E  file. The  relation  records  an association that is not expressed by any other relation, and in partic-ular, a one-to-one association between the identifiers of two files.  

8. Includes -  The includes is used for Audit fields (eg : Date , Time ,User name , Change Date etc) It is File-To- File Relation. We Just include the file and all Audits Fields Will be available in parent file.

9. Qualified By - This relation is used on the KEY field only. It is a File-To- Field relation,For Example, in a file we need to search for the value. which exactly is not present and we are not sure about the value is there or not , In that case it will return a previous or immediate after present value

as per given *Previous or * Next by user.

                                    

# end                                                                                                

SYNON : Data Modeling or Data Design Concept

A Synon/2E Data Model is a structured, organized description of a set of data and its relationships of a business or organization. Data models are intellectual and sometimes graphical tools representing logical data relationships. A Data model does not comprise in itself a true representation of all the business's information, but, is a simplified view of it.

Goals Of Data Modeling

A data model must meet three main objectives to be deemed acceptable:

Comprehensive - Every item of information (field) that is relevant to the organization should be identified.

Non-Redundant - Every item of information should appear once and only once. This elimination of
repeating groups of data is one of the elements of what is commonly known as Normalization.

Consistent - There should be no mutually incompatible representations of information (data), nor conflicting rules about what can be done with data. That is, a particular data element should have the same attributes each and every time it is found in the model.

Synon/2E Concepts and Vocabulary

The Edit Database Relations screen allows you to describe the data portion of an application. The data portion  consists of entities (files), attributes (fields), and data relations.
Let's define the terms we will be using throughout this course.
Data Relation - A logical association between two Synon entities or a Synon entity and
a Synon field. 

Entity - A group or list of Synon Data Relations. 

Attribute - A unit or element of information. This is also known as a field. 

Condition - A specific value or values associated with an attribute. A condition may
be a discrete value, a comparison, or a range of values.

# end

SYNON Data Base : Edit Database Relations Panel

Start with Data Base : Edit Database Relations Panel  

This is the Synon/2E Edit Database Relations Panel used to define the all fields (Attributes) and files (Entities) which makes a Synon/2E Data model.

The Synon Data Model that is the Edit Database Relations screen shows the following items:

1. User Class
2. Current Model
3. User Profile
4. Work Station ID - Time/Date
5. Positioning Fields

Here is a example of Edit database Relation Screen:



User Class - *DSNR or *PGMR (Designer or Programmer). Two types of users are allowed to edit the Synon Data Model, Designers or Programmers(As shown in above example Designer). A Designer is responsible for the contents of the data model or the data relations that means all the field and length and other attributes are defined in designer. Only one Designer is allowed in the model at any given time. When Designer is using the data model, every one else is locked out means other users cannot enter into that model.On the other hand a Programmer , is not permitted to modify the Data base relations found in the Data Model as previously designed . A programmer can specify programs, subroutines, and access paths. In Programmer mode, multiple programmers can use data model at the same time.

Current Model - The Name of the Data model you have selected is displayed on the above example screen. In our example, the name of our model is displayed at positioned colored in RED  as per the security policy it is not shown here. Here on each screen header will show the current data model is being used by the user either Designer or Programmer.

User Profile - The name of the user editing the model will give the name of the user currently using the model as shown in example (eg op: XXXXXXX ).

Work Station ID - Time/Date - Work Station ID is the ID of the Work Station using the data model(QPADEV017W).
You will also notice the data and time in the header upper right hand corner. Here, the time is not dynamic. To get a current time,Every  time you have to press F5=Reload/Refresh

Positioning Fields - In the above of each screen Type, Object, Relation, and Referenced object fields are appears as blank lines. These lines are actually positioning fields or used for Filter the record. These fields are used by the users (Designer or Programmer) to selectively display the specific detailed information about the data model. For example, to see all of the Objects beginning from the letter  'E', position the cursor above the Object field, enter a  'E' and Press ENTER.
All names starting from E will come up and will be positioned as shown in below Screen.