on 08-04-2018 2:14 PM
We have four digit company codes and some companies have four ledgers assigned (2 in fiscal year and 2 in calendar year). I was thinking to have one posting period variant per company to manage all four ledgers using OB52. E.g if we want June 2018 open (fiscal year it will be period 8 while in calendar year it will be period 6).
so my first question is there a way to manage only one posting period variant and manage both fiscal and calendar year. I am reading through forums and seems like it is not possible. I would like to confirm this?
if the answer to above is no then is there a way the posting period variant can be more than 4 characters. I would like to name them four digit company code + a letter to identify fiscal year or calendar year. Since these are limited to four characters I am not getting a unique variant for each of the companies.
Hi Hassan,
It is standard SAP design that system will check the posting period for leading ledger only. System won't check the posting period for non-leading ledger.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi hassanmurad
I would NOT recommend to change the table field length, though technically you can using the Access key, but it would be a system modification.
Additionally, if you change the field length, you would have to look at the impact in all the programs and tables where this field would be used.
A better way would be to create a posting field variant using unique identifiers rather using the current four field length
Regards
Sanil Bhandari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Sanil,
That is what we ended up doing as we couldnt find any other solution to this - we have two posting period variants for each company now, one to manage fiscal periods and other to manage calendar periods. Interesting was to find when we post entries it only checks for fiscal period (lead ledger) and not the parallel ledger, however, when jobs are run specifically for ledger groups it does check accordingly but it did serve our purpose.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.