Interface implement in SAP MII

[ankit12]

Hi All,

Can we implement interface concept in SAP MII as we implement it in java. As Interface in java is a blueprint of a class.

I have seen as SAP using it in two or more transactions in workbench in standard folder. So is it possible to use of interface in SAP MII.

Please let me know if further details needed.

Regards,
Ankit Gupta

[agentry_src]

Hi Ankit,

If you already see it in MII transactions, to which ones are you referring? Not much detail to your question. Please provide more. For starters, what kind of application are you trying to create? Why do you wish to use IIJ? What makes it more desirable than more standard MII content tools? Etc. etc.

Thanks, Mike

[ankit12]

Hi Mike,

Thanks for your comment. I will try to be more specific in this comment describe below:

Interface: SAPMPM/ERPShopFloorIntegration/frame/workflow/IPlunginHandler in SAP OEEINT (in SAP MEINT these will be in Visiprise folder). In this transaction, you will see not one action block is used. Only transaction variable are defined(like in java interface, no implementation is there). Moreover, this is used in multiple transactions defined below.

Transaction1: SAPMPM/ERPShopFloorIntegration/frame/workflow/StdSAPBAPIHandler

Here in this transaction in first sequence you will find as it is stating “This transaction implements IPluginHanlder.”

Transaction2: SAPMPM/ERPShopFloorIntegration/frame/workflow/GenericWebService

Same with this transaction.

IWorkflowHanlder is another one transaction name that is working like an interface. Hope this will clarify the question I asked.

Now coming to the second point as you asked about the requirement needed to implement this in the workbench is, just wanted to check if we can make use of this concept in SAP MII.

I was not able to attached the screenshot in this comment. Please refer the path I have given if you are also using SAP OEEINT. If you are using SAPMEINT then you will find these in the Visiprise folder

Regards,
Ankit Gupta

[former_member185280]

You use the 'Dynamic Transaction Call' Action. At design time you can point this action to your 'interface' transaction so you can map the correct inputs and outputs. Thru the link editor you can assign the name of the actual transaction you want to call at runtime. This usually can be specified in some kind of configuration somewhere. You have to develop the logic for dealing with that yourself.

Regards,
Christian

[former_member185280 · Accepted solution]

Here is an older blog that might be relevant.

https://blogs.sap.com/2013/11/21/sap-me-61-custom-plugins-xslt-java-mii-transaction-for-sapmeint-wor...

At this point if you want more information you probably need to start digging around in the documentation and/or practicing some google-fu.

Regards,
Christian

[ankit12 · Accepted solution]

Hi Christian,

Thanks for the pointing me to the right direction.

What I have understood from the above blog link is that, YES we can develop these custom interfaces through the NWDS and make use of it in the MEINT workflows by giving their references into the workflow configurations.

I have searched my question in all search engines using google-fu technique and guess what, you know better google-fu then me. 🙂

Regards,
Ankit Gupta

[former_member185280]

I think what you are referring to is the use of the 'Dynamic Transaction Call' action block. With this action you can set the called transaction by name at runtime. This can act as a kind of user exit where different transactions can be executed dynamically based on some logic determined at runtime. When doing this you want the 'interface' or inputs and outputs across the different transactions consistent so there is usually a default or 'interface" transaction defined in the project that you can copy to make your custom one. There is no hard concept like in java where you can say transaction x implements y or whatever. I think this is done in some of the RDS like OEE where you may want to tweak the default bapi calls or whatever. If thats not what you are referring to then we probably need more info from you.

Regards,
Christian

[ankit12]

Hi Christian,

Thanks for your response. Please see my comment above for more information.

In addition to that, if we are not using these interfaces in any transactions, can be remove them from the folder as they are not getting used anywhere. Or they do mean something?

And when you say, “I think this is done in some of the RDS like OEE where you may want to tweak the default bapi calls or whatever”. Could you please specify more on this?

Regards,

Ankit Gupta

[former_member185280]

I wouldn't get rid of them if they were provided in a standard offering from sap like OEE or ME. "RDS like OEE..." I am referring to the ME and OEE applications that you can get from SAP that leverage MII in some way.

Yes you can make use of this concept in your MII dev.

Regards,
Christian

[ankit12]

Hi Christian,

Thanks for your response. I was trying to figure out the same approach about using this concept in SAP MII. What I have tried for implementing this approach is developing a simple concept of adding two numbers with following steps:

Steps 1: created one transaction with two inputs transaction variable and one output variable. (like one Interface developed without any action block in transaction)

Now the real question is, how I can use this developed interface into another transaction as we are using these interfaces in transactions.

Could you please guide me on this?

Regards,
Ankit Gupta

[former_member185280]

You use the 'Dynamic Transaction Call' Action. At design time you can point this action to your 'interface' transaction so you can map the correct inputs and outputs. Thru the link editor you can assign the name of the actual transaction you want to call at runtime. This usually can be specified in some kind of configuration somewhere. You have to develop the logic for dealing with that yourself.

Regards,
Christian

[ankit12]

Hi Christian,

Thanks for your guidance.

I was able to develop this scenario. For replicating this, as you suggested I am using 'Dynamic Transaction Call' Action.

However, in the standard SAP transactions as I have mentioned in above comment SAP is not using any 'Dynamic Transaction Call' Action.So, how SAP is implementing it without using any 'Dynamic Transaction Call' Action block.?

Could you please give more insight about this?

Regards,

Ankit Gupta