Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

How to configure SAP's standard Job Request form - Part 1

volker_vongloeden
Advisor
Advisor
‎08-24-2010 3:08 AM
0 Kudos

For quite some time the SAP Solution Manager provides all necessary tools to control the whole governance around background jobs. Two key elements are the standardized and web-enabled Job Request form on the one hand where end users or project team members can request new jobs or can request changes to existing jobs. And on the other hand you have the central Job Documentation which allows central Best Practice documentation of background jobs. Both (Job Request and Job Documentation) are working in an integrated manner so that error prone double maintenance is no longer necessary.

Time and again customers are asking how they can adjust the standard Job Request form (or also the Job Document) so that it better fits the customer needs and terminology. In this sequence of three blogs the following shall be explained:

 

How to maintain static value helps for selected fields

In order to maintain static value helps (valid for Job Request form and Job Documentation) you have to access transaction SPRO in your SAP Solution Manager. Follow the path

SAP Solution Manager > Scenario-Specific Settings > Job Scheduling Management > Extended Configuration > Adapt Organization Data

When you execute this SPRO activity you have to enter one of the five following tables

  1. AGS_ORGUNIT_CUST in order to maintain data about "Organizational Units" like the name of units used in your company
  2. AGS_REGION_CUST in order to maintain data about regions like EMEA, AMERICAS or APJ
  3. AGS_BUSAREA_CUST in order to maintain "Business Areas" like Sales, Procurement etc.
  4. AGS_BUSNSS_PRIO in order to maintain "Business Priorities" other than just 1,...,4 for the background job (which may differ from pure scheduling priorities)
  5. AGS_SCHED_REST_C in order to maintain additional categories for scheduling restrictions (this is only valid for the detailed Job Request or Job Document but not for the Basic View of the Job Request form)

 

 

Once you entered on entry then you can push "Maintain" and add a new entry or change/delete an existing entry. The first column is always used as a short text or for abbreviations and the second column is then used for the corresponding long text.

 

Remark: Entries that you made for these static values help have to be translated by yourself! For more information visit http://help.sap.com/ and search for "SE63" which is the translation transaction.

Now if you access the Job Request form and open the respective field where you maintained some static value help (in our case "Organization") you get to see those maintained entries.

In the How to configure SAP's standard Job Request form - Part 2 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.

Labels in this area
Popular Blog Posts