cancel
Showing results for 
Search instead for 
Did you mean: 

Label printing doubts.

former_member184739
Contributor
0 Kudos

Hello Experts,

     Can anyone suggest me what are the pros/cons of using printing labels via GLM vs Regular output types/programs based on SmartForms?

Thanks

Prabaharan.A

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Prabaharan,

If we want to discuss on this, lot of Pros and cons.

Pros -

1. Functional consultant can make the report template (wwi) without depending on ABAP.

2. No Transport request/work bench TR required for any change in the templates.

3. WWi templates part of master data, unique in environment.

4. you have a beautiful functionality (Import/export) in place to move the templates across.

5. For labels, testing is more important task than development. you have to do couple of testings. more helpful while dealing as masterdata (without depending on transport request).

6. wwi report templates are multi lingual. same template can be used in multiple languages. reduce the development time.

Cons -

1. WWi is a black box for new people/learners.

2. have to spend more time on learning the concept.

3. if the business have more no. of labels, then wwi reports would be beneficial. or else for small no.s you can use smart forms, etc., you can save more time, which you are spending on investigation/learnings on wwi reports.

4. to fetch some of the parameter symbols, you need to spend more time to build the function module to pull the values.

5. Bit technical/ logical, while dealing with windows word functionality.

6. Debugging would be main difficulty, if you come across with any issues.

7. If you have standard symbol in place to fetch the values that's fine. or else it consumes lot of time to fetch the value to template. need both technical and functional expertise. for ex- batch no.s from production.

8. Lot of errors related to wwi patch upgradation issues, when using first time. really it's challenge to deal with Basis/Administration and let them understand and get it solved.

you have a lot to discuss about the deifference. same time you have good/ user friendly functionality in place. If you are well familiar with wwi functionality........you can just ignore the cons.

Regards

kamal

former_member184739
Contributor
0 Kudos

Hello Kamal,

Thanks for such a valuable reply.Please find my insights and correct me if i am wrong.

1. Functional consultant can make the report template (wwi) without depending on ABAP.

I am a huge fan of ABAP(As i am an ABAP Developer ) and interested in developing it in ABAP.

2. No Transport request/work bench TR required for any change in the templates.

3. WWi templates part of master data, unique in environment.

4. you have a beautiful functionality (Import/export) in place to move the templates across.

5. For labels, testing is more important task than development. you have to do couple of testings. more helpful while dealing as masterdata (without depending on transport request).

The above points are really valuable like 'No Transport request' for any change in Template.

6.wwi report templates are multi lingual. same template can be used in multiple languages. reduce the development time.

Smartforms too can be made multi lingual.

1. Additionally as you mentioned smartforms saves time to develop and familiar to any ABAP developer .

2.Debugging is possible here.

3.One more disadvantage in WWI Templates is the Business user must log into SAP system and enter the necessary Transaction to do printing. But if we develop internet applications(Including mobile applications) using Webdynpro ABAP or BSP we can do printing directly from browser.

4.Also i can avoid cons you have listed.

Please feel free to correct me.

Thanks

prabaharan

christoph_bergemann
Active Contributor
0 Kudos

Dear Prabaharan

WWI is the EH&S technique to collect data form data base to be printed in a document. WWi will never be completely replaced within th next 5 tp 10 years by a different technique to be used in SAP EH&S

But there is a clear trend ot use AdobeForms (as Smartforms are "oldfashioned"). Examples of use of AdobeForms can be found in e.g. SAP Product and Reach Compüliance suite

Generally: WWI is based on microsoft Word. Whatever lyou you might be thinking of is therefoer supported (landscape, portrait, page site, etc. etc.)

For an "ABAPer" WWI is really no "nice" tool as you can not "debug" Regardinmg your other topic:

"One more disadvantage in WWI Templates is the Business user must log into SAP system and enter the necessary Transaction to do printing. But if we develop internet applications(Including mobile applications) using Webdynpro ABAP or BSP we can do printing directly from browser."

You can use WebDynpro etc. or BSP to get the report shown. The only "con" is: you need to have locally WWI installed (or at least you need a WWI gen. Farm). Only if beforehand e.g. pdf is generated (which is possible using WWI) you can directly retrieve pdf.

Years ago there has been a TechnIData solution to be used in Browser to display the WWI document.

Therefore in EH&S area Smartforms etc. is no alternative in comparison to WWI (as you need to "reprogram" the whole WWI logic which is shipped/distributed by SAP). There is only one exception:

SAP EH&S DG data is printed using "Smartforms" and similar techniques (because of SAP SD integration etc.)

One "major "benefit of using WWI: you get "reports" having versions etc. which might not be possible without problmes using Smartform. Furtheremore WWI is suported in ALE distribution (you can distribute WWI documents form one system to the othr using ALE).

