2024年3月28日发(作者：)

Note 105621 -

Note Language: English

Authorization check for the condition screen

Version: 15 Validity:

Valid from 12.02.2004

Summary

Symptom

Up to now you cannot exclude certain condition types and subtotal lines

from being processed or displayed in the condition screen by restricting

the authorizations.

More Terms

VH609

Cause and Prerequisites

This was not programmed.

Solution

A solution is only possible by means of a modification. Concerning the

maintenance responsibility, refer to Note 170183 and 381348. The following

text describes a solution option based on a modification. Inquiries and

problem messages concerning this subject are not covered by support but

only by Remote Consulting subject to costs.

By creating two additional authorization fields and a new authorization

object and by using user exits

o

o

o

o

USEREXIT_FIELD_MODIFICATION,

USEREXIT_FIELD_MODIFIC_LEER,

USEREXIT_FIELD_MODIFIC_KZWI, and

USEREXIT_FIELD_MODIFIC_KOPF

to display and manually change conditions and user exit

oUSEREXIT_PRICING_CHECK

to create new conditions, a solution is available which only allows

creation, manual change and display of those condition lines of a pricing

procedure for which the user has an authorization. For conditions and

subtotal lines for which the user has no authorization, only the condition

key and the description are dsplayed, all other fields are hidden.

Restrictions

consulting note contains an example of how the SAP authorization

concept can be used in pricing and which important points you have to

take into account. Everything that differs from this example belongs

to the consulting area.

You then have to assign access authorizations for every user for all

pricing procedures used and the level numbers used in these pricing

procedures. If you do not do this, the system no longer displays the

Page 1 of 7

2.

07.09.2007

Note 105621 -Authorization check for the condition screen

condition lines or no longer displays them in the same scope as you

need them for your work.

the change mode (for example VA02), the deletion of conditions or

the starting of a new pricing within this solution cannot be prevented

(the user exits required for this are missing).

If the creation of a condition is not allowed due to a missing

authorization, the system displays an error message which prevents

further processing. This line can only be eliminated by deletion.

On the empty condition lines, only the field for the condition key is

ready for input. The condition rate can be entered only after you

pressed ENTER and after a successful authorization check.

4.

5.

Procedure in detail

nance of authorization fields

a)If table ZAUTHCUST does not yet exist in your system, start

transaction SE11 as of Release 4.6A to create it.

In releases up to and including 4.5B, you can call Transaction SU20

as a direct access (then you must choose 'Customer' on the initial

screen), and the system generates the table becomes automatically

if it does not yet exist.

Then proceed as follows:

o

o

Choose 'Create'

Enter the following values:

-

-

Short text: 'Authorization fields'

Delivery class 'C' (Customizing table, maintenance only by

customer, no SAP import)

Development class: Use a user-defined development class (in the

following referred to as ZAUT).

-

oEnter the following variables:

-

-

-

ZKALSM with data element KALSM (or KALSM_D as of Release 4.0A)

ZSTUNR with data element STUNR

Select ZKALSM as a key field.

oMake the following entries under 'Technical settings':

-

-

Data class USER (customer data class)

Size category '0' (expected data records: 0 to 68,000)

07.09.2007Page 2 of 7