Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

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.

Field Mapping

...

Field

...

Description

...

Unit of Measure

...

ACKSTATICON

...

Acknowledgment Status Icon

...

String

...

ACK_STATE

...

XI: Acknowledgment Status

...

Number

...

ADAPICON

...

ADAPTSTATICON

...

ADAPT_STAT

...

Integration Engine: Adapter Status

...

String

...

ADAPT_TP_I

...

Pipeline Service Type

...

String

...

ADAPT_TYP

...

Pipeline Service Type

...

String

...

ADMINUSER

...

User name processing message

...

String

...

AT1

...

AT2

...

AT3

...

AT4

...

AT5

...

BULKMESSAGE

...

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

...

DIRPARTY

...

DIRSERVICE

...

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

...

ERRCODE

...

ERRLABEL

...

ERRPAYLOAD

...

EVENT_SUBTYPE

...

String

...

EVENT_TYPE

...

SXMB_MONI

...

String

...

EXEDATE

...

EXETIME

...

EXETIMEST

...

UTC Time Stamp in Long Form

...

YYYYMMDDhhmmssmmmuuun

...

EXPANDED

...

GEN_ENTRY

...

XMS: Flag (true/false)

...

0 (false) | 1 (true)

...

HOST

...

Application server

...

String

...

IB_NAME

...

IB_NS

...

IB_OPERATION

...

IB_PARTY

...

IB_PARTY_AGENCY

...

IB_PARTY_TYPE

...

IB_SYSTEM

...

INITDATE

...

INITTIME

...

INITTIMEST

...

UTC Time Stamp in Long Form

...

YYYYMMDDhhmmssmmmuuun

...

INT_NUM

...

INT_TIMEST

...

ITFACTION

...

Integration Engine: Action for Interface

...

String

...

JOBICON

...

JOB_ID

...

LINECOLOR

...

LOG_ICON

...

MAINDOC

...

MANDT

...

Client

...

String

...

MANUALSTAT

...

XMS: Flag (true/false)

...

0 (false) | 1 (true)

...

MESSAGE_ID

...

MSGGUID

...

XI: Message ID

...

String

...

MSGSTATE

...

Integration Engine: Message Status

...

String

...

MSGTYPE

...

Integration Engine: Message Type

...

String

...

MSG_SIZE

...

Message Size

...

Number

...

OB_NAME

...

OB_NS

...

OB_OPERATION

...

OB_PARTY

...

OB_PARTY_AGENCY

...

OB_PARTY_TYPE

...

OB_SYSTEM

...

PARENTMSG

...

PELNAME

...

PERSIST_ID

...

PID

...

Integration Engine: Pipeline ID

...

String

...

QOSMODE

...

Integration Engine: Quality of Service

...

String

...

QUEUEGUID

...

ID for Message Queue

...

String

...

QUEUEICON

...

QUEUEINT

...

Name of tRFC Queue

...

String

...

QUEUENAME

...

QUEUESTATE

...

REF_TO_MSG

...

XI: Message ID

...

String

...

REF_TO_REC_MSG

...

XI: Message ID

...

String

...

REORG

...

Reorganization Status

...

String

...

REORGICON

...

Reorganization Status Icon

...

String

...

REST_VERS

...

Sequence Number for a Message Log ID

...

Number

...

RETRYCOUNT

...

Retry count

...

Number (Count)

...

RETRYCOUNT_MAN

...

Manual Retry Counter

...

Integer

...

RND_NUMBER

...

Random Number for Integration Engine Messages

...

Number

...

SECURITY

...

Security Flag

...

Number

...

SENDDATE

...

SENDTIME

...

SENDTIMEST

...

UTC Time Stamp in Long Form

...

YYYYMMDDhhmmssmmmuuun

...

SNDRGUID

...

Sender ID

...

String

...

STATICON

...

STATUS

...

TASK

...

TYPETEXT

...

USERINFODATA

...

Key for Engine Look Up Table

...

Byte sequence

...

USERINFOSTORAGE

...

Unique Identifier for Saving USERINFO Metadata

...

Byte sequence

...

UTCDIFF

...

UTCSIGN

...

VERS

...

Sequence Number for a Message Log ID

...

Number

...

VERSION

...

WI_ID

...

WS_HASH_CODE

...

Message ID Hash Code

...

Integer

...

XI_PROXY

...

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.

...