Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

hi can any one explain,

0 Kudos

From fixed value ranges, value table, interval in domain, which will triggered first?
and value table is a domain specific and it will automatically generates the foreign key relationship if we define the value table in the domain, so for this reason only we are creating value table or else it has any other advantages over check table?


Active Contributor

1. You ask "Which will triggered first" : see the diagram here

2. Don't you think that it's already a huge advantage, and this advantage justifies the existence of a value table!? Moreover the values in a value table can dynamically change as they are changed by applications, while values in a domain can only be changed manually.

Active Contributor
0 Kudos

Same question has been raised here:

"Value Table versus Single Values ('fixed value') and Intervals ('fixed range')":

Both have their advantages and disadvantages. You can assign non, one of each or both.

Please always consult the ABAP documentation / Performance Assistant (F1) first, search for related threads, and then come back with further questions if necessary:

Single Value and Interval

  • The value range of a domain can be limited by defining fixed values. In this case, only the values entered in the fixed values are possible for all the table fields referring to this domain. The fixed values can be single values or intervals.
  • Fixed values and intervals generally have to be transported, the values are the same in the different systems. The transport of the fixed values is linked to the transport of the domain.
  • For maintenance reasons, if you have hundreds, thousands of single values, a value table might be more suitable

Value table

  • In some cases you already know when you define a domain that all the fields referring to this domain should be checked against a certain table. This information can be stored in the domain by entering a value table.
  • The system proposes the value table as check table when you try to define a foreign key for this field. You can override this proposal.
  • Entering a value table does not implement a check. The check against the value table only takes place when a foreign key is defined.
  • Value table records can be transported, but they dont have to be transported, they can be different in the different systems. The transport of the value table records is separate from the domain. Depending on the setup of the value table, the records can be maintained by users in all systems.
  • Value tables also offer to store more data about the record

Main Difference

  • As described above, Single Values are always automatically checked at Input in a mask. Value table records are only automatically checked at Input in a mask, when the value table is used as a check table in the case as a defined foreign key for the field.


  • If a check table and fixed values are defined for a table field, only values that exist in both the check table and in the fixed values can be entered in the field.