CO validation according BUKRS

[Former Member]

Hi there. Could You tell me some tips how to validate CO in such scenario:

-

---

At this moment we've got 1 Controlling Area (Let's say CA1)

We've got 4 CoCodes (let's say CC1, CC2, CC3 and CC4)

The Controlling Area CA1 is common for all 4 CoCodes. That's an Cross-company-code cost accounting .

The problem is that Co Posting Periods are closed 'globally', for the whole Controlling Area CA1 ( = for all CoCodes assigned to CA1, that is CC1, CC2, CC3 and CC4).

I need to create transaction in which user could open/close Co Periods separately for each CoCode. So for example Period 1 can be closed for CC1, but it's opened for CC2 etc.

-

---

I know that I need to create a Z-table, which will keep info about periods closed. I think it's structure could be the same as KAPS ("CO Period Locks") table with BUKRS field added by me. Now I know I should use OKC7 Tcode. But what now?

Could You give me some tips about most suitable solution? I'm newbe in world of rules, callup-points and other validation components.

I'll be very thankful for help. Greetings.

[Former Member]

Piotr,

Use t-code GGB4 and do your validation.

Amit.

[Former Member]

Hi!

I'm not very familiar with CO, but you can close and open periods for each company code, using transaction OB52.

Check this out first, it might help you.

Regards

Tamá

[Former Member]

Amit

GGB4 will lead me to OKC7

Tamás Nyisztor

That's not sufficient because of internal CO documents posted in our company.

[Former Member]

Piotr,

yes will takes you to OKC7 now you can do your chages here.

Am not too familier with this issue that much only i can help you

Amit.

[Former Member]

Hello Piotr,

have you solved your problem? I have the same issue with our customer. Maybe you can give me some advice how to solve this issue with the periode locking on company code level.

Thanks in advance!

kind regards

Chris