Error message display for me"invalid colmun " when i implement stored procedure

Question

Hi guys
in this stored procedure below i have proplem in colmun in sex type i have two values Male and female
but when i search by this colmun from interface it give me invalid colmun why
this is my stored procedure
Create Procedure sp_Employee
    @EmployeeID       NVARCHAR(50),
    @EmployeeName     NVarchar(100),
    @SexType          Nvarchar(50)
AS
Declare @SQLQuery as nvarchar(2000)
SET @SQLQuery ='SELECT * from ViewEmpTEST Where (1=1)'
 If @EmployeeID <>''
         Set @SQLQuery = @SQLQuery + 'And (EmployeeID = '+ @EmployeeID+') '
If @EmplyeeName  <>''
         Set @SQLQuery = @SQLQuery + ' AND (EmplyeeName  LIKE
N''%'+@EmplyeeName +'%'') '
If @SexType <>''
          Set @SQLQuery = @SQLQuery + 'And (SexType = '+ @SexType+') '
Exec (@SQLQuery)
and this is my view ViewEmpTEST
SELECT     CONVERT(varchar, dbo.Employee.DriverID) AS EmployeeID, dbo.Employee.EmplyeeName, dbo.Employee.DriverName,
                      dbo.Nationality.NationalityName, dbo.Employee.ResidentNo, dbo.Country.CountryName, dbo.Branch.BranchName, dbo.Employee.ResignDate,
                      dbo.Employee.HealthCarNo, dbo.Jobs.JobName, dbo.Department.DepartmentName, dbo.Employee.PlaceIssue, dbo.Employee.Deduction,
                      dbo.Employee.ExpireDateMedical, dbo.Employee.PolicyNumber, dbo.Employee.ExpireDateResident, dbo.Miritial.MiritualStatus,
                      dbo.Status.StatusType, dbo.Sex.SexType, dbo.Employee.UnactiveReason, CONVERT(varchar, dbo.Employee.BirthDate, 103) AS BirthDate,
                      CONVERT(varchar, dbo.Employee.DateToday, 103) AS DateToday, dbo.Employee.UserID, dbo.Employee.PassportNo, dbo.Employee.Bonus,
                      dbo.Employee.AccountType, dbo.Employee.PlaceOfBirth, dbo.Employee.ExpireDateresidentHijri, CONVERT(varchar, dbo.Employee.PassportDateStart,
                      103) AS PassportDateStart, dbo.Employee.PassportDateExpire, dbo.Employee.EntryNo, dbo.Employee.PlacePassport, CONVERT(varchar,
                      dbo.Employee.Salary) AS Salary, dbo.Employee.AccountNo, dbo.Religon.ReligonName, dbo.Employee.Mobile, dbo.Employee.Email,
                      CONVERT(varchar, dbo.Employee.SexID, 103) AS SexID, CONVERT(VARCHAR, dbo.Employee.StatusID, 103) AS StatusID, dbo.Employee.JoinDate,
                      dbo.Employee.JobDetailes, dbo.BloodType.BloodType, dbo.Class.ClassName, dbo.Employee.OccupationID, dbo.Ocuppation.OcuppationName
FROM         dbo.Employee LEFT OUTER JOIN
                      dbo.Ocuppation ON dbo.Ocuppation.OccupationID = dbo.Employee.OccupationID LEFT OUTER JOIN
                      dbo.BloodType ON dbo.BloodType.BloodID = dbo.Employee.BloodID LEFT OUTER JOIN
                      dbo.Class ON dbo.Class.ClassID = dbo.Employee.ClassID LEFT OUTER JOIN
                      dbo.Department INNER JOIN
                      dbo.Jobs ON dbo.Department.DepartmentID = dbo.Jobs.DepartmentID ON dbo.Employee.JobID = dbo.Jobs.JobID LEFT OUTER JOIN
                      dbo.Miritial ON dbo.Miritial.MiritialID = dbo.Employee.MiritialID LEFT OUTER JOIN
                      dbo.Branch ON dbo.Branch.BranchID = dbo.Employee.BranchID LEFT OUTER JOIN
                      dbo.Status ON dbo.Status.StatusID = dbo.Employee.StatusID LEFT OUTER JOIN
                      dbo.Sex ON dbo.Sex.SexID = dbo.Employee.SexID LEFT OUTER JOIN
                      dbo.Religon ON dbo.Religon.ReligonID = dbo.Employee.ReligonID LEFT OUTER JOIN
                      dbo.Country ON dbo.Country.CountryID = dbo.Employee.CountryID LEFT OUTER JOIN
                      dbo.Nationality ON dbo.Nationality.NationalityID = dbo.Employee.NationalityID
