Travel PLAN status irrelevant if no business process / workflow existent?
we are using FI-TV-PL in form of a substitutable process. The traveler himself does not issue plans or bookings, we do it centrally via a travel service team (technically we will either use travel assistant with POWL or a customized UWL process). The creation of the travel plan does not involve any approval or workflow items, so technically it will always remain "open". We don't excplicitely make any processes depend on the status of the travel plan either.
My idea was to just hide the status of the travel plan in FITV_POWL_TRIPS etc. because for our business process it is completely irrelevant. However, I'm not 100% convinced I can technically really completly ignore this plan status. I'm afraid I've overlooked something and it could influence the normal trip status directory and our request-expense business process.
Is this fear superfluous?
tl;dr: Travel plan status is functionally irrelevant for us, but is it also technically irrelevant with respect to the trip?