Manually Changing sli_status in T_LINEITEM

Greetings,

First some background, we have a custom report for our flex packages that uses line items in dummy houses to differentiate between different number of shows in packages. Our patrons order a 4-show, 5-show, or 6-show package and are put into a dummy house and then later, once each show has a finalized run, they exchange seats from the dummy into an actual performance in a new order. The report is written to not count line items with the VTO or RET status so any packages that are returned, are removed from the report but those exchanged (VOO) are still counted.

Unfortunately, one woman ordered 2 subscriptions and actually exchanged seats in both into the actual performance so even after both orders were fully refunded, her original order with the dummy house (the one the report looks at) still has one lineitem with a VOO sli_status and the report is therefore counting this as a 1-show package (which does not exist) and the total numbers are slightly off.

Here is my questions, can anyone think of any negative impact to going into the back end and manually changing the sli_status of this one lineitem so that it is no longer counted in the report? I would put thorough order notes in to explain the change that was made for historical purposes, but I can't think of any real negative ramifications aside from confusion if someone ever tried to look up this order for some reason (hence the order notes). Anyone have any other thoughts?

Thanks!

Parents
  • I cannot help you with this issue - as we book our packages identical to you and have had similar problems in the past. My biggest concern would be making sure you locate all the tables that contain the sli_status - that will quickly become a riskier task when making manual updates on the backend. 

    HOWEVER... would you be willing to share your report? I'm currently attempting to dig into the Package Order Listing report for it to function properly for us and I keep running into dead ends. Your report seems like a decent solution... enash@2st.com if you're able and willing.

    Thank you!

Reply
  • I cannot help you with this issue - as we book our packages identical to you and have had similar problems in the past. My biggest concern would be making sure you locate all the tables that contain the sli_status - that will quickly become a riskier task when making manual updates on the backend. 

    HOWEVER... would you be willing to share your report? I'm currently attempting to dig into the Package Order Listing report for it to function properly for us and I keep running into dead ends. Your report seems like a decent solution... enash@2st.com if you're able and willing.

    Thank you!

Children
No Data