FB02 Authorization Issue

[Former Member]

Hi ,

Is it possible in SAP to allow the users to change the document on the assignment field, text field, reference field & the document header field etc but NOT allow the users to change the blind date field through FB02 ?

Please Help.

Regards,

Kakali

[Former Member]

Hi,

Check what authorization object is checked to change the "blind date field" through authorization trace in ST01.

Restrict authorization accordingly.

Regards,

Sandip

[Former Member]

Hi,

To know whether SAP provides restriction on certain field, we can first check whether there is an authorizaiton field exists for those fields. Please check the filed name (document number - BELNR) with the entries available in SU20. if this field doesn;t exist means SAP doesn't provide any checks or restrictions for that specific filed. In such cases you need to develop your own auhtorization objects and include them in the respective programs (Modify source code).

Regards,

Gowrinadh

[Former Member]

Pardon my ignorance, but what is a "blind date field"?

If you are refering to the "valuta datum" then you control this via the permitted posting periods => transaction OB52 etc.

Cheers,

Julius

[Former Member]

I think he is referring to Base Line Date when he says "blind date"

we had a similar requirement, which we addressed using custom coding and custom authorization objects.

I beleive you cannot control this with standard authorization objects.

[Former Member]

>

> we had a similar requirement, which we addressed using custom coding and custom authorization objects. 
> I beleive you cannot control this with standard authorization objects.

There are some other options depending on the situation.

An alternative would be to create a transaction variant which hides the screen or sets it to display only. This transaction variant is assigned to a custom tcode and users can use that itself.

Pro's - very quick to create, no change to standard SAP

Con's - you need an extra transaction

On the balance of it, I would probably choose your approach in this situation.

[Former Member]

there's a lot of configuration possible in FI. you can define the screen in a way you need with transactions:

O7Z2

O7Z1

O7V1

in addition there are rules that can be defined, screen variants (O7E6) - all of which i would try before i visit SHD0.

[Former Member]

>

> in addition there are rules that can be defined, screen variants (O7E6) - all of which i would try before i visit SHD0.

That's a good point. Personally I would take a variant transaction over using a PID to control the input screen for the "disallowed" users.

[Former Member]

Hello,

I would prefer to go with Alex,instead of making changes in IMG, that will changes screen for all he user,this requirement would be for few users only, i would go with Alex..

Thanks,

Prasant k Paichha

[Former Member]

> that will changes screen for all he user

This should be given preference in my opinion, so that there is consistent system behaviour.

The OP does not mention wanting users to have different behaviour even although their access seems the same.

Cheers,

Julius

[Former Member]

Hello,

1. Design of the tcode is based on the tcode's program which you can check in se93.If in program edit is not specified for blind date then you cannot edit if you need to modify the blind date then you need to change the program.

2. Or you can enble trace st01 and check which auth object is getting checked when you update blind date, according to that you can change the auth object.

Hope this clarifies.

Thanks

[Former Member]

>

> 1. Design of the tcode is based on the tcode's program which you can check in se93.If in program edit is not specified for blind date then you cannot edit if you need to modify the blind date then you need to change the program.
> 

Hi Shweta,

That is not correct, as both Mylene & I have given potential alternatives to changing standard program code depending on the exact requirement