SAP ABAP IMG Activity HR_LSO_M1C8D1E21A8 (BAdI: Specify Correspondence Control Options)
Hierarchy
☛ EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   ⤷ PE-LSO-TM (Application Component) Training Management
     ⤷ LSO_IMG (Package) SAP Learning Solution - IMG
IMG Activity
ID HR_LSO_M1C8D1E21A8 BAdI: Specify Correspondence Control Options  
Transaction Code S_AEN_10000571   (empty) 
Created on 20050310    
Customizing Attributes HR_LSO_M1C8D1E21A8AT   BAdI: Specify Correspondence Control Options 
Customizing Activity HR_LSO_M1C8D1E21A8PO   BAdI: Specify Correspondence Control Options 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name LSO_CORRESPONDENCE41    

Use

In this IMG activity, you control creation of correspondence requests.

In the IMG activity Specify Correspondence Control Options per Delivery Method or in the Correspondence Control Options infotype (5048), you defined the conditions under which correspondence requests should be created, depending on the delivery method or course type. By doing so, you have already specified the minimum number of possible correspondence requests.

In this IMG activity, you can now fine-tune these rules and take account of special considerations for the underlying business processes. The two BAdI methods enable you to specify whether:

  • Correspondence requests are created in line with the course- or course type-specific rules.
  • The default values of certain correspondence requests should be adjusted. These defaults include:
    1. Correspondence type
    2. Output medium
    3. Indicator for automatic output
    4. Output language

Please note:

  • You cannot change the recipient role or the notification group.
  • Neither the worklist nor the output log contain information as to whether certain correspondence requests were not created by the BAdI.
  • The SAP standard system does not check whether the relevant form template (for example, PDF form) actually exists in the required language. If the template does not exist in the system in the required language, the system determines a default language. This is usually the original language of the form template.

For more information, see the documentation for the individual methods.

This BAdI enables a high degree of flexibility when creating correspondence requests. Note the following points about customer implementations:

  • The scenario of who should receive which notification through which medium and when can quickly become very confusing for the administrator outputting correspondence. This is particularly true in the case of correspondence requests that are triggered and processed automatically and as such, are not under the direct control of the administrator. For example, in the case of a learner booked for a course by the training administrator, it should be easily recognizable which notifications have already been sent and which not.
  • A non standard implementation of the BAdI could result in unnecessary or the wrong correspondence being created and sent.
  • In the case of the medium SMS, you should ensure that you do not send very big files (such as PDF documents) by SMS.
  • If you change the correspondence type, it can lead to the content being changed too. The semantics of the coorespondence request can change completely as a result.

Requirements

You have worked through the IMG activity: Specify Correspondence Control Options per Delivery Method or maintained the Correspondence Control Options infotype (5048) for specific course types or courses to specify the rules underlying correspondence control.

Standard settings

SAP delivers a standard implementation of the BAdI. In this standard implementation, only the output language is adjusted. The system proposes the communication language of the recipient. If no communication language is stored for the recipient, the language of the course is used, or in the case of a prebooking, the language of the prebooking. If this is not available, the system uses the value stored in table T77S0 for the SEMIN CLANG switch.

Activities

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.

Interface

Method GET_OUTPUT_OPTIONS

Method GET_RECIPIENT_OPTIONS

Example

  • You offer courses for employees and external customers. You want to include more detailed information in the correspondence sent to customers than in the correspondence sent to your employees, since employees have access to the information they need through the Learning Portal. In addition, you want to use a different layout in customer correspondence.
  • Since your field staff do not check their Internet mailboxes very regularly, you want to send them a short SMS.
  • The learner's manager should receive no correspondence for certain courses. (In many cases this specification can be made in infotype 5048.)

Implement the BAdI according to your company's requirements. When you do so, bear in mind that you must implement both methods. It may be necessary to call the SAP standard implementation directly from your customer implementation.

Your specific customer requirements dictate which of the two methods you use to best map your requirements, or whether you need to use both methods.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050311 
SAP Release Created in 600