SAP® ERP Listeners
You can create RFCs on the SAP system that invoke services on IBM webMethods Integration. This allows SAP users to access the information that is available using SAP® ERP. Before you can create an RFC that invokes a service, you must configure the SAP system to have an RFC destination for an RFC listener running at SAP® ERP. This enables the SAP system to send RFCs. You must also configure the SAP® ERP to have an RFC listener that listens for RFCs from the SAP system.
Creating SAP® ERP Listener
Complete the following fields to create a new SAP® ERP listener:
| Field | Description |
|---|---|
| Add Listener | |
| Type of listener | Type of listener. For example SAP® ERP. |
| Select a version | Version of the listener type selected. |
| Listener | |
| Listener name | Name of the new listener. |
| Program ID | Program ID specified when creating the corresponding RFC destination in the SAP system. This field is case sensitive. |
| Retry limit | Number of times that the system must attempt to start the listener if the initial attempt fails. When the value is set to zero, the system makes a single attempt. |
| Retry backoff timeout | Time in seconds that the system must wait between each attempt to start the listener. This field is irrelevant if the value of Retry limit is zero. |
| Connection mode setting selection | |
| Gateway host | Gateway Host for accessing the SAP system. This must be exactly the same parameter as you chose for the corresponding RFC destination in the SAP system. |
| Gateway service | Gateway Service corresponding to the SAP system number. |
| Repository server | Outbound connection alias used as a repository for function interfaces and structure definitions of inbound calls. This way it is possible to use RFCs even if they are not defined in the calling system. |
| Logging | |
| RFC trace | Enable RFC tracing. Default is disabled. |
| Log transaction status | Enable logging of transaction status. Default is enabled. |
| Store message body | Enable the message body of the incoming document to be stored, even when a transaction is created (or maintained), and can be monitored later in the transaction list. |
Note: Only one RFC listener can be enabled for a Program ID across projects.
SAP® ERP Listener Notification
A listener notification works in conjunction with a listener to filter and process the RFC requests and IDocs in SAP® ERP. SAP® ERP uses the following listener notifications to process requests:
- ALE Listener Notification(synchronous) - Handles incoming IDocs synchronously.
- RFC Listener Notification(synchronous) - Handles incoming RFCs and tRFCs synchronously.
You can change the priority of the listener notification execution by dragging and changing the position of the notification in the list.
Note: In this context, synchronous or asynchronous refers to the processing on IBM® webMethods Integration and not on how the message was processed on the SAP system. However, in case of ALE listener notification, a TID is always assigned to the message. In the case of an RFC listener notification, a TID is present in the pipeline only for transactional RFC calls from the SAP system.
Create New ALE Listener Notification(synchronous)
Complete the following fields to create a new listener notification for ALE Listener Notification (synchronous).
| Field | Description |
|---|---|
| Account | |
| Name | Listener Notification name. |
| Description | Listener Notification description. |
| Action | |
| Name | Select the listener notification type as ALE Listener Notification(synchronous). |
| IDoc | |
| IDoc Type | Identifies the type of IDoc expected by the listener notification. |
| Cim Type | IDoc type extension (CIM type/customer extension type). |
| SAP system release | IDoc release. |
| Old IDoc type 2 IDoc version |
|
| Request Field Selection | |
| Name | Name of the input parameter. |
| Type | Java data type of the input parameter. |
| Execution Mode | |
| Service invoke | Name of the Flow service to invoke when the notification is received. |
| Forward confirm event | Enable or disable the SAP ERP to forward the Confirm TID event triggered by the tRFC protocol to the same destination where the document is forwarded. |
| Monitor iDocs | Enable or disable the SAP ERP to link the IDoc packet's TID with the DOCNUMs of the IDocs in that packet. |
Create New RFC Listener Notification (Synchronous)
Complete the following fields to create a new listener for RFC Listener Notification (Synchronous) notification:
| Field | Description |
|---|---|
| Account | |
| Name | Listener Notification name. |
| Description | Listener Notification description. |
| Action | |
| Name | Select the listener notification type as RFC Listener Notification (Synchronous). |
| Function | |
| Function pattern | Type all or part of the name of the function module for which you want to create a listener notification (SAP® ERP). Use pattern-matching characters if you are unsure of the complete name and want SAP® ERP to search for several RFCs with similar names. For example, enter RFC_FUNCTION_* in the field. |
| Group pattern | Type all or part of the name of the group for which you want to create a listener notification (SAP® ERP). Use pattern-matching characters if you are unsure of the complete name and want SAP® ERP to search for several RFCs with similar names. |
| Reset | Reset the search. |
| Apply | Apply the pattern or exact search. |
| Function name | Lists the function names matching the pattern. |
| Group name | Group name to which the matching functions belong. |
| Description | Description of the matching functions. |
| Request Field Selection | |
| Name | Name of the input parameter. |
| Type | Java data type of the input parameter. |
| Reply Field Selection | |
| Name | Name of the output parameter. |
| Type | Java data type of the output parameter. |
| Execution Mode | |
| Service invoke | Select the Flow service to invoke when the notification is received. |
Note:
- The documents, Notification\_NameRequestDocument for Request document name and Notification\_NameReplyDocument for Reply document name are created when a listener notification is created. You can view the documents by clicking the i/o icon in the Flow service.
- You must select routing listener for routing listener notifications and RFC listener for RFC listener notifications.
- While publishing a project:
- Assets such as listeners are not published. The listeners are selected from the pre-existing listeners or new listeners are created during deployment.
- Assets such as listeners with no associated listener notifications are not displayed for publishing.