The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help

CurrentEN Web>CustomizingDocumentation>CustomizingFunctions>CustomizingCheck

From S 39.5.27

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 erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed (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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 = Relationship The number of data items (columns) of the relation (of the foreign key) with the mentioned index and ID of DI varies between the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [Exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [Exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): X vs. N2, EXIT rejected.=`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]):` `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 is displayed additionally: = `> DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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] and might hence 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 listed above.
`Broken value incarnation DI [data item ID] is missing a sub DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 possesses a VR type but no value range.
`OLE DI [data item ID] (DT [data table ID]) encountered with DB type "[DB type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.
`DI[data item ID 1] and DI[data item ID 2] share the same DB-Pos. (DT [data table ID])`	In each data table, the DB pos. must be unique. DIs with identical values in the SQL ID parameter as well as SQL = 4 form an exception. These data items may possess a double DB pos.
`DT021: invalid ACR start position!`	In DI Pos.OS, the wrong DB pos. of the first object protection field is stored.
`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)` NEW	This DI or this data table only exists in PLANTA and not in the database NEW 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 to 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 lengths specification in DT: [variable name]` `* Column: [SQL ID], Type: NUMBER`	In the DB, no field length is stored for the respective columns.

From S 39.5.15

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 erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed (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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 (of the foreign key) with the mentioned index and ID of DI varies in the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [Exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]): 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 is displayed additionally: = `> DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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] and might hence 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 listed above.
`Broken value incarnation DI [data item ID] is missing a sub DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 ("[ValueRangeType") 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 type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.
`DI[data item ID 1] and DI[data item ID 2] share the same DB pos. (DT [data table ID])`	In each data table, the DB pos. must be unique. DIs with identical values in the SQL ID parameter as well as SQL = 4 form an exception. These data items may possess a double DB pos.
`DT 021: invalid ACR start position!`	In DI Pos.OS, the wrong DB pos. of the first object protection field is stored.
`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]`	This DI or this data table only exists in PLANTA project and not in the database. Notes Each real, active DI must also exist as a column in the database. Each active data table must also exist in the 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]` NEW	The field length stored in the database is incorrect. This message is also displayed for standard DIs.
`No DB lengths specification in DT: [variable name] * column: [SQL ID], type: NUMBER` NEW	In the DB, no field length is stored for the respective columns.

From S 39.5.13

Automatic System Customizing Check

Information

Users for which the Customizer rights parameter is activated, receive the Problems in System Customizing error message upon login.
- In this dialog message, errors in the system customizing of customer specific objects (data items, exits, etc.) are pointed out. If erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed in the dialog message.
- 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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 (of the foreign key) with the mentioned index and ID of DI varies in the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID] , fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [Exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]): 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 is displayed additionally: = `> DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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 listed above.
`Broken value incarnation DI [Data item ID] is missing a sub-DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 ("[ValueRangeType") 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 type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.
`DI[data item ID 1] and DI[data item ID 2] share the same DB-Pos. (DT [data table ID])`	In each data table, the DB pos. must be unique. DIs with identical values in the SQL ID parameter as well as SQL = 4 form an exception. These data items may possess a double DB pos.
`DT 021: invalid ACR start position!`	In DI Pos.OS, the wrong DB pos. of the first object protection field is stored.
`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]` NEW	This DI or this data table only exists in PLANTA project and not in the database. Notes Each real, active DI must also exist as a column in the database. Each active data table must also exist in the database as a table. This message is also displayed for standard DIs.

From S 39.5.7

Automatic System Customizing Check

Information

Users for which the Customizer rights parameter is activated, receive the Problems in System Customizing error message upon login.
- In this dialog message, errors in the system customizing of customer specific objects (data items, exits, etc.) are pointed out. If erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed in the dialog message.
- 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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 (of the foreign key) with the mentioned index and ID of DI varies in the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID] , fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [Exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]): 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 is displayed additionally: = `> DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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 listed above.
`Broken value incarnation DI [data item ID] is missing a sub-DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 ("[ValueRangeType") 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 type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.
`DI[data item ID 1] and DI[data item ID 2] share the same DB-Pos. (DT [data table ID])`	In each data table, the DB pos. must be unique. DIs with identical values in the SQL ID parameter as well as SQL = 4 form an exception. These data items may possess a double DB pos.
`DT 021: invalid ACR start position!` NEW	In DI Pos.OS, the wrong DB pos. of the first object protection field is stored.

