Thursday, April 16, 2015

How to update the Inactive status for a Benefit/Deduction in mass in Human Resources

Hi Guys..

Occasionally we come across a situation where we have to inactivate/activate deductions and benefits in mass. Gladly i stumbled upon an article in the kb that does the task marvelously.

check it out..
Cheers..

How to update the Inactive status for a Benefit/Deduction in mass in Human Resources

When you run the HR Reconcile utility for 'Update Benefit Setup' and "Update Benefit Enrollment', the gets created on the HR side even for Benefit and Deduction codes that are Inactive  on the Payroll side. If you want to also set them to be inactive on the HR side, the only current functionality is to mark the code inactive in the HR Enrollment window one employee at a time. The 'main' setup for the code does not have an Inactive field that to roll down, so there is not functionality to do this in mass.  How can you also set the Benefit/Deduction codes to be inactive on the HR side all at once?
Current design to only update one employee/code at a time.
Current design to only update one employee/code at a time.
To inactivate the benefit and deduction codes in mass, run the below SQL scripts...
To inactivate the benefit and deduction codes in mass, run the below SQL scripts below against the company database in SQL Server Management Studio for the scenario that fits your needs:

*Before running any update script, it is always recommended to make a current backup copy of the company database first!


Scenario 1: DEDUCTIONS ONLY: The first script below will 'find' where the status code on the deduction on the HR side does not match the status code on the same code in the Payroll Deduction Master table, so you can view what codes do not match.  Then run the second script to 'update' the status on the HR side and the End Date, to match the status and End Date as stored on the Payroll side. Run these scripts against the company database to affect deduction codes only:


DEDUCTIONS:
---------------------------------------
Select a.EMPLOYID, a.deducton as 'Deduction', b.inactive as 'HR_Active',
a.inactive as 'Payroll_Active', a.DEDENDDT as 'DED End date'
from UPR00500 a
join BE010130 b
on a.EMPLOYID = b.EMPID_I
and a.DEDUCTON = b.BENEFIT
where a.INACTIVE <> b. inactive
---------------------------------------
update a set a.inactive = b.inactive, a.BNFENDDT = b.DEDENDDT
from BE010130 a
join UPR00500 b
on b.EMPLOYID = a.EMPID_I
and b.DEDUCTON = a.BENEFIT
where b.INACTIVE <> a.INACTIVE
-------------------------------
IMPORTANT NOTE: The benefit and deduction codes may have the same code ID, and are stored in two different tables on the Payroll side (UPR00500 and UPR00600), however, they are stored together as one record in only one table on the HR side (BE010130). So take note what script you ran last as it will overwrite the status and End Date on the record in HR, and will apply to both the benefit and deduction on the HR side. So if you have any instances where the deduction is inactive, but the benefit is active (or visa versa), you will need to pay attention to what script you ran last. It is recommended for these situations to view the code in the front-end and activate back the one needed in the front-end.



Scenario 2: BENEFITS ONLY:  The first script below will 'find' where the status code on the benefit on the HR side does not match the status code on the same code in the Payroll Benefit Master table, so you can view what codes do not match. Then run the second script to 'update' the status on the HR side and the End Date, to match the status and End Date as stored on the Payroll side. Run these scripts against the company database to affect benefit codes only:

BENEFITS:
---------------------------------------
Select a.EMPLOYID, a.BENEFIT as 'Paycode', b.inactive as 'HR_inactive',
a.inactive as 'Payroll_inactive', a.BNFENDDT as 'BEN End date'
from UPR00600 a
join BE010130 b
on a.EMPLOYID = b.EMPID_I
and a. BENEFIT = b.BENEFIT
where a.INACTIVE <> b. inactive
---------------------------------------
update a set a.inactive = b.inactive, a.BNFENDDT = b.BNFENDDT
from BE010130 a
join UPR00600 b
on b.EMPLOYID = a.EMPID_I
and b.BENEFIT = a.BENEFIT
where b.INACTIVE <> a.INACTIVE
---------------------------------------

