Blank Char Missing when text continues over 72 char on 4.6C

[Former Member]

Hi All,

We are on R/3 4.6C and have just applied support packs:

R/3 Pack 51

BASIS Pack 51

HR Pack A4

Since installing these packs, all of our Work Items and Emails generated from Workflow are concatenating strings and variable substitutions together.

This occurs when the content on a line is longer than 72 characters, the blank character between the two words, where a line continuation would occur, is removed.

I have attached some examples on:

http://mailman.mit.edu/pipermail/sap-wug/attachments/20060519/e511a9d9/OSSNote_849657No_space_betwee...

There is a SAP note for this problem for version 6.2 onwards (SAP Note number 849657) where the problem lies in function SWU_TEXTLINES_REPLACE.

SAP has advised us to modify the function with the fix from Note 849657:

*---

• Fix to note 849657: Depending on the value of the line format (tdformat)

• blanks need to be inserted resp. must not be inserted.

*---

IF h_subrc = 0.

IF i = 1 OR h_itf_text-tdformat = '=' OR h_itf_text-tdformat = '/=' " = /= Langzeile

OR h_itf_text-tdformat = '(' OR h_itf_text-tdformat = '/('. " ( /( Rohzeile

CONCATENATE value h_itf_text-tdline INTO value.

ELSE. " * Defaultabsatz / Neue Zeile /: Steuerkommando /* Kommentarzeile >x Fixzeile

CONCATENATE value h_itf_text-tdline INTO value

SEPARATED BY ' '.

ENDIF.

However, This did NOT WORK on our 4.6C System.

This also affects our help screens.

Is there anyone still on 4.6C with has the latest support packs applied that has this problem?

Have you been able to find a fix?

Please… Can anyone help?

Kind regards,

Tom

View attachment on SAP WUG post:

http://mailman.mit.edu/pipermail/sap-wug/2006-May/022569.html

http://mailman.mit.edu/pipermail/sap-wug/attachments/20060519/e511a9d9/OSSNote_849657No_space_betwee...

[Former Member · Accepted solution]

This must be support pack issue. better check with SAP for correction and suggession.

[Former Member]

We have submitted a SAP note on this issue back in April and SAP is currently working on a solution, but the suggestions that they have put forward has not helped so far.

I am wondering if there is anyone out there still on 4.6C (support pack 51) and experiencing the same problem? If so, were they able to fix it? and how?

I really do not want to go and modify all of the task body description because we have hundereds of them.

Cheers,

Tom