Generally, all information that is used in the respective business transactions can form the basis for the collection and aggregation of application data in the information structures.
Much of this information is designed, however, for the internal control of a business transaction rather than for updating statistical data.
Therefore, if a user wishes to define his/her own information system by using self-defined information structures , he/she must be able to clearly recognize which type of information he/she can use for the Logistics Data Warehouse. The definition of field catalogs guarantees that this information can be easily recognized.
A field catalog (as understood in statistics updating) defines a group of relevant fields from the application. You can thus use a mixture of fields from any document hierarchies.
This means that all fields that refer to the sales organization (distribution channel, sales district, product hierarchy, etc.), can be combined into one field catalog. It is not important for the user to know whether these fields are used at document header, document item, or schedule line level.
A field catalog therefore takes on the following functions:
Long names are not supported in LIS. You can only include fields in the field catalog if their table name/structure name/field name does not exceed ten characters.