IMPORTANT NOTE: The benefit and deduction codes may have the same code ID, and are stored in two different tables on the Payroll side (UPR00500 and UPR00600), however, they are stored together as one record in only one table on the HR side (BE010130). So take note what script you ran last above as it will overwrite the status and End Date on the record in HR, and will apply to both the benefit and deduction on the HR side. So if you have any instances where the benefit is inactive, but the deduction is active (or visa versa), you will need to pay attention to what script you ran last. It is recommended for these situations to view the code in the front-end and activate back the one needed in the front-end.



Scenario 3: ALL: Use this script if you know a code (benefit and deduction) is inactive on the Payroll side for 'all' employees, and you just want to update the status for all the employees enrolled in it on the HR side too: (The first script will find all records for that code, whether a benefit or deduction, where it is not inactive on the HR side, and the second script will update the status for that code to be inactive for all employees enrolled in it on the HR side.)

Select * from BE010130 where BENEFITSTATUS_I <> '2' and BENEFIT = 'xxx'
---------------------------------------------------------------
update BE010130 set BENEFITSTATUS_I = '2' where BENEFIT = 'xxx'

--update the xxx placeholder for the benefit or deduction code that you would like to mark as inactive on the HR side. Note that this script just sets the INACTIVE status and does not update the Benefit/Deduction End Date on the HR side. Also refer to the note above in Scenario 2.

Benefit Status values mean:
1=active
2=inactive
3=waived


Applies to
  • Microsoft Dynamics GP 2015
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0, when used with:
    • Human Resources
    • Human Resources Management

Wednesday, March 25, 2015

Setup information for Electronic Reconcile Format Configurator


Hi everyone,
Found a very important article on Format Configurator in Electronic Bank Reconciliation
Cheers..


This article contains information about setting up the Electronic Reconcile Configurator.

MORE INFORMATION
General Setup for Electronic Reconcile Format Configurator

The process of setting up the Format Configurator in Electronic Reconcile is very lengthy and the following detailed steps will help to make this setup easier. Before setting up the Format Configurator, you must have a printed copy of the download file format specifications from your bank. Because bank formats vary greatly, you must contact your bank and request these specifications for the file format. The format specifications will contain details about each field being downloaded and values of all relevant codes for the bank. This information is necessary to be able to setup the Format Configurator as each bank is different and there is no standard format to enter.

Electronic Reconcile Format Configurator (Routines | Financial | Electronic Reconcile | Configurator):

Section 1 - Enter Format Information

Bank Format - The Bank Format field is an identifier for your format. Enter a unique name for this format, but typically this is the name of your Bank.

Description - This is a required field. Enter an additional description for the Bank Format.

File Format - Follow the steps below for the version you are using:

 -Microsoft Dynamics GP 2010 and prior versions - The File Format field can be selected from the drop-down list as Fixed Field, Comma Delimited, or Tab Delimited. The bank determines which option from the list that you will select. Therefore, you must contact them if the format specifications do not state the format to use.

-Microsoft Dynamics GP 2013 - The File Format field has a choice of BAI or User Defined. If you are using the Bank Administration Institute format, select BAI. For all other formats/banks, select User Defined. In the File Type field, you can choose Fixed Field, Comma Delimited or Tab Delimited as specified by your bank.



Uses Status Codes option is marked only if your bank uses Status Codes to additionally define Transaction Codes. This information is also determined by each bank. Therefore, if the format specifications do not state if your bank uses Status Codes, you must contact the bank. (This is not used very often.)

Record Type Identifier - The Record Type Identifier will contain Start Position and End Position fields if you are using the Fixed Field format and a Field Number field if you are using Comma Delimited or Tab Delimited file formats. This will be where the system should look in the line to determine what type of line (header, footer or detail) it is. If the bank doesn't use a record type code, then you can improvise by selecting a fixed value in the file.

-Fixed Field - Enter the starting and ending position of the field that will contain the value for the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

