Read-Only Compositions

[Former Member]

Hi all!

Is it possible to set a Composition VAT as read-only? We will populate the Composition by running a rule but we don´t want the users to be able to edit it manually.

Thank you,

Eugenia

[christoph_bergemann]

Hello Eugenia

your question: Is it possible to set a Composition VAT as read-only?

Answer: clearly yes.

EH&S does have a number of access objecs. You can decide whether a user does have read or write acess to a value assignment (property); next you can use the usage of the VAT to decide if or if not the user should have read or write access.

Example: you can decide if the user can have read or write acess to "denisty". Next level is: if the user does have read or write access to "density" you can decide if the user should have read or write access to data record having e.g. usage PUBLIC/REG_WORLD.

Hope that helps

With best regards

C.B.

[Former Member]

Hi Cristoph!

We implemented that option at first but it doesn´t work because we need the user to run a rule that completes the Composition but the user shouldn´t be able to modify it.

If we set the authorization not to write the Composition, when the user runs the rule, we get an error because he is not able to write.

We would need the Composition to be written by a rule but read-only for the user that runs it.

If we define the VAT Composition as Internal use, users are not able to see it. The same thing happens if we hide the Composiiton tab.

We would need the Composition tab to behave as characteristics set as "not editable" in the VAT table-based. Characteristics can be completed by rules, but they can´t be modified by any user (just rules).

Thank you for your suggestion. Do you have any other idea?

Eugenia

[christoph_bergemann]

Hello Eugenia

now I understood better your demand. Potentially may be there is a solution. As you may be now there is the "Status" on Spec Header available which you be sued for several purposes. This could be an approach (I assume your are using the rules delivered by SAP (former Technidata)

1.) You should create an own secondary data user exit in cg02

2.) The user would use this exit as he/she would use any other one. The code will do like this:

Set the Status from "released" to "IN work" (ignoring that the user does not have the correct acess rights rto do that); then the rule set is executed and the result stored as a composition VAT; at least the rule switch the status from "In work" to "Released"

The user it self does not ! have the access right to "Status" (or can not change the Status). Now the Composition VAt is "blocked" as the user does not have the right to change something as long as the Status is not changed and this is not allowed because he/she do not have enough access rights

This approach should work.

These are the benefits:

Composition VAT can be created by the usrer using the rule set; but the VAt cannot be changed by user

This need ot be considered: (user can display the VAT)

This need to be considered:

If you are using the "rules" provided by SAP (TechnIData) You will not achieve the aim (in my opinion) and a I not sure if you can use these rules (and the ruel editor) in such a way that they ignore the "access rights" therefore your are "forced" to generate an "exit" (own code) by your own (with the whole logic of calculation etc:).

Next idea: the VAT is still cretaed by the rul set. But you change the value assigbment in suich a way that the comp tab is not visible. Now a further report etc. (many options) is used to populate a different property of type composition there the suer does nhave only display rights;

But I bleive you should not use this approach.

With best regards

C.B.

PS: you could use the same approach regarding properties with characteristers and you need not to use your "table approach" topic.

Edited by: Christoph Bergemann on Aug 13, 2011 5:31 PM

[Former Member]

Hi Christoph!

We would need to test the options of including code in the user exit. In addition to having to include a specific Usage for this Composition, we would need to add additional coding to avoid Authorization Objects that are also restricting modifications based on Usages as well.

As we are going live next September 12th and UAT has already started, we don´t have enough time to include more code.

What we finally did, was to hide the Composition (VAT SPRO configuration) but this isn´t really what we need because we are not going to be able to check if the values were populated correctly. This is a temporary solution.

Thank you for your help! I´ll let you know if we implement that code as an Enhancement after Go Live.

Eugenia

[christoph_bergemann]

Hello Eugenia

I believe in this situation you have a further option: now you have "hided" the tab but in reality the data is there. You can use output variant "EXCEL" and others to retireve the data. You must know that only by hiding the tab the rest of SAP EH&S is working "normal" that means as the data is really there (as a VAT) especially the outputvariants (and you can use e.g. WWI techniques as well to retrive the data) can be used to show the data (in my opinion)

Therefore the rule sets could be used as needed by you; the user can not change the result (because TAB is missing) and at the moment you can still control/check the data

With best regards

C.B.

Edited by: Christoph Bergemann on Aug 19, 2011 9:02 PM