Message Behaviour
来源:互联网 发布:编辑gif的软件 编辑:程序博客网 时间:2024/06/10 16:29
MESSAGE
Variants:
1.MESSAGE xnnn.
2.MESSAGE ID id TYPE mtype NUMBER n.
3.MESSAGE xnnn(mid).
4.MESSAGE msg TYPE mtype.
Effect
Sends a message. Messages are stored in the table T100, are processed using transactionSE91 and can be created by forward navigation.
The ABAP runtime environment handles messages according to the type declared in theMESSAGE statement and the context in which the message was sent. The following message types exist:
- A - Abend
- : Transaction terminated
- E - Error
- : Error message
- I - Info
- : Information
- S - Status
- : Status message
- W - Warning
- : Correction possible
- X - Exit
- : Transaction terminated with short dump
Messages are mainly used to handle user input on screens. The following table shows the behavior of each message type in each context. An explanation of the numbers used is included at the end of the table:
A E I S W X
--------------------------------------------------------------
PAI Module 1 2 3 4 5 6
PAI Module for POH 1 7 3 4 7
6
PAI Module for POV 1 7 3 4 7
6
--------------------------------------------------------------
AT SELECTION-SCREEN ... 1 8 3 4 9 6
AT SELECTION-SCREEN for POH 1 7 3 4 7 6
AT SELECTION-SCREEN for POV 1 7 3 4 7 6
AT SELECTION-SCREEN ON EXIT 1 7 3 4 7 6
--------------------------------------------------------------
AT LINE-SELECTION 1 10 3 4 10 6
AT PFn 1 10 3 4 10 6
AT USER-COMMAND 1 10 3 4 10 6
--------------------------------------------------------------
INITIALIZATION 1 11 3 4 11 6
START-OF-SELECTION 1 11 3 4 11 6
GET 1 11 3 4 11 6
END-OF-SELECTION 1 11 3 4 11 6
--------------------------------------------------------------
TOP-OF-PAGE 1 11 3 4 11 6
END-OF-PAGE 1 11 3 4 11 6
TOP-OF-PAGE DURING ... 1 10 3 4 10 6
--------------------------------------------------------------
LOAD-OF-PROGRAM 1 1 4 4 4 6
--------------------------------------------------------------
PBO Module 1 1 4 4 4 6
AT SELECTION-SCREEN OUTPUT 1 1 4 4 4 6
--------------------------------------------------------------
Procedure: see
Messages
--------------------------------------------------------------
- The message appears in a dialog box and the program terminates. When the user has confirmed the message, control returns to the next- highest area. All the internal sessions are deleted from the stack.
- The message appears in the status line. Then PAI terminates and the system returns to the current screen. All the screen fields combined usingFIELD orCHAIN are now ready for input. The user must enter new values. The system triggers the PAI event again, with the new values.
- The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after theMESSAGE statement.
- The message appears in the status line of the next screen. The program continues immediately after the message statement.
- The message appears in the status line. Then the system continues as in 2, except that the user can quit the message using ENTER without having to enter new values. The system continues handling the PAI event from immediately after the message statement.
- No message is displayed and a runtime error, MESSAGE_TYPE_X, is triggered. The short dump text contains the message identification.
- The program terminates with a runtime error DYNPRO_MSG_IN_HELP. While F1 and F4 are processed, the system cannot send error messages or warnings.
- The message appears in the status line. Then the system stops selection screen processing and returns to the selection screen itself. The screen fields specified in the additions to theAT SELECTION-SCREEN statement are now ready for input. The user must enter new values. The system then starts processing the selection screen again with the new values.
- The message appears in the status line. Then the system continues as in 8, except the the user can quit the message using ENTER, without having to enter new values. The system continues handling the PAI event from immediately after the message statement.
- The message appears in the status line and the processing block terminates. The list level is displayed as before.
- The message appears in the status line and the processing block terminates. The system then returns to the program call.
- For a demonstration of messages in different contexts, see Example Programs for Messages.
- Message Behaviour
- Undefined Behaviour
- Behaviour Desinger
- jade中的agent behaviour
- Erlang OTP 自定义behaviour
- erlang otp 自定义behaviour
- Supervisor Behaviour监控树
- erlang 如何自定义 behaviour
- Behaviour Driven Development
- Global Organizational Behaviour
- Unity Enemy behaviour
- Behaviour Driven Development
- erlang 四大 behaviour【转】
- Unity3d behaviour designer 心得
- message
- message
- message
- Message
- MS SQLDRVER学习应用几点总结
- VS2008编译webrt错误:cerror LNK2019: unresolved external symbol "void __stdcall DeleteMediaType
- 给刚毕业的程序员……
- 继承与派生
- linux下基于TCP协议的socket通信
- Message Behaviour
- js基础学习第二天(关于DOM和BOM)二
- MySql Server版启动批处理
- STM8S 中断唤醒,定时唤醒,窗口看门狗
- Android ListView Item ContextMenu
- linux下的网络编程
- js常用正则表达式
- linux下的多线程
- 十个开源的Javascript框架