cancel
Showing results for 
Search instead for 
Did you mean: 

CommonDistriChannel etc

Former Member
0 Kudos

Hi friends,

I would like to know the following:

a. We define Common Distri channels and Divisions by VOR1 and VOR2 so that we share the master data. Then why again OVAM, OVAN and OVAO is needed? What does these 3 t codes offer? When r they used?

Reply awaited.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

If you come across a need so that if you have different distribution channels and divisions, wherein you have to refer one distribution channel and division properties to be applicable to others also while executing sales documents, we have to use the above T.codes OVAM, OVAN, OVAO.

If we want all the sales document types can be allowed for all the distribution channels or divisions, we will not enter any value or input in the reference field.

Mohan

Award points if it adds information

Answers (3)

Answers (3)

Former Member
0 Kudos

These transaction codes mean :

<b>OVAN</b> - Assign Sales org/ div to Reference div

<b>OVAM</b> - Assign Sales org/ dch to Reference dch

<b>OVAO</b> - Assign Sales org to Reference Sales org.

Now what does this means?

Whenever you define a sales document for a particular organisation, then for subsequent division, dch or a sister sales organisation , you can use these T Codes to refer sales document data from any other sales org or the original sales org. for subsequent use. For eg:.

<b>Sales organization Reference sales org.</b>

<b>AB AB

BC AB

CD AB

EF EF</b>

Here S org BC and CD get documents with refernec to S org AB. But whereas AB and EF have there own definde sales document.

Thanks

Reward if helpful

Adi

Former Member
0 Kudos

If OVAM, OVAN and OVAO are not maintained, it will give an error to create an sales Order. Hence it is must that OVAM, OVAN and OVAO are maintained in configuration.

Regards,

Rajesh Banka

reazuddin_md
Active Contributor
0 Kudos

Hi Gavrav P,

As you said,

Defining common distribution channel and division is to share the master data i.e. Condition master data, Customer master data & Material master data.

Similarly,

we Combile the sales org', Dbt channel & Division to share all other sales areas which will be permitted to the document types.

eg: if you want to create Order in Sales area we need assign doc type OR to permitted sales area, as we all know.

(1000/10/01 is permitted to "OR" doc type,)

where as we have 50 sales areas which is permitted to doc type- OR,

will take 50 times to assign this sales areas to OR type,instead of this,

we make 1 sales area as reference and use all the sales areas within this Type.

*i hope it clears,

Rewards,