Controlling Area

[Former Member]

Hi,

Iu2019m trying to create IT1008 record (through PO10) for an org. unit and when I enter a controlling area, Iu2019m getting an error that says controlling area XXXX already exists for org. XXXXXXXX. Is it true that one controlling area is only linked to one org. unit? Or am I missing something?

By the way, this works fine through PPOME. Why is the system behavior different?

Donnie

[christine_morin · Accepted solution]

Hi Donnie,

Let me explain further. Note 397571 is pointing out the cause of that error. It means that for release 4.6C and higher a controlling area can only be assigned to one Organizational unit (standard behaviour).

If you want assign a controlling area also if it is already assigned in the structure above you can remove X from PPOM INHIH (as per note 356186).

Regards

Christine

[Former Member · Accepted solution]

I'll take a look at the notes and the switch and would come back with my findings.

Thanks,

Donnie

[Former Member · Accepted solution]

We found the following to be aware of:

1.Controlling area linked to company code on top level org.unit

2. On next level, we enter a new Cost Center. This actually opens up the field 'Controlling area'. It will be linked to Cost Center if the user hits return/saves. However, often the user enters a value here (seing an input field). This has the following effect:

- An infotype 1008 is created for org.unit level 2 with the same cost Center as before.

- This infotype now has no Personnel area/subarea, as these are inherited from above.

- When hiring people into this org.unit, now PA/PSA is defaulted - because the system stops looking for these values as soon as it hits an infotype 1008.

3. We tried to correct this by actually saving the Controlling Area physically on top level. This creates the message you get. We then have to delete the 1008 records on lower units before entereing Controlling Area on top unit.

Kirsten

[Former Member · Accepted solution]

Hi Christine,

I'm back with my findings. So I removed the flags from PPOM INHIH and PPOM INHIC switches and I'm able to assign different cost objects on root and sub org. unit. However, I was wondering about the impact of removing the flags from those switches. Will it have any impact on FI/CO, dataloads etc.?

Thanks,

Donnie

[christine_morin]

Hello Donnie,

If enterprise organization is active in a controlling area, you can only maintain an organizational unitu2019s cost center and company code assignments in Controlling that is why you can only assign a controlling area to one organizational unit.

What I meant by upper org. unit is just the organizational above in the hierarchy (such as the root org. unit).

Hope it is helpful,

Christine

[Former Member]

Thanks again Christine. There is no org. unit above mine. I also checked the org. unit displayed in the error. That unit is also a random unit (not the root) and there is no relation between that and mine. What is PO10 looking at?

Donnie

[christine_morin]

Dear Donnie,

You can only assign a controlling area to one organizational unit. If you implement the Controlling component, you can find more information in SAP Library under Financials u2192 Controlling u2192 Controlling Methods u2192 Authorizations u2192 Enterprise Organization.

When you create a new Account Assignment for an Org. Unit, the inheritance is always ON from the upper relationship of Org. Unit. Entry ' ' (blank) in table T77S0 PPOM-INHS is not relevant in this case. And the difference between transaction PPOME and PO10 is that in PO10, the Account Assignment always respect the values of the upper Org. Unit.

Hope I could clarify your request,

Regards

Christine

[Former Member]

Thanks Christine. Actually, we have the PPOM INHS activated in our system so that positions inherit acc. assignment features off org. units.

Also, I did not quiet understood the upper org. part. I'm trying to create a brand new org and there is no org. unit above it.

p.s. What is the rationale behind the restriction for one controlling area per org. unit?

Donnie