-Comma Delimited or Tab Delimited - Enter the number of the field that contains the Record Type Code from Bank (The Record Type Code from Bank is entered in Section 2).

Save the Format after Section 1 has been completed before moving on to Section 2 of the Electronic Reconcile Format Configurator window.

Section 2 - Enter Record Types
Note You will only have to define the Record Types that are relevant to Electronic Reconcile. If a section is labeled as optional on the bank specifications, you do not have to set it up in the Format Configurator. The Detail Record Type is always a required section in a bank's specifications.

Bank ID - The Bank ID will default in with the Bank Format from section 1 as soon as you tab into the Record Type field in the second column. This field cannot be changed or edited.

Record Type - The Record Type field can be selected from the drop-down list as Header, Detail, or Footer. All bank formats will require a Detail Record Type, but the header and footer Record Types may be optional. You may only setup each of the Record Types one time as multiple headers or footers are not available.

Record Type Code from Bank - The Record Type Code from Bank field is defined in your bank's specifications. This field must be a unique and constant identifier for the format to match the information in the Detail Record Type. This is the most important field in setting up the Format Configurator to correctly match the download file with the reconciliation.  (So the Record Type Identifier will tell the system which column to look in to see what type of row it is, and then to look at the value in Record Type Code from Bank field to read if it is a header, detail or footer line.)
# of fields - The number of fields indicates how many fields are to be defined in Section 3. Enter the number of fields contained on the line for the Record Type being defined. This information must be entered for each Record Type that is required in the bank's specifications.



Section 3 - Enter Field Information

When you click on a Record Type in Section 2, the corresponding number of fields will display in Section 3.

Record Type - The Record Type field in the left-most column of Section 3 will default in when you select a Record Type in Section 2.

# - The number field will default in with the number of fields that you entered in Section 2.

Field Type - The Field Type field is used to define each of the relevant fields for each of the Record Types. Select the Field Type from the drop-down list that includes options for Accounts, Dates, and amounts. If the exact name of your field from your bank's specifications does not appear in the list, you may have to either select an option that is similar or use the Filler/Ignore option. Again, you only need to define the relevant fields, most importantly: Account Numbers, Check Numbers, Check Dates, Check amounts, Transaction Codes, Record Type Codes, etc.

Note Just as with Record Types, you will only have to define the fields that are relevant to Electronic Reconcile. If there is a field on the bank's specifications that cannot be defined with an existing Record Type or does not have to be defined, use the Filler/Ignore option.


Format - The Format field defines the type of output format for certain fields. Formats only have to be set for Field Types that contain dates or a currency amount, as these are the only options for Formats. There are no options for text or string. Therefore, if the field is not a date or a currency amount, just leave the Format field blank. The From and To fields are used to enter the character positions of the field. Enter the starting and ending character position for each field in each Record Type. The From and To fields must be entered if using the Fixed Field File Format, so if you are using Tab Delimited or Comma Delimited File Formats you can leave these fields as zero.

Transaction Codes (Codes Entry - Transaction Codes Entry)

While still in the Electronic Reconcile Format Configurator window, go in the Transaction Codes Entry window through the path listed above in the top Menu Bar. If you have not defined the Transaction codes, you will get the message "Record Type match not found" on the error report.

Transaction Codes identify the type of transaction that each Detail line represents. Electronic Reconcile requires a Transaction Code in a configured Bank Format to work correctly. You must have Transaction Codes or Record Type Codes defined to use Electronic Reconcile. These codes must come from the bank and must be listed on the bank's specifications.

Transaction Type - The Transaction Type field is used to define each of the different types of transactions that appear on your bank's specifications. Select a Transaction Type from the list to match or to closely match your bank's specifications. Note that the options in the list are the only currently supported types. At this time, the two options that will match using Electronic Reconcile are Check Paid and Deposit Cleared.

Note: In Microsoft Dynamics GP 2013, options for Transfer Credit and Transfer Debit have also been added and will electronically match in Electronic Reconcile. However, you must enter the Bank Transaction Type Codes in as defined by your bank. Additional functionality in Microsoft Dynamics GP 2013 is also that you can have multiple Transaction Type Codes for each Transaction Type.


