cancel
Showing results for 
Search instead for 
Did you mean: 

How to hide SLED in deliveries?

prabakaran_gurusamy2
Active Participant
0 Kudos

Dear Experts,

is it possible to make display only for DOM and DOE(Date of expire) in delivery items?

Thanks and Regards,

Prabakaran Gurusamy

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello Prabakaran,

Suggesting you,

Check for VL02N any field modification user exit is available like sales order field modification(mv45afzz program) so that you can make those fields display only(grey out) through coding or u can try with transaction variant SHD0. These could help you.

Thanks,

Prabhu. 

JL23
Active Contributor
0 Kudos

Prabhu Dhamodaran,

why are you considering own developments if it is a SAP bug which can be fixed with implementing the OSS note? Where is the benefit in doing so?

Former Member
0 Kudos

yes agreed

Former Member
0 Kudos

Disable that field  in the  role which is assigned to that transaction  ( take help of basis)

JL23
Active Contributor
0 Kudos

Arunkumar Sugumar, can you explain in more detail, authorization is usually not on field level, maybe you have something else in mind which could not yet be understood

Former Member
0 Kudos

general different users will be given different authorizations based on their role in the orgn.

We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.

USe SUIM and SU21 T codes for this.

Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.

If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.

This means you have to allocate an authorization object in the definition of the transaction.

For example:

program an AUTHORITY-CHECK.

AUTHORITY-CHECK OBJECT <authorization object>

ID <authority field 1> FIELD <field value 1>.

ID <authority field 2> FIELD <field value 2>.

...

ID <authority-field n> FIELD <field value n>.

The OBJECT parameter specifies the authorization object.

The ID parameter specifies an authorization field (in the authorization object).

The FIELD parameter specifies a value for the authorization field.

The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.

To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.

Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.

You program the authorization check using the ABAP statement AUTHORITY-CHECK.

AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'

ID 'ACTVT' FIELD '02'

ID 'CUSTTYPE' FIELD 'B'.

IF SY-SUBRC <> 0.

MESSAGE E...

ENDIF.

'S_TRVL_BKS' is a auth. object

ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.

The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.

This Authorization concept is somewhat linked with BASIS people.

As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.

Take the help of the basis Guy and create and use.

JL23
Active Contributor
0 Kudos

All fine for an own development, but VL02N is a standard transaction. Do you recommend to to change the standard to implement your own customized authorization checks?

Do you think that this is the appropriate reaction to a problem that has already an OSS note for a fix?

prabakaran_gurusamy2
Active Participant
0 Kudos

Dear Experts,

I mean that we have date of manufacturing and date of expiry in delivery. some time warehouse user changing that, is there any way to make these fields display only?

Thanks and Regards,

Prabakaran Gurusamy

JL23
Active Contributor
0 Kudos

have you ever asked why they are changing it, or is this just  a bad behavior that the user change anything what is open to change in a screen.

Our 40000+ users around the world are probably the laziest users ever as they really only touch the minimum.

Implement OSS note 1487990 - SLED/BBD changeable in VL02N although defined in Batch

After this it will not be possible to update the field

Lakshmipathi
Active Contributor
0 Kudos
have you ever asked why they are changing it,

May be they are trying to learn SAP by doing some unwanted action and see how system is behaving

G. Lakshmipathi