Restrict language in which a MSDS report can be generated

[Former Member]

Dear All,

we want to restrict the languages in which a MSDS report can be created in CG02. Means that we do not want that the users can change the report language in CG02.

Example:

The language in the generation variant is maintained as ZH (Chinese) and this should be the only language for which a report with this generation variant can be generated. In CG02 while generating a report the language can be overwritten so that for example a MSDS in German can be generated.

Do you have any idea how to restrict this? Is there any existing authorization object, etc. we can use?

Cheers,

Kathrina

[Former Member · Accepted solution]

Hi all,

do you have a unique template for China which is different from the German one ?

If so, I believe there should be a way to restrict the language possible for a country by 'playing' with following customizing:

    EH&S

        Product Safety

            Report Shipping

                Basic setting for shipping from SD documents

                    Assign Language and Lead Time to Country

                    (table TCGRL)

    EH&S

        Product Safety

            Report Shipping

                Basic setting for shipping from SD documents                   

                    Specifiy Condition Schemas for Report Generation Variant Selection

                         Condition Schema: Edit Table 4

                         (table TCGR4)

Hope this helps,

Have a pleasant day,

         François

[christoph_bergemann · Accepted solution]

Dear Kathrina

the proposals of Francois will help to deal how report shipment is acting and which released report is shipped to the customer. Using the other condition tables you can be more specific. Therefore if user would generate e.g. MSDS_DE/DE and MSDS_DE/ZH only the "DE" version is shipped to the customer. In most cases there exists differencies between legislation of country. I clearly assume that nobody will try to use a REACH MSDS to bring it to a chinese customer (and the effort in manipulating the document is very high (in this case))

Therefore  it is a common solution to define which type of document (generation variant, langauge etc.) will be send by the system using the report shipment. It is an option as in most cases it takes "time" etc. to manipulate the document it self.

We need to differentiate between

"Report from template" and "Create report". In both case the user can create a document and "manipulate "it (locally). May be an idea could be (nether have invested here) to try to introduce a "passcode" in WWI document, so that after opening the document in WWI the user can only use "Edit" or whatsoever technique to "manipulate "the template by using the passcode. In any case. if you are "technically experienced" there are number of techniques availabe to "manipulate" the document.

C.B.

[christoph_bergemann]

Dear Katharina

regarding:

"the language in the generation variant is maintained as ZH (Chinese) "

Only by using some "special" WWI logic you can do that in combination with generation variant. Therefore on level of generation variant your demand can not be fulfilled as you can not hinder the generation of a WWI report in language "ZH". You need to understand, that we are talking about two types of languages.

If you later generate a WW report you define a language (e.g. MSDS_EU in EN). The released report get the language "EN" assigned. The content of the WWI report can be "in theory" different. This functionality is used only in context of labels. Here you need the chance to print one legal text in many languages on a document

Regarding:

Do you have any idea how to restrict this? Is there any existing authorization object, etc. we can use?

a.) no authorization object is existing in EH&S standard

b.) SAP standard is not providing a corresponding functionality

But there are some options which you could analyze. Personally I believe the effort is not worth the result.

In any case:

1.) You can change the authorization concept in such a way that nobody is allowed to use" Create report"

2.) You prepare an Userexit which "nearly" provides the same functionality (create report). Here you can prepare "screen" which might help to hinder somebody to generate the report in the "wrong" language; or you can try to "implement" further authorization objects etc.

Let us come to the "basic" question: what will happen if the user is using the "wrong" language? "Nothing" (only a report is created to much) and may be the system will not find the raw report which need to be used in MSDS distribution process (in this case user will get a report request in cg50)

So in 95% of the cases: simple training of the topic is much cheaper as to try to invest money to get a solution

With best regards

C.B.

[Former Member]

Hi Christoph,

thanks for your reply.

The background of the question is that the German departement wants to prevent that the Chinese departement can create MSDS reports in German or English, save them locally, modify them or whatever....so they wanted to restrict it so that the Chinese departement can only access/work with their Chinese MSDS....

So training is not the real solution for that requirement. 🙂 So we will see if we go to implement some customer coding or if the German departement has to live with it.

Cheers,

Kathrina

[christoph_bergemann]

Hello Kathrina

in WWI process by using I believe the "dot" (wwi dot file) or the "ini" file (wwi ini) you can "prevent" on some level changes in the document. But it is "clear": if you are a person with high technical background this will not help.

We have two processes: "report from template" and "create report"; both behave the same in the context of your requirement.

Tricky now is that I belive there is no "authorization object" availble to pervent the use of "report from template". You can only hinder somebody to create a report (because further access objects are availble).

Therefore I am sorry: the compentence center has to live with the situation. It is clear that on the "high" level the chinese people will get a "legal" problem if they change the content. In any case:

As you may be now: you can create MSDS and Label. And Content of label abnd MSDS should be "the same" (regarding substance data).

With best regards

C.B.

PS: you should take into account (may be) that you can define different layouts per region (one europe and one for china).

Now in the "create report" process you can prepare the access rights in such a way that the chinese people can not generate a european one and vice versa