config for vendor account group which decides that purchasing view is required

[Former Member]

HI experts,

Do you know if there is any config for vendor account group which decides that purchasing view is required or company code view is required for specific vendor when used in purchase order?

e.g. when we use partner function CP and enter some vendor code against this Partner function, system gives error that ‘partner is not extended to purchasing org XXXX’.

How this message is controlled? For Contact person, just general data is sufficient from process point of view, but system is asking to maintain purchasing data as well.

[sairam_enugula]

Hi,

When you create vendor centrally using XK01 tcode you will be creating the vendor for purchase organization you can create PO. if you create vendor using FK01 you cannot use the vendor to create a PO.

partner functions can be controlled with account group and partner schema go through the nodes in below path

Materials Management - Purchasing - Partner Determination - Partner Roles - Define Permissible Partner Roles per Account Group

Materials Management - Purchasing - Partner Determination - Partner Settings in Purchasing Documents - Define Partner Schemas & Assign Partner Schemas to Document Types