Transaction Type Code - The Transaction Type Code field is used to enter the value for each Transaction Type and this value is given to you as part of the file specifications from your bank. Enter the Transaction Type Code value that corresponds to the selected Transaction Type. This information must come from the bank and cannot be improvised if it is not available on the bank's specifications.

G/L Account - The G/L Account field is available only for the following Transaction Types: Interest Income, Other Income, Other Expense, and Service Charge. Enter the G/L Account Number of a General Ledger Posting Account for the adjustment that will be generated. Electronic Reconcile will automatically create adjustments for these transaction types if they appear in the downloaded file from your bank.

Note The Interest Income, Other Income, Other Expense, and Service Charge transaction types do not electronically match, and instead will create Adjustment entries on the reconciliation. (Click the Adjustments button on the Select Bank Transactions window).

Account Description - The Account Description field will default in with the description of the account from General Ledger and is not editable.

Distribution Reference - The Distribution Reference field can be used to enter an additional reference for the adjustment that will be made. You can enter a Distribution Reference if you want, but it is not a required field.

Document Type - The Document Type field will default in with the Transaction Type that you selected at the top of the Transaction Code Entry window: Interest Income, Other Income, Other Expense, or Service Charge. This field cannot be changed unless you go back and change the Transaction Type field.

Define Status Codes - The Define Status Codes button only becomes available if you have marked the Uses Status Codes option in the Electronic Reconcile Format Configurator window. Define Status Codes is only available for certain Transaction Types: Check Paid and Deposit Cleared. After selecting one of these 2 Transaction Types, you would select the Define Status Codes button to go into the Status Codes Entry window. Here you would select: Paid Check, Check Reversal, Stop Pay, or Stop Pay Reversal for the Status Type and enter the corresponding Status Code from your bank's specifications. Again this information has to come from your bank and cannot be improvised or Electronic Reconcile will not work correctly.



Special notes to remember when setting up Electronic Reconcile:
  • You must have a printout of the file format specifications from your bank before setting up the Electronic Reconcile Format Configurator.
  • Every bank is different. Therefore, you cannot follow one standard format for all banks.
  • If you open the .TXT or .CSV file with Notepad, the system will typically not read any information after position 245. So make sure all the required fields to be mapped are in the first part of the line if your lines are more than 245 characters. The information after 245 will be read as a new line and appear on the Unprocessed Data Record error report as "Record Type match not found: Record Type = " because there isn't one. This would be acceptable if no fields after position 245 are not needed. If there are fields that are needed, you will need to contact your bank to see if they are able to reconfigure the file to be smaller and not exceed 245 characters.
  • The Electronic Reconcile Format Configurator only needs to be setup once when first starting to use Electronic Reconcile, and then you just keep downloading .TXT or .CSV files from the bank to match this Format Configurator.
  • The following fields must be present in your bank format: Transaction Code, Account Number, Check/Serial Number, Transaction Amount, Record Type Code, and the Bank Cleared Date. If your format uses Status Codes, then the Transaction Status Code must also be present in the configuration.
  • If you have gone through all of the Electronic Reconcile process and no transactions are marked off as cleared in your Bank Reconciliation module, most likely something is not set up correctly in the Electronic Reconcile Format Configurator. The most common error message that will be received is a "Record Type Match Not Found" error on the Unprocessed Records report that prints after trying to download.
  • If you try to re-download after you have already downloaded the .txt file from the bank, you will receive "Duplicate" error messages because the system sees the transactions as duplicates instead of just downloading new transactions.
  • If you try to delete a Reconcile and re-enter the information after you have already downloaded the .txt file from the bank, you will receive "Duplicate" error messages because the system sees the transactions as duplicates.
  • Make sure the Bank Account Number is unique for the checkbook that is set up with Electronic Reconcile. If the Bank Account Number is set up with a different checkbook, Electronic Reconcile will not be able to match the downloaded transactions and you will receive a message stating that the Bank Account Number is not set up.
  • In the Codes Entry window of the configurator, the types that will automatically match are: Check Paid, Deposit Cleared, Transfer Debit and Transfer Credit.
  • If you enter an increase adjustment or a decrease adjustment in the Reconcile Bank Adjustments window, the following adjustment types create an adjustment transaction in the Reconciliation Bank Adjustments window: (For example, 'interest' or a 'misc fee' on your bank statement would not be in GP (so nothing to match to), so you need the system to book the adjustment/journal entry in GP for these types.)
    • Interest Income
    • Other Income
    • Other Expense
    • Service Charge
  • If you enter an increase adjustment, a decrease adjustment, or a withdrawal in the Bank Transaction Entry window, you are prompted to manually mark the adjustment. When you receive this message, you must manually mark the records in the configurator file.
  • Checks will be matched by the Check Amount and Check Number. Deposits will be matched by the Deposit Amount and Deposit Date (within a default 8 day range, but you can override that when prompted to be a different day range.) 
  • The Bank Cleared Date can affect the matching process. GP will only clear checks in which the Bank Cleared date is AFTER the Check Issue Date in GP. GP would not clear a check on a date prior to the date it was actually issued in GP.  
  • GP will ignore any leading zeroes on a check in the matching process and in fact, will strip them off the check number when importing. Leading zeroes will not affect the matching process for the check number. GP is able to match the check number, regardless of any leading zeroes.
