Creating ABAP Messaging Channel Applications
Procedure
1. Execute transaction SE80.
2. Within the context menu of the Object Navigator choose .
3. Enter an application name of your choice, for example, AMC_SIMPLE_TEST.
4. Choose an appropriate Package and click on Save.
5. Enter a description in the field Short Descript.
6. In the tab Channels enter a channel name of your choice, e.g. ping and click on this field. The channel name must start with a slash (/). Maintain the following fields:
-
Message-Type ID : A dedicated message type is assigned to each channel. In other words: only messages of the assigned message type can be transferred over the channel. Thus, the access APIs are type-safe. Also, the ABAP compiler and Runtime ensure the consistent message transfer.
-
Scope (System, Client, or User): The Channel Access Scope defines whether a channel is cross-client or client-specific. With the latter Channel Access Scope, the exchange of messages between producer and consumer sessions can be limited to sessions residing in the same client. Otherwise it is cross-client.
-
Authorized Program : The access rights for the channels are realized via code based authorization. For each channel, and depending on the access role as consumer or producer, a white list of ABAP reports, function groups, classes, or alike have to be maintained, otherwise the access will be rejected.
Save your entries.

