Skip to Content

In Part 1 of this blog sequence you learned How to configure SAP’s standard Job Request form – Part 1. Now in this second part of the blog you shall learn how to influence whether selected fields shall be visible, mandatory or pre-filled with certain entries. Later on the third part of this blog will explain how you can influence basically any arbitrary field within the form regarding visibility or re-naming.

How to configure if selected fields shall be visible, mandatory or pre-filled with certain entries

In order to configure the properties of certain fields within the Job Request form you have to access transaction SPRO in your SAP Solution Manager. Follow the path

SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Integration with Service Desk > Adapt Job Request Form > Create WebDynpro Component Configuration

SPRO F4

SPRO Felder verstecken

When you execute this SPRO activity you access transaction SE80 where you have to select Web Dynpro Comp. / Intf. and select WD_AGS_EJR_JOB_REQUEST and display this entry. Then open the tree branch Component Configurations and double-click on CC_AGS_EJR_JOB_REQUEST. Then push the button Start Configuration. A new browser window will open.

Conp Config

Within the new window the field Component Name should be filled with WD_AGS_EJR_JOB_REQUEST and the field Configuration ID with CC_AGS_EJR_JOB_REQUEST. Then push the button Change.

Comp Config 2

The next screen allows now the configuration of certain fields in tab strip Component-Defined. The following (perhaps rather cryptic) entries each describe certain general sections within the Job Request form (some of them may only be seen in the Detail View and not in the Basic View of the Job Request Form):

  • ndCcBizContext – Business Context
  • ndCcSchedule  – Scheduling
  • ndCcSdk          – Service Desk Context
  • ndCcSolution    – Solution Context
  • ndCcErrHandle  – Error Handling
  • ndCcGeneral    – General

If you select one of the above areas you get to see several related field entries that can be configured.

Config

Now the logic is basically as follows:

  • If you flag a field starting with req then this field will become mandatory to fill out within the Job Request form (like in this example the field “Region”). If this field is not flagged then the field is only optional within the form. Within the Job Request form mandatory fields are marked with an additional red asterisk
  • If you flag a field starting with vis then this field will be visible within the Job Request form. If the field is not flagged then the corresponding field will be hidden and hence not shown in the Job Request form (like in this example the field “Business Area”)
  • If you enter values in some fields then these values are pre-filled within the Job Request form (like in this example the “EMEA” for field “Region”)

Before our configuration the (default) Job Request form looked as follows for the Business and Service Desk context:

Vorher

After our configuration the same Job Request form appears as follows for the Business and Service Desk context:

Nachher

Fields like Region, Country Code or Short text are pre-filled. Fields like Region and Country Code became mandatory fields. Fields like Business Area, Sold to Party or Processor are hidden. Keep in mind that fields that you are hiding (like Sold to Party) may require a given value that you also have to pre-fill within the configuration step. Otherwise all Job Requests cannot be saved without errors.

In the next part of this blog you will learn how to influence whether selected fields shall be visible, mandatory or pre-filled with certain entries

If you will attend TechEd 2010 you can also visit the following Hands-on session

ALM272 – Manage Your Background Jobs Using Job Scheduling Management in SAP Solution Manager

Frequently asked questions around the topic of Job Scheduling Management are listed and answered under the following link http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Job+Scheduling+Management

If you are interested in further reading. The following blogs provide further details about Job Scheduling Management functionalities within the SAP Solution Manager.

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Shahul Hameed Mohamed Farouk Mohamed Farouk

    Hi Volker,

    Great blog on JSM Job Request screen.

    May I know when Part 3 is coming out (for the below) ? 🙂

    “In the next part of this blog you will learn how to influence whether selected fields shall be visible, mandatory or pre-filled with certain entries”


    Appreciate the detailed explanation on this.. another area which I could not find anywhere is “How to create Job Documentation from Job Request itself ?”


    I know its possible to create “Job Request” from Job Doc.. but is the reverse possible ?


    Thanks in advance

    Regards

    Shahul

    (0) 
    1. Volker von Gloeden Post author

      Hello Shahul,

      since two years I am focussing my work on Business Process Improvement with Business Process Analytics and no longer focus in JSM. So I myself won’t write any part 3 blog. I don’t know if other colleagues are looking into this.

      Of course you can create a Job Doc in reference to the the Job Request. But you don’t do it out of the request screen (where an end user wants to apply for a new job or change)itself, but you do it in the processing mode of the request (as the IT user who is evaluating teh request), i.e. the underlying CRM document.

      Kind Regards

      Volker

      (0) 
      1. Shahul Hameed Mohamed Farouk Mohamed Farouk

        Hi Volker,

        Thanks for the reply. Will also be doing BPM/BPO later 🙂

        I just want to clarify your statement above:-

        “but you do it in the processing mode of the request (as the IT user who is evaluating teh request), i.e. the underlying CRM document.”


        Does this means, based on the CRM doc (whether Incident/ChaRM or both), the IT user will have to MANUALLY create the Job Doc (based on the Job Req)

        OR

        There is an option is JSM Workcenter, to convert Job Req to Job Doc ?

        I dont see an option in JSM workcenter.


        Thanks again.

        Your inputs will be helpful.


        Regards

        Shahul

        (0) 
        1. Volker von Gloeden Post author

          Hi Shahul,

          the user triggers the Job Doc creation from within the Incident or Change Request in the JSM assignment block, but then the data from teh Job Request is automatically taken over for the Job Document.

          So starting the creation and pushing the save button is manual work, but the filling out the Job Doc is done automatically.

          Kind Regards

          Volker

          (0) 

Leave a Reply