SAP ABAP Message Class RSBCTXSA (Messages for xSA)
Basic Data
Hierarchy
☛
BI_CONT (Software Component) Business Intelligence Content
⤷ BW-BCT-EPM (Application Component) Spend Analytics Content
⤷ RS_BCT_XSA_ABAP (Package) xSA ABAP Objects
⤷ BW-BCT-EPM (Application Component) Spend Analytics Content
⤷ RS_BCT_XSA_ABAP (Package) xSA ABAP Objects
Attributes
Message class | RSBCTXSA | |
Short Description | Messages for xSA | |
Changed On | 20141101 | |
Last Changed At | 091618 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | File can not be converted, due to missing filename for converted file. | The short text describes the object sufficiently | |
2 | 001 | File &1 can not be opened for reading. Check source path and filename. | The short text describes the object sufficiently | |
3 | 002 | File &1 can not be written to server. Check the target path. | The short text describes the object sufficiently | |
4 | 003 | Data Collection Process is locked by user &1. Try again later. | The short text describes the object sufficiently | |
5 | 004 | Loading Process started with Alias Id &1 | The short text describes the object sufficiently | |
6 | 005 | File &1 can not be opened for writing on application server &3 | Space: object requires documentation | |
7 | 006 | Filepath or server name not maintained in table RSXAADMIN. | The short text describes the object sufficiently | |
8 | 007 | Hierarchy upload successful for InfoObject &1 | The short text describes the object sufficiently | |
9 | 008 | Hierarchy activation successful for InfoObject &1 | The short text describes the object sufficiently | |
10 | 009 | Hierarchy upload of InfoObject &1: InfoObject is not a characteristic | The short text describes the object sufficiently | |
11 | 010 | Hierarchy upload of InfoObj. &1: Hierarchy-bearing attr. &2 is incorrect | The short text describes the object sufficiently | |
12 | 011 | Hierarchy upload for InfoObject &1: Error during master data table read | The short text describes the object sufficiently | |
13 | 012 | Hierarchy upload of InfoObj. &1: Node &2 has no parent-node | The short text describes the object sufficiently | |
14 | 013 | Hierarchy tables successfully read for InfoObject &1 | The short text describes the object sufficiently | |
15 | 014 | Cycle Type of Cycle &3 changed to &1 by user &2. | The short text describes the object sufficiently | |
16 | 100 | ****************UPLOAD AND RELEASING DATA***************** | The short text describes the object sufficiently | |
17 | 101 | Data upload &1 (&2) can not be released due to wrong upload status. | The short text describes the object sufficiently | |
18 | 102 | Data upload &1 (&2) is already released. | The short text describes the object sufficiently | |
19 | 103 | Time out for status monitoring for process chain &1. Check process chain. | The short text describes the object sufficiently | |
20 | 104 | Update successfully finished for process chain &1. | The short text describes the object sufficiently | |
21 | 105 | Errors occured in process chain &1. | The short text describes the object sufficiently | |
22 | 106 | Data upload to inbound layer started for upload &1, file &2. | The short text describes the object sufficiently | |
23 | 107 | No active upload could be found for file type &1. | The short text describes the object sufficiently | |
24 | 108 | Action not possible due to errors in the previous upload &1 (&2) . | The short text describes the object sufficiently | |
25 | 109 | Upload &1 (&2) successfully deleted. | The short text describes the object sufficiently | |
26 | 110 | Upload &1 (&2) could not be deleted. Inform system administrator. | The short text describes the object sufficiently | |
27 | 111 | The exchange rate upload failed. Please check file &1. | The short text describes the object sufficiently | |
28 | 112 | Exchange rate upload finished. | The short text describes the object sufficiently | |
29 | 113 | Process Chain could not be started. Check Process Chain &1. | The short text describes the object sufficiently | |
30 | 114 | Data upload can not be started because upload &2(&1) is still active. | The short text describes the object sufficiently | |
31 | 115 | Missing authorization for starting data upload. | The short text describes the object sufficiently | |
32 | 116 | Process step &1 does not exist. Upload status can not be changed. | The short text describes the object sufficiently | |
33 | 117 | The given value &1 for upload status is not valid. | The short text describes the object sufficiently | |
34 | 118 | No authorization to change upload status. | The short text describes the object sufficiently | |
35 | 119 | The structure of file &1 is invalid. | The short text describes the object sufficiently | |
36 | 120 | Data upload succesfully started for UploadId &1 by user &2. | The short text describes the object sufficiently | |
37 | 121 | Data upload (&1) did not start. Background job could not be scheduled. | The short text describes the object sufficiently | |
38 | 122 | UploadId &1 inserted into table RSXA_RELEASED_ID for ACTION &2 . | The short text describes the object sufficiently | |
39 | 123 | UploadId &1 could not be inserted to RSXA_RELEASED_ID for ACTION &2. | The short text describes the object sufficiently | |
40 | 124 | &1, Status changed to process step &2 with status &3 by user &4. | The short text describes the object sufficiently | |
41 | 125 | Upload &2 (&1) deleted by user &3. | The short text describes the object sufficiently | |
42 | 126 | Deletion of Upload &2 (&1) by user &3 failed. | The short text describes the object sufficiently | |
43 | 127 | The file &1 cannot be created because the process (&2) is still active. | The short text describes the object sufficiently | |
44 | 128 | The file &1 cannot be imported because the process (&2) is still active. | The short text describes the object sufficiently | |
45 | 129 | Previous process (&2) was cancelled. Contact your system adminstrator. | The short text describes the object sufficiently | |
46 | 130 | File conversion started for file type &1. | The short text describes the object sufficiently | |
47 | 131 | Process Chain &1 started. | The short text describes the object sufficiently | |
48 | 132 | Upload can not be released because upload &1 (&2) is not yet finished. | The short text describes the object sufficiently | |
49 | 133 | Action not possible, due to already running processes. Try again later. | The short text describes the object sufficiently | |
50 | 134 | Attribute Change Run started. | The short text describes the object sufficiently | |
51 | 135 | Attribute Change Run could not be started. | The short text describes the object sufficiently | |
52 | 136 | Automatic file categorization failed for &1 files. | The short text describes the object sufficiently | |
53 | 137 | Data processing stopped for file &1. File validation ended with errors. | The short text describes the object sufficiently | |
54 | 200 | *** Manual Classification *** | The short text describes the object sufficiently | |
55 | 201 | Change to classification initiated (change to data in 0XSA_DS02): &1 &2 | The short text describes the object sufficiently | |
56 | 202 | Change to classification succeeded: &1 &2 | The short text describes the object sufficiently | |
57 | 203 | Change to classification failed: &1 &2 | The short text describes the object sufficiently | |
58 | 215 | The short text describes the object sufficiently | ||
59 | 300 | *******************Messages for Checks***************** | The short text describes the object sufficiently | |
60 | 301 | Checks: File &1 is UTF8 compatible. | The short text describes the object sufficiently | |
61 | 302 | Checks: File &1 could not be opened. | The short text describes the object sufficiently | |
62 | 303 | Checks: File &1 is not UTF8 compatible. Check the used codepage. | The short text describes the object sufficiently | |
63 | 304 | Checks: Your are not authorized to open file &1. | The short text describes the object sufficiently | |
64 | 305 | Checks: Wrong count of delimiters in row &1(expected &3, actual &2). | The short text describes the object sufficiently | |
65 | 306 | Checks: File &1 is consistent in terms of delimiter usage. | The short text describes the object sufficiently | |
66 | 307 | Checks: ProcessChain &1 is active. | The short text describes the object sufficiently | |
67 | 308 | Checks: ProcessChain &1 is not active. Upload process can not be started. | The short text describes the object sufficiently | |
68 | 309 | Count of delimiter in header and row is not the same. | The short text describes the object sufficiently |
History
Last changed on/by | 20141101 | SAP | |
SAP Release Created in |