Ansicht
Dokumentation

HR_ECM_00_LT_E01 - Business Add-In: Extract Participant Information for Outbound IDOC

ABAP Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Use this Business Add-In to extract the participant data of an employee using methods other than the standard ones.

The Business Add-In consists of five methods, as described below.

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

The following import parameters are provided:

• PERNR
  Personnel number.

• BEGDA
  Begin date of the data extraction.

• ENDDA
  End date of the data extraction.

• MESSAGE_HANDLER
  Reference to interface IF_HRPA_MESSAGE_HANDLER. If any messages should be sent to the frontend, you can add them to the message list using method ADD_MESSAGE of this interface or function module HR_ECM_ADD_MESSAGE.

The following export parameters must be provided by your coding:

• PROCESS_STANDARD
  Indicator to be set to 'X' if you want the system to ignore the result of your implementation and perform the standard routine.

• IS_OK
  Indicator to be set to SPACE if errors have prevented your routine from retrieving the data successfully.

The following change parameters must be supplied by your coding:

• EE_NAME_TAB
  This table contains all information about the name of an individual employee:

• BEGDA
  Valid from date indicates the begin date of the validity period of a record.

• ENDDA
  Valid to date indicates the end date of the validity period of a record.

• ENAME
  Formatted name of employee or applicant.

• VORNA
  First name.

• RUFNM
  Known as.

• MIDNM
  Middle name.

• NACHN
  Last name.

• NACH2
  Second name.

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

The following import parameters are provided:

• PERNR
  Personnel number.

• BEGDA
  Begin date of the data extraction.

• ENDDA
  End date of the data extraction.

• MESSAGE_HANDLER
  Reference to interface IF_HRPA_MESSAGE_HANDLER. If any messages should be sent to the frontend, you can add them to the message list using method ADD_MESSAGE of this interface or function module HR_ECM_ADD_MESSAGE.

The following export parameters must be provided by your coding:

• CONTACT_INFO
  Structure containing contact information such as telephone number, mobile number, fax number, pager number and email address.

• PROCESS_STANDARD
  Indicator to be set to 'X' if the system should ignore the result of your implementation and perform the standard routine.

• IS_OK
  Indicator to be set to SPACE in case any error has prevented the method to extract the data.

This method replaces the complete data extraction routine related to the employee's postal address.

The following import parameters are provided:

• PERNR
  Personnel number.

• BEGDA
  Begin date of the data extraction.

• ENDDA
  End date of the data extraction.

• MESSAGE_HANDLER
  Reference to interface IF_HRPA_MESSAGE_HANDLER. If any messages should be sent to the frontend, you can add them to the message list using method ADD_MESSAGE of this interface or function module HR_ECM_ADD_MESSAGE.

The following export parameters must be provided by your coding:

• PROCESS_STANDARD
  Indicator to be set to 'X' if you want the system to ignore the result of your implementation and perform the standard routine.

• IS_OK
  Indicator to be set to SPACE in case any error has prevented the method to extract the data.

The following change parameters must be provided by your coding:

• EE_POST_TAB
  This table contains all relevant information about postal address of an individual employee:

• BEGDA
  Valid from date indicates the begin date of the validity period of a record.

• ENDDA
  Valid to date indicates the end date of the validity period of a record.

• LAND1
  Country key.

• PSTLZ
  Postal Code.

• REGIO
  Region (State, Province, County).

• ORT01
  City.

• STRAS
  Street and House Number.

• LOCAT
  2nd address line.

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

The following import parameters are provided:

• PERNR
  Personnel number.

• BEGDA
  Begin date of the data extraction.

• ENDDA
  End date of the data extraction.

• MESSAGE_HANDLER
  Reference to interface IF_HRPA_MESSAGE_HANDLER. If any messages should be sent to the frontend, you can add them to the message list using method ADD_MESSAGE of this interface or function module HR_ECM_ADD_MESSAGE.

The following export parameters must be provided by your coding:

• ADDITIONAL_INFO
  Structure containing additional information such as ID number, date of birth, nationality, hire date, leaving date and leaving reason.

• PROCESS_STANDARD
  Indicator to be set to 'X' if you want the system to ignore the result of your implementation and perform the standard routine.

• IS_OK
  Indicator to be set to SPACE if errors have prevented your routine from retrieving the data.

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

The following import parameters are provided:

• PERNR
  Personnel number.

• BEGDA
  Begin date of the data extraction.

• ENDDA
  End date of the data extraction.

• TAXTY
  Tax type (optional parameter).

• MESSAGE_HANDLER
  Reference to interface IF_HRPA_MESSAGE_HANDLER. If the evaluation of the default compensation area encounters any messages that should be sent to the frontend, you can add them to the message list using method ADD_MESSAGE of this interface or function module HR_ECM_ADD_MESSAGE.

The following export parameters must be provided by your coding:

• PROCESS_STANDARD
  Indicator to be set to 'X' if you want the system to ignore the result of your implementation and perform the standard routine.

• IS_OK
  Indicator to be set to SPACE if errors have prevented your routine from retrieving the data successfully.

The following change parameters must be provided by your coding:

• EE_TAX_TAB
  This table contains all tax information of an individual employee:

• BEGDA
  Valid from date indicates the begin date of the validity period of a record.

• ENDDA
  Valid to date indicates the end date of the validity period of a record.

• TAXTY
  Tax type.

• TXPCT
  Tax rate.

• LAND1
  Country key.

• REGIO
  Region (State, Province, County).

• CITYC
  City Code.

• PSTLZ
  Postal Code.

• The formatted name comes from a country-specific infotype or routine.

• The telephone number comes from a country-specific infotype or routine.

• The postal address comes from a country-specific infotype or routine.

• The ID number comes from a country-specific infotype or routine.

• The tax information comes from BSI (third-party software provider).

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 ~ 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.

Activation and deactivation of the Business Add-In can only be done for all three methods together. If for one of these methods you still want to perform the standard coding, add the line PROCESS_STANDARD = 'X' (applies to GET_EMPLOYEE_NAME_INFO, GET_EMPLOYEE_CONTACT_INFO, GET_EMPLOYEE_POSTAL_ADDRESS, GET_EMPLOYEE_ADDITIONAL_INFO, GET_EMPLOYEE_TAX_INFO).

ABAP Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Length: 11298 Date: 20240523 Time: 210325     sap01-206 ( 147 ms )