PLM_FOX_OBJ - Message from development class PLM_FOX_OBJ
The following messages are stored in message class PLM_FOX_OBJ: Message from development class PLM_FOX_OBJ.
It is part of development package PLM_FOX_OBJ_COM in software component LO-PDM. This development package consists of objects that can be grouped under "Basis and Help Classes of PLM_FOX Implementation".
It is part of development package PLM_FOX_OBJ_COM in software component LO-PDM. This development package consists of objects that can be grouped under "Basis and Help Classes of PLM_FOX Implementation".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Indicator for type '&1' cannot be determined |
| 002 | Parameter '&1' for class '&2' is not available |
| 003 | ECM processor cannot be initialized |
| 004 | Material '&1' not available |
| 005 | No system time zone could be read |
| 006 | The date can only be considered for a specific day |
| 007 | Object '&1' &2 does not contain any data |
| 008 | No object dependency found for object '&1' '&2' |
| 009 | No data available for object dependency for object '&1' '&2' |
| 010 | Unknown type '&1' for object dependency '&2' |
| 011 | Incorrect number of table lines in &1: &2 |
| 012 | Unknown status '&1' for object dependency '&2' |
| 013 | No cross reference available for '&1' '&2' |
| 014 | No characteristic for variant function '&1' |
| 015 | No characteristic for variant table '&1' |
| 016 | Class '&1' &2 is not available |
| 017 | Configuration profile '&1' has interface design '&2' |
| 018 | Error when accessing table '&2' for material '&1' |
| 019 | Invalid Mafid '&1' for classification '&2' |
| 020 | No management data for variant table '&1' |
| 021 | Active link of variant table '&1' to DB table '&2' |
| 022 | Inactive link of variant table '&1' to DB table '&2' |
| 023 | Empty variant table '&1' |
| 024 | Valid from date &1 is after the valid to date &2 |
| 025 | No parameter was entered for the validity explosion |
| 026 | Classification object '&1' is not supported |
| 027 | Unknown status '&1' for variant table &2 |
| 028 | No administrative data exists for variant function '&1' |
| 029 | Unknown status '&1' for variant function &2 |
| 030 | No header data available for class '&1' '&2' |
| 031 | No INOB-Entry for classification '&1' |
| 032 | No internal ID available for configuration profile '&1' '&2' '&3' '&4' |
| 033 | Classification '&1': No KSSK entry with object '&2' |
| 034 | Error when reading BOM '&1' |
| 035 | No value entered for the type of date |
| 036 | No data has been entered for object '&1' '&2' |
| 037 | Explosion profile '&1' not available |
| 038 | No constraints available for constraint network '&1' |
| 039 | Invalid combination of object type '&1' and class type '&2' |
| 040 | Classification '&1': |
| 041 | Unknown status '&1' for configuration profile object &2 &3 |
| 042 | Unknown status '&1' for characteristic &2 |
| 043 | GUIDs for BOM item have already been deleted |
| 044 | Initial change number transferred for check |
| 045 | Sum of all change numbers: &1 |
| 046 | Sum of all alternative dates: &1 |
| 047 | Internal Error: Missing Effectivity Parameter for &1 |
| 048 | Sum of change numbers: &1 |
| 049 | Sum of alternative dates: &1 |
| 050 | Change number &1 does not exist |
| 051 | Internal ID does not exist for interface design '&1' |
| 052 | No basic data exists for interface design '&1' |