Comment text not saving to configured length value

[Former Member]

Hi all,

I'm experiencing a problem in BPC 10.0 NW (SAPK-80102INCPMBPC) with the saving of comments/text in one Model.

When I use the EPMSaveComment formula to save some text that exceeds 255 characters, it ignores the characters from 256 onwards. Now you're obviously going to think that it's because the Comment Length has not been set via the Web Front End > Administration > Models > ..., but as you will see from the image below the length has been set to the maximum 1332.

I have retested the functionality in a new clean adhoc worksheet and can confirm that it's not to do with the template we're using. I have also tested it in the QA and DEV clients, only to find that in our Development client it is working as it should be (all three clients are configured the same with 1332 chars) but the QA and PROD clients are somehow stuck at a maximum of 255 characters.

Any thoughts/solutions would be most welcome.

Thanks in advance.

John

[Former Member · Accepted solution]

Thanks Vadim, but I've already seen that one and I'm pretty sure it's not relevant. This I believe was the original note to apply when the maximum length was increased by SAP. The patch level of my system is the equivalent of SP9 (801 0002) whereas the note suggests upgrading to SP5 (which we're already past).

Our system already has the capability to use 1332 characters and we are already successfully using this many characters on another Environment in our Production client with no problem, so the cause has to be something else.

The system is live and working perfectly except for this one annoying issue, which inconsistently is not a problem in our development client. The whole Environment was transported through the normal BW transport tool to our QA and then Production clients and it's only just come to our attention that this is one small bit is not working properly.

Regards

John

[former_member186338 · Accepted solution]

Ups, you have not mentioned that the issue is environment dependent!

Look on: http://service.sap.com/sap/support/notes/1938881

[Former Member · Accepted solution]

Many thanks Vadim and apologies for not mentioning the other environment was working.

I've checked the UJ0_PARAM_APP tables in all three clients and I can see that they all show 1332 as the length, but when I check the generated table for comments, then I can see that in the Development client it is 1332, but in QA and Production it is erroneously showing 255. So, many thanks for pointing me to the right notes (I think I probably didn't see this one as "length" is misspelled in the description of the note!).

So, my next question is about applying the fix. We can apply the note 1910379 correction to avoid future issues, but I'm concerned about doing a re-transport. If I transport just the Model (i.e. capture the Environment, but then exclude everything except this one Model) would that be enough to correct the generated table? And what would happen to my data in the Model - would it be OK?

Could I manually change the MAX_COMMENT_LENGTH of table UJ0_PARAM_APP (as suggested in note 1938881) to match what is in the generated table (i.e. 255) in my QA and Production clients and then change the length via the Web Front End again to fix it all without transports?

Many thanks once more.

John

[former_member186338 · Accepted solution]

"Could I manually change the MAX_COMMENT_LENGTH of table UJ0_PARAM_APP (as suggested in note 1938881) to match what is in the generated table (i.e. 255) in my QA and Production clients and then change the length via the Web Front End again to fix it all without transports?" - why not?

[Former Member · Accepted solution]

Vadim,

Just to update, this did work for me. It took me a while to realise that I could actually change the value directly in SE16, but once done the value was the same as in the generated table. Logging into the Web Front End I could see the value had changed down to 255 (as per my change). I then changed the value in the Web Front End and checked that it had updated both the UJ0_PARAM_APP table and the generated comment table, which it had and a quick test in an EPM sheet to save some text proved it was working beyond the 255 characters.

Many thanks.

John

[former_member186338 · Accepted solution]

It's better not to change values using SE16 You have Web Front End...

[Former Member · Accepted solution]

Agreed, but in this case it was the only way to fix it enough so that the Web Front End could be used again. All is good now!

[former_member186338]

Why not to search SAP notes? "bpc comments length"

http://service.sap.com/sap/support/notes/1617083

some manual changes has to be done!

Vadim