How to design structure of the constant table for intranet web applications

My definition

constant table - Db table that use to keep value and description or running number for something e.g. Table_Constant

   System    Key    Subkey        Descript
     A     status     01          Waiting 
     A     status     02          Reserved 
     A     running1   no_current    99
     B      ...

My question is Is there any concept support for this below approach.
the company has many intranet systems(website) for different department which each has the constant value like status that used in its system , the current implement is for all system to use the Table_Constant as the only table to keep each system 's constants (which usually not relate to the different systems)

In my opinion I think each different systems should have the different constant table to keep its own constant. But the use of only one table has an advantage when debug/ maintenance the system.