Hierarchy
⤷ OPU-GW-COR (Application Component) Gateway Framework
⤷ /IWFND/MGW_PUSH (Package) GW Framework - Odata Channel - Notification
IMG Activity
ID | /IWFND/MGW_NOTF_CNTF | OData Channel: Notification Content Formatter |
Transaction Code | /IWFND/59000013 | (empty) |
Created on | 20111104 | |
Customizing Attributes | /IWFND/MGW_NOTF_CNTF | OData Channel: Notification Content Formatter |
Customizing Activity | /IWFND/MGW_NOTF_CNTF | OData Channel: Notification Content Formatter |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /IWFND/GW_BADI_FORMATTER |
Use
Each application can format the Notification content before it is pushed or pulled from the SAP NetWeaver Gateway system. To format the notifications implement the BAdI /IWFND/BD_MGW_NOTIF_FORMATTER. The BAdI is called by the Notification Receiver in Gateway before it is pushed or persisted.
Requirements
Standard settings
There is neither an active BAdI implementation nor a default implementation delivered by SAP for the BAdI definition.
The BAdI is a filter based "single use" BAdI.
Activities
BAdI Filter Paramaters:
- SERVICE_DOC_NAME - External Name of the service document.
- SERVICE_DOC_NAMESPACE - The namespace under which the service document is defined.
- SERVICE_DOC_VERSION - The four digit version number for the service document. Eg 0001
- COLLECTION_NAME - External name of Collection in the service document
- DELIVERY_CHANNEL - Delivery channel name. The delivery channel name is a mandatory filter parameter. The delivery channel filter parameter can be:
- A pattern from the delivery address specified in the format as "urn:sap:channel:<channel name>/<request URI>" while subscribing an entity (OR)
- An RFC connection name of type "G" maintained in transaction SM59 for the delivery address while subscribing an entity.
Note: The filter parameter DELIVERY_CHANNEL is derived out of delivery address. If delivery address is not specified while subscribing for an entity then BAdI will never be called. This is applicable even for pull based subscriptions where delivery address is optional. For pull based notifications if formatting is required then provide a dummy delivery address while subscribing and maintain the same as filter parameter for the DELIVERY_CHANNEL
Example
To map SAP internal user names in the payload with external user names.
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20130213 |
SAP Release Created in | 250 |