on 02-16-2015 6:46 AM
Dear Experts,
On month end closing we keep SAP Production client closed for all the users irrespective of the domain where there are working in (Logistics , Finance)
.There are many logistics users which execute certain business transactions which posts accounting documents. I want to know is it right practice to close all the users during finance month end closing ro there is other way round which we can apply to process our business in SAP with our disrupting finance.
Thanks & Regards
Saurabh
Hi Saurabh,
Please refer the following SAP Help content:
Authorization Group
The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.
Use
A posting period can be made available to only a limited set of users using the authorization group.
Procedure
If only a limited set of users is to be able to post in a particular posting period, proceed as follows:
Add the posting period authorization (authorization object F_BKPF_BUP) to the authorizations of the selected users. Assign an authorization group (e.g. '0001').
Enter the account type '+' for the posting period variant to which the restriction is to apply. Enter the period(s) whose use is to be restricted in the first period, those which are available to all users in the second period, and the authorization group (e.g. '0001') in the last column.
Examples
A posting period can be successively restricted. If, e.g. 10 users have the posting period authorization with authorization group '0001', and 3 of these 10 users also with authorization group '0002'.
If the period is only to be accessible to the 10 selected users the authorization group '0001' is entered in the posting period variant. Access can later be restricted to the remaining 3 users by entering '0002'.
Regards,
Umamageshwaran.S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Saurabh,
As suggested earlier by expert. Financial closure is very crucial process during the MEC/QEC/YEC. So you need to take proper precaution, also it will effect the Management accounting. As the financial closure will lead to the report to the Statutory body too.
Best practice :-
1. Create a exception list for the user who will not be get effected by this activity.
2. Assign the validation rule to the User - involved in activity.
3. This can also be achieved by creating a batch job (SM36 or SM37).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saurabh,
One approach you can consider is creating a set for certain users to have exception. Then create a validation rule against this set so that they will the be the only one allowed to post.
Hope this helps.
Jayj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saurabh,
At the month end closing no need to close production server. Instead you can create a authorization object who will do month end activity and keep open periods for that object in OB52 and for remaining users close the previous period and open only current period. Then users will do there routine activity, if they try to post in previous periods, system will not allow them.
Regards,
Mukthar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ahamed,
In my current client, they consider month end closing from mid of the month (for Feb month they finalized the date as 16th Feb) because the payroll in run on 14th every month and if there are any discrepancy then they post it coming days of the month.
In this situation, what should be the work around .
Regards
Saurabh
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
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.