The Mileage Account in the BDM doesn't seem to serve any purpose since Frequent Flyer Mileage System (FMS) performs all the query / update of the mileage credits earned. Further to this, we are not allowed to change FMS at all.
I'm planning to assume the Mileage Account to be used in the near future when a rewriting of the FMS is allowed. For the time being, the Mileage Account will only store the status of the Account, ie whether it is active or not.
Is this assumption safe? I believe I have not changed the BDM anywhere here. Any suggestions is appreciated.
I'd suggest, for starters, doing a quick search to see how many of us have dealt with the issues of the requirements. You did hit on something important in considering the problem - that you're not allowed to rewrite/change the FFMS, as the client's told you explicitly not to.
You do need it, though - there has to be a provision for being able to allow flights using frequent flier miles. (It's in the Pay for Itinerary usecase.) If you think about it, there are ways to get around the "do not alter" requirement for FFMS - specifically, it doesn't say that you can't access the FFMS database, but rather that they don't want you rewriting it. So consider how you might allow for that in your design, if you choose to go that route.
And just for safety of consideration - it's not the only solution out there. Doing a search myself, I see others have tackled it entirely differently, so it's something you might think about. [ October 19, 2005: Message edited by: Theodore Casser ]
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
Joined: Mar 07, 2002
First of all, thanks for your response. I did go through the different feedbacks from the forum here. Some, as you have said, mentioned about accessing the FMS database directly and some even mentioned of the FMS system updating the Mileage Account entity in FBN.
I'm a bit hesitant to go for the 1st approach since this would require understanding of certain business logics and the FMS system and not just merely performing an update to the FMS database.
With regards to the 2nd approach, that would be leaning towards a "re-writing" of the FMS system.
Coming to the above conclusions, I felt that the Mileage Account could be redundant (well, at least for now). It would be useful when FMS can be enhanced or rewritten.
Well, I could be wrong - your further feedback is much appreciated.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com