RSAODS SAP Message Class - Messages for the operational data store

RSAODS is a standard message class available within your SAP system (depending on your versionand release level). Below is a list of all the messages available for within this class and a link to any long text associated with each message. These messages are very simple to use and can be implemented into your ABAP code using the MESSAGE statement and the following syntax.

MESSAGE I000(RSAODS).

Note the value "I" represents an information messsage but can be replaced with E for error, W for warning, S for Status/Success, A for Abend/Termination and X for exit which does not display a message and causes a runtime error. Click here for more information about SAP Messages

Message class details can be viewed directly within your SAP system by entering the object name RSAODS into the relevant SAP transaction such as SE91 or SE80.

000 **** Error from PSA ****
001 Errors accessing partition parameters for table & (-> long text)
002 Errors occurred with drop/truncate partition & for table &




003 Error occurred while deciding partition number for DP &
004 Error updating PSA partition administration table RSTSODSPART
005 Request & not found
006 Invalid parameters for &
007 Invalid PSA Segments supplied
008 Could not insert entry for PSA & into instance table
009 Versioning not possible for PSA &
010 Error in generating technical name for PSA &
011 Error getting fields for PSA &
012 PSA & does not exist
013 No PSA found with name & and version &
014 Fieldlength too long for fields of PSA &
015 No fields were supplied
016 PSA instance does not exist for PSA &
017 PSA table name was blank
018 Invalid Parameter & & for field &
019 RFC system failure when checking requests: &1 &2 &3 &4
020 RFC communication failure when checking requests: &1 &2 &3 &4
100 No entry was made for the structure of the transferred data
101 Table C_T_TABLE is initial and does not contain any data
102 The structure entered is not known to the system
103 An internal error occurred when displaying data
104 Please select at least one record of the data to be maintained
105 An internal error has occurred when displaying data in the POPUP
106 No DDIC-structure was specified when calling the RSAR_POPUP_GET_VALUES
107 Handle for generated DDIC structure is invalid
108 Timeout when generating a DDIC structure name
109 Data has been saved
110 Create data record: The data record already exists



111 Number of data records to be edited: &
112 The display was limited to & data records
113 No data was changed
114 Error when generating a data element
115 Error when generating a domain
116 Timeout when generating a DDIC data element name
117 Error when creating data elements
118 No data exists in the corresponding PSA table
119 No data packet numbers could be determined for request &
120 An error occurred when reading PSA data
121 No PSA data could be found
122 An internal error occurred in the data maintenance module
123 The action was cancelled by the user
124 Select at least one entry
125 A maximum of & entries can be selected
126 Error when generating the DDIC structure &
127 You must only select one data packet when entering data record numbers
128 Data record number "FROM" is greater than data record number "TO"
129 Parameter error in the call
130 No generated program was found for InfoSource & in source system &.
131 Error while exporting data
132 Error when determining the PSA name
133 Request & data packet & available in request list
134 Enter a valid segment number
135 More than 75 fields selected. Filter has a limit of 75.
136 Data of request & already deleted
200 *** PSA API ***
201 Incorrect call of function module &.
202 Do not transfer any data to the PSA API
203 There is no PSA for InfoSource & and source system &
204 For key date & there is no PSA for InfoSource & and source system &
205 There are no fields for PSA & version &.
206 Error when inserting in PSA table &
207 Incorrect call sequence of the function module RSAR_ODS_API_GET
208 No data exists for this selection in PSA
209 There are no PSA tables for these selection criteria
210 Parameter error; No request transferred to PSA API
211 The requests are deleted from BW
212 No Repository entry & but database table exists
213 Table & inconsistent; see longtext
214 Fieldname for &1 could not be determined
250 Inconsistent application & <> & for PSA &
251 Inconsistent user object & for PSA &
252 Inconsistent technical name &1 <> &2 for PSA &3
253 PSA-table name inconsistent & <> & for PSA &
254 Error during assignment of Request &1 to Partition .