SAP ABAP IMG Activity HRPAYAT_KSB_B2A_FLIS (BAdI: Listing of Possible Names of ELDA Files)
Hierarchy
☛ SAP_HRCAT (Software Component) Sub component SAP_HRCAT of SAP_HR
   ⤷ PY-AT (Application Component) Austria
     ⤷ P03C (Package) HR Customizing: Austria
IMG Activity
ID HRPAYAT_KSB_B2A_FLIS BAdI: Listing of Possible Names of ELDA Files  
Transaction Code S_L4H_49003244   (empty) 
Created on 20130206    
Customizing Attributes HRPAYAT_KSB_B2A_FLIS   BAdI: Listing of Possible Names of ELDA Files 
Customizing Activity HRPAYAT_KSB_B2A_FLIS   BAdI: Listing of Possible Names of ELDA Files 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPAYAT_KSB_B2A_FLIS    

Use

This Business Add-In (BAdI) is used in the Payroll Austria (PY-AT) component. You can use this BAdI to override the type according to which the system determines the possible file names of ELDA files for a mass import of sick leave certificates.

Using report RPCKSBA0_B2A, you can start the mass import of ELDA files. If you specify a logical directory there, you can use this BAdI to determine the name of the files to be uploaded.

Requirements

You select in report RPCKSBA0_B2A a logical directory for importing ELDA files.

Standard settings

The default implementation uses the naming convention "KB??????" defined by ELDA, whereby each question mark represents a digit. A file extension does not belong to the template.

For the first import, the BAdI uses the name KB000000. For additional import runs, the BAdI starts from the last imported file. The system determines the name of the last imported file from table T5AB0. The BAdI receives the file name in the method GET_FILE_LIST via the change parameter CH_FILELIST.

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.

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
HRPAYAT_KSB_B2A_FLIS AT Austria
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRPAYAT_KSB_B2A_FLIS 0 HLA0003815 Subsequent Activities 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20130206 
SAP Release Created in