Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Introduction

Functions shall represent the various functions or services carried out by the ULBs. Functions are provided through various responsibilities centers called Departments.

Functions of the ULB can have three levels within it.

  • First level under this group represent various functions both obligatory and discretionary. Identified as 0 in the template.

  • Second Level in function would represent the particular type of service under a function,
    known as “Function Description”. Identified as 1 in the template

  • Third level will represent a particular cost center, Known as “Cost Centre”, which
    provides the service. Identified as 2 in the template.

Data Table

*Sr. No.

*Name

*Code

*Level

Parent Type

1

General Administration

10

0

Nil

2

GENERAL ADMINISTRATION:Administration

1011

1

General Administration

3

General Department

101100

2

GENERAL ADMINISTRATION:Administration

4

Public Works

20

0

Nil

5

PUBLIC WORKS:Roads and Pavement

2021

1

Public Works

6

Roads and Building Maintenance

202101

2

PUBLIC WORKS:Roads and Pavement

Procedure

Data Definition

  • Sr No: Defines the serial no of the line item.

  • Name: To indicate the Function name, User can select a particular function code while recording a transaction in the system. This will facilitate in generating a report at the function level.

  • Code: The unique code give to the individual function.

  • Level: As per NMAM the Function can be defined in the tree structure, so the Level indicates the structure in which the function would be setup. Root nodes will be level 0 and the next level funds will have value as 1 and the next level as value 2.

  • Parent Type: If the ULB’s using multiple Functions then a Hierarchy of “Parent - Child “can be setup for the Function, so under each Parent Function a multiple child function can be setup.

Steps to fill data

  • Identify Functions that exists at a ULB level.

  • Download both the attached template and to updated all the details as per the above information in the empty template provided. The sample data template can be used as a reference to fill in the data.

  • Read through all the information above before updating the template with relevant information.

Validations

  • All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.

  • Function Code should to be unique.

  • The name should be unique, as the name is listed in drop-down of the transaction screen for selection.

  • The Length of the Code should not exceed 50 characters.

  • The Length of the Name should not exceed 100 characters.

Attachments

  • Refer to “Function” in the uploaded template.

  • For sample data reference, refer to the uploaded “sample date” file.

  • No labels