BPS Documents not storing/saving in Production

[former_member353620]

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

[Former Member · Accepted solution]

John,

we had exactly the same problem during our development stage of the project.

We've found the following issue in our production system.

check it out, if you also had the same problem.

"Document attributes might not have been generated probably. This can happen for example

after a transport into the system. In this case you have to regenerate the document attributes again manually. How to do this you can look up in note 537104.

Hope it helps.

[former_member353620 · Accepted solution]

hari79,

Thanks for your reply. Actually, we've generated the document attributes in each system using exactly the method described in OSS note 537104. Still, we're experiencing the problem I described above.

The user receives no error message that anything is wrong. No system log or ABAP dump error messages are generated. It looks as if the document has been stored, but when you log out and back in, the document is gone.

- John

[former_member93896 · Accepted solution]

Hi John,

I don't know the solution. Put a break-point into function module UPC_BW_DOCUMENT_UPDATE and check the LS_ERROR variable. Unfortunately, the error information is not passed to the user in all cases.

Regards

Marc

SAP NetWeaver RIG

[former_member353620 · Accepted solution]

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

[former_member93896 · Accepted solution]

John,

The class is correct. So the question is what characteristic cause the error. Once you know this, do a check using the BW document administration tools.

If you can't fix it put the information you have so far into a message for SAP support.

Regards

Marc

SAP NetWeaver RIG

[former_member353620]

It turns out the problem had an interesting cause. I did as Marc suggested and pored over lines and lines of code watching this execute in the debugger. When it gets to the part where it checks the valid document attribute characteristics, the values contained in the internal table that it read from the database did not match what was actually in the database. Checking this table, it turns out that it was a buffered table. Our Basis team found that our system hadn't actually been bounced in weeks (!). So, a simple bounce of the system flushed the buffers, and forced a correct read from the database. The documents now save properly.

Interestingly, even though the code for saving documents encounters a condition for which it is completely aware that it's an error, it never passes this fact back to the calling programs/functions. Therefore, it only ever says "Data was saved." and you have no clue that the document never saved. Grrr....

Message was edited by: John Gooch