BPS STS Authorization for Approval Button on HTML STS Page

[Former Member]

Hi,

I need help. I'm almost desperated.

How can I authorize to inactivate the Approval button for STS User.

The start page of our STS planning is the overview page with a list of links with all units to plan.

(The planer user sees all Links and is able to click of the details Links of all units. But on the second STS Page the user can start with the Button OPEN PLANNING the layout. The authorization check, if the user is allowed to plan the data is be done in the layout itself. So if the user has no authorization to see or plan unit B, he wouldn't get the layout.)

Therefore the user need to have rights for R_STS_SUP (because of the STS Start page).

Now my question: How can I authorize the Buttons (Set for processing, Send for Approval, Approve) on the Second STS Page? User planer are able to approve their own plan and that is not good ;o)

If that not works. How can I start with the 2. STS page to start planning? So that the User which is only allowed to plan Unit C, get the second Page of STS and the UNIT C is already set.

Or how can I reduce the 1. STS page only to the units the user is able to plan.

So please help me ;o)

[Former Member · Accepted solution]

Hello Marlen,

first does the question have to be permitted, why each user on authorization-object R_STS_SUP is entitled? This authorization-object is reserved by definition only the user, which acts as a “super-user“. This authorization-object permits both the entrance into the spreading tracking-view (with you as “1st page” mentioned) and the extensive functions like approving.

Take a look an the SAP library:

Authorization for special access Status and Tracking System (R_STS_SUP)

"This authorization object provides the assigned users with the status of a superuser in relation to the Status and Tracking System. The object enables changing access to all plan data, independent of whether and where a user of the cost center hierarchy it is based on is assigned. The authorization object is intended for members of a staff controller group, who are not part of the line organization of the company, but who nevertheless must be able to intervene in the planning process."

The “normal final-users“ in the STS is entitled usually only on the authorization-object R_STS_PT, that is permitted the entrance into the detail view (with you as “2nd page” mentioned) and the permission function to beyond that exclude should.

Furthermore the usual bi-authorizations pull with the call of the WebInterfaces, if in the InfoCubes which are under the relevant planning-areas the authorization-objects were defined (for example accounting area, sales organization), so that a user only entitled units see it and / or. to call should.

Maybe try first to permit the final-users only for the authorization-objects R_STS_PT and not additional for R_STS_SUP and have a look. Or did you already tried this way?

Regards

Daniel Eiduzzis

[Former Member]

Hi Every one,

Can you please help me with this:

When I click Save Button after I finish the comment edit in STS, I got error says

Business Server Page (BSP) error.

Message E SBDS 106 cannot be processed in plugin mode HTTPS

I tried to search the oss note regarding to this error, but couldn't find any thing. Can any one please suggest what is the issue?

Thanks

Edited by: BarretteZhong on Oct 27, 2010 4:45 PM

[Former Member]

Hi Danial, Marlen,

I have encountered the similar issue on the second page of the status and tracking system. I have all the button disabled (can not be click to the next sequence). I have both the R_STS_SUP and R_STS_PT in my profile. Can you please give me some clue on how can I set the button as executable?

Thanks!

Barrette Zhong

[Former Member]

As mentioned above. R_STS_SUP should only be assigned to 'super-users', who need to have an overviiew of the whole planning organisation. In this case, the buttons can be enabled using the 'Edit' button from the details page.

Most users should only have R_STS_PT, and be assigned to specific organisational entities in the STS customising. In which case the required buttons should be enabled (unless the entity is lock, e.g. by another user).

Stephen