Skip to Content
Technical Articles
Author's profile photo Martin Lauer

Implementation of a naming convention in Job Scheduling Management

h3. Introduction    The {code:html}Job Scheduling Management Standard{code} recommends (and supports) the definition of a naming convention for jobs in order to encode as much information as possible into the job name which eases job management (for example the search in transaction SM37).Knowning this rule it’s now easy to translate the meaning of the job name: Run *S*AP’s *MRP* report *D*aily for plant *0001* in Germany (*DE*) in client *800* of system *TT5*.     h3. Documentation  The implementation of a BADI of the Enhancement Framework  ( is described in the tutorial “[How to implement a BADI |]” in the SAP Library. Please read it first.  h3. How to Let’s create now a custom implementation of a naming convention in SAP Solution Manager.  Start SE80 and view package AGS_EXTJOB_REPOSITORY navigate to +Enhancements+ -> +Enhancements Implementations+ -> +AGS_EJR_NAME_SPACE+.   Deactivate the SAP implementation as shown in the screenshot by deselecting the +Implementation is active+ option, save and activate the SAP implementation. Deactivate SAP Implementation  Now create your own implementation.  Click onto +New+ and enter BAdI Definition BADI_AGS_EJR_NAME_SPACE and the properties of your implementation. After a click onto +OK+ the BAdI implementation and the implementing class – in this example ZCL_JOBDOC_NAMING_CONVENTION –  are created.In order to create an SE61 text to document your naming convention start transaction SE61 and create a new document of type +General Text+ and enter the description. SE61 general text  Afterwards you can implement method EXLAIN_NAMESPACE_RULE. Just copy the code from the SAP Implementing Class CL_AGS_EJR_NAME_SPACE_JOB and replace the name of the SE61 document.Use SAP implementation as referenceThe implementation of method GET_NAMESPACE_RULE is straight forward: just return your pattern as string and it will be pasted into the job name field on request.      This step is important: In order to get called by the BAdI Framework you have to define the right filter value. Define a new filter value +JOBDOC+ for parameter +APPLICATION+ as shown in the screenshot below. Define filter  The methods CHECK_NAME and PROPOSE_NAME provide data by a dedicated class CL_AGS_EJR_NAMING_CONV_INFO. This class has two attributes: a key-value table and a reference to a Job Management API.  Parameter Interface

Assigned tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      i read your blog.
      But now i have more questions than before 🙂
      i am not a programmer myself , only Basis guy.

      How can i implement the following check ?
      I implemented a naming convention with mutiple parts : e.G: Country, Module etc.
      Now i want to check, wether the relavant position of the job name inherts the correct data (2 character language code, 2 charatcter module name ...)
      How can i implement this ?

      Roland Fischl

      Author's profile photo Martin Lauer
      Martin Lauer
      Blog Post Author

      Hi Roland,Martin