JSM -> Integration with SD or CHARM mandatory?

[former_member184682]

Hello

we have solman 7.1 SPS5

We are evaluating the JSM scenarios

Right now our two priorities are as follows

1) we need to have a central repository of our jobs (documentations) in solution manager.

2) Automated scheduling of the jobs from solution manager via our job scheduling tool onto the satellite systems

I did read the JSM documentations in detail and also understand that when a JR is created, a CRM document is created in the background. This CRM document (say in the form of SD incident or a CHARM SMCR) is then picked up by IT and further processed, a job documentation is created out of it and then scheduled etc

So my questions are as follows

a) Would it be an option to avoid this integration with SD or CHARM?

b) Would it be an option to give end users the option to directly create job documentations (no job request as a first step) filling in all the details about the job, schedule,variant etc?

If the answer to the above two are NO, this means SD or CHARM configuration in the solution manager is a mandatory task to be able to use JSM ? Because the SPRO nor the documentation at /jsm is very clear about this. The documentation says JSM CAN be integrated with SD or CHARM or both, but its not very clear if this is a mandatory task?

Also there is a document abotu prerequisites for solman 7.1 JSM and this aspect is not mentioned there

Any inputs are much appreciated. Our current concern is that SD/CHARM configuration does take time and efforts

Thanks

[Vivek_Hegde · Accepted solution]

Hi,

a) Would it be an option to avoid this integration with SD or CHARM?

Yes, JSM can be integrated with SD or ChaRM, BPM. But it is not mandatory to integrate. You can very well use the standalone JSM features in solman.

b) Would it be an option to give end users the option to directly create job documentations (no job request as a first step) filling in all the details about the job, schedule,variant etc?

Yes, It is possible.

You can make use of following SICF service to launch JD directly.

Service: default_host  -> sap -> bc -> webdynpro -> sap -> wd_ags_ejr_jobdoc_fpm

(http://yyyyyhost:portxxxx/sap/bc/webdynpro/sap/wd_ags_ejr_jobdoc_fpm?sap-client=001)

Create an external alias for this service and provide necessary authorozations to users who will be creating JD.

Regards,

Vivek

[former_member184682 · Accepted solution]

Hello Vivek

Thanks for the answer, which was in line with my understanding

I now have a few more questions if you could help with.

a)What would i be losing if i go ahead with this approach. i.e

I ask end users to directly create job documentation instead of starting with a job request instead?

b) How would my end users be able to track whether their job is scheduled or not?

c) Would it be still possible that the end user can only create a job documentation and Save it? but does'not have the right to Schedule?

d) I observed that while creating JD directly, there are certain fields that a end user would not be able to understand like the logical component etc. Which other wise would be auto filled if a user selects a system in the JR instead. Your thoughts?

I still think that integration with SD would be a very good option because it brings with it some kind of segregation between IT and End user responsibilities etc.

[former_member184682 · Accepted solution]

Hi,

Any thoughts?

[volker_vongloeden · Accepted solution]

Hello,

here are some answers from my side

a) The job document is a persisting document and normally no end user  is able to fill it our completely. Normally the end users can only provide business and organizational information, then the application support on IT side has to continue the documentation and then the scheduling team has to complete technical details in the documentation. So it is right that it is technically feasilbe that end users directly create some job document, but organizationally it doesn't really make sense. The Job Request in SolMan is bridigng the gap between business and IT and should help to provide some standardized process.

b) Normally you use the post processing framework beneath CRM to realize this. So once the Incident with Job Request is completed the end user would get an email.

c) Yes, scheduling has some separate authorization profile.

d) You can customize the Job Request (as well as the Job Document), please see http://scn.sap.com/community/it-management/alm/solution-manager/blog/2010/08/24/how-to-configure-sap.... Nevertheless typcically you have to include this in your end user training to explain how the F4 value help needs to be used to assign system/client via logical component.

Integration with SD is surely a good thing but requires far more configuration and organizational change than just introducing the Job Documentation. We always recommend starting with the Job Documentation first (especially if you have some implementation or upgrade project where you need to (re-)document  jobs). Later on you switch-on the Job Request integration.

Kind Regards

Volker

[former_member184682 · Accepted solution]

Dear Volker

Many thanks for writing this in detail. So is it right that SAP recommends to start small with JD only ? and then at a later point in time introduce JR?

This means it will be completely IT  teams who would be initially importing all existing jobs and creating JD's out of them? also it would only IT teams who would be creating JD manually out of end user submitted new word/excel based requests (till the time JR setup is agreed and put in place)

Is it because of the prerequisite integration of Charm and Service desk functionalities that you mention JR requires far more configuration and organizational change compared to JD only setup?

Also i was curious how JRs were created before Service Desk/ Charm were introduced?

We were interested if we can still have JR but not integrated it with SD/Charm. For notification purposes we coudl write a simple BADI for email trigger as soon as JR is created so the IT teams can respond to it etc and then create JD out of it automaticaly

Many thanks in advance

Chandrakanth

[volker_vongloeden · Accepted solution]

Hello,

as the job doc can be used stand-alone as well as integrated it is the most logical way to start with.

The job req is a web form and as soon as you save it, then a CRM document is created. Hence you need to integrate either with SD or ChaRM.when you want to use JR.

Regards

Volker

[former_member184682 · Accepted solution]

Dear Volker

Thanks a lot for claryfing some important questions

I was reading the documentation from /jsm and the sap notes regarding this.

Most of the documentation is focussing on JR and Charm / SD integration

Would you be able to point me to some documentation that shows Standalone JD usage in more details. 

Above you mentioned that End users might not be able to enter all the details and IT has to pick it up from there . Was wondering if we could have have some illustration (like we have for other JR--> SD/Charm scenarios) with screenshots for JD standalone usage

Would you have something like this?

Also , though you mentioned that SAP in general recommends to start with JD standalone and then integrate JR, the documentaion available in jsm doesnot seem to indicate this recommendation. Because there was a lot of emphasis on JR and how it adds value (which i agree to completely though). The standalone JD usage seems to be  no where officially emphasized.

Many thanks in advance

Thanks

Chandrakanth

[volker_vongloeden · Accepted solution]

Hello,

it is true that the blogs and documentation are mainly describing the whole integration between the components as this is unique in the industry. But there are also blogs like http://scn.sap.com/community/it-management/alm/solution-manager/blog/2010/02/13/a-new-column-in-tran... where the integration is briefly mentioned but not emphasized as the JD can be used standalone.

Regards

Volker

[former_member184682 · Accepted solution]

Volker,

Super thanks again for the answer.

Would be extremely helpful if you could create a new doc in the /jsm media library that describes the JD standalone usage. I really beleive that this will clarify a lot of questions for newbies in the JSM area who would like to start small.

Many thanks in advance

Chandrakanth

[former_member184682 · Accepted solution]

Hi Voker

Would your team consider my request above. It would really help many customers as currently most of the documentation on the media library focusses on Charm/SD integration which as you mentioned could be done as a second step once standalone JD based usage is setup and working as expected

Many thanks in advance

Chandrakanth