Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
During our close we stop P&L postings on +2 in order to run all settlement processes that same night. After all settlements are completed, we do not want users to be able to post transactions to cost objects in CO (CC's, IO's, etc.) therefor needing to rerun allocations or settlements again. However, we continue with a variety of +3 & +4 postings to B/S accounts and below the line P&L accounts. (Cash, IC billings, Revals, Taxes).
My question is which line in OKP1 should be blocked in order to prevent users from posting journal entries that could hit CO cost objects on say +3 or +4? Would it simply be all the lines in OKP1? Is there a line in OKP1 that would block postings to only IO's, or NWA's as an example, or say any cost object that may be subjected to allocations?
Using OB52 is not an option for us right now since we are not using Auth groups AND we manage all co codes in OB52 singularly (over 150). So, blocking all the G&A accounts that are cost elements (over 150 times) isn't feasible.
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Popular White Papers
In the Spotlight   _.____.__ |
