BPS Documents not storing/saving in Production

Question

We are using the Document functionality in BPS layouts to create and store a Microsoft Word document associated with a particular cell.  We have set all the necessary characteristics' document attribute properties, and these have been generated in each of our systems, Development, QA, and Production.
This functionality is working perfectly in our Development and QA environments.  However, in Production, the user creates a document, he/she can see the document icon in the Excel-in-Place layout, and saves.  When the user comes back into the layout, the icon is missing.  The document cannot be seen in the Administrator's Workbench->Documents central administration.  In QA and in Development, the documents successfully save, and can be viewed in the Admin. Workbench->Documents.
As far as I can tell, all configuration is the same in all three environments.  I've checked the bds service in SICF and it's active across the board.  I've checked all that I can in the Document Modelling Workbench, and everything is identical.  I even see the table these are stored in (BDSPHIO10), but it's empty in Production, filled with values in QA and Dev.
What am I missing?  Why is this not working in Production?
Thanks for any help you can offer.
- John Gooch
214-978-6549
Hunt Consolidated, Inc.
Dallas, TX

Answer 1

Thank you for your suggestion, Marc.  I placed the breakpoint as described and then tried to execute the planning folder as before and store a document.  When I clicked 'Save', I reached the breakpoint and began stepping through the code.  When it called the function module 'SKWF_LOIO_WITH_PHIO_CREATE', the LS_ERROR came back with:
ID =   SKWF_SDOKKERRS
Type = E
No =   030
V1 =   BW_LO_TRAN
I checked the description of the error message in T100, and it looks like the error is:
"Characteristic of class 'BW_LO_TRAN' is not valid."
When it calls function module 'SKWF_PHIO_STORE_CONTENT' next, the error is E001 in the same class:  "'&1' does not exist."  I'm assuming this is due to the failure of the previous function module call.
Any idea how I can make the "characteristic of class 'BW_LO_TRAN'" valid?
Thanks again, this gives me more information about the potential problem.
- John