Understanding Data Relationships Rules
These rules apply to data relationships:
Only one set of current rules can exist for a supported table. For each set of rules, sequencing is set up to determine the order of the default values. Each sequence level for a set of rules must be unique.
The destination table must be the same as the basis table.
If more than one entry program exists for a table, the default rules are the same regardless of the entry program. For example, for the F0006 table, the default rules are the same for both the Business Unit Master (P0006) and Job Cost Master (P51006) programs.
A single basis column and value can populate multiple destination columns and values. For example, if the basis column is category code 01 and the value is ABC, then the destination columns could be category codes 02 and 03 with values 123 and XYZ, respectively, within the same table.
The basis and destination columns are edited based on the data dictionary rules for the respective data item. For example, assume that an administrator defines category code 01 as the basis column. When a user selects the visual assist for the basis value, the user should see a list of values for category code 01.
The data relationships functionality can also be used by customers who conduct business with the government. You can set up data relationships rules for government contracts.