OKP1 - Locking all fiscal years

[Former Member]

Greetings!

My company is using ECC 6 and we are managing our periods opening and closing via OB52 and OKP1 for FICO transactions.

Our issue is that all fiscal years (from 0001 to 9999) are opened in OKP1 - all transactions boxes are unchecked - except for past operational fiscal years and past periods of the current fiscal year - which we lock manually on an on going basis.

This is an issue because nothing prevent a user from executing a CO only transaction with an incorrect fiscal year: for instance 2113 instead of 2013 - even if the fiscal year is not opened in OB52.

Surely we do not have to manually lock all periods until 9999...

I tried to use customizing OKEQ or program RKCOOKP1 but the focus is only on one fiscal year AND the only fiscal years we can use within these are those which are active for version 0 of controlling area (for us, this means 1997 to 2015).

So, I have several questions:

- why on OKP1 we can enter any fiscal years up to 9999 if we have only defined relevant fiscal years for CO up to 2015? I tested for instance executing Results analysis calculation for fiscal year 2113 and it works. SAP write RA data against fiscal year 2113...

- How can I lock periods in OKP1 in mass, over a large range of fiscal years to make sure no end user will accidentally execute a CO program for an incorrect fiscal year?

Many thanks for your help!

Sylvain

[iklovski]

Hi,

That's a bit strange, as posting in CO should also be dependent on the version assignment to fiscal year. What is your setting in OKEQ transaction?

Regards,

Eli

[Former Member]

Hello,

We are using version 0 and for "Settings for each fiscal year", we have year 1997 to 2015 defined. None of them are locked - all of them are flagged for "Integrated planning" and "Copying allowed".

I do not see anything else that can be relevant for the issue here in terms of settings but if you have a particular setting in mind, I would be most grateful to hear from you!

Thanks,

Sylvain

[iklovski]

Hi,

Well, you can use a new tool for period lock (please, see note 1781268), which allows mass maintenance for OKP1. Still, it sounds strange that despite of having a version assigned to year, say 2113, you can create a CO document in this year.

Regards,

Eli

[Former Member]

Hello,

Thanks for your answer.

In fact,note 1781268 references program RKCOOKP1 which does not help as you can only run it fiscal year by fiscal year (and we have roughly 9990 to manage!).

"You use the program RKCOOKP1 so you can set period locks in the background. The program only permits you to enter a fiscal year and a version.
If you want to set several versions over several fiscal years, you must start the report N times.
This is not always feasible".

Based on your experience, what would you expect to see in OKP1?

When I enter fiscal year 2113, you would expect an error message considering that fiscal year is not defined for version 0?

Or you would expect to see all fiscal year locked by default?

Many thanks!

[Former Member]

Hello,

I am sorry I misinterpreted the content of the note! I got confused between the symtoms of the problem and the note itself!

(I would like to give you points but I cannot find the usual button...)

[iklovski]

So, does it answer your needs? If yes, just mark it as 'correct answer'. Otherwise, please get back.

[Former Member]

Hello,

Sorry for the delay in my answer. No, it did not help. The reason is that the program is only managing fiscal years defined in OKEQ (in our case up to 2015). It does not handle all "fiscal years" (up to 9999) despite the fact that these are "opened" in OKP1.

Note that Results analysis does not create CO documents per se. It just saves postings in a table. It is the subsequent CO settlement which creates postings (and, here, OB52 settings are taking over). 

I am really curious as to what the typical SAP settings are for OKP1.... Aren't you able to view OKP1 for say fiscal year 2113? Do you have an error message? Or, if you are able to view 2113, are all transactions locked in the OKP1 list?

Many thanks,

Sylvain

[iklovski]

Hello,

I do have a possibility to manage OKP1 in whatever year. What I cannot, as I mentioned before, is to post a CO document in a year, which is not assigned to an active version. If you do have this possibility, I'd check with OSS why it's happening.

Regards,

Eli

[Former Member]

ok. Interesting to know you too can "manage" OKP1 in whatever year.

Are you using results analysis? (not all companies are using this functionality - for instance Tcode KKAI or KKAK). I do not believe Results Analysis is posting anything. It feeds the settlement. It is the settlement which creates CO document. Look at table COSB if you have postings... perhaps you are not using RA...

If you do, I would be curious to know if you can (in test mode of course!) launch calculation for 2113... I never though of this possibility until one of our user accidentally ran it for that fiscal year... I find this very dangerous...

Thanks,

Sylvain

[iklovski]

No, I don't use RA, indeed... and the versions management corresponds only to CO postings, naturally.

Well, I can suggest several solutions:

a) Enter manually in table KAPS the blocking entries. I believe, RA activity is called 'KABG' in terms of business transaction.

b) Develop a solution which will be incorporated in the functions reading KAPS table, in a spirit of note 1697047

Regards,

Eli

[Former Member]

Hello,

Yes, I agree with you. Looks like we need to target the table directly. I will follow this up with our dev team.

Thank you very much for your help (again, I cannot find how to assign points!)

[former_member862468]

Hi Sylvain/Eli,

This is a good discussion, it helped me. I am also trying to understand how are the default settings configured. how is OKP1 defaulted to lock all periods or open all periods in the first place. is it configured some where. thank you.

Shriya

[Former Member]

Hello,

Glad you found this discussion interesting!

We had our developers developped a program to close all periods/transactions of all "non operational" CO fiscal years in OKP1. By launching this program in background, I was able to close all fiscal years.

I give you below some technical details that I supplied our developper.

Hope this helps!

Program SAPMKCSP is launched by Tcode OKP1 and updates the structure RKCSP. This program feeds table KAPS.

In table KAPS, each field PSPxxx refers to one period of the fiscal year selected in field "Fiscal year GJHAR". There are 16 periods per fiscal years.

The column "Business Transaction" refers to a type of transaction which can be locked or unlocked for a period depending on whether or not there is an "X" in a "period lock" column (16 columns corresponding to the 16 periods).

Whenever there is an "X" in the table KAPS, there is a tick mark in the corresponding intersection in OKP1, indicating that the period and the business transaction is locked.

[former_member862468]

Hi Sylvain,

Thank you for the detailed information. Also, do you know by default will the OKP1 periods be all open or closed. one of my business user told me that they used to have all the OKP1 periods closed previously for all years and they used to open only the required period. when i see now all periods in OKP1 are open. I mean even if i look at year 9999, all the periods are open however business user contradicts that they used to be all closed. I can use your solution to close all the years but I am trying to understand why it changed?

thanks for your help.

[Former Member]

Hello,

I do not know how it used to look in the past but logically, you would think that OKP1 should work the same way as OB52 i.e. everything is locked by default and you only unlock the periods you need to.

This is not the case...

(I am a functional guy so I do not know if technically, there was a reason for the change)...

Sylvain

[former_member862468]

Thanks Sylvain...appreciate your responses...yeah i thought the same but i read somewhere that since mostly CO document are the derivative documents that flow from other modules, it tends to be open for all the periods but i wanted to see if it is true or if there is any other reason.

Eli/Ajay, any reason that you could think of