Automatic System Customizing Check

Information

Users, for which the customizer rights parameter is activated receive the Problems in System Customizing dialog message.
- In this dialog message, errors in the system customizing of customer specific objects (data items, exits, etc.) are pointed out. If incorrect changes are made to standard objects, these errors are not listed in the dialog message, with a few exceptions (see table below).
- The messages are listed below one another.
In the following table, the different error messages and their meaning are explained.
In case an error message that is displayed on your screen is not listed in this table, please contact PLANTA.

Message	Explanation
`DI [data item ID] and DI [data item ID](DT [data table ID]) have the same Python ID "[data item Python ID]"`	The DI Python ID must be unique in the data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and same SQL ID) must have the same DB pos.
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ident of DI of the relation])` `ERROR: Mismatching number of local ([number of data items in the relation]) vs. foreign ([number of data items in the relation]) columns.` Subsequently, one of the following messages will be displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ident of the DI of the relation])` `ERROR: Truncating foreign part of the key. This relation cannot work; rejected.` `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ident of the DI of the relation])` `ERROR: Truncating local part of the key. Depending on the DIs involved, this relation may or may not work; rejected.`	Relation type = Relation The number of data items (columns) of the relation (foreign key) with the mentioned index and ident of DI differs between the current table and the referenced (target) data table. This relation is ignored.
`Broken EXIT rejected: Exit [exit ID] (source ID [source data item ID], destination DT [destination data table ID], fetch DI [fetch data item ID] )`	The Exit has not been customized properly. It neither has a fetch DI nor a fetch DI.
`Broken FETCH EXIT rejected: Exit [Exit ID] (source ID [source data item ID], destination DT [target data table ID], fetch DI [fetch data item ID])`	The Exit has not been customized properly. It neither has a source DI nor a fetch DI.
`Broken EXIT [exit ID] (source ID [source data item ID], destination DT [target data table ID], fetch DI [fetch data item ID])` `Data types of key DIs not matching: N4 (DI 002675, DT 479) vs. X (DI 002556, DT 471), EXIT rejected.`	The Exit has not been customized correctly: The DB type of the source DI as well as the DB type of the primary key from the fetch data table do not match. Note If the width of the columns is similar, like e.g. for DB type N2 and N4, the exit is not ignored since in certain cases it may work. Another example are data items with DB type X but different DB length
`Broken EXIT: DI 027756 (DT 029), Exit [Exit-ID] (source ID [source data item ID], destination DT [target data table ID], fetch DI [fetch data itemID]):` `DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The Exit has not been customized correctly: The DB type of the data item on which the exit is customized, as well as of the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [Exit-ID] (source ID [source data item ID], destination DT [target data table ID], fetch DI [fetch data itemID]):` `Data table of FEXIT DI and source key DI do not match: 082 vs. 080, EXIT rejected.` If the exit mentioned above is used on a DI, the following message will be displayed additionally: `DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The Exit has not been customized correctly: The data table of the DI on which the exit is stored does not correspond to the data table of the source DI.
`DI [data item ID] (DT [data table ID]) failed to retrieve its associated exit [Exit-ID], hence might be dysfunctional.` `The exit in question is likely to be nonexistent, or rejected due to reasons mentioned above.`	The exit of the DI could not be loaded for one of the reasons mentioned above.
`Broken value incarnation DI [data item ID] is missing a sub DI with function [KO oder ID] - incarnation property disabled.`	An incarnation requires a sub DI with ID function as well as one with KO function.
`DI [data item ID] not found, required by programmed exit of DI [data item ID]`	The respective data item does not exist or is deactivated.
`DI [data item ID] not found, required by formula of DI [data item ID]`	The respective data item does not exist or is deactivated.
`DI [data item ID] (DT [data table ID]) has a valid VR type set ("value range type") but no actual VR text.`	The data item has a VR type but no value range.
`OLE DI [data item ID] (DT [data table ID]) encountered with DB type "[DB-Typ]", setting to "X"`	DIs with class 13 must have DB type X.
`Table with id "[data table ID]" has no primary key relation and will thus not be loaded`	The data table has no primary key.
`Could not resolve DB position alias for DI [DI ID]!`	It is a DI with SQL = 3 for which there is no SQL DI = 1 and identical SQL ID.
`Di[data item ID 1] and Di[data item ID 2] share the same DB pos. (DT [data table ID])`	The DB pos. must be unique in each data table. DIs with identical values in the SQL ID parameter and SQL = 4 present an exception. These data items must possess a double DB position.
`DT021: invalid ACR start position!`	In DI Pos.OS, the wrong DB pos. of the first object protection field is specified.
`Database Schema does not match System Customizing / Data Dictionary:` `Missing column in DB: DI[data item ID] in Dt[data table ID 1]` `Missing table in DB: DT[data table ID 2]` `Table has no field called UUID: PLANTATable (xxx, DTxxx)`	This DI or data table only exists in PLANTA and not in the database or the UUID is missing in the PLANTA data table Note Each real, active DI must also exist as a column in the database. Each active data table must also exist as a table in the database. This message is also displayed for standard DIs. If changes have recently been made to the database, it may be sufficient to delete the "target" subdirectory in the PLANTA Server directory and restart the server
`Wrong column length in DB: [Variable name]` `* Column: [SQL ID], Type: [Data type]. Found: [Field length on the database], expected: [expected field length]`	The field length stored in the database is incorrect. This message is also displayed for standard DIs.
`No DB length specification in DT: [Variable name]` `* Column: [SQL ID], Type: NUMBER`	In the DB, no field length is stored for the respective columns.