Mail notification up on unintentional changes to posting periods (OB52)
Posting periods are used to control the postings done in a company code at any given point. Posting periods are defined in posting period variant and posting period variant is assigned to company code.
In regular production scenario, only one posting period is open at any point in time (Except during month end closing time where 2 period are open to handle MEC activities). This helps to restrict backdated postings in the periods for which, month end reporting has already been completed. However, there is no technical restriction/notification mechanism in the system while opening the previous periods.
Below technique can be implemented to notify Finance team/people who are required to be informed about unintentional changes to posting periods when ever already closed previous periods are opened by some one. This can’t be controlled by authorization as we do need OB52 access for some users to handle MEC. But below solution ensures that, this access can’t be exploited by users.
Current period information is stored in table table T001B and can be maintained using maintenance view V_T001B. Mail notification functionality can be implemented by using table maintenance events.
There are many table maintenance events provided by SAP which are triggered at different point in times. In this case, event 02 (After saving the data in the database) can be used. ABAP coding can be done under this event to send the e-mail notification with required details like company code, period changes, to which account type(D,K,S,A,M,+) this change was done, user who is doing this change, date and time of change etc. to finance team. Respective team can validate if this change is done with proper approvals or not. This solution helps especially when document posting and MEC activities are outsourced to some other vendor.
I am not explaining about the coding part for sending e-mail here as there are so many articles already published on how to send mail from SAP. Additional checks can be placed in coding based on business requirements.
Your valuable comments are most welcome
Best regards,
Vinod Vemuru.
Very useful document.
Thanks for sharing
Regards
Sanil Bhandari
Valuable Info...Many Thanks.
Best Regards,
Naresh K.
Hi,
Good documentation. Thanks for sharing the same.
Regards
Singaiah Pathuri(singh)
Hi Vinod,
Helpful document shared. Thanks for sharing.
Srinu.
Thanks all for reading this document 🙂
Hi Vinod
Really its useful...thanks for sharing...
Regards
Sampat
Thanks Sampat 🙂
Dear Vinod,
It is very useful.
Also suggest how to find log / change record of OB52.
Regards,
L.Ananthakrishnan
Hi krishanan,
After adding the table maintenance event, you can Loop the internal table EXTRACT and check the field ACTION content. This has value U for all changed records. So, we can pick up the changed records like this.
If you are asking in general, change logs can be checked through t-code SCU3 for the table T001B.
Thanks,
V V
Hi Vinod,
Thanks for your suggestion.
Regards,
L.Ananthakrishnan
Hello Vinod,
Very informative and thanks for sharing such a useful document 🙂
Regards,
Lakshmi S
Thanks Lakshmi 🙂
Hello Mr. Vinod,
Great job....thanks for sharing.
Kind Regards,
kalim
Thanks Kalim 🙂
Wonderful document, I did address this kind of requirement in different way... But, I now know the best way.
Thanks for sharing.
Regards,
Narin Kamuni
Thanks Narin.
Could you share the solution which you implemented? I guess you created a custom program to check change logs 😉 ???
Absolutely right.... it was on logs and we have scheduled it to check the log every day and trigger emails...
Regards,
Narin Kamuni
Good guess 😆
With this solution, it would be a real time update. As soon as the period is changed, concerned parties are informed immediately to prevent any accidental postings.
Thanks,
V V
Thanks Vinod for sharing this.. Very useful information for Finance.
Regards,
Kavita
Thanks Kavita 🙂
Hi Vinod,
Very useful and Helpful document.
Regards
Arvind Leo Pereira
Hi,
Thanks for the document seems a very good way to notify for posting periods. But I am facing an issue . Whenever i try to create a table maintenance for V_T001B it asks for access key. Also on going to Environment->Modification->Events for V_T001B it does not allow to add any FORM routines for any events.
Has any one faced this issue? Your help will be much appreciated.
Thanks
Azhar
Hello,
Access key is required for even ztable events. Your BASIS team can help here.
Are you getting any error while adding the form routines?
Thanks,
V V
Hello Vinod,
Good document.
Thanks,
Neha
Thanks Neha 🙂
Wonderful document. Thanks a lot. Good job Vinod
Thanks Sam 🙂
Hi
A very useful article. Thanks
Regards,
Saurabh
Thanks Saurabh 🙂
EVENTS IN TABLE MAINTENANCE - ABAP 开发 (ABAP Development) - SCN Wiki
haha....I posted a week earlier 😛 Though concept is same, idea is different.
Both useful,
Thank you.
HI Vinod,
Very helpful information...Thank you.
Regards,
Rasheed
Hi,
Useful information but I have clarification whether this is applicable for opening of all account types + or even for single account type such as A, K or V?
Thanks
Gayani
Hello,
We can restrict the account types in coding. Say, If you want to trigger mail only for customer and vendor period opening changes, then before mailing, place a check to see for which account type (D&K) period is being changed.
Thanks,
V V
Thanks Rasheed, Gayani, Melin 🙂
Very Good Information. Thanks for detailed info.
Br,
Iqbal
Thank you for this added value,
i have one question if you choose a special posting period variant, no event is triggered. As a result there won't be a mail notification.
Is there a solution to this error?
your prompt response would be highly appreciated,