BAPI_CUSTOMER_GETDETAIL1 fails with locked customer record

Question

I'm using the above mentioned BAPI to retrieve some customer classification details, and calls to it fail when someone has the customer record locked (viewing it in VD02 or XD02, for instance).
I can certainly understand this behaviour if I were trying to update the classifications or the customer record itself.  I can even understand why one might want to be able to block this call when the record was being edited so as not to provide out-of-date information, but in my usage slightly outdated information is perfectly acceptable, and the failure of the call is much worse.
Is there a BAPI function that provides the same data that isn't blocked by record-level locks, or a way to consume this function without being blocked in this fashion?
Thanks in advance

Answer 1

My mistake - it's actually BAPI_OBJCL_CHANGE that I'm looking at as failing when the customer record is locked.
In retrospect this makes a little more sense, but I suppose I hoped that since classifications are maintained outside the KNA1 table structure that locking the customer record would not lock the customer's classifications, and that those would only be locked if they were being modified.  It appears that's not the case.
I would still be interested to hear of any workarounds for this issue, though.