ESS - Changes to ''Other bank"

[Former Member]

When an employee makes a change to their "Other bank" on ESS on a day or using a day other than the first day of a pay period, the old amount and the new amount is deposited into the same account.

What would cause this to happen? How can I correct this?

Thanks,

[siddharthrajora · Accepted solution]

it all comes down to the use cases being used and time contraint if you have 3 then multiple records are allowd.

check the table V_T7XSSPERSUBTyp and v_t591A,

also there is anote for this , you can raise a message for SAP too

to get the note,

Also check the note 965324 for the use cases and time contraint to be used.

[Former Member · Accepted solution]

Hi Sidharth,

Thank you for the information. I think the time constraint on this subtype still has to be 3 as in some companies employees are allowed to have more than 2 other banks (with or without gaps etc) at the same time interval.

As a result of that thought A6 is the appropriate use case to go with for the other bank subtype.

The problem here is when the user delimits or changes an existing "Other Bank" subtype (for example changes the amount from 50 to 150) and if such a change happens from a start date in the middle of a pay period, then the payroll program processes both the payments i.e. 50 & 150 as two payments to the same account number etc.

One way to do it correctly is to train the employees to always start the change from a beginning of a pay period. But this will become high maintenance over a period of time. The second way is to implement the BAdi and make the default start date to be always a beginning of the pay period.

I looked for a note as you mentioned in the service market place but could not find any. Can you please mention what the note is about? Does it tackle the duplicate processing of payments in the payroll program or does it tackle the ESS side of the transaction?

Thank You for your inputs.

Regards,

Raj.

[Former Member]

Many thanks to all that reviewed and or replied to this post. We used SAP Note 454352 Option 2 to solve our problem. Our ABAP guys installed the note and it fixed the issue.

Thanks,

[Former Member]

I'm also in the same boat. Looking for a best business practice. In the mean time I gave the functional specification document to ABAPer to implement the HRXSS_PER_BEGDA BAdi by changing the Default_Date method for 0009 subtype 1 in such a way that the default BEGDA is the start date of the pay period based on difference between system date and the payment date in V_T549Q.

By practice it is known that when an existing "Other Bank" details are changed using PA30, then the old one should be delimited as of the last date of the previous pay period. While the delimiting is automatically happening, when done using ESS, the default start date is what the problem is. Hopefully implementing the BAdi will resolve this.

I was wondering if it would've been easier to say that the best practice is to always default the BEGDA as the start of the next payroll period.

Hope implementing the BAdi will solve your problem too.

Good Luck,

Raj.