How to configure SAP’s standard Job Request form – Part 2
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
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.
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.
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.
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:
After our configuration the same Job Request form appears as follows for the Business and Service Desk context:
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.
- Creating a Job Request with SAP Solution Manager
- SAP is first vendor to provide a comprehensive Job Management Suite
- Job Interception: Controlling end-user scheduled jobs
- Implementation of a naming convention in Job Scheduling Management
- Re-directing transactions SM36, SM37, SA38: Controlling end-user scheduled jobs – Part 1
- An easy way to identify end-user scheduled jobs which bypass your central scheduling tool
- A new column in transaction SM37 – Job Documentation
- Re-directing transactions SM36, SM37, SA38: Controlling end-user scheduled jobs – Part 2
- Creation of Job Documentation Macros
- Job Documentation Templates
- How to configure SAP’s standard Job Request form – Part 1