on 06-21-2012 2:13 PM
Hello,
I have real strange problem with XD02 transaction. I will try to explain it using simple example.
One month ago, user 1 (with role A) and user 2 (with role B) had enter data in transaction XD02 and could save it without any problems.
Before three days ago, user 1 (with role A) can save data entered in transaction XD02 but user 2 (with role B) can't save data (there is no error message, it simply doesn't save changes!).
Now, my question is: could it be that role B have some malfunction or perhaps there is another reason why this is happening?
Many thanks in advance for prompt replies!
Cheers;)
Sam
Check for update terminations in SM13.
It's rather strange for a transaction to allow making changes and not saving. If a user has no authorization for certain object, usually SAP doesn't even let them into that object. Allowing to make a change and not saving looks like a programming bug. Since there is a specific time when this started, check what transports went in on that date or few days before. There could be some bug in a user exit. If there is no custom development, send a message to SAP.
If something worked before and stopped working then obviously something must have changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I forgot to mention one important part, sorry: transaction which doesn't show data is custom transaction named "z_test" which is directly related to transaction XD02.. I think problem could be in some of the past transports...
My question is this: is there any simple way I could check what could be the problem or how to track what happened? I don't need direct solution because it takes time to solve this issue, I only need to find how this could happened?
Thank you,
Sam
dear,
you would request the abaper to debug it.
regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Little but important update: It looks like that SAP can't save data on one location while on another location it saves without any problems, with same SAP licence username/password. First I thought problem was in XD02 or custom transaction but now I think it depends on location where data is added? Is this possible and how to solve it?
Thanks,
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
after saving check transaction su53.
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When user-2 after saving the sale order in change mode, what message system was popping up at the bottom ?
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
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.