First level link type support:
This field is used in a different way from a syntax point of view according to whether the user is defining a first level support or a grouping support. Within the framework of a first level support, it is necessary to define the values of the different components of the index previously specified.
The number of values entered must absolutely be equal to the number of index key components. It is not possible to use only the first or second part of an index.
Key component entry syntax rules:
1/Each key component must be separated by a semicolon.
2 / Each alphanumeric value must be between quote marks.
3/ Although not mandatory, but in order to avoid all risks of conflict in variable names, it is strongly recommended to enter each field name before by its standard class abbreviation.
Grouping type support:
The field to field associations are easy to define and agree perfectly with the links to a single component.
Unfortunately, certain links require addition information to be correctly established.
The Address table (BPADDRESS) is a good example. This contains a BPANUM field containing the entity code for which the address is defined. The problem rests in the fact that the BPANUM field can contain either a BP code, a Company code or even a Site code. Additional information is required to discriminate more precisely the relationship between BPADDRESS and BPARTNER. This information is stored in the BPATYP field. If the user wants to work only in the address sub-group relative to the BPs, it is therefore necessary to add an additional filter: