/SMB/BCAPI - Messages with relation to BC-API

The following messages are stored in message class /SMB/BCAPI: Messages with relation to BC-API.
 It is part of development package /SMB/BCAPI in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "BC-API handling in Solution Builder".
Message Nr ▲
Message Text
000Database table/view not found: &1
001Table class &1 of table &2 is not supported
002Unable to create object mappings for BC-Set &1
003Invalid mapping: Name &1, Type &2, Table &3
004Table &1 of variant not found in BC-Set &2
005BC-Set ID is initial
006Failed to retrieve field descriptors for table &1
007No variants have been supplied
008Tablename is initial
009Objectname is initial
010Objecttype is initial
011BC-Set not found: &1
012BC-Set Variants not found: &1
013Missing PME data for file &1 of solution &2 (BC-Set &3)
014Test failed: BC-Set &1 file &2 reason &3
015Invalid mapping: Objectname &1, Objecttype &2
016BC-API language error
017BC-API mapping error
018Error reading customizing: &1
019Field &1 does not exist in table &2
020Remote usage is not supported
021Method is not implemented
022Failed to retrieve metadata for activity &1, object &2
023The mappings must contain exactly one Customizing object/type
024Solution is initial
025Definition is not bound
026Error retrieving metadata for table &1 from destination &2
027Unexpected table in data &1
028Activation with BC-API is currently not supported
029Subobject &1 is not part of the customizing scope
030Error reading customizing
031This feature is not supported
032Key field determination only supported for BC-Sets without View Clusters
033BC-API language problem. Reason: &1
034BC-API language problem with DDIC object. Cannot be solved. Reason: &1
035Log ID &1 for BC-Set &2 could not be locked
036Unsupported customizing object &1, type &2 (see long text)
Privacy Policy