From S 39.5.3

Automatic System Customizing Check

Information

Users for which the Customizer rights parameter is activated, receive the Problems in System Customizing error message upon login.
- In this dialog message, errors in the system customizing of customer specific objects (data items, exits, etc.) are pointed out. If erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed in the dialog message.
- 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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 (of the foreign key) with the mentioned index and ID of DI varies in the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID] , fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [Exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]): 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 is displayed additionally: = `> DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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 listed above.
`Broken value incarnation DI [data item ID] is missing a sub-DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 ("[ValueRangeType") 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 type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.
`DI[data item ID 1] and DI[data item ID 2] share the same DB-Pos. (DT [data table ID])`	In each data table, the DB pos. must be unique. DIs with identical values in the SQL ID parameter as well as SQL = 4 form an exception. These data items may possess a double DB pos.

From S 39.5.2

Automatic System Customizing Check

Information

Users for which the Customizer rights parameter is activated, receive the Problems in System Customizing error message upon login.
- In this dialog message, errors in the system customizing of customer specific objects (data items, exits, etc.) are pointed out. If erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed in the dialog message.
- 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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [Data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 (of the foreign key) with the mentioned index and ID of DI varies in the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [Exit ID] (source ID [source data item ID], destination DT [source data table ID] , fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]): 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 is displayed additionally: = `DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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 listed above.
`Broken value incarnation DI [data item ID] is missing a sub-DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 ("[ValueRangeType") 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 type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.
`DI[data item ID 1] and DI[data item ID 2] share the same DB pos. (DT [data table ID])` NEW	In each data table, the DB pos. must be unique. DIs with identical values in the SQL ID parameter as well as SQL = 4 form an exception. These data items may possess a double DB pos. Currently, these DIs in the Problems in System Customizing dialog message must be displayed anyway.

New from S 39.5.0

Automatic System Customizing Check

Information

Users for which the Customizer rights parameter is activated, receive the Problems in System Customizing error message upon login.
- In this dialog message, errors in the system customizing of customer specific objects (data items, exits, etc.) are pointed out. If erroneous changes to standard objects are made, these errors, except for few exceptions, are not listed in the dialog message.
- 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 IDs must be unique within a data table.
`Could not resolve DB position alias for DI [data item ID]!`	Parallel data items (SQL = 4 and equal SQL ID) must have the same DB pos..
`Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID 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 is displayed: `Broken relation: DT [data table ID] ordinary [relation type] (index [index data table (foreign table)], DI [ID of 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 [ID of 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 (of the foreign key) with the mentioned index and ID of DI varies in the current data table and the referenced (target) data table. This relationship is ignored.
`Broken EXIT rejected: Exit [Exit ID] (source ID [source data item ID], destination DT [source data table ID] , fetch DI [fetch data item ID] )`	The exit was not customized correctly, it has no 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 was not customized correctly, it neither has a source DI nor a fetch DI.
`Broken EXIT [Exit ID](source ID [source data item ID], destination DT [source 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 was not 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 [source data table ID], fetch DI [fetch data item ID]): DB types of FEXIT and fetched DI do not match: X vs. N2, EXIT rejected.`	The exit was not customized correctly: The DB type of the data item on which the exit is customized, as well as the fetch DI do not match.
`Broken EXIT: DI 040753 (DT 082), Exit [exit ID] (source ID [source data item ID], destination DT [source data table ID], fetch DI [fetch data item ID]): 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 is displayed additionally: = `> DI 040753 (DT 082) tries to use fetch exit 00002336 out of context, hence will be dysfunctional.`	The exit was not 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 listed above.
`Broken value incarnation DI [data item ID] is missing a sub-DI with function [CO or ID] - incarnation property disabled.`	An incarnation requires a sub-DI with ID function as well as one with CO 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 ("[ValueRangeType") 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 type]", 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 ident alias for DI [DI ID]!`	It is a DI with SQL = 3, for which no DI SQL = 1 and same SQL ID exists.

39.5 Venus Current EN

PLANTA project

PLANTA pulse

PLANTA project

Suche in Topic-Namen
Suche in Topic-Inhalten