This article was TechKnowledge Document ID: 19396


Applies to
  • Microsoft Dynamics GP 2010
  • Electronic Reconciliation Management, when used with:
    • Microsoft Dynamics GP 10.0
    • Microsoft Dynamics GP 9.0
    • Microsoft Business Solutions–Great Plains 8.0
    • Microsoft Business Solutions–Great Plains 7.5
    • Microsoft Great Plains Dynamics 7.0
    • Microsoft Great Plains eEnterprise 7.0
    • Great Plains Dynamics 6.0
    • Great Plains eEnterprise 6.0

Monday, March 23, 2015

How to enable the Projection button in the Depreciation Projection window for Fixed Assets

Hi Guys..
Found a very important KB article on enabling Fixed Asset projections button in the Depreciation Projection window..
Check it out..


To make the Projection button available in the Depreciation Projection window for Fixed Assets, follow these step.

Note  The following steps require you to run delete scripts by using the Microsoft SQL Query Analyzer tool. We recommend that you create a backup of your data before you follow these steps.
  1. Make sure that all users exit Microsoft Dynamics GP.
  2. Use one of the following methods to start the Support Administrator Console, Microsoft SQL Query Analyzer, or SQL Server Management Studio depending on the program that you use:
    • Method 1: SQL Server Desktop Engine (MSDE2000)

      Click Start, point to All Programs, point to Microsoft Administrator Console, and then click Support Administrator Console.
    • Method 2: SQL Server 2000

      Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
    • Method 3: SQL Server 2005

      Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    • Method 4: SQL Server 2008Click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
    • Method 5: SQL Server 2008 R2
      Click Start, point to All Programs, point to Microsoft SQL Server 2008 R2, and then click SQL Server Management Studio.
    • Method 6: SQL Server 2012
      Click Start, point to All Programs, point to Microsoft SQL Server 2012, and then click SQL Server Management Studio.
  3. Run the following commands against the Company database:

    DELETE FA40203
    DELETE FA41900

    Notes
    • FA40203 is the Fixed Assets Depreciation Book Setup table (used for tracking projections and depreciation).
    • FA41900 is the Projection Report Master table.
  4. Start Microsoft Dynamics GP.
  5. Verify that the Projection button is available. To do this, follow one of these steps, depending on the program that you are running:
    • For Microsoft Dynamics GP 10.0 and later versions:

      On the Microsoft Dynamics GP menu, point to Tools, point to Routines, point to Fixed Assets, click Projection, and then verify that the Projection button is available.
    • For Microsoft Dynamics GP 9.0 and Microsoft Business Solutions – Great Plains 8.0:

      On the Tools menu, point to Routines, point to Fixed Assets, click Projection, and then verify that the Projection button is available.

