/IAM/CONFIG - Message for Configuration
The following messages are stored in message class /IAM/CONFIG: Message for Configuration.
It is part of development package /IAM/DDIC in software component CA-IAM-ENG. This development package consists of objects that can be grouped under "Common DDIC and surrounding functions (F4,View-Maint.,.)".
It is part of development package /IAM/DDIC in software component CA-IAM-ENG. This development package consists of objects that can be grouped under "Common DDIC and surrounding functions (F4,View-Maint.,.)".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Enter a key |
| 002 | No mapping found for object category &1 |
| 003 | No active system connection for issue categories available |
| 004 | No active system connection for activity categories available |
| 005 | No setting found for object type &1 |
| 006 | You have no authorization for this function (authorization object &1) |
| 007 | No active implementation for BAdI &2, object category &1 |
| 008 | Add corresponding customizing entry for object category &1 and system &2 |
| 009 | BAdI implementation for object category &1 contains syntax errors |
| 010 | Object category &1 is not supported in the local system |
| 011 | Type &1 does not exist |
| 012 | BAdI implementation of /IAM/BADI_OBJECT_TYPE for object type &1 missing |
| 013 | Sort number &1 already exists |
| 014 | Activity type &1 with category 'information' is not supported |
| 016 | Only one main reference object is allowed |
| 017 | Main reference object cannot be deactivated |
| 018 | Node cannot be created due to recursion |
| 019 | Subactivities cannot be created due to recursion |
| 020 | No system key available in system landscape directory for &1 |
| 021 | Save your changes to continue |
| 022 | No usages of code &1 found in code groups |
| 023 | Usages of code &1 found in code groups |
| 024 | Deactivate codes assigned to a code group instead of deleting them |
| 025 | Deactivate existing codes instead of deleting them |
| 026 | Select only one entry in the table |
| 027 | Code groups that you are not authorized to change are not visible |
| 028 | Application &1 belongs to SAP and cannot be deleted |
| 029 | Only one Print Form can be defined as Default Print Form |
| 030 | No active implementation of BAdI /IAM/BADI_OBJECT_TYPE for obj. type &1 |
| 031 | Field &1 of structure &2 does not exist in &3 structure of obj. type &4 |
| 032 | Field &1 incompatible between struct. &2 and struct. &3 of obj. type &4 |
| 033 | Object type &1 does not provide a UI structure name or element name |
| 034 | Object category &1 is already assigned to another object type &2 |
| 035 | Different mappings exist for specified target systems and category &1 |
| 036 | Entry &1 not valid |
| 037 | Catalog &1 does not exist |
| 038 | Code &1 does not exist |
| 039 | Code group &1 does not exist |
| 041 | Code &1 is not active and cannot be used |
| 042 | Deletion not possible; code assignments exist for code group &1 |
| 043 | Code &1 is still in use in code groups |
| 044 | You cannot delete catalog &1 as it is still in use |
| 045 | Alias &1 not found |
| 046 | Save your changes first |
| 048 | No valid jump destination found for category &1 |
| 049 | Clicked field marker not found |
| 050 | Do not use the characters *, +, %, and @ in key &1 |
| 051 | Do not use a blank in key &1 |
| 052 | Do not use only '0' in key |
| 053 | Object type &1 cannot be deleted because it is still in use |
| 054 | Object category &1 cannot be deleted because it is still in use |
| 055 | Object type &1 does not provide a UI structure name |
| 056 | Incompatible structure/data element for object type &1 |
| 057 | Unknown internal error in program &1 |
| 058 | Issue type &1 cannot be assigned to an activity template |
| 059 | An existing activity template already uses the key &1 |
| 060 | There are activity types that have no partner roles assigned |
| 061 | One activity template is not linked to the net |
| 062 | Internal error during creation of XML file for graphic |
| 063 | Partner Role &1: Business partner group hierarchy is missing |
| 064 | Partner Role &1: Business partner group hierarchy &2 does not exist |
| 065 | Position &2 does not exist in business partner group hierarchy &1 |
| 066 | Enter either a business partner number or a position |
| 067 | Enter a partner role code if a position is entered |
| 068 | Activity category &1 is not available |
| 069 | Object category &1 for object type &2 is not available |
| 070 | Mapping &1 with step &2 does not exist |
| 071 | BAdI definition for object type &1 missing |
| 072 | Drop the template on a valid node |
| 073 | Enter a partner role code |
| 074 | Entry already exists |
| 075 | Authorization group &2 does not exist for application &1 |
| 076 | Application &1 does not exist |
| 077 | System &2 does not offer any active access type for object type &1 |
| 078 | Category &1 is already entered for object type &2 in system &3 |
| 079 | No text in language &2 found for application &1 |
| 080 | No text in language &2 found for criticality &1 in application &3 |
| 081 | No text in language &2 found for priority &1 in application &3 |
| 082 | No text in language &2 found for duration &1 in application &3 |
| 083 | No text in language &2 found for country/region &1 |
| 084 | No mapping found for object category &1 and node &2 |
| 085 | Node category &1 does not exist for node &3 of business object &2 |
| 086 | Template &1 cannot be deleted because it is assigned in Customizing |
| 087 | Number range intervals are mandatory entries |
| 088 | Number range &1 is not valid |
| 089 | Function &2 in application &1 does not exist in BRFplus |
| 090 | Application &1 does not exist in BRFplus |
| 091 | Application is missing for function &1 |
| 092 | Issue type &1 is still being used by &2 and cannot be deleted |
| 093 | No text in language &2 found for timepoint &1 |
| 094 | No text in language &2 found for time zone &1 |
| 095 | No long text exists |
| 096 | No text in language &2 found for logical system &1 |
| 097 | No text in language &2 found for object category &1 |
| 098 | Code &1 is not assigned to code group &2 |
| 099 | Code &1 cannot be assigned without a valid code group |
| 100 | Code group &1 cannot be assigned to code group &2 to avoid recursion |
| 101 | No authorization to define code groups for catalog &1, auth. group &2 |
| 102 | Authorization check problem with authorization object &1 |
| 103 | No authorization to access data of object category &1 in system &2 |
| 104 | Hierarchy tree not needed for position origin &1 |
| 105 | Position &1 does not exist or is not valid for partner role code &2 |
| 106 | BAdI implementation for position origin &1 is missing |
| 107 | Code group &1 does not belong to catalog &2 |
| 108 | Code group &1 is already assigned to code group &2 as a subcode group |
| 109 | Role &1 is not unique in activity template &2, despite acty type settings |
| 110 | You cannot enter partner role &1 more than once |
| 111 | Code group &1 is not active |
| 112 | It is not allowed to use issue type of category &1 as subissue types |
| 113 | Issue type &1 of issue category &2 is already assigned |
| 114 | You must define a responsible partner role |
| 115 | No text in language &2 found for follow-up action &1 |
| 116 | No text in language &2 found for document type &1 |
| 117 | Document type &1 does not exist |
| 118 | Document schema &1 does not exist |
| 119 | Function is not supported for application &1 |
| 120 | &3; Launchpad Customizing not updated; role &1 or instance &2 missing |
| 121 | Launchpad Customizing for BRFplus rule maintenance not configured for &1 |
| 122 | Partner role codes starting with 'SAP' are not in the allowed namespace |
| 123 | Only partner role codes starting with 'SAP' are in the allowed namespace |
| 124 | Attachment schema &1 does not allow attachments to be added |
| 125 | Default attachment type &1 is used |
| 126 | Document schema &1 assigned to BO &2 is not allowed |
| 127 | MIME type &1 does not exist |
| 128 | MIME type &1 is already assigned to document type |
| 129 | Document type &1 is already assigned to document schema |
| 130 | Document type &1 cannot be deleted because it is still in use |
| 131 | Document schema &1 cannot be deleted because it is still in use |
| 132 | Text type &1 is already assigned |
| 133 | Partner role cannot be used because it is inactive |
| 134 | Enter position or business partner only for a given partner role code |
| 135 | Code group will be ignored if response type of &1 is not set to code(C) |
| 136 | Code &1 is not assigned to catalog &2 |
| 137 | Issue type &1 is still in use in issues |
| 138 | |
| 140 | Enter an initiator partner role |
| 141 | For partner roles with position origin ' ' you can only assign BPs |
| 142 | Role code &1 has already been entered for the responsible partner role |
| 143 | Role code &1 has already been entered for the initiator partner role |
| 144 | Role code &1 has not been entered in Customizing |
| 145 | You are not allowed to enter the initiator partner role &1 |
| 146 | Responsible partner role &1 is not yet entered |
| 147 | Mandatory partner role &1 is not yet entered |
| 148 | All existing role codes are entered |
| 149 | Issue type text is not entered |
| 150 | Activity template text is not entered |
| 151 | User &1 (&2 &3): Has business partner assigned |
| 152 | User &1 (&2 &3): Business partner &4 was successfully created |
| 153 | PFCG role &1 does not exist |
| 154 | Telephone number for business partner missing |
| 155 | E-mail address for business partner missing |
| 156 | Document type &1 does not fit to activity template &2 |
| 157 | User &1 (&2 &3): Business partner creation possible |
| 158 | User &1 (&2 &3): Business partner creation not possible |
| 159 | User &1 (&2 &3) data differs from business partner data: Update possible |
| 160 | User &1 (&2 &3): Business partner &4 was successfully updated |
| 161 | Log deleted |
| 162 | Position and business partner not permitted in same row &1 |
| 163 | Partner role (row &1) is not assigned to the issue type in Customizing |
| 164 | Default partner role is not yet entered |
| 165 | Role codes have not been entered in Customizing |
| 166 | Parameter cannot be maintained without follow-up action |
| 167 | No user with PFCG role &1 exists |
| 169 | No active BAdI implementation for follow-up action &1 |
| 170 | Maintain the parameter for the follow-up action in activity template &1 |
| 171 | Activity template (row &1) has different activity type in Customizing |
| 172 | Activity type &1 is still in use, for example, by activity template &2 |
| 173 | Partner role (row &1) is not assigned to the activity type in Customizing |
| 174 | No text in language &2 found for partner role &1 |
| 175 | The duration unit must be a unit of time, for example, day, month, year |
| 177 | An existing partner role has already been defined as the default role |
| 178 | MIME type &1 not allowed for document type &2 |
| 179 | Digital signature not allowed for activity type &1 |
| 180 | Use a signature strategy with signature method '&1' |
| 181 | Unexpected selection option &1 |
| 182 | Invalid value '&2' for selection option &1: '*' is not allowed here |
| 183 | Enter a value for selection option &1 |
| 184 | Digit. signature application &1 or digit. signature object &2 not found |
| 185 | 'Default Remark' indicator must be unique for status '&1' and action '&2' |
| 186 | Signature object &1 unknown |
| 187 | Status prof. &1 uses action &2, which is not valid for activity cat. &3 |
| 188 | Status profile &1 uses action &2, which is not defined in Customizing |
| 189 | BO action &1 is not allowed due to use of status action &2 |
| 190 | BO action &1 is not allowed due to use of status profile &2 |
| 191 | Status profile '&1' cannot be assigned to activity type '&2' |
| 192 | Status profile '&1' cannot be assigned to issue type '&2' |
| 195 | Issue type &1 cannot be used because it is inactive |
| 196 | Issue type &1 has no issue category assigned in Customizing |
| 197 | Text type '&1' only allows '&2' for historical texts |
| 199 | Residence time set to &1 days (default value in Customizing) |
| 200 | No print forms entered for activity type &1 |
| 201 | No print forms entered for issue type &1 |
| 202 | Printing not allowed for issue category &1 |
| 203 | Selection of defects is not supported for activity forms |
| 204 | |
| 210 | Settings for date determination cannot be saved due to self-reference |
| 211 | Settings for date determination cannot be saved due to recursion |
| 212 | Timepoint code &1 could not be used here |
| 215 | Only change requests of category MOC can have children |
| 220 | &1 is already a Prerequisite Activity for Automated Status Change No. &2 |
| 221 | Activity Template &1 is already assigned |