Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Data Description

The TREAD_DYN event is used in SAP to flexibly extract data from ABAP tables within the managed system.

Potential Use Cases

This event could be used in the following scenarios:

  • Extract business process data for a use case related to business data.

  • Extract data from a custom table (Z table) not included in the PowerConnect core product.

  • Visualize an end-to-end business process based on the data extracted.

Metric Filters

To extract data from a particular table in your environment, follow the steps below:

  • Log into the managed system and execute the /n/bnwvs/main transaction.

  • Table reader filter needs to be maintained in the Administrator->Metric filters->Table reader filter

  • Please define filter name (should be unique) and table on the header level:

It is possible to define select conditions and list of field to be selected for each table using corresponding option on the left panel.

Select conditions sample:

If the aim is to extract delta data, appropriate where conditions should be added in the query itself. For these purposes following placeholders are foreseen:

Placeholder

Description

$now

extractor current execution time in system time zone

$today

extractor current execution date in system time zone

$timestamp

extractor current timestamp in UTC

$timestamp_st

extractor current timestamp in system time zone

$lastrun

extractor last execution timestamp in UTC

$lastrun_st

extractor last execution timestamp in system time zone

$lastrundate

extractor last execution date (system time zone)

$lastruntime

extractor last execution time (system time zone)

Field values to get sample:

Wildcards are accepted here.

Decode option should be used to decode field content from BASE64 format.

Splunk Event

Important Note: Data will only be extracted if the Metric Filters have been defined. Please see instructions above on how to define the metric filters.

The data shown below only includes the default fields that are included as part of the TREAD_DYN extractor. The field values that are extracted will depend on the select conditions and field values selected, which are defined in the Metric Filters.

The event will look something like this in Splunk:

SAP Navigation

Important Note: Data will only be extracted if the Metric Filters have been defined. Please see instructions above on how to define the metric filters.

Please log into the managed system and execute the SE16 transactions. Enter the Table Name that you would like to extract (example below). Select Table Content button

Go to Settings → “Fields for Selection” to view the fields in table

This pop shows the field name and a description of the field. Clear entries from the selection.

Then select the fields that you would like to view and then select the “Confirm” button.

You will now see the fields you would like to search.

Enter the desired user selection parameters and then hit the Execute button.

The data shown will match the data extracted and sent to Splunk. Take note of selection criteria, since this selection criteria will need to be used to define the Metric Filters.

Field Mapping

Important Note: Data will only be extracted if the Metric Filters have been defined. Please see instructions above on how to define the metric filters.

The data shown below only includes the default fields that are included as part of the TREAD_DYN extractor. The field values that are extracted will depend on the select conditions and field values selected, which are defined in the Metric Filters.

Field

Description

Unit of Measure

CURRENT_TIMESTAMP

The date time stamp when the information was collected

YYYYMMDDHHMMSS

EVENT_SUBTYPE

String

EVENT_TYPE

TREAD_DYN

String

TABNAME

Table Name

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.

+ | -

  • No labels