Skip to Content

Data didnt hit ECC because of a stuck queue (smq2) with errenous data

So I was wondering, is there a way to force a particular interface to work down a specific queue in smq2 to avoid any backlog with troublesome data in particular queue? Or is there a way I could bypass the errored data after a certain number of attempts and move onto the next object to try for processing.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Oct 10, 2017 at 10:58 AM

    Ive seen that this can be done as per :

    https://help.sap.com/viewer/ff4b17c66c55101488e1c652adb52951/7.02.18/en-US/04827440c36ed562e10000000a155106.html

    But I am stuck in sxmb_adm - when I try to look for the sender/receiver si's when in 'Configure Filter for Queue Prioritization' I see a load of sap standard interfaces and some old interfaces of ours but a lot of our new interfaces are missing, is there a way of resynching this screen with our pi system (7.4) so I can see all the si's so I can create a filter?


    Thanks

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 12, 2017 at 08:17 AM

    Ive done this using eoio and creating a new queue name.

    Add comment
    10|10000 characters needed characters exceeded