Message Number list used by SAP ABAP Program LTBL2F03 (Include LTBL2F03)
SAP ABAP Program LTBL2F03 (Include LTBL2F03) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | LM - 191 | Release status of interim limit: &1 (&2), last released by: &3 | |
2 | Message Number | LM - 425 | Object & is locked by a generic lock set in another application | |
3 | Message Number | LM - 424 | Postprocessing is not possible during an end-of-day processing run | |
4 | Message Number | LM - 376 | Position the cursor on a line item | |
5 | Message Number | LM - 374 | User error in online mode | |
6 | Message Number | LM - 373 | User error in online mode | |
7 | Message Number | LM - 314 | Data was not updated - an error occurred while locking E_VTBLIL24 | |
8 | Message Number | LM - 249 | No update - maximium of lock attempts by E_VTBLIL24 reached | |
9 | Message Number | LM - 217 | Limits for &1 could not be generated automatically | |
10 | Message Number | LM - 001 | Limit type & is not defined | |
11 | Message Number | LM - 110 | LM was not updated because a limit type could not be locked/unlocked | |
12 | Message Number | LM - 109 | No update, since limit type &1 could not be locked | |
13 | Message Number | LM - 101 | Error while modifying table &1 | |
14 | Message Number | LM - 097 | No currency found for the company code or client | |
15 | Message Number | LM - 085 | There is inconsistent data in Limit Management | |
16 | Message Number | LM - 084 | Error occurred while inserting data in table &1 | |
17 | Message Number | LM - 083 | System error occurred in program &1 | |
18 | Message Number | LM - 080 | Function module &1 was called incorrectly |