SAP ABAP IMG Activity /MRSS/SQE_MATCHING (BAdI: Qualification matching)
Hierarchy
☛ MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net
   ⤷ PM-WOC-MO (Application Component) Maintenance Orders
     ⤷ /MRSS/SQE (Package) MRS qualifications: engine
IMG Activity
ID /MRSS/SQE_MATCHING BAdI: Qualification matching  
Transaction Code /MRSS/35000040   IMG activity: /MRSS/SQE_MATCHING 
Created on 20061005    
Customizing Attributes /MRSS/SQE_MATCHING   BAdI: Qualification matching 
Customizing Activity /MRSS/SQE_MATCHING   BAdI: Qualification matching 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /MRSS/SQE_MATCHING    

Use

You can use this BAdI to define how the customer-specific fields are matched. You can also change the field catalog that is used to output the analysis of the matching result.

This BAdI is called when qualification matching is carried out in MRS.

Requirements

Before you implement the USER_DATA_MATCHING method, you must implement the customer-specific attributes for qualification matching:

  • For the requirements profile, implement the customer include CI_REQ_ADDN_ATTR.
  • For the employee profile, implement the customer include CI_EMP_ADDN_ATTR.

Standard settings

The BAdI is active in the standard system. In the default code for the USER_DATA_MATCHING method, fields with the same name as the two customer includes listed above are compared for identical content. If the content is identical, the system assigns 1 to the criterion as part of the matching process. If the content is not identical, the system assigns 0 to the criterion. The default implementation also returns an internal table with analysis information, which you can display with the "Analysis of the Matching Result" function.

Activities

The BAdI provides the following methods:

  • HR_ASSIGNMENT_GET (returns the HR assignment for the output)
    This method is not used at present.
  • USER_DATA_MATCHING (matches the fields defined by the customer)
    A commented default implementation is provided for this method.
  • TRACE_FIELDCAT_CHANGE (changes to the field catalog for outputting the matching trace)
    When you call the "Analysis of the Matching Result" function, the system displays the results for the individual aspects of the matching process in ALV grid controls. The field catalogs can be changed when these controls are initialized. The import parameter IV_TRACE_TYPE indicates the aspects of the matching process (for example, structured qualifications) for which the field catalog is used. The sample code contains comments that explain the significance of the possible values.
  • ADDITIONAL_MATCHING
    You can implement this method to carry out additional matching for customer fields (it is possible to define customer-specific fields in the free employee search that are not integrated into the customer-specific fields of the requirements profiles)
  • ADDITIONAL_MATCH_RES_GET
    You can implement this method to display one or more employees at the top of the results list of the employee search, regardless of the matching result. These can also be employees that are not contained in the results list.

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG /MRSS/SQE_MATCHING 0 HLB0009110 Cross-Application Components 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20090903 
SAP Release Created in 195