The client, the user id, the language, transaction. Information about where the error occurred. It tells you the SAP release and the Basis support pack level, as well as information about the operating system and hardware. However, for this information, I usually go to System->Status on the failing system. This information can be useful for determining the release level. This section may give other hints on resolution, so read carefully. For failures in standard SAP objects, this should always be your first port of call in resolving the error. By using these to search the notes system (formerly known as OSS), you might find a note, or some notes, that fix the problem. Various combinations of keywords may be suggested. Hints are given for the keywords that may be used to search on the note system. Here is the technical explanation of what went wrong How to correct the error Sometimes there’s helpful hints here, most often it’s just standard information. Not much information to be found here, except a brief description of the nature of the cause of the dump. Depending on the exact failure, some sections may contain very little. Some of these sections contain useful information, others not. The different sections (in no particular order) and how they help Dumps that happen in SAP standard code probably need a fix from SAP. own-developed code), can usually be fixed by the programmer. Dumps that happen in the customer namespace ranges (i.e. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |