Air Ticket Benefit Carry forward Issue – Resolution Provided

By /

Ankur_Sharma_0-1718256132455.png

Air Ticket Benefit Carry forward Issue

Business Context: The actual ticket accrual amounts expire when air tickets are accrued over a long period of time, leading to inaccurate ticket accrual balances.

How the employee’s ticket accrual was computed and when it expired is shown in the example below. Due to improper parameter declaration at the feature TBPAR, the system is lapsing the balance by year. Consequently, the employee’s overall ticket balance should reflect 3, as ticket accrual occurs from 2022 to 2024.

 

Year Begin

 Year End

Ticket Accrual

Remarks

01.01.22

31.12.22

1

Ticket Lapsed in Year 23, if it’s not encashed

01.01.23

31.12.23

1

Ticket Lapsed in Year 24, if it’s not encashed

01.01.24

31.12.24

1

 

Total Ticket

 

1

 Ticket Benefit should have come as 3

TBPAR Feature Specification:

According to the screen print below, if you set the Return value to 12, the system will automatically lapse the ticket benefit accrued by every 12 months, with the expectation that the ticket benefit will be automatically encashed annually. Therefore, there won’t be any carry forward whatsoever.

Ankur_Sharma_6-1718256199053.png

For the clients that were already gone live with the Feature TBPAR Parameter as 12, this can’t be modified, even if we update the value to 99 this won’t affect the ticket benefit type accrual Process beyond 12 months at the Master data level.

There are genuine business scenarios, where employee may not have encashed his/her ticket benefit hence ticket benefit should get accumulate, rather than lapsing the benefit which is a huge loss to the employee.

Resolution:

Please create a new Ticket Benefit sub type and maintain the return value as mentioned below to extend the ticket benefit accrual carry forward up to 8 years

LEAV is a standard Ticket Benefit Subtype and in this example we have created New ticket benefit type as AIRT

 

Ankur_Sharma_7-1718256229021.png

Feature TBPAR new return value Maintained in order to carry forward the accumulated Ticket benefit up to 8 Years (96/12=8)

Ankur_Sharma_8-1718256306187.png

Corrections at a Master Data level:

  1. Create a new Ticket Benefit subtype (In this Example created as AIRT)
  2. Delimit the old subtype in IT3408 and update the master data record with new subtype effective new start Date.
  3. Nullify the balances in the old sub type using Air ticket Correction Info Type 3410

Ankur_Sharma_9-1718256336954.png

Per Screen Print Above New Ticket Benefit Type Created as AIRT and updated it with an effective date as 01.02.2024

Ankur_Sharma_10-1718256358954.png

Per the above Screen Print, Old balance lying the old sub type has been Nullified, and the remaining balance has been adjusted in the New Ticket Benefit Type.

 

Scroll to Top