SAP ABAP IMG Activity HR_ECM_00_LT_E03 (Business Add-In: Inbound Processing for Exercise Confirmation IDOC)
Hierarchy
☛ EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   ⤷ PA-EC-LT (Application Component) Long-Term Incentives
     ⤷ PAOC_ECM_LTI_BL (Package) Long Term Incentive Plans - Business Logic
IMG Activity
ID HR_ECM_00_LT_E03 Business Add-In: Inbound Processing for Exercise Confirmation IDOC  
Transaction Code S_PLN_06000120   (empty) 
Created on 20030514    
Customizing Attributes HR_ECM_00_LT_3_2_E   LTI - Not required - Not critical - User Exits 
Customizing Activity HR_ECM_00_LT_E03   BAdI HRECM00_EXERCISE 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRECM00_EXERCISE    

Implement this Business Add-In to extract exercising data - used in the function module HR_ECM_PROCESS_EXERCISE_IDOC - using data processing other than the standard one.

The Business Add-In consists of the three methods described below.

PROCESS_IDOC

This method enables you to fully or partially write or change the IDoc; it replaces the complete data extraction routine related to the employee's name.

The following import parameters are provided:

  • INPUT_METHOD
    Indicates whether the IDoc should be processed in a dialog box or not. Possible values are:
    • ' ' - Background (no dialog)
    • 'A' - Show all screens
    • 'E' - Start the dialog box on the screen where the error has occurred.
  • MASS_PROCESSING
    For advanced workflow programming only.
  • IDOC_CONTRL
    This table contains one entry for each IDoc's control record and is only used by the function module for importing data. Typically, the only fields used by the inbound function module are Docnum (the IDoc number), and either Mestyp (Message type) or IDoctp (Basic IDoc type).
  • IDOC_DATA
    This table contains one entry for each IDoc data segment. The following fields are relevant to the inbound function module:
    • Docnum - IDoc number
    • Segnam - name of the segment
    • Sdata - segment data.

The following export parameters are provided:

  • IN_UPDATE_TASK
    Set this indicator to specify whether or not Update Task is used to update the database.
  • CALL_TRANSACTION_DONE
    Set this indicator to specify whether or a Call Transaction is used to update the IDoc's status.
  • IDOC_PROCESS_FLAG
    Set this indicator to determine whether or not normal inbound processing takes place (value is either initial or not 'X').
  • SUBRC
    Return code.
  • IDOC_STATUS
    The table that should contain one record for each processed IDoc. Possible values for the filed Status are:
    • '51' - Error occurred
    • '53' - IDoc successfully processed.
  • RETURN_VARIABLES
    A table containing the document numbers of the IDoc and the processed application object. These numbers are used for workflow (for example, error handling) and for linking the IDoc to the corresponding application object.
  • SERIALISATION_INFO
    A table containing the return value of function module, SERIALIYATION_CHECK, which is called in the inbound function module.

SET_EXPORT_PARAMETERS

This method replaces the complete data extraction routine related to the employee's contact information.

The following import parameters are provided:

  • IN_UPDATE_TASK
    Set this indicator to specify whether or not Update Task is used to update the database.
  • WORKFLOW_RESULT
    This controls whether any events are triggered.
  • APPLICATION_VARIABLE
    This optional parameter si passed on to the workflow.
  • RETURN_VARIABLE
    Description as same as above.

IDOC_STATUS_PROCESS

This method works through list of IDoc status .

The following importing parameters are provided:

  • IDOC_CONTRL
    See above.
  • IDOC_DATA
    See above.

The following export parameters are provide:

  • IDOC_STATUS
    See above.

Example

Requirements

Standard settings

Recommendation

Activities

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

The screen for creating BAdI implementations is now displayed.

2. Enter a short text for the implementation in the Short text for implementation field.

3. From the tab index, choose Interface.

The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

4. Save your entries, and assign the implementation to a development class.

5. Place the cursor on the method, and double-click to enter method processing.

6. Enter the coding for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.

7. Save and implement your coding. Return to the Edit Implementation screen.

8. Save the entries on the Edit Implementation screen.

Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

9. Choose Activate.

Further notes

For more information on using Business Add-Ins, refer to the SAP Library under Basis Components ->ABAP Workbench (BC-DWB) ->Changing the SAP Standard (BC)->Business Add-Ins.

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  20031028 
SAP Release Created in 200