Especially labels are of "special" kind and I have really no idea how to use SmartForms to print them.

E.g. take a look here regarding examples of labels:

http://www.kroschke.com/static/img/zoom/10601/0478_ksi.png

http://www.sdb.ch/images/Label.gif

http://www.brewes.de/bilder/produkt/popup/ottokraftstoff-etikett-fuer-behaelter-von-3l-50l-2515.jpg

http://www.brewes.de/bilder/produkt/popup/heizoel-etikettfuer-behaelter-von-3l-50l-2514.jpg

http://www.brewes.de/bilder/produkt/popup/aceton-etikett-fuer-behaelter-von-3l-50l-nach-ghs-2524f7.j...

http://ebsoft.de/sites/default/files/Labor/A6-EU.png

C.B.


Former Member
0 Kudos

Hi Prabaharan,

I feel it's not correct to debate and decide which one is good and which is bad.

both have their advantages and dis advantages too.

purely business demand plays a role, to choose.

even in EH&S stream lot of clients using Adobe forms/ smart forms, without touching wwi. when dealing with regulatory forms like IATA, IMDG, etc., as there is no additional business in immediate future.

for ex: I can say you have a standard business, there is no further extensions in reports and also you have less usage.........directly choosing ABAP forms option.

especially in chemical business, day to day life....lot of new regulations/laws are coming into picture. to comply to those regulations, process become more stringent.

chemical business also not stadard. introducing lot of new raw materials to minimise the cost as well as to comply the new regulations. if you compare to last 10 years and now, heavy metals usage (mercury, lead, etc.,) drastically minimised in production to comply to regulations.

when ever you have small formulation changes in proces, forms need to be changed.

and you aware of the business support how it works. for each small modifications/ changes client will be charged for ABAP development.

In production shop floor, lot of safety instructions and hazardous related labels printed for each batch. and most of them are replica's with minimal changes. If you are developing them in ABAP, those will be costing a lot.

If standard symbols available in system, end user can adopt them to report template and run their business without any technical (ABAP) dependency.

New clients are showing interest towards GLM, some of them were using different dot.net based solutions for their label requirements. for them managing that tool and interface with sap for data.......leading to cost.

finally i can say, GLM is not competitive towards ABAP functionality. purely cost perspective to client, if they have more business towards labels.

Regards

kamal

former_member184739
Contributor
0 Kudos

Hi Christo,

Hope you had a great christmas.

Can you explain more on this

1."You can use WebDynpro etc. or BSP to get the report shown. The only "con" is: you need to have locally WWI installed (or at least you need a WWI gen. Farm). Only if beforehand e.g. pdf is generated (which is possible using WWI) you can directly retrieve pdf."

Thanks

prabaharan

former_member184739
Contributor
0 Kudos

Hello Kamal,

Thanks for your thoughts.We can opt to WWI as it is user-friendly(AvoidsTechnical depedency).This 

  factor is really useful from end-user perspective.Thanks a lot

Prabaharan

christoph_bergemann
Active Contributor
0 Kudos

Dear Prabaharan

SAP GUI, BSP and WebDynpro are "user interfaces" only.

One example how to go on:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b85f25-d99f-2e10-b8a2-96e0b54cc...

or: http://www.consolut.com/en/s/sap-ides-access/d/s/doc/YP-RELNPLMWUI_702_RCP2_M

If you take a look in function group c12j of SAP EH&S you will find e.g. function modules like:

C12J_WWI_ADHOC_REPORT_SHOW

or

C12H_WWI_SHOW_DIRECT

and others. On the top function modules like:

C12H_WWI_DISPLAY_WEBGUI

exist (I have nether used this).

Therefore you can use WebDynpro or BSP as UI to "simulate" CG54/CG50 based on your needs.

First let's discuss "WWI" shortly. WWI is dedicated to create reports which will be stored in SAp database. Normally these reports are stored ass "WWI" documents direct in database( WWI is based on WinWord therefore "rtf" definition).

These reports can be displayed/used et.c in e.g. CG54/CG54 and CVD1 (report distribution).

Using WebDynpro etc. UI you can "recreate" CG54 screen logic (by using e.g the aforementioned function modules) to directly disply from Web the WWI report.

Many companies have the trend/need to e.g. make available e.g. Safety Data Sheets to their customer as "Pdf" files. Here by clever use of function modules etc.and with some enhancements you could get a pdf shown in WebDynpro or BSP. MOst of the companies use report distribution process to make available pdf files to e.g. portals (a number of threads in this forum are dealing with this process e.g. http://scn.sap.com/thread/1558114

C.B..

PS: may be check as well:

http://scn.sap.com/message/9629057

http://scn.sap.com/message/13474032

Answers (0)