/IAM/CONFIG_INT - Customizing Messages That Cannot Be Redefined
The following messages are stored in message class /IAM/CONFIG_INT: Customizing Messages That Cannot Be Redefined.
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 | Node category of Business Object Proc. Framework could not be determined |
| 002 | System initialized some fields |
| 003 | Not enough visible lines available to take over all selected objects |
| 004 | No usages of code group &1 found in other code groups |
| 005 | View cluster &1 could not be called |
| 006 | Direct navigation not possible; go to next level first |
| 007 | Cannot call action &1 of business object &2 |
| 008 | Business object &1 does not exist |
| 009 | Specify either a user status action or a BO action |
| 010 | Status field &1 does not have a valid status &2 |
| 011 | Status &2 of status field &1 will be used |
| 012 | Deactivate existing statuses instead of deleting them |
| 013 | Status action &1 will be used |
| 014 | Adobe form does not have a suitable interface parameter |
| 015 | Wrong combination of import parameters for method call &1 |
| 016 | Enter a valid text type |
| 017 | Historical text type &1 does not allow field control for text fields |
| 018 | Deactivate existing status actions instead of deleting them |
| 019 | User status action &1 is not defined in Customizing |
| 020 | For delivered BO actions, only the option "Action Prohibited" is valid |
| 021 | Enter the reference to be used for timestamp calculation |
| 022 | Enter the offset to be used for timestamp calculation |
| 100 | ***** Generic Messages for BOL ****************************************** |
| 101 | BOL object type &1 is not part of the component &2 |
| 102 | Data element &1 is no attribute of BOL object type &2 |
| 103 | BAdI &1 does not have the filter attributes CLIENT and CATEGORY |
| 104 | BAdI &1 does not exist |
| 105 | &1 has to be an elementary search help |
| 106 | Search help &1 does not exist in current system |
| 107 | Search help of type &1 in component &2 requires key element &3 |
| 108 | Table &1 cannot be read via RFC connection &2 |
| 138 | Document type &1 cannot be deleted because it is still in use |
| 139 | Hierarchy tree is not needed if you have not specified a position origin |
| 159 | Name or country/region is missing |
| 160 | Business partner log |
| 161 | Creation of business partner for user &1 skipped |
| 162 | User &1 was assigned to business partner &2 |
| 166 | Please assign user &1 to person &2 |
| 167 | Multiple values for parameter &1 are not allowed |
| 168 | Parameter &1 is not supported by follow-up action &2 |
| 169 | Please assign user &1 to business partner &2 |
| 202 | Error when saving shared objects memory |
| 203 | Error when reading shared memory |
| 204 | Error when reading remote data into shared memory |
| 250 | Business Object Action &1 does not exist for automated status change |
| 251 | User Status Action &1 does not exist for automated status change |
| 252 | Activity Template &1 does not exist or is set to inactive |
| 253 | Please enter an Activity Template |
| 254 | Activity Template &1 with category &2 is not allowed |