Inheritance Mechanism for Infotype and Related Fields

In addition to the attributes described in the prior topic , tables T588MFPROPS and T588MFPROPC both feature the key fields Infotype (INFTY), ID for Infotype Versions (ITVERS) and Subtype (SUBTY), which enable the system to differentiate among the infotype, infotype version and subtype, respectively.

Note Note

The information presented in this topic exceeds the general knowledge that is required to create (or migrate) infotypes in(to) this release. Individuals who have particular expertise in this subject matter or who desire deeper knowledge of this issue may nonetheless consult this topic for reference.

End of the note.

To avoid the necessity of maintaining entries for all country versions and all subtypes, the standard system features an inheritance mechanism, described in the following diagram, which instructs it to evaluate the most specific of the key fields INFTY, ITVERS and SUBTY. In the context of this mechanism, generic entries are created by setting the key field ITVERS or the key field SUBTY (or both key fields) to space ( ‛ ’ ), as shown below in Diagram E.

This graphic is explained in the accompanying text.

If corresponding entries also exist in table T588MFPROPC – and provided that the FIXED attribute is not specified in table T588MFPROPS for these entries – then the inheritance mechanism will evaluate the key fields in the manner described below, in Diagram F.

This graphic is explained in the accompanying text.

If entries exist in table T588MFPROPC for which the FIXED attribute is specified in table T588MFPROPS, then the evaluation of key fields continues as described in Diagram F, but omits all customer entries that are “fixed” in table T588MFPROPS.