S_BCFG_API - Exception texts for package S_BCFG_API_*
The following messages are stored in message class S_BCFG_API: Exception texts for package S_BCFG_API_*.
It is part of development package S_BCFG_API in software component BC-CUS-TOL-API. This development package consists of objects that can be grouped under "Business Configuration Support API".
It is part of development package S_BCFG_API in software component BC-CUS-TOL-API. This development package consists of objects that can be grouped under "Business Configuration Support API".
Message Nr ▲ | Message Text |
|---|---|
| 000 | The given text table definition &1 contains no language key. |
| 001 | The last container operation contradicts a preceding operation, key=&1. |
| 002 | error = &1. |
| 003 | Individual transaction objects are not supported in current special mode |
| 004 | Missing container id. |
| 005 | table = &1, line = &2, field = &3. |
| 006 | An error occured during conversion. |
| 007 | There is no primary table line for text table &1. |
| 008 | Conversion errors: &1. |
| 009 | Expected key field &1 is not found within the provided data. |
| 010 | For the given dictionary structure &1 no customizing object was supplied. |
| 011 | The dictionary structure &1 is already mapped to customizing object &2. |
| 012 | |
| 013 | The given IMG activity &1 does not exist. |
| 014 | The given IMG activity &1 does not use the customizing object &2. |
| 015 | Failed to read table entry at index &1. |
| 016 | View cluster objects are not supported in current commit mode. |
| 017 | Unexpected mismatch with existing mapping, object &1, type &2, table &3. |
| 018 | Found unsupported value: &1. |
| 019 | Container factory for type &1 is always registered. |
| 020 | Container factory for type &1 is not registered. |
| 021 | Invalid container type. |
| 022 | Container factory for type &1 is not bound. |
| 023 | Container is not bound. |
| 024 | The object &1 is locked by user &2. |
| 025 | Enqueue failed for object &1 caused by invalid lock mode &2. |
| 026 | Enqueue failed for object &1 caused by invalid operation &2. |
| 027 | Enqueue failed for object &1 caused by invalid client reference. |
| 028 | Enqueue failed for object &1 caused by system failure. |
| 029 | The container is already locked by enqueue operation. |
| 030 | It is not allowed to change customizing objects in client &1. |
| 031 | It is not allowed to change customizing objects on production systems. |
| 032 | Changes to cross-client customizing objects are not allowed in client &1. |
| 033 | Changes to cross-client customizing objects require transport recording. |
| 034 | Changes to customizing objects require transport recording in client &1. |
| 035 | Changes to customizing objects must not be recorded in client &1. |
| 036 | Unsupported customizing object &1, type &2. |
| 037 | The BC set already exists in the object directory. Choose another ID. |
| 038 | The BC set must assigned to a transport request to be modified. |
| 039 | Cannot modify classical BC set &1. No transport support. |
| 040 | Cannot load BC sets with generic deletes. |
| 041 | No authority to access table &1. |
| 042 | |
| 043 | Unsupported type &2 of object &1, but object is supported with type &3. |
| 044 | Missing maintenance dialog for customizing object &1, type &2. |
| 045 | Unsupported table name &3 for customizing object &1, type &2. |
| 046 | Unsupp. cust. obj. &1, delivery class A is not automatically adjustable. |
| 047 | Full stack simulation mode: BC set &1 persistence not allowed |
| 048 | Customizing objects whitelist is inactive |
| 050 | Function not yet supported at RFC destination &1. Please apply note &2. |
| 051 | Error while getting dictionary data: &1&2&3&4 |
| 052 | Unsupported DDIC table type in object &1 (&2), table &3, type &4. |
| 053 | Missing table name in mapping of object &1, type &2. |
| 054 | Unexpected mapping error with object &1, type &2, table &3. |
| 055 | Missing required foreign key definitions in text table &1, primary &2. |