Data Description
The SXMB_MONI event is used in SAP to monitor the processing for XML messages, track message status, and errors.
Potential Use Cases
This event could be used in the following scenarios:
To monitor XML messages for integrations monitoring use cases.
Identify actionable business errors associated with an integration using the message payload, and alert respective business process teams.
Review message processing response times when identifying integration bottlenecks.
Trend message volume over time for a specific interface.
Metric Filters
Important Note: SXMB_MONI events will not be extracted without configuring the interface using Metric Filters.
Go to the /n/bnwvs/main transaction code in the managed system. Then go to Administrator → Metric filters → More → SXMB filter.
Then select the “Insert Row” button and add the desired configuration parameters based on the parameters below, and select the Save button.
Status group - This field is optional, but can be used if you would like to select a specific message status group for extraction.
Status - This field is optional, but can be used if you would like to select a specific message status for extraction.
Direction - This field is optional, but can be used if you would like to select a specific message direction for extraction.
Party - This field is mandatory and is used to specify the sender/receiver party for the integration scenario.
Component - This field is mandatory and is used to specify the sender/receiver component for the integration scenario.
Name - This field is mandatory and is used to specify the integration name.
Namespace - This field is mandatory and is used to specify the namespace for the integration schema you would like to extract the messages for.
Payload - This field is mandatory and is used to toggle whether the message payload should be extracted for the integration schema. Note that enabling this feature can significantly increase the data volume sent to Splunk.
Active - This field is mandatory and is used to toggle whether the messages for the integration schema are extracted. Checking the check box will enable data extraction, and unchecking the check box will disable the data extraction.
The data will now be extracted according to the parameters entered in the Metric Filters configuration.
Splunk Event
Important Note: SXMB_MONI events will not be extracted without configuring the interface using Metric Filters.
The event will look like this in Splunk:
SAP Navigation
Important Note: SXMB_MONI events will not be extracted without configuring the interface using Metric Filters.
Log into the managed system and execute the SXMB_MONI transaction, and select the “Monitor for Processed XML Messages” button.
Then enter the desired user selection parameters and hit the execute button.
The summary statistics related to the messages will then be displayed. This information is captured in the SXMB_MONI event.
To view the message detail go to one of the Message IDs, and click the “Message ID” field for the message of interest. Then go to the MainDocument section on the left side of the screen, and you will see the payload, which can be extracted by the SXMB_MONI extractor using the Metric Filters.
If the message is in an error status, you can also view the error payload by selecting the Error section on the left side of the screen. This data is extracted by the SXMB_MONI extractor if the Metric Filters is configured to extract the payload.
Field Mapping
Field | Description | Unit of Measure |
|---|---|---|
ACKSTATICON | Comment | String |
ACK_STATE | XI: Acknowledgment Status | Number |
ADAPICON | Comment | String |
ADAPTSTATICON | Comment | String |
ADAPT_STAT | Integration Engine: Adapter Status | String |
ADAPT_TP_I | Pipeline Service Type | String |
ADAPT_TYP | Pipeline Service Type | String |
ADMINUSER | User Name | String |
AT1 | Integration Engine: XML String | String (XML) |
AT2 | Integration Engine: XML String | String (XML) |
AT3 | Integration Engine: XML String | String (XML) |
AT4 | Integration Engine: XML String | String (XML) |
AT5 | Integration Engine: XML String | String (XML) |
BULKMESSAGE | Not More Closely Defined Area, Possibly Used for Patchlevels | String |
BULK_ERROR | Error in Bulk | String |
CHILDCOUNT | Numc3, internal use | String |
CLIENT | Client ID | String |
COMMITACT | XMS: Flag (true/false) | 0 (false) | 1 (true) |
CURRENT_TIMESTAMP | The date time stamp when the information was collected | YYYYMMDDHHMMSS |
DIRPARTY | Party in Directory | String |
DIRSERVICE | Service(Process Name) in Directory | String |
EO_REFID | Integration Engine: Reference Type | String |
EO_REFID_I | Integration Engine: Reference Type | String |
EO_REFID_O | Integration Engine: Reference Type | String |
EO_REFVAL | Integration Engine: Reference Value | String |
EO_REFVL_I | Integration Engine: Reference Value | String |
EO_REFVL_O | Integration Engine: Reference Value | String |
ERRCAT | XI: Error Category | String |
ERRCODE | XI: Error ID | String |
ERRLABEL | XI: Status Detail: Description | String |
ERRPAYLOAD | Error Payload | String (XML) |
EVENT_SUBTYPE | String | |
EVENT_TYPE | SXMB_MONI | String |
EXEDATE | System Date | YYYYMMDD |
EXETIME | System Time | HHMMSS |
EXETIMEST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | YYYYMMDDhhmmssmmmuuun |
EXPANDED | Single-Character Indicator | String |
GEN_ENTRY | XMS: Flag (true/false) | 0 (false) | 1 (true) | x (true) |
HOST | Application Server | String |
IB_NAME | Inbound Interface Name | String |
IB_NS | Inbound Interface Namespace | String |
IB_OPERATION | Operation of Service Interface | String |
IB_PARTY | XI: Communication Party | String |
IB_PARTY_AGENCY | XI Partner: Agency | String |
IB_PARTY_TYPE | XI Partner: Identification Schema | String |
IB_SYSTEM | Receiving System | String |
INITDATE | System Date | YYYYMMDD |
INITTIME | System Time | HHMMSS |
INITTIMEST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | YYYYMMDDhhmmssmmmuuun |
INT_NUM | Numc3, internal use | Number |
INT_TIMEST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | YYYYMMDDhhmmssmmmuuun |
ITFACTION | Integration Engine: Action for Interface | String |
JOBICON | Comment | String |
JOB_ID | Job ID | String |
LINECOLOR | Not More Closely Defined Area, Possibly Used for Patchlevels | String |
LOG_ICON | Not More Closely Defined Area, Possibly Used for Patchlevels | String |
MAINDOC | Payload | String (XML) |
MANDT | Client ID | String |
MANUALSTAT | XMS: Flag (true/false) | 0 (false) | 1 (true) |
MESSAGE_ID | GUID in 'CHAR' Format in Uppercase | String |
MSGGUID | XI: Message ID | String |
MSGSTATE | Integration Engine: Message Status | String |
MSGTYPE | Integration Engine: Message Type | String |
MSG_SIZE | Message Size | Number |
OB_NAME | Outbound Interface Name | String |
OB_NS | Outbound Interface Namespace | String |
OB_OPERATION | Operation of Service Interface | String |
OB_PARTY | XI: Communication Party | String |
OB_PARTY_AGENCY | XI Partner: Agency | String |
OB_PARTY_TYPE | XI Partner: Identification Schema | String |
OB_SYSTEM | Sending System | String |
PARENTMSG | XI: Message ID | String |
PELNAME | Pipeline Element Name | String |
PERSIST_ID | GUID in 'CHAR' Format in Uppercase | String |
PID | Integration Engine: Pipeline ID | String |
QOSMODE | Integration Engine: Quality of Service | String |
QUEUEGUID | ID for Message Queue | String |
QUEUEICON | Queue icon | String |
QUEUEINT | Name of tRFC Queue | String |
QUEUENAME | Comment | String |
QUEUESTATE | Integration Engine: Queue Status | Number |
REF_TO_MSG | XI: Message ID | String |
REF_TO_REC_MSG | XI: Message ID | String |
REORG | Reorganization Status | String |
REORGICON | Comment | String |
REST_VERS | Sequence Number for a Message Log ID | Number |
RETRYCOUNT | Numc3, internal use | Number (Count) |
RETRYCOUNT_MAN | Manual Retry Counter | Integer |
RND_NUMBER | Random Number for Integration Engine Messages | Number |
SECURITY | Security Flag | Binary |
SENDDATE | System Date | YYYYMMDD |
SENDTIME | System Time | HHMMSS |
SENDTIMEST | UTC Time Stamp in Long Form | YYYYMMDDhhmmssmmmuuun |
SNDRGUID | Sender ID | String |
STATICON | Comment | String |
STATUS | Job Processing Status | String |
TASK | ccBPM Process Definition | String |
TYPETEXT | Type of interface (Asynchronous or Synchronous) | String |
USERINFODATA | Char 20 | String |
USERINFOSTORAGE | Unique Identifier for Saving USERINFO Metadata | String |
UTCDIFF | The UTC OFFSSET in HHMMSS that the data was collected in | HHMMSS |
UTCSIGN | The UTC positive or negative OFFSET indicator. Positive (+) means add UTCDIFF to find the time zone of the data, negative (-) means subtract the UTCDIFF to find the time zone adjusted date time the data was collected in. | + | - |
VERS | Sequence Number for a Message Log ID | Number |
VERSION | Sequence Number for a Message Log ID | Number |
WI_ID | Work item ID | Number |
WS_HASH_CODE | Message ID Hash Code | Integer |
XI_PROXY | XML Object Type: Name | String |