BL SAP Message class Anwendungs-Log
BL is a standard message class available within your SAP system (depending on your version and 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 I001(BL).
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.
Messages can also contain the & symbol, this means custom values can be added to the message when it is displayed, this is done using the WITH statement
MESSAGE I001(BL) with ld_field1.
Message class details can be viewed directly within your SAP system by entering the object name BL into the relevant SAP transaction such as SE91 or SE80.
001 - & & & &
002 - Specify the object first (not generically)
Additional information exists about message 002 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 002 class bl.003 - & & & &
007 - No log was created for object &
Additional information exists about message 007 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 007 class bl.008 - No log was created for object & and sub-objekt &
Additional information exists about message 008 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 008 class bl.009 - Check entry
010 - Objekt & is not maintained
Additional information exists about message 010 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 010 class bl.011 - For object &, no sub-object & is maintained
Additional information exists about message 011 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 011 class bl.012 - Please specify a sub-object for object &
Additional information exists about message 012 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 012 class bl.013 - No header has yet been created for the specified (sub-)object
Additional information exists about message 013 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 013 class bl.014 - Neither text nor user exit has been specified for the (sub-)object
Additional information exists about message 014 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 014 class bl.015 - Please reorganize number range for application log
Additional information exists about message 015 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 015 class bl.016 - The last log number has been allocated
Additional information exists about message 016 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 016 class bl.017 - There is no long text for message & &
018 - No log was found for these selection criteria
Additional information exists about message 018 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 018 class bl.019 - & log(s) deleted
Additional information exists about message 019 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 019 class bl.020 - None of the marked logs could be deleted
Additional information exists about message 020 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 020 class bl.021 - Only & log(s) could be deleted
Additional information exists about message 021 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 021 class bl.022 - The log was deleted
Additional information exists about message 022 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 022 class bl.023 - Neither text nor user exit were specified for the specified message
Additional information exists about message 023 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 023 class bl.024 - There is no further information for this log
025 - There is no further information for this message
026 - Please place the cursor on a valid line
027 - You have reached the maximum expansion step
028 - You have reached the minimum expansion step
029 - Mark the end of the block
030 - You have reached the first marked log
031 - You have reached the last marked log
032 - Select entries for deletion
Additional information exists about message 032 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 032 class bl.033 - The expiry date of this log can only be increased
Additional information exists about message 033 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 033 class bl.034 - You do not have authorization to display all specified logs
Additional information exists about message 034 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 034 class bl.035 - No messages were found for the specified view
Additional information exists about message 035 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 035 class bl.036 - There are no messages for the log no. &
037 - You are not authorized to display the specified log
Additional information exists about message 037 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 037 class bl.038 - You are not authorized to delete the specified log
Additional information exists about message 038 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 038 class bl.039 - You do not have authorization to archive the required logs
Additional information exists about message 039 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 039 class bl.040 - The application log number range interval is not maintained
Additional information exists about message 040 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 040 class bl.041 - The application log number range interval is not internal
Additional information exists about message 041 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 041 class bl.042 - The application log number range object does not exist
Additional information exists about message 042 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 042 class bl.043 - You do not have authorization to delete all these logs
044 - Parameter in log header standard text could not be replaced
045 - Parameter in message standard text could not be replaced
046 - The documentation module &1 could not be found
Additional information exists about message 046 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 046 class bl.047 - The standard text output type must be specified
Additional information exists about message 047 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 047 class bl.048 - Text module (long text) &1 conversion unsuccessful.
Additional information exists about message 048 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 048 class bl.049 - The parameters &1 &2 and &3 must be specified at the same time.
051 - &1 Application logs were not deleted.
Additional information exists about message 051 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 051 class bl.052 - Delete all application logs whose expiry date has been reached.
053 - There are no logs whose expiry date has been reached.
054 - Job cannot be created, see system log
055 - Job contains invalid job data, see system log
056 - Job name not specified
057 - Job definition error (JOB_OPEN)
058 - Invalid start date or period.
059 - Job step definition error
Additional information exists about message 059 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 059 class bl.060 - User &1 does not exist
061 - Report RSSLG200 not found.
062 - Job creation and release error
063 - The created job could not be selected.
Additional information exists about message 063 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 063 class bl.064 - Job selection error.
065 - Job &1 could not be deleted after a definition error.
Additional information exists about message 065 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 065 class bl.066 - Period definition cancelled.
070 - Sample Message &1, &2, &3 (Test)
100 - Message could not be formatted (too complex).
Additional information exists about message 100 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 100 class bl.101 - Message &1 is not defined in language &3 and work area &2.
Additional information exists about message 101 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 101 class bl.102 - The parameter &1 has an invalid length.
Additional information exists about message 102 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 102 class bl.190 - From line = &1 > &2 = to line: Inform SAP
191 - No errors
192 - Mark a message with the cursor
193 - From error importance = & > & = to error importance: Inform SAP
194 - Errors. Update not possible.
195 - Message handler call error: incorrect I_IDENTIFICATION value
196 - Log not created by SMSG Message Handler
200 - Log currently locked by user &1.
Additional information exists about message 200 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 200 class bl.201 - Log cannot be saved: Object/subobject not specified
Additional information exists about message 201 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 201 class bl.202 - The DDIC structure &1 does not exist or has errors
Additional information exists about message 202 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 202 class bl.203 - Message incomplete (seriousness, area, number, or exception missing)
Additional information exists about message 203 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 203 class bl.204 - Context inconsistent (see long text)
Additional information exists about message 204 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 204 class bl.205 - Parameters inconsistent (see long text)
Additional information exists about message 205 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 205 class bl.206 - Object &1 or subobject &2 does not exist
207 - Log not found (in main memory)
208 - No log found in the database
209 - Message not found (in main memory)
210 - No authorization. Activity not performed
211 - No current message
212 - No current log
213 - Authorization already assigned
214 - No logs to be loaded specified
215 - Log already loaded (LOGNUMBER: &1, LOGHANDLE: &2)
216 - No filter criteria specified
217 - Inconsistent context-dependent statistics definition
Additional information exists about message 217 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 217 class bl.218 - Application log internal number assignment error
219 - No detail information exists for the selected message
220 - Choose a message in the list with the cursor
221 - Choose a message or log
222 - No detail information exists for the selected log
223 - No log data exists
224 - The log already has a permanent number (&1)
225 - No log specified for deletion
226 - Delete logs which have expired or can be deleted earlier
227 - Only the first & deletable logs are displayed
Additional information exists about message 227 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 227 class bl.228 - Select at least one log to delete
229 - Select one or more logs for display
230 - Number of deletable logs: &
231 - No relevant changes found for structure &
232 - Select only one message
233 - Disp. prof.: Field cat. level &1: Table/field name missng (see long text)
Additional information exists about message 233 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 233 class bl.234 - Disp. prof.: Field cat. messages: table/field name missng (see long text)
Additional information exists about message 234 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 234 class bl.235 - Disp. prof.: Field cat. lev. &1: Struct. &2 does not exist (see long txt)
Additional information exists about message 235 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 235 class bl.236 - Disp. prof.: Field cat. messages: Struct. &1 does not exist (see lng txt)
Additional information exists about message 236 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 236 class bl.237 - Disp. prof.: Field cat. level &1: Fld &2-&3 does not exist (see long txt)
Additional information exists about message 237 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 237 class bl.238 - Disp. prof.: Field cat. messages: Fld &1-&2 does not exist (see long txt)
Additional information exists about message 238 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 238 class bl.239 - Display profile: Field catalog level &1: Internal error (see long text)
Additional information exists about message 239 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 239 class bl.240 - Display profile: Sort sequence level &1 is inconsistent (see long text)
Additional information exists about message 240 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 240 class bl.241 - Display profile: Inconsistent message sort sequence (see long text)
Additional information exists about message 241 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 241 class bl.242 - Display profile: Message field catalog is empty (see long text)
Additional information exists about message 242 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 242 class bl.243 - Display profile: Message field catalog: Internal error (see long text)
Additional information exists about message 243 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 243 class bl.244 - No sort criteria specified
245 - More than &1 sort criteria specified
246 - Custom control container name not specified
247 - Function is not currently possible
248 - Display Prof: Fld catalog level &1: Tab./fld name double (see long text)
Additional information exists about message 248 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 248 class bl.249 - Disp. Prof: Fld catalog messages: Tab./fld name double (see long text)
Additional information exists about message 249 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 249 class bl.250 - Use transaction SLG2 to delete logs
251 - Control does not exist
252 - Message number 999999 reached. Log is full
Additional information exists about message 252 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 252 class bl.253 - Internal Error: Access to generated data failed
254 - Internal amodal call error: Session ID not specified
255 - Disp. prof.: Fld catalog level &1: fld &2-&3: pos. error (see long text)
Additional information exists about message 255 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 255 class bl.256 - Log Is Incomplete
Additional information exists about message 256 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 256 class bl.257 - No log could be found in the archive
258 - Error when reading archive &1
259 - Not all logs from the archive could be displayed
Additional information exists about message 259 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 259 class bl.260 - Start date later than end date
261 - Start time later than end time
262 - Wrong field name passed
300 - ******** Messages for example programs *****************************
301 - Maximum weight exceeded
Additional information exists about message 301 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 301 class bl.302 - The flight is overbooked
Additional information exists about message 302 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 302 class bl.303 - Aircraft &1 is not available at this time
Additional information exists about message 303 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 303 class bl.304 - Payment by passenger &1 has not yet been checked
Additional information exists about message 304 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 304 class bl.305 - Flight permission has not yet been granted
Additional information exists about message 305 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 305 class bl.306 - Payment for passenger &1 has been received
307 - Booking for passenger &1 cancelled
308 - Steward(ess) &1 is ill and not available
309 - Crew breaks cannot be kept
Additional information exists about message 309 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 309 class bl.310 - Passenger &1 can only be booked in a smoker seat
311 - Booking for passenger &1 checked and correct
312 - Booking checked and correct
313 - Scheduling (time zone &1 start &2 end &3) Return code: &4
314 - The aircraft is not available. At least &1 seats are required
315 - Test message with par &1, par &2 par &3 and par &4
316 - No other aircraft types with more than &1 seats is available
317 - Settlement successfully performed for passenger &1
318 - Settlement postponed, passenger &1 has not confirmed the flight
319 - Flight cancelled
320 - Message &1 for chapter &2
321 - Incomplete address data for customer &1 in document &2
Additional information exists about message 321 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 321 class bl.322 - Invoice &1 incomplete. Bank a/c details missing
Additional information exists about message 322 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 322 class bl.323 - New price: Special offer in document &1 is no longer valid
Additional information exists about message 323 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 323 class bl.324 - Invoice &1 successfully created
325 - Return routine '&1' called
326 - This message goes to CALLBACK_DETAIL_MSG
327 - &1 customers flew for free (see detail)
328 - Settlement airline &1
329 - Flight &1 from &2 to &3
330 - Invoice &1 errors
331 - A flight is displayed here
332 - Select a flight
400 - ************* Verification program messages ****************
401 - This is a message without message variable
402 - Message with a message variable &1
403 - Message with two message variables &1 and &2
404 - &1, &2 and &3. Three message variables
405 - 4 message variables: &1, &2, &3 and &4
Search for further information about these or an SAP related objects