/IAM/OBJECT_INT - Object Messages That Cannot Be Redefined
The following messages are stored in message class /IAM/OBJECT_INT: Object 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 | Value &1 could not be converted to a valid quantity |
| 002 | Value could not be converted to Boolean ("X" = true," " = false) |
| 003 | Code &1 could not be used (preconditioned code group &2) |
| 004 | Internal error during Workflow event creation (Class &1) |
| 005 | No valid BAdI implementation for actual client and follow-up action &1 |
| 006 | Follow-up action &1 not supported for system &2 |
| 007 | Mandatory object type &1 missing for follow-up action &2 |
| 008 | No unique system for follow-up action &1 |
| 009 | Follow-up action &1 not executed |
| 010 | Internal error during mapping call &1 |
| 011 | Action needs parameter structure of type &1 |
| 012 | Value for parameter &1 of action is missing or wrong |
| 013 | Missing authorization to perform action activity &2 (author. object &1) |
| 014 | Action could not be processed for business object &1 |
| 015 | Action is only allowed from status &1, but the current status is &2 |
| 016 | Action is only allowed from BO status &1, &2, current status is &3 |
| 017 | Action is forbidden for BO status &1, &2, current status is &3 |
| 018 | Object &1 &2 in system &3 successfully created by follow-up action &4 |
| 019 | Digital signature process started; choose 'Sign' to proceed |
| 020 | Target system for follow-up action &1 missing |
| 021 | Mandatory parameter &1 missing for follow-up action &2 |
| 022 | ID mapping active in target system &1 for follow-up action &2 |
| 023 | Digital signature Customizing is inconsistent |
| 024 | Digital signature is not possible because PDF generation failed |
| 025 | Scheduling for &1 &2 not executed |
| 026 | &1 &2: &3 has been scheduled automatically |
| 027 | &1 &2: &3 has been rescheduled automatically |
| 028 | &1 &2: &3 has been removed automatically |
| 029 | Action EXECUTE_USER_STATUS_ACTION called without a user status action |
| 030 | Replace temporary number &1 set by system |
| 031 | Assigned action &1 is not valid for business object |
| 032 | User status action &1 is not allowed for &2 |
| 033 | A user status prevents the action being executed |
| 034 | &1 changed to &2 |
| 035 | No further entry could be created |
| 036 | Value could not be converted to tri-state ("X"=Yes," "=No,"-"=Undefined) |
| 050 | &2 Mandatory field "&1" must be filled &3 |
| 099 | ------------------------------------------------------------------------- |
| 100 | Indexing &1: Extraction started |
| 101 | Indexing &1: Extraction completed |
| 102 | Extracting package &1 |
| 103 | Extraction of package &1 completed |
| 104 | Object type &1 not supported by extractor impl. &2 |
| 105 | Model node &1 has sel. options but no suitable backend query was found |
| 106 | Extraction error: No request entry for root node &1 |
| 107 | Extraction error: Object type, root node name, or category missing |
| 108 | Indexing &1: Extraction stopped due to errors |
| 109 | Full indexing mode (initial extraction/model change/index corruption) |
| 110 | Field &1, &2 omitted: No corresponding back-end field at same level |
| 111 | Inconsistent call of extractor: Empty request, nothing to select |
| 112 | Extraction error: No data for field &1, &2 |
| 113 | High number of lines (&1) for current package |
| 114 | Package size not limited for current package |
| 115 | Starting key selection via BOBF query &1 |
| 116 | No indexable objects found |
| 117 | Package size is &1 |
| 118 | This is the last package |
| 119 | Object node &1 missing in call for ESH object type &2 |
| 120 | Get ESH object type &1 instead of &2 in extractor class &3 |
| 121 | Starting data selection for node &1 via BOBF query &2 |
| 122 | Data selection for node &1 found &2 lines |
| 123 | Key selection found &1 lines |
| 124 | Delta extraction mode (change pointer based) |
| 125 | Extraction error: No matching BO node for model node &1 |
| 126 | Field &1, &2 omitted: Cross-BO mapping not supported by this extractor |
| 127 | Extraction error: No matching BO node data for model node &1 |
| 128 | Extraction error: Duplicate BO node data; aborting |
| 129 | Extraction filter &1, &2: No corresponding back-end field; aborting |
| 130 | Extraction error: Conversion of field &1 (value &2) to &3-&4 failed |
| 131 | Delta mode (change pointer based) |
| 132 | Empty request, no keys provided |
| 133 | No root level data provided |
| 134 | Invalid parent node type id &1 provided for node &2 |
| 135 | Check of relation fields: Structure of &1 has no field &2 |
| 136 | Check of relation fields: Relation field &1 of &2 line &3 is initial |
| 137 | Line &1 of &2 has no parent |
| 138 | Line &1 of &2 has more than 1 parent (&3) |
| 139 | Starting consistency check |
| 140 | Consistency check completed |
| 141 | Ambiguous change pointer &1: created &2 modified &3 deleted &4 (->ignore) |
| 142 | Objects to be processed: &1 (New: &2, modified &3, deleted &4) |
| 143 | Starting data selection from BOBF BOs |
| 144 | Data selection from BOBF BOs completed |
| 145 | Starting mapping of BOBF data to ESH model structures |
| 146 | Mapping of BOBF data to ESH model structures completed |
| 147 | Mapping to node &1 created &2 lines |
| 148 | Category &1 is unknown |