How to out put graphics on pre-printed diamonds (Rhombus)in GLM labels

Dear Satya

i did not 100% get your question. I start with this:

"How can i print that ? if i use the graphic with out red borders in WWI graphic path it will effect my SDS out put."

this is the generally handling: You have a "graphic" which can be assigned e.g. to a phrase., If there is data in database and you have prepared properly WWI layout the graphic will be printed based on data.

I assume you are looking on this challenge. In SDS you would like to print the graphic with red border and in label with out using the same data.

I am sorry. my blog "WWI for experts is now "disrupted". and i am not sure if my GLM blog has a reference: but we have seen "similar" discussion in the past. In this case: person would like to have the "option" to "rotate" the graphic in one layout but not in the other.

Check this thread: https://archive.sap.com/discussions/thread/1400700

The "simplest" approach is: use two data records using two different phrases having link to the graphic with red border and without the red border. THis is the "easy" way to get a solution. But end user will not be happy (as now two data records are used)

The next option is: you need a "WWI" symbol (newsymbol) there you can check the generation variant used during WWI generation. If Report symbol is "SDS" related to can retrieve "Graphic with red border" and if it is "Label" related: you can retrieve Graphic with out red border" (check the discussion in "rotate graphic")

PS: looking on: https://help.sap.com/doc/erp2005_ehp_07/6.07/de-DE/97/cb2f51a6737062e10000000a44538d/frameset.htm (sorry german version)

you should invest more timein trying to understand GCG-HAZPIC and GCG-HAZBLA symbols. I believe this is clearly anoption (you can print then "white" (and not black) to get rid of "red border")

Dear Satya

you need to differentiate the "raw report" part and the "final report" part. So let us try step by step

1.) According to the SAP help (refer to my link) report symbol GCG-HAZPIC and GCG-HAZBLA are of type "parameter"; so you should may be check first: how does they work? How to use them properly in WWI?

2:) in context of: How can this FM switch the phrase in the Characteristic , Like we have to maintain another rating (LABEL1) for this in usage ? and the same Rating we have to maintain in generation variant also ?

This is option 1.) (very simple; stupid and straightforward)

You have a property with a "class based" structure and you have therein a phrase based characteristic

Now you create (fictive example) phrase "blue" and assign graphic file one (with red border); then you create a second phrase "blue" but you assign graphic file two (without red border)

I data base you could create VAT 1 with phrase "blue" (red border symbol) with usage "LABEL/REG_WORLD"

and VAT 2 with phrase "Blue" (no red border) with usage "STANDARD/REG_WORLD

The generation variant for SDS/MSDS generation will be defined different in comparison to generation variant of label (topic of used "ratings") and you will get the result you are looking for

This simple approach is "easy" for developper (no special WWI action; standard WWI architecture); straight forward set up of generation variant etc.

The "negative" part is: you must create two data records with content "Blue" (which is in most cases not accepted by the end user etc.)

Then we have option 2.) which uses the "generation variant" as an input to "change" the graphic file to print. Because of legal reasons I can not share the approach to go on like that; but this is an option

Option 3 might be:

You generate a new characteristic in the "property" having the value "MSDS" or "Label"; by using clever WWI techniques (and some methods) you could try as:

IF the new characteristic contain value "MSDS" then use graphic file with red border; if Label: use graphic file without border.

This option has the "pro" that you need only one "VAT" with phrase blue (but logic is than in WWI layout)

These are potential options. You should always (if possible) use the "simplest" approach (for developer and end user)

By clever use of transaction "CG02" this is option 1.

Hope this helps