KB 026 – SOST filter configuration

  1. For API, you need to populate the filter with following.
  2. Basically, this will extract messages with status history either 701, 702, 073 or 723 which mean that the message has been transmitted successfully.

    The format of the field is <field name7>_<table name>.

    KB 026 – SOST filter configuration 1

    I think size of the attachment should be checked in Splunk. Use field ATTLEN_SOOD and the field unit is in byte.

    KB 026 - SOST filter configuration 2

  3. If you want to extract only the TRANSMITTED messages
  4. KB 026 - SOST filter configuration 3

  5. If you want to extract only messages WITH ERRORS
  6. KB 026 - SOST filter configuration 4

  7. How do I know the numbers?
  8. Unfortunately, I had to look at SOST source code.

    KB 026 - SOST filter configuration 5

  9. CAUTION: Not all fields that you can see in transaction SOST can be used as a filter directly.

    5.1 Sender field is not a field in the database but the sender is derived from field SNDTP, SNDYR, SNDNO of table SOOS.

    KB 026 - SOST filter configuration 6

    So you can use the above fields in SOST filter to filter by specific sender.

    In N71, if you want to filter by me, create the following.

    KB 026 - SOST filter configuration 7

    5.2 Recipient field is not a field in the database but the recipient email address is derived from field RECTP, RECYR and RECNO in table SOOS.

However, you cannot filter by recipient because the RECNO changes all the time although the same recipient is used.

KB 026 - SOST filter configuration 8

Download PDF version here