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 7 Next »

Overview

Master data service maintains information of Government, Chart of Account, Department, Expenditure and Project. We can create these details and search the same details based on given parameters/request data.

Version History

Current version : 0.1.0

Prerequisites

Before you proceed with the configuration, make sure the following pre-requisites are met

  1. Java 8

  2. Mongodb instance

  3. Required service dependency - Department entity service.

Features

Create endpoint of master data service is secure and we need the access token for creating any master data.

Master data service maintains the details of below services:

Government :

This maintains the Government details and support create and search Government details. While creating the Government , we need a unique Id for the Government and a name for the same. Optionally, we can pass some additional details as part of attribute. In case of search, passing the unique id(s) as search parameters can given you all the details of the Government.

API List

Chart Of Account :

This maintains the Chart of Account(COA) details and support create and search COA. While creating the Chart of account, we need to pass the Government Id, majorHead, subMajorHead, minorHead, subHead, groupHead, objectHead and corresponding head names & types. A unique code named COACode will be generated always by combining (concatenating) majorHead, subMajorHead, minorHead, subHead, groupHead, objectHead with hyphen("-") and store with the given request.
Searching the details for COA will be done based on the provided search parameters like chart of account Ids, COACode, Government Id, majorHead, subMajorHead, minorHead, subHead, groupHead, objectHead.

API List

Department :

Maintains the create and search department details. While creating the department, pass the Government Id, department code, department name, parent department if any. Searching the department details will be on given parameters like ids, Government Id, department code, department name.

API List

Expenditure :

Maintains the expenditure details And provide create and search functionality. In case of creating the expenditure, need to pass the Government id, department id, code, name , type (can be "SCHEME","NON_SCHEME") details. While searching the expenditure details, pass the given parameters like ids, Government id, name, code.

API List

Project :

Maintains the project details and provide create and search functionality. In case of creating the project, need to pass Government, name, code, expenditure id, department entity id, location ids. While searching, pass the ids, Government id, name, code, expenditure id, location id.

It contains department entity information along with its hierarchy level and also attaches master department information (department id - UUID). Here we keep all children information list at every department node (department record). Leaf level department will not have any children info. Children list contains department entity id list, which makes current department entity parent of all children list (department id list), that's how it maintains department entity level.

API List

Interaction Diagram:

Environment

There will not be any environment variables required specific to the environment (migration).

Configurations and Setup

  1. Update all the DB and URI configuration in the dev.yaml, qa.yaml, prod.yaml file.

  2. Make sure keycloak server is up and running And have been configured with required client ID.

References and Notes

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.