Applies to
  • Microsoft Dynamics GP 2015
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0, when used with:
    • Fixed Asset Management

Wednesday, December 19, 2012

Dynamics GP 2013 released today.

Finally , the most awaited Dynamics GP 2013 has been made available for download.


The direct links to the download pages are below:

Make sure you look at the updated system requirements as well:

New Licensing Procedures

Microsoft Dynamics GP Business Ready Licensing (BRL) or Module Based Licensing (MBL) Customers, current on their service plan, must contact their Partner to request their Microsoft Dynamics GP 2013 registration keys. Registration keys will not be visible in CustomerSource until an order has been placed and completed for Microsoft Dynamics GP 2013.

Partners can place their Customer’s order by following these instructions. Once the order is placed, the Customer will be able to see their registration keys in CustomerSource. 

A. These customers can transition upgrade to Perpetual Licensing via a LMT Upgrade if their current Microsoft Dynamics GP 2010 VOICE First Registration Date is prior to October 1, 2012. The Customer will receive like functionality (per the LMT Upgrade Rules as defined in the Perpetual Upgrade Policy) and their service plan end date will remain the same at no additional cost. 

B. A LCT Upgrade is processed if the Customer’s current Microsoft Dynamics GP 2010 VOICE First Registration Date is on or after October 1, 2012. The Customer will receive PLP credit from their current solution to apply to the Microsoft Dynamics GP 2013 Perpetual solution.

Effective December 19, 2012, qualified Partners will be able to generate Microsoft Dynamics GP Perpetual license keys for TWO, Inc. using the demo/dev template in the License Key Configuration (LKC) tool in VOICE under Developer Tools. Partners that qualify to receive a not for resale copy of GP 2013 Perpetual for their own internal use will have their accounts and license keys updated in early January 2013.

cheers..
Feradh Zain.

Friday, February 3, 2012

DynamicsGP.me - Support System Launched

DynamicsGP.me team today launched the incident tracking system for Microsoft Dynamics GP & Dynamics RMS with the aim to cater clients with critical issues.
The clients can track and follow up with the incidents logged in the system.
Please visit the Support System here.

Cheers.


Wednesday, May 11, 2011

Dynamics GP 2010 R2 Downloads

Microsoft Dynamics GP 2010 R2 can be downloaded through Partnersource and CustomerSource since Mid April.This is the one of the rarest moments when the Microsoft actually released their product BEFORE their announced launch date - 1st of May. :)

For New features : What's New document.

Product Download Links :

PartnerSource


Product Release Downloads for Microsoft Dynamics GP 2010
Word Template Generator for Microsoft Dynamics GP 2010 R2
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Visual Studio Tools for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Web Services for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for eConnect for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Web Services for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Integration Manager for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Personal Data Keeper for Microsoft Dynamics GP 2010
Dexterity Development System Releases for Microsoft Dynamics GP 2010 (Available soon)

CustomerSource


Product Release Downloads for Microsoft Dynamics GP 2010
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Visual Studio Tools for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Web Services for Microsoft Dynamics GP 2010
Software Development Kit (SDK) for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for eConnect for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Web Services for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Integration Manager for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Workflow for Microsoft Dynamics GP 2010
Service Packs and Hotfixes for Personal Data Keeper for Microsoft Dynamics GP 2010
Dexterity Development System Releases for Microsoft Dynamics GP 2010

A Big Thank you goes out to Mariano for the compilation of links .
Cheers.
Feradh Zain

Thursday, April 21, 2011

Nomination for Most Influential MS Dynamics People

Nomination for the 100 Most Influential MS Dynamics Person for year 2011 is on..

Cast your votes before 22nd April 2011 :


Mohammed Feradh Zain.