WHERE     (dbo.Nationality.NationalityID IS NULL) OR
                      (dbo.Nationality.NationalityID IS NOT NULL) OR
                      (dbo.Country.CountryID IS NULL) OR
                      (dbo.Country.CountryID IS NOT NULL) OR
                      (dbo.Jobs.JobID IS NULL) OR
                      (dbo.Jobs.JobID IS NOT NULL) OR
                      (dbo.Miritial.MiritialID IS NULL) OR
                      (dbo.Miritial.MiritialID IS NOT NULL) OR
                      (dbo.Branch.BranchID IS NULL) OR
                      (dbo.Branch.BranchID IS NOT NULL) OR
                      (dbo.Status.StatusID IS NULL) OR
                      (dbo.Status.StatusID IS NOT NULL) OR
                      (dbo.Sex.SexID IS NULL) OR
                      (dbo.Sex.SexID IS NOT NULL) OR
                      (dbo.Class.ClassID IS NULL) OR
                      (dbo.Class.ClassID IS NOT NULL) OR
                      (dbo.Ocuppation.OccupationID IS NULL) OR
                      (dbo.Ocuppation.OccupationID IS NOT NULL) OR
                      (dbo.BloodType.BloodID IS NULL) OR
                      (dbo.BloodType.BloodID IS NOT NULL)
what is the proplem in statment sextype in stored procedure

Answer 1

Start over - completely.  The tsql for your view is poorly written. 
One does not have a sex, one has a GENDER. 
I can understand a conversion of datatype like "CONVERT(varchar, dbo.Employee.DateToday, 103) AS DateToday", but not "CONVERT(varchar, dbo.Employee.SexID, 103) " - style 103 is for datetime datatypes and the column name SexID does not
remotely imply that datatype. 
Similarly, stop being so lazy and specify the length of your converted varchar column rather than allowing it to default to some length.  And if you are going to convert to varchar, shouldn't you be converting to nvarchar given that your procedure
arguments are nvarchar?  Consistency will only help your code stability and correctness.
To continue with the datetime to varchar conversion, is this an attempt to simply strip the time component from a column that is datetime?  If so, simply convert it to date and avoid any possibility of error due to interpretation assumptions with the
converted string and its format.
Lastly, do you really need all of those outer joins?  I find it difficult to believe that an employee does not have a required relationship with a majority of those tables.
As for your problem, please post the complete and entire error message - exactly as displayed.  Presumably you have performed a basic test of your view and verified that it still works (i.e., nothing was changed about the tables involved in the view
after the view was created).  Something like "select top 1 * from dbo.ViewEmpTEST where SexType = 'x';" should execute successfully and return an empty resultset. 
And, of course, the SexType column is (presumably) nvarchar, so you will need to enclose the value you are searching for in your dynamic sql with single quotes.  If you intend to provide dynamic searching functionality, you will need to learn to code
it and debug it yourself.  The others have already indicated that this approach is a security-risk.  At the very least, you should capture the string that you are attempting to execute and visually examine it yourself when you discover that
it does not work.  It will then become obvious (assuming the code you currently have posted is what you are using) that the error is your inclusion of the SexType argument in the string:
select ... where ... And (SexType = male)