on 06-09-2014 4:59 AM
Dear all,
We are having problems with our users in posting periods. Is there a way to trace who or what process has changed the posting periods? I know that we can check at the change log to see what has been changed. The problem is the system always showing the same user id who did the last changes while they claimed that they didn't do so. Only accounts and IT got the authority to change the posting periods.
Is there any other ways that we can get history of changes to posting period? We don't want our users to do back dated transactions while the period is opened accidentally by users.
Thanks and Regards,
Leng
Hi,
Try this query:
SELECT T0.[AbsEntry], T0.[Code], T0.[Name], T2.[U_NAME], T3.[U_NAME] FROM AFPR T0 left join OFPR T1 on T0.[AbsEntry] = T1.[AbsEntry] and t0.loginstanc = t1.loginstanc-1 left join OUSR T2 on t2.userid = t0.usersign2 left JOIN OUSR T3 ON T3.USERID = T0.usersign2 ORDER BY T0.[AbsEntry]
Thanks & Regards,
Nagarajan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Naga,
I have just tried the query and added UpdateDate to the query. The change log also serves the same function but is it possible that the change log is not accurate? Our users complaint that he/she is not the last user who amend the posting period while the change log show his/her user id as the last user who amended the period status.
Thanks,
Leng
Hi,
There are few cases reported to SAP related to change log issue. You may refer if you want from SAP Business one customer portal. ( 1508699 ,1996870 ,1778374 )
But I don't find any SAP note related to posting period.
Check with Access log for user login details for that particular user and compare with login date with updated date.
If this series issue, please raise ticket to SAP support.
Thanks & Regards,
Nagarajan
Hi,
You can refer AFPR table to check the user sign and updated date.
Also from change log , with show difference button you can check by whom and when the posting period updated.
Also you can restrict your user to do back dated entries by use of notifications.
IF (@object_type ='301'AND @transaction_type in (N'A', N'U') )
BEGIN
IF EXISTS (SELECT T0.TransId FROM JDT1 T0 where datediff(day,getdate(),T0.Refdate)<-7 and T0.[TransType] >=13 and T0.[TransType] <=67 and T0.TransId = @list_of_cols_val_tab_del AND T0.UserSign >=2)
BEGIN
Set @error =1
set @error_message = ' U Can not post back date entry more than 7 back day'
SELECT @error , @error_message
END
END
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No Leng,
It is not at all possible . Change Logs are always correct.
Its just that some else is using other's User ID and Passwords.
Its very common issue. Users used to give all these statements.
We need to authenticate the system more strongly..
You should put a notification/authorization on posting periods that no one else other than Manager or superuser would able to change it.
That's the only way , you would able to control it.
Thanks
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.