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 (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm) is described in the tutorial "[How to implement a BADI | http://help.sap.com/saphelp_nw70ehp1/helpdata/en/44/f518d884056c30e10000000a114a6b/frameset.htm]" 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. 
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. 
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.
The 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. 
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. 
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. 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.The 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. 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. - SAP Managed Tags:
2 Comments
