User guide - Master Data

This page present the list of data/properties/resources that can be managed and updated in OpenLMIS, and the division of who can easily do it – either the in-country OpenLMIS users (Table 1), or the development team (Table 2).

 

Table 1. The list of data / properties / resources that can be managed by the in-country OpenLMIS users

OpenLMIS Users

Data / Properties / Resources

Create

Update

Tips

Equipment (Inventory) Items

Must be defined before creating new Equipment:

  • Equipment Catalog

  • Programs

  • Facilities

Facilities

Must be defined before creating new Facility:

  • Facility Types, 

  • Facility Operators, 

  • Geographic Zones

Must be define after creating new Facility to use it in application:

  • Associated Programs

  • Supervisory Nodes

  • Requisition Groups

Notice that changing the facility type may change requisition template for the specific facility

Facility Types

 

Ideal Stock Amounts

 



Product

General note: The product update does not affect the requisition or stock forms that were created before the change. Product changes will be visible only on the requisition forms or on the stock forms that will be created after these changes.

Orderable

Must be defined after creating new Orderable to use it in application:

  • Program Orderables

  • Facility Type Approved Products

Program Orderable

Must be defined before creating new Program Orderable:

  • Programs

  • Orderable Display Categories

Facility Type Approved Products

Must be defined before creating new Facility Type Approved Products:

  • Orderable

  • Program Orderables

  • Facility Types

Orderable Kits

Must be defined before creating new Orderable Kits:

  • Orderables

Processing Periods

Must be defined before creating new Processing Periods:

  • Processing Schedules

Processing Schedules

Must be defined after creating new Processing Schedules to use it in application:

  • Processing Periods

New processing schedules must be added by the development team to the appropriate requisition group to start using it in requisition

Programs

 

Reasons

Must be defined before creating new Reasons:

  • Reason Categories

  • Reason Types

  • Programs

  • Facility Types

Requisition Templates

Must be defined before creating new Requisition Templates:

  • Facility Types

  • Programs

Roles

 

Service Accounts



Supervisory Nodes

Remember that removing a parent from the supervisory node will also result in the lack of an object that will be able to approve its requisition.  For this reason, remember to assign another parent who will approve the requisition.

Supply Partner Associations

Must be defined before creating new Supply Partner Associations:

  • Programs

  • Supervisory Nodes

  • Facilities

  • Orderables

Supply Partners

Must be defined after creating new Supply Partners to use it in application:

  • Associations

Users

Must be defined after creating new User to use it in application:

  • Users roles

Users Roles

Must be defined before creating new Users roles:

  • User

  • User rights

  • Supervisory Nodes



Table 2. The list of data / properties / resources that must be managed by the development team

Development Team

Data / Properties / Resources

Create / Update

Commodity Types

Currencies

Email Notifications

Facility FTP

Facility Operators

Geographic Levels

Geographic Zones

Lots

Nodes

Orderable Display Categories

Organizations

Requisition Groups

Requisition Group Program Schedules

Stock Card Line Item Reasons

Stock Destinations

Stock Reasons

Stock Sources

Supervisory Nodes

Supply Lines

Time Zones

Trade Items

Translations

User Rights