Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Bill-to Party address change restriction

Former Member
0 Kudos

Dear All,

I am trying to restrict a few users from changing the Bill-to Party address in VA02... any thoughts on how this can be done ?

Navigation:

VA02 - Header Details - Partners Tab (Bill-to Party) Address

Regards,

Nick

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Nick,

A google search for this issue reveals the following from SAP SD forums:

http://sapsdforum.com/2007/09/19/how-to-refrain-users-from-changing-some-fields-in-t-code-va02/

Q:How to restrict users for not changing some fields in T-code va02?

A:There are two ways to do this:

- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.

- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).

The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.

Hope this helps,

Tom

3 REPLIES 3

Former Member
0 Kudos

Please help...I am new to SAP software

Thanks

Nick

Former Member
0 Kudos

Hi Nick,

A google search for this issue reveals the following from SAP SD forums:

http://sapsdforum.com/2007/09/19/how-to-refrain-users-from-changing-some-fields-in-t-code-va02/

Q:How to restrict users for not changing some fields in T-code va02?

A:There are two ways to do this:

- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.

- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).

The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.

Hope this helps,

Tom

0 Kudos

Before the transaction variants are created, i would first question the need of this. Each Sold-to can have 1 or more than 1 Bill-to, isnt it? do you want to restrict only for one customer or is it for all bill-to party's for all customers?

I dont know the set up out there, but there are couple of things you could pobably do. Please test it before you implement it.

Go to SU24, switch the prposed value for VA01, VA02 for the object V_KNA1_BRG from NO to YES.

check in the sales order program if this object vaue is checked.

in the authorizations for sales orders, when you re-generate the role and merge it with new data, the object V_KNA1_BRG would get called, maintain the account groups you want to allow 01 and 02 actviteis on sold-to-ship-to........

create a seperate authorization for display (activity 03) for the Bill-To

If this doesnt fit your need, please follow the transactio variant option suggested