Skip to Content
0

Layout for GLM is not saveable

Sep 22, 2017 at 11:52 AM

107

avatar image

Hi specialists,

For GLM we have a new template which contains more Information than usual.

We tried to import this template via CG34 in the next system. While trying to save the system reacts with the message DP 465 and the save process fails.

After correcting some customizing in out sandbox the error appears still. Detailled Debugging shows that the upload from the embedded word into the later DRAO structure creates an internal table with ca. 46000 lines. Unfortunately one object can only contain 9999 lines (Due to Limitation of DRAO-ZAEHL as NUMC/4 field). SAP recommends us to install KPRO to save the layout. Until now we never had any issues with layouts and for raw reports the compressing mode is activated hence no issues either. But this is not available for SBV documents.

I don't want to install KPRO for just one layout which doesn't work.

Does anybody have an idea how I can resolve this issue without installing KPRO?

Best regards,

Gernot

glm
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Gernot Ditten Sep 22, 2017 at 11:53 AM
0

Sorry, message id is D9 465 (typo error)

Share
10 |10000 characters needed characters left characters exceeded
Christoph Bergemann Sep 23, 2017 at 07:03 AM
0

Dear Gernot

check if you can "separate"/"Split" WWI layouts parts. As you might know. we can use now "Includes". That means:

You might have one "big" WWI layout. This laoyut has reference to a number of "includes". any include is a "seperate" SBV document

Second. Can you simplify your layout? we are now using GLM for such a long time: we never ever have seen a similar issue (same in other WWI areas)

C.B.

Share
10 |10000 characters needed characters left characters exceeded
Mark Pfister
Sep 27, 2017 at 06:42 AM
0

Hello Gernot,

I recently ran into the same issue - but for uploading a vendor MSDS as PDF. But I remember that this was the case for files being bigger than - I think it was 50 MBs.
For a WWI Layout that is quite a lot of data! Even all the EU SDS Chaperts together (Inlcuding the Annex) are only ~15MB.

Why is your WWI Templates so unusual big - do you have graphical elements logos on it as graphic?
Could you replace these graphics with phrases (that contain / link to the graphic)?

Kind Regards

Mark

Share
10 |10000 characters needed characters left characters exceeded
Ralph Paczkowski
Oct 04, 2017 at 01:37 PM
0

Hello Gernot,

can you simply distribute the template via ALE?

Ralph

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Dear Ralph

can we distribute a template via ALE? And if you: we do we use the "standard approach for downlaod upload? Thn ALE would be really simpler..

For a released report. yes we can use ALE

Can you explain please?

Thanks

C.B.

0
Gernot Ditten Oct 17, 2017 at 10:26 AM
0

Hello colleagues,

thank you for all the answers. I have been in Holidays thus I'm just replying now.

What I found out in the meantime is that the size is 3 MB as doc-file while growing to 115 MB when converted to a rtf which is the Format stored in SAP. We do not have any graphics on the layout but a lot of formatting.

@Mark: Our GLM Layouts are quite big concerning WWI coding because we use so-called language Switch logic. So we can print multi-language Labels in different languages with the same layout and often just one raw report depending on the input languages.

I have to ask the layouter from SAP. Maybe we have to include technic for this special Label as well.

@Ralph: I would have to discuss this as well with the SAP Consultant. But then we would have a static Label. I assume as we touch it and try to save Manual changes the issue would appear again.

I Keep you updated as soon as I have new Information.

Gernot

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Dear Gernot

we have never faced same issue. May be our lables "are simpler" (even I would define them as "complex").

For normal WWI layouts the "Include" techniques is always a choice. But labels are not that "simple" and there is a risk that (because of layout) you can not use "include"

What is surprising is the dramatic increas in filesize for "rtf" conversion. Hereyou may be should check with a "word"/RTF" specialist". I could imagine that by "simplifinig" font etc. topics you will succeed.

In any case. a OSS dialog might be helpful; may be there is the need to optimize WWI environment and may be SAP can improve so that the file sizeis reduced.

The "core" issue is a "word" issue. That means: using "doc" you can use "small" files. But rtf is ASCII based and there forebig

I am sorry. Only for released WWI reports you can use "Zip" variant. This is not possible in combination with layout

I would be interested regarding result of OSS dialog

C.B:

0
Gernot Ditten Oct 25, 2017 at 01:47 PM
0

I could copy component by component (partly form other layouts but having same coding) into another layout with textboxes and now I could save it. Now we have the guess that during the saving process in the original document the Settings for saving were

'Embed fonts in the file'

and this is the Problem.

I will try that for the original file.

Best regards,

Gernot

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Dear Gernot

i realy believe that the issue is generated by "Embed fonts in the file" tag. The story is high level as:

in rtf you will see reference to "font" information (this is the "normal" story). Therefore: normally WinWird will just handle that but if you use the "embed" tag i believe WinWord is forced to storw font data in "Rtf" file as well (so for any font you have use in rtf fiel you will get "font" data). Now you will get the same issue as with "jpg" etc. pictures. The size of rtf file must "explode" as rtffile is a strictly ASCII related text file Font and picture data must be stored therefore on "byte" level. And the clearly rtf file size will explode. I would be interested to get feedback whta has happened if you do not use this tag (still the same isssue). General experience is;: there are not so many chances to use "include" etchnique in "Label" layout, Only if you have "simple" structured lables you can use "Include" technique

C.B:

1

Hi Gernot Ditten ,

What I found out in the meantime is that the size is 3 MB as doc-file while growing to 115 MB when converted to a rtf

Like Christoph I think that has to do with the Fonts that are not supported by RTF.

I would propose to change the font in the *.DOC to a standard one (Ariel, Ariel UNICODE) and then try the RTF conversion and see what is happening...
Kind Regards
Mark

0