LOY Expiration engine does not work equally for redemption and cancellation
Last updated on JANUARY 01, 2018
Applies to:Siebel Loyalty Engine - Version 220.127.116.11 SIA  to 18.104.22.168 SIA  [Release V8]
Information in this document applies to any platform.
On : 22.214.171.124 SIA  version, Loyalty
When cancelling one redemption item that use one accrual item expiring in current date, but not in the current time, the "Accrual - Cancellation " is correct but the accrual item is created/set as expired.
Some Airline companies, using Siebel Loyalty Application, expects to have the Accrual item available until the 00:00:00 of the current date, beeing available during all the Day.
And so the the redemption and cancellation engine process should be working equally to put the point back to normal, allowing the LOY member to use the point until the end of the current business day.
Scenario: When cancelling one redemption using one accrual item that will expire in current date but not in the current time, the "Accrual - Cancellation " is correct but the accrual item is created as expired. The type is set to Expired.
However, TAM Airlines expects to have the Accrual item available until the 00:00:00 of the current dat.
1. Use an Accrual transaction where its accrual item will expire in the current date;
2. After that, create a new Redemption transaction and processed it;
3. In sequence, cancel the Redemption transaction, created by step "2". Notice that an "Expired" redemption item was created for the current accrual id.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms