V2 updates are in processing.
Processing of V2 updates has finished and subsequent V1 updates are running.
V2 update modules are waiting to be processed.
Processing of V2 updates has finished.
Use the F1 help and analyze the dictionary objects that are referenced by the screen field.
Analyze the corresponding syslog entry (SM21).
Analyze the failed update record (SM13).
Start the Debugger with /h and create a breakpoint on statement MESSAGE.
Executable program (Report)
Definition of the technical attributes of a field (for example its length)
Definition of a field help (F1 documentation) and field labels that appear on screens
Description of the meaning of a field in a certain business context
Definition of the possible entries of a field
Process After Input Modules (PAI Modules)
Business Application Programming Interface (BAPI)
User authorizations may not be sufficient to display the current screen number.
A program contains more than one screen.
There is an inconsistency in the SAP basis system.
A screen is composed from more than one subscreen.
Perform an ABAP trace restricted to the activities of the process (SE30).
Check the Detail Display in the process overview (SM50).
Start debugging the program from the process overview (SM50).
Analyze the job log (SM37).
Enforced customer control for change management
Operating system access only for experts
Access only possible via 8-digit passwords
Changes only in test systems
If there are differences in the program flow compared to the execution in another system
If there are duplicate keys in an internal table
If the transaction concept is fulfilled
If the customizing is correct
On the Database
On the Application Server
On the Frontend
Function groups can be executed via transaction SE37.
Function groups contain global data objects that can be access by all function modules that belong to this function group.
Function groups are containers for function modules.
Name of the user that caused the dump.
Extract of the source code where the exception occurred.
Name of the component to which the affected source code belongs.
The input the user made on the screen before the dump occurred.
A call stack, showing all previously executed functions and subroutines.
CALL FUNCTION AUTHORITY-CHECK
Enter /h in the command field.
Choose menu system -> utilities -> Debug ABAP.
Enter debug in the command field.
It's not possible to switch on the debugger during runtime. You have to start a program in the ABAP editor with option start -> debugging.
Via the ok code JDBG in SM37
Application coding (Debugging, Breakpoint at statement 'message')
System coding (System Debugging, Breakpoint at statement 'message')
R/3 kernel (Use the Dynpro Trace)
Determine the memory consumption of ABAP programs.
Trace the execution hierarchy (function modules, subroutines,...) of an ABAP program.
Trace SQL Statements.
Logs critical user actions.
Provides information about the user and transaction that triggered a syslog message.
Allows it to directly jump to the relevant source code from the syslog message.
Customers maintain user exits with transaction SMOD.
The location in the source code where the customer exit is called can be changed.
Customers maintain user exits with transaction CMOD.
Immediately after V1 has finished.
Immediately after V2 has finished
The user who started the update has to manually trigger the V3 processing.
The customer has to regularly schedule a batch job that processes V3 update requests.
MESSAGE ID 'AT' TYPE 'S' NUMBER 100.
MESSAGE E123 by Fielda Fieldb