VAT auto populating usage reg world public

[Former Member]

How can I change a logic to VAT (characteritics level ) to auto populate other usage rather than public:reg world ?

[christoph_bergemann]

Dear Krishna

this is really a very "basic" quesition and topic is (or should be really) well known.

a.) you can defined by VAT only "one" global default usage (check customizing)

b.) if you have prepared anything for a.) the user can "switch" per session to a different "default" usage. This "default usage" overwrites any thing as defined in system

C.B.

PS: during the write of usage to database the "access rights" of user are checked. So if user is not allowed to use this combination of rating and validity area no usage can be set up in the VAT

PPS: you can do the "same" on identifier level

[Former Member]

so If I want to add one more default rating , I can add in customizing ? Are you talking about usage customizing ?

[christoph_bergemann]

Dear Krishna

you need two steps. You first define "usage" you would like to use and then you can add this usage to a VAT (if  needed). Both actions are done in customizing

You can not define a "rating" alone

C.B.

[Former Member]

can we add two usage  while customizing VAT ( spro - hope you are referring to activity - create new vat in spro ) .Let me see if I see any place to put multiple usage there so that I get auto populate those usage in cg02 .

[christoph_bergemann]

Dear Kishna

as explained. you can define per VAT ONE ! default usage. But user can "overwrite" this (using functionality in CG02) and select his/her own usage to use. But User must pay attention. This decision is stored on user level. If user does not "switch" back the system can not use the "global" usage anymore (for this user !)

C.B.

[Ralph_P]

Hi Krishna,

you can only define one usage profile as standard for one VAT, but this profile can of course contain more than one validity area. Maybe that helps your case.

Ralph

[christoph_bergemann]

Dear Krishna

only small add on to what Ralph added. Using the SAP capabilities you can definea "default usage"

Here you can prepare the "usage" using lot of approaches. you can set up usage as:

PUBLIC REG_WORLD + STANDARD + REG_WORLD

You can set up as PUBLIC, DE + FR + ....

You are totally free. But not many combinations makese sense and honestly: most of the properties could  still use "PUBLIC/REG_WORLD".

Example: density:  why do you might need something different? for other properties it makes no sense to define a "useful" usage (e..g OEL). as you don't know. should the next record be of typ "PUBLIC, DE" or "PUBLIC, FR" or...

C.B.

PS: Once again usage can be at the same time:

PUBLIC DE+ STANDARD DE ++++ (so can can define "many" usage in one "usage profile"); but as mentioned. does not always make sense