Authorisable object for "Price List type" or "Customer group"

[Former Member]

Dear Colleagues of SD,

My organisation is seeking to further confine the usage of the price list type and / or the customer group by providing necessary authorisation, if possible.

Would any one of you be aware of any objects at that level? If yes, please do enlighten.

Thanks in advance.

Regards,

Tariq

[Former Member]

HAI

YOU CAN CREATE THE CUSTOMER GROUP FROM THE MENU PATH - SPRO - SD - MASTER DATA - CUSTOMERS - SALES - MAINTAIN RESERVE FIELDS IN CUSTOMER MASTER ,

AND FOR THE PRICE LIST TYPE - SPRO - SD - BASIC FUNCTIONS - PRICING - MAINTAIN PRICE RELEVANT MASTER DATA FIELD AND THEN CREATE NEW ONE

THEN ASSIGN THE PRICE LIST IN THE CUSTOMER MASTER ALONG WITH CUSTOMER GROUP FOR THAT PARTICULAR CUSTOMER MASTER DATA.

IF YOU REQUIRED ANY THING ELSE MEANS PLEASE CONTACT

[Former Member]

Hi,

I am not getting you exactly. I understood that you are trying to create pricing condition records based on price list type and customer group. For the pricing conditions, you need authorization to release. These pricing conditions will be available for creating sales order once they are released. If this is your requirement, you can achieve this by controlling the processing status in the condition records. With the help of an ABAPer this can be done.

Create processing status PS1, PS2 and PS3. The User1 will log on and enter the pricing condition and the he sets the processing status PS1. Now the release status is u2018Blockedu2019. The User2 will log and check the prices and approves the price by changing the processing status to PS2. Now the release status is u2018Blockedu2019. The User3 will log on and checks the prices and finally approves the price by changing the processing status to PS3. Now the release status is u2018Releasedu2019.

The link between processing status and release status will be made by the ABAPer by program.

Hope this will be useful to you.

Regards,

K Bharathi

[Former Member]

Hi,

Thanks for the reply but its not what you have suggested as the solution which i am seeking.

When I say "authorisation objecf" for these two I intend to authorise the "usage" of one or more of these in a sales order. Let me elaborate it a bit.

Supposing there are entries like P1, P2 & P3 for price list types and CA, CB & CC for customer groups. the prices are all on released status by the price administrator who has full access to it. It is the end user who i am concerned about who creates sales orders.

I want to limit enduser1 to price list type P1, P2 & CC such that in his orders he cannot select P3 & CA, or CB. While enduser2 to be confined to P3, CA & CB. and likewise for other users.

Am i expecting too much if i require the above?

Thanks in advance.

Tariq