cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

MII Queue for ME Interfaces

Former Member
0 Likes
276

All,

I am not sure whether this question will fit under MII forum. If not, please ignore it.

All data communication between ECC and ME is executed via MII SAPMEINT package and error/logs are managed in MII Queue Monitor.

My question is,

Is it possible to leverage MII Queue Monitor function to other custom interfaces that we plan to build between legacy and ME system via MII.

If yes, then how difficult would be. I thought it would be feasible to use MII queue monitor function to track the error logs for this custom interfaces if the efforts are minimum.

Thanks

Mahesh

Accepted Solutions (1)

Accepted Solutions (1)

agentry_src
Active Contributor
0 Likes

I am pretty sure that the Queue Monitor is purpose built for ME specifically for the SAPMEINT interface. I think you will find more people familiar with it on the ME forum.

But having said that, have you looked at the user exits for the interface? There is some customization capability built into most of the ME interfaces using MII. You may find that there is enough flexibility there to accomodate your Legacy interfaces. I know that there are some built-in, but sadly have not worked with them directly.

Regards,

Mike

Former Member
0 Likes

The Queu monitor and other applications related to SAPMEINT are specifically build for SAPMEINT. That is why they are write-protected in MII.

The Queue monitor save all data in the Database before posting them from ECC to ME (or vice versa). You can build a similar program for your legacy system .

Answers (0)