Modelling adoption

[Former Member]

Hi all,

I'm playing with the modelling capabilities in the ESR (specifically the SAP ProComp interaction model) and am finding it a little cumbersome. When reading about these capabilities it seemed like there might be an opportunity to speed up the development process by reusing some models. Unfortunately, I find that the creation of objects isn't as fluid as I would like - for example, if I created a service interface with an operation in the model, I would expect the service interface to contain that operation when I created the assignment instead of having to go back to the model and create that operation as a separate task. Likewise when creating the operation, it should come prepopulated with the message type that has been specified in the model. Or, if I had done all this modeling why couldn't I just assign/create the message type and get the option 'do you want to create the objects using this?' which would in turn create an operation and service interface.

So this has lead me to wonder:

1) What kind of adoption there is within the SAP community?

and 2) What are the advantages in using the modelling capabilities.

Based on my experience so far, I'm considering ignoring the modeling capabilities and going back to creating the various objects the way I always have.

Thanks,

Mike

[rajasekhar_reddy14 · Accepted solution]

Mike,

I have faced same problem while trying to use Modeling concept ,we have not used modeling in current project.

Thank you,

Rah

[Former Member · Accepted solution]

Thanks Rah - I suspected that might be the case. Anybody else? Has anyone found it helpful to have these capabilities? If so, how?