cancel
Showing results for 
Search instead for 
Did you mean: 

Editing Unauthorized location products in Demand Planning

Former Member
0 Kudos

Hi,

Scenario:

We have restricted access to planning data wherein a user belong to a particular location cannot edit data for a product belonging to some other location. This functionality works well in SNP, where if we select a product for a location that is not authorized for the user, we cannot move from display mode to edit in Interactive Planning. The icon does not change from pencil icon to the spectacle icon in interactive planning.

In DP however, when i load data for a characteristic restricted to a location for which the user has no authorization, and try to switch to edit mode from display mode, the planning book changes to edit mode ( icon changes from pencil to spectacle) and we are able to edit data. However due to authorizations, we cannot save the data though we can edit.

Query:

From above, can we make DP equivalent to SNP - Is it possible to disallow edit mode while loading data for a characteristic for an authorized location ( this DP location characteristic is 9ALOCNO). The intended result is the pencil icon during display mode does not change at all to the spectacle icon in edit mode.

Thanks for all your guidance.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

You can create Selection ID in demand planning as per Product Location combination & you can use this selection ID to restrict user in to unwanted product location combination.

Hope this will help you.

Regards

Sujay

Former Member
0 Kudos

Presuming you are on a newer version of SCM (4.1 or higher), the security concept for interactive planning (DP) uses the BI security concept. What you need to do in this situation is to create an authorization object (use tcode RSCEADMIN) and set the 00ACTVT variable equal to 03 and set 9ALOCNO equal to the plant you want and also include a colon (

This security concept is not the traditional role based authorization, it is new, it is good, it takes a little work to think the right way, but the logs are great and it is watertight once you get it in place.

let me know if you need more details.

Former Member
0 Kudos

Hello Dave,

Thanks for your reply. We are working on SCM 4.0 system. Would this apply for 4.0 as well? Why do SNP and DP behave differently? Was this differentiation achieved by standard means (that you cannot go into edit mode for SNP and can go for DP). Is there any influence of APO Authorization objects for this situation? Look forward to your response. Thanks!