One purchase org to multible company codes

[Former Member]

Hi

I have a problem with my org. structure - hope someone can give me a hint.

I have build the structure as:

1. - Root node

1.1 - Company code 1

1.1.1 - Department 1

1.1.2 - Department 2

1.2 - Company code 2

1.2.1 - Department 1

1.2.2 - Department 2

1.3 - Company code 3

1.4 - Company code 4

1.5 - Company code n

1.9 - Purchasing org

I have my purchasing org assigned on 1.9, when I have one purchase org to all my company codes.

I has read some other treads which tells that the purchase org must be on the same level as the company code

If I do it in this way I will get a dump when I create a SC. If I maintain the purchasing org on root level this work fine but then I get the warning message "You may not create a company below a purchasing organization" in PPOMA_BBP

Do anyone have an good idea how to solve this.

Thanks in advance

[pvanhoove]

Hello,

Your structure as described should work, I allready test it

Even the restriction "You cannot create a company below a purch org" can be overpassed by deactiviting the error message in the standard code and this is working fine too.

Check again responsability on pruch group and attributes below companies. Multi company purch organization should work.

Rgds,

Pierre

[former_member293881]

Hi,

Refer OSS notes 1016292 and 1017211 for org structure definition.

Regards,

Rahul Mandale

[Former Member]

The 'Function' tab card in transaction PPOMA_BBP is used to define

companies, purchasing organizations, and purchasing groups in your

organizational plan. Furthermore it is used to map these units

onto corresponding identities in your backend system. This means,

the company code you're defining on the tab card 'Function'

represents the backend ID of that specific company node.

Talking about a single backend system, this mapping must be one to one:

A company corresponds to exactly one company code 'BUKRS' in the

backend system. It is not allowed to define a single 'BUKRS', 'EKORG',

or 'EKGRP' for several organizational units in your EBP system.

To facilitate cross company-code purchasing you have to use the

attribute 'company code' (BUK) on tab card 'Attributes' instead.

Explanation: The company code defined on tab card 'Function' is the

company code the regarding user belongs to, whereas the company code

defined as attribute BUK via tab card 'Attributes' is the company code

the user may use for purchasing. If no attribute BUK is defined,

the user only can use the company code he belongs to (i.e., which

is according to his 'native' assignment to his company).

Summary: Though a bit confusing, it was necessary to differentiate

between the following two meanings:

<i> The assignment of employees to a company, i.e. a company code.

This is done on the tab card 'Function'.

[ii] The set of company codes, which the users may use for purchasing.

In cases where it differs from <i> (e.g. cross-company

purchasing), one has to define it via the tab card 'Attributes'

and the attribute 'BUK'.

Generally, an EBP user must be is assigned to a company. The error

message BBP_CUST(004) is raised, when you miss to flag at least

one of the users parent nodes as a 'Company' on tab card 'Function'.

The error message BBP_CUST(004) has nothing to do with the company

code but with the fact that a company as such is missing.

[Former Member]

Can anyone help me, please.

Thanks in advance