Skip to Content
avatar image
Former Member

badi HRXSS_PER_BEGDA not behaving as expected

Hi all,

I am facing an issue with the badi HRXSS_PER_BEGDA. For bank info type when I creating new record for other bank in personal profile screen then even if I set the value of begda in he badi, it is still saving the today's date as the begda in the bank infotype.

Kindly help in resolving this issue.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Dec 26, 2014 at 05:32 AM


    Check the note 947172

    Check the usecase A4 and A6 for Main Bank and Other Bank

    Implement DEFAULT_DATE method of this BADI. This method will allow you set the required date based on the following parameters – country grouping, personnel number, infotype, subtype. This will allow us to define the rules for specific infotype/subtype based on the country grouping, employee or any other attributes of the employee.

    You have to set the BEGDA (Start Date) parameter of the method to manipulate the effective date requirements.

    Add comment
    10|10000 characters needed characters exceeded

    • please check 1985127 - BADI HRXSS_PER_VALIDITY 'Can only be implemented SAP-internally' The error message you are reporting is desired behaviour for maintaining bank record. Please go through below explanation for further understanding: For ESS scenario - Personal details, Address, Bank details, Famil member & details... and etc., by default new/change record is saved on current system date. We provide customer with BAdi HRXSS_PER_BEGDA, to maintain records valid from past date or future date. Using this BAdi, you can default date either in future or past. When you are maintaining date in future then system will allow you to create record valid from that date only. When you are maintaining past date in this BAdi then end user would be allowed to create record valid from the past date. We usually recommend our customer to maintain past date in BAdi for Address or Family member. For bank records, you must maintain default date in future, preferrably starting from next payroll period. End user should not be allowed to change bank detail for current payroll period after payroll is run because that may cause inconsistency. To avoid such situations, you must allow end user to create record from future date only. In such case the error message you are getting is appropriate