HRXSS_PER_BEGDA - Implementing Custom Effective Dates with a BADI

Question

What am I missing?
We have a need to implement different effective dates based on infotype.
( For example, we want changed to IT 210 (US - WithHolding) to be effective
on the first day of the current (unprocessed) pay period).
IT 6 (address)  anf 9 Bank will also have there own date logic.
To this end, we implemented BADI   HRXSS_PER_BEGDA through the config, 
as ZHRXSS_PER_BEGDA with an implementation class
of ZCL_IM_HRXSS_PER_BEGDA  .
To keep it simple, as a first test,  we left the business logic out and just hard coded a date  as follows:
method IF_EX_HRXSS_PER_BEGDA~DEFAULT_DATE.
  if INFTY = '0006' .
    begda  = '20071001' .
  endif .
endmethod.
( an external breakpoint confirms that the code is reached)
I would have thought that this would have set the start date to 10/01/2007 .
When I chang an address through the portal, the effective date, both displayed on the ESS side, and as saved on the backend, is always [today].
What am I missing?
...Mike
We're running :
NW 2004S, ESS 1.0 SP09 Web DynProVersion
with ECC6.0 ERP2005 on the R/3 side

Answer 1

HI Michael,
I have similar problem that you described here. I have implemented the BADI - HRXSSPER_BEGDA to default the start date of dependents' infotype (0021) to a date in the past based on employee's hire date. However, the start date is always shown as current date. I have used a simple code as
IF INFTY = '0021'.
BEGDA = '20090901'.
ENDIF.
I shall be glad if you help me resolve this issue. Thanks a lot.
Regards,
Shakir