SAP ABAP Message Class S_BCFG_API (Exception texts for package S_BCFG_API_*)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CUS-TOL-API (Application Component) Business Configuration API (SAP-internal)
⤷
S_BCFG_API (Package) Business Configuration Support API

⤷

⤷

Attributes
Message class | ![]() |
S_BCFG_API |
Short Description | ![]() |
Exception texts for package S_BCFG_API_* |
Changed On | ![]() |
20130531 |
Last Changed At | ![]() |
120021 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | ![]() |
The given text table definition &1 contains no language key. | The short text describes the object sufficiently | |
2 | ![]() |
The last container operation contradicts a preceding operation, key=&1. | Space: object requires documentation | |
3 | ![]() |
error = &1. | The short text describes the object sufficiently | |
4 | ![]() |
Missing container id. | The short text describes the object sufficiently | |
5 | ![]() |
table = &1, line = &2, field = &3. | The short text describes the object sufficiently | |
6 | ![]() |
An error occured during conversion. | The short text describes the object sufficiently | |
7 | ![]() |
There is no primary table line for text table &1. | The short text describes the object sufficiently | |
8 | ![]() |
Conversion errors: &1. | The short text describes the object sufficiently | |
9 | ![]() |
Expected key field &1 is not found within the provided data. | The short text describes the object sufficiently | |
10 | ![]() |
For the given dictionary structure &1 no customizing object was supplied. | Space: object requires documentation | |
11 | ![]() |
The dictionary structure &1 is already mapped to customizing object &2. | The short text describes the object sufficiently | |
12 | ![]() |
The short text describes the object sufficiently | ||
13 | ![]() |
The given IMG activity &1 does not exist. | The short text describes the object sufficiently | |
14 | ![]() |
The given IMG activity &1 does not use the customizing object &2. | The short text describes the object sufficiently | |
15 | ![]() |
Failed to read table entry at index &1. | The short text describes the object sufficiently | |
16 | ![]() |
View cluster objects are not supported in current commit mode. | Space: object requires documentation | |
17 | ![]() |
Unexpected mismatch with existing mapping, object &1, type &2, table &3. | The short text describes the object sufficiently | |
18 | ![]() |
Found unsupported value: &1. | The short text describes the object sufficiently | |
19 | ![]() |
Container factory for type &1 is always registered. | The short text describes the object sufficiently | |
20 | ![]() |
Container factory for type &1 is not registered. | The short text describes the object sufficiently | |
21 | ![]() |
Invalid container type. | The short text describes the object sufficiently | |
22 | ![]() |
Container factory for type &1 is not bound. | The short text describes the object sufficiently | |
23 | ![]() |
Container is not bound. | The short text describes the object sufficiently | |
24 | ![]() |
The object &1 is locked by user &2. | The short text describes the object sufficiently | |
25 | ![]() |
Enqueue failed for object &1 caused by invalid lock mode &2. | The short text describes the object sufficiently | |
26 | ![]() |
Enqueue failed for object &1 caused by invalid operation &2. | The short text describes the object sufficiently | |
27 | ![]() |
Enqueue failed for object &1 caused by invalid client reference. | The short text describes the object sufficiently | |
28 | ![]() |
Enqueue failed for object &1 caused by system failure. | The short text describes the object sufficiently | |
29 | ![]() |
The container is already locked by enqueue operation. | The short text describes the object sufficiently | |
30 | ![]() |
It is not allowed to change customizing objects in client &1. | The short text describes the object sufficiently | |
31 | ![]() |
It is not allowed to change customizing objects on production systems. | The short text describes the object sufficiently | |
32 | ![]() |
Changes to cross-client customizing objects are not allowed in client &1. | The short text describes the object sufficiently | |
33 | ![]() |
Changes to cross-client customizing objects require transport recording. | The short text describes the object sufficiently | |
34 | ![]() |
Changes to customizing objects require transport recording in client &1. | The short text describes the object sufficiently | |
35 | ![]() |
Changes to customizing objects must not be recorded in client &1. | The short text describes the object sufficiently | |
36 | ![]() |
Unsupported customizing object &1, type &2. | The short text describes the object sufficiently | |
37 | ![]() |
The BC set already exists in the object directory. Choose another ID. | The short text describes the object sufficiently | |
38 | ![]() |
The BC set must assigned to a transport request to be modified. | The short text describes the object sufficiently | |
39 | ![]() |
Cannot modify classical BC set &1. No transport support. | The short text describes the object sufficiently | |
40 | ![]() |
Cannot load BC sets with generic deletes. | The short text describes the object sufficiently | |
41 | ![]() |
No authority to access table &1. | The short text describes the object sufficiently | |
42 | ![]() |
The short text describes the object sufficiently | ||
43 | ![]() |
Unsupported type &2 of object &1, but object is supported with type &3. | The short text describes the object sufficiently | |
44 | ![]() |
Missing maintenance dialog for customizing object &1, type &2. | The short text describes the object sufficiently | |
45 | ![]() |
Unsupported table name &3 for customizing object &1, type &2. | The short text describes the object sufficiently | |
46 | ![]() |
Unsupp. cust. obj. &1, delivery class A is not automatically adjustable. | The short text describes the object sufficiently | |
47 | ![]() |
Function not yet supported at RFC destination &1. Please apply note &2. | The short text describes the object sufficiently | |
48 | ![]() |
Error while getting dictionary data: &1&2&3&4 | The short text describes the object sufficiently | |
49 | ![]() |
Unsupported DDIC table type in object &1 (&2), table &3, type &4. | The short text describes the object sufficiently | |
50 | ![]() |
Missing table name in mapping of object &1, type &2. | The short text describes the object sufficiently | |
51 | ![]() |
Unexpected mapping error with object &1, type &2, table &3. | The short text describes the object sufficiently | |
52 | ![]() |
Missing required foreign key definitions in text table &1, primary &2. | The short text describes the object sufficiently |
History
Last changed on/by | ![]() |
20130531 | SAP |
SAP Release Created in | 703 |