Developer Manual Import Payroll Data

The information contained in this document is current as of the date of publication and subject to change. Because Tally must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Tally, and Tally cannot guarantee the accuracy of any information presented after the date of publication. The information provided herein is general, not according to individual circumstances, and is not intended to substitute for informed professional advice. This document is for informational purposes only. TALLY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT AND SHALL NOT BE LIABLE FOR LOSS OR DAMAGE OF WHATEVER NATURE, ARISING OUT OF, OR IN CONNECTION WITH THE USE OF OR INABILITY TO USE THE CONTENT OF THIS PUBLICATION, AND/OR ANY CONDUCT UNDERTAKEN BY PLACING RELIANCE ON THE CONTENTS OF THIS PUBLICATION. Complying with all applicable copyright and other intellectual property laws is the responsibility of the user. All rights including copyrights, rights of translation, etc., are vested exclusively with TALLY SOLUTIONS PRIVATE LIMITED. No part of this document may be reproduced, translated, revised, stored in, or introduced into a retrieval system, or transmitted in any form, by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Tally Solutions Pvt. Ltd. Tally may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written licence agreement from Tally, the furnishing of this document does not give you any licence to these patents, trademarks, copyrights, or other intellectual property. 2010 Tally Solutions Pvt. Ltd. All rights reserved. Tally, Tally 9, Tally9, Tally.ERP, Tally.ERP 9, Shoper, Shoper 9, Shoper POS, Shoper HO, Shoper 9 POS, Shoper 9 HO, TallyDeveloper, Tally Developer, Tally.Developer 9, Tally.NET, Tally Development Environment, Tally Extender, Tally Integrator, Tally Integrated Network, Tally Service Partner, TallyAcademy & Power of Simplicity are either registered trademarks or trademarks of Tally Solutions Pvt. Ltd. in India and/or other countries. All other trademarks are properties of their respective owners. Version: Developer Manual Import Payroll Data/2.0/September 2010

Import Payroll Data

Scenario
A Company Global Enterprises using payroll in Tally.ERP 9 requires an extension where data is imported automatically from Excel to Tally.ERP 9. Their HR Department is maintaining all the Employee information in Excel. They do not want to enter them again in Tally and need an automated solution. Also, the attendance records are available in Excel. They need an automated solution to import both these records. The excel sheet for Employee Masters contains all the details about the employees as shown below:

Similarly, the Attendance Vouchers are as follows:

They need the above Employee List and Attendance Vouchers to be imported into Tally.ERP 9 without having to key them in.

Requirement Statement
Since the above data is in Excel Format which needs to be automated, a TDL Extension must be built to gather all the necessary information and import the same into Tally.ERP9 automatically.

Solution
I. To import the Employee Masters from Excel to Tally.ERP 9, a. We need the external data with the required fields gathered in the collection using the following code:
[Collection: TSPL FFE EmployeeDataExcelColl] ODBC :"Driver={Microsoft Excel Driver(*.xls)};Dbq="+ @@TSPLFFEEmpMasterFilePath SQL : "Select * from [Employee$]" SQLObject : TSPL FFE Employee Excel Master Client Only : Yes

In the above collection, ODBC attribute is used to specify the driver information and the path of the Excel Source File. The path can be accepted from the user in any variable. SQL attribute is used to select all or relevant columns/ data from the Table or Sheet. In the above example, this attribute is used to fetch all the Employee details from the Excel Sheet Employee. The attribute SQL Object is used to map the columns to meaningful methods. Client Only attribute informs to collect data locally and not to send request to the server for collection data.

Note: This solution works at either ends i.e., Server end or Remote Client end since Client Only attribute is enabled in the Collections.

b. The following function walks over a collection of Employee details viz., TSPL FFE Excel Employee collected from Excel to import in Tally.ERP9; by using action SET VALUE.
[Function: TSPL FFE ImportEmployeeMaster] VARIABLE : ProgressCount : 1 : Number

80 : SET : ProgressCount 90 : NEW OBJECT: Cost Centre

100: IF : NOT ($$NumItems:TSPLFFEExcelEmployee > 0) 110: RETURN 120: END IF 130: START PROGRESS : ($$NumItems:TSPLFFEExcelEmployee)+ : "Importing" : "Employees" 140: WALK COLLECTION : TSPL FFE 150: SET VALUE : ForPayroll: 160: SET VALUE : Name : 170: SET VALUE : Category : 180: SET VALUE : Parent : 190: SET VALUE : DateOfJoin: . . . 460: 470: 480: 490: SET SET SET SET VALUE: VALUE VALUE VALUE ExcelEmployee Yes $EmployeeName $EmployeeCategory $EmployeeGroup $EmployeeDOJ

PassportExpiryDate:$EmployeePassportExpiry : VisaNumber : $EmployeeVisaNo : VisaExpiryDate : $EmployeeVisaExpiryDt : WorkPermitNumber : $EmployeeWorkPermitNo . .

520: 530: 540: 550: 560: 570: 580:

SAVE TARGET SHOW PROGRESS : ##ProgressCount SET : ProgressCount : ##ProgressCount + 1 END WALK END PROGRESS DISPLAY COLLECTION:TSPLFFEEmpInformation Collection RETURN : TRUE

On creation of all Objects, a report displaying the Employees with their details is shown.

II. Similarly, to import Attendance Vouchers, the following Collection is gathered from Excel, walked over in a Function and methods are set to create the voucher.
[Collection: TSPL FFE AttendanceDataExcelColl] ODBC : "Driver={Microsoft Excel Driver (*.xls)}; Dbq=" + @@TSPLFFEAttdVchFilePath SQL : "Select * from [Attendance$]" SQLObject : TSPL FFE Attendance Excel Voucher Client Only : Yes

TDL Capabilities Used

I. II. User Defined Functions Fetch Object attribute at Function Level