/SCMTMS/COND - Message Class for conditions
The following messages are stored in message class /SCMTMS/COND: Message Class for conditions.
It is part of development package /SCMTMS/CONDITION in software component TM-BF-CND. This development package consists of objects that can be grouped under "BO Conditions".
It is part of development package /SCMTMS/CONDITION in software component TM-BF-CND. This development package consists of objects that can be grouped under "BO Conditions".
Message Nr ▲ | Message Text |
---|---|
001 | Condition &1 does not exist, BRFplus applciations are deleted only |
002 | Multiple conditions with the same cond. ID exist; unused cond. deleted |
003 | Copy of BRFplus Application for conditon &1 failed |
004 | Enter a name for the copied condition |
005 | Condition &1 cannot be changed from BRFplus to direct BO access |
006 | Condition &1 is inactive and does not return results |
007 | No BO data defined for condition type in table /SCMTMS/I_CNDDEF |
008 | BO node definition without BO definition is not supported |
009 | BO used for condition does not match BO used in data access definition |
010 | Condition type &1 allows only 1 cond. per system; cond. &2 already exists |
011 | Data access definition &1 does not exist |
012 | Invalid name; a BRFplus application already exists with this name |
013 | SAP-TM-specific conditions cannot be changed in customer systems |
014 | Condition name already used in an existing condition |
015 | Condition name must not contain any spaces |
016 | You have to enter a condition type |
017 | You have to indicate an origin of condition |
018 | Copy not possible. Not all objects of application &1 are active. |
019 | Condition name must not be longer than 25 characters |
020 | Severe error in BRFplus call for condition &1; check BRFplus application |
026 | Only standard conditions are used for condition type &1 |
030 | Requested condition not found |
031 | You are not authorized to display the requested condition(s) |
032 | You are not authorized to perform this action for the condition |
033 | You are not authorized to create this condition |
034 | You are not authorized to edit this condition |
035 | You are not authorized to delete this condition |
036 | Maximum length of condition ID for chrge mgmt conditions is 20 characters |
037 | Only one data access definition is allowed to BO based conditions |
038 | You are not authorized to transport this condition |
039 | |
047 | Business object &1 does not exist |
048 | There must be at least one data access definition |
049 | Enter a valid input definition for data access definition &1 |
050 | Node &1 belongs to different business object &2; adjust node or BO |
051 | Field &1 belongs to different node; adjust field |
052 | Business object &1 not allowed for this condition type |
053 | Data crawler and business object access not allowed |
054 | Class with class name &1 does not exist |
055 | Class with class &1 name does not implement correct interface &2 |
056 | For condition type &1 only BO &2 data can be used in condition definition |
057 | Key Field Value is not in value range of data element |
058 | Key Field Value is specified, but Key Field Name is not |
059 | Data element &1 does not exist |
061 | Condition &1 is still being used |
062 | Condition &1 is still being used by freight order type &2 |
063 | Condition &1 is still being used by freight unit type &2 |
064 | Condition &1 is still being used by freight booking type &2 |
065 | Data crawler profile &1 does not exist |
066 | Step &2 was not defined for data crawler profile &1 |
067 | Data crawler profile &1, step &2 has no element &3 |
068 | &1 is not a data dictionary element |
069 | Only default DAD can be used for condition type &1; &2 is not default DAD |
070 | Table-based input supported only for conditions based on BRF+ expression |
071 | Field name is required when you use a table type with no structure |
072 | Assigned data crawler &1 uses incorrect start BO node |
073 | Data crawler step &1 must not be defined without data crawler profile |
074 | Data crawler fieldname &1 must not be defined without data crawl. profile |
080 | BRFplus object cannot be transported |
101 | Data access definition &1 of condition &2 had no result for &3 |
102 | Value &1 not supported as class attribute for class &2 |
103 | Lean BRFplus trace has been saved with external ID &1 |
201 | Variant &1 unknown |
300 | Data access definition &2 of condition &1 found value &4 for BO &3 |
301 | You need to save to finalize BRFplus update |