SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

CAA2 Contract account

Former Member

‎03-30-2011 3:03 PM

0 Kudos

Hello,

I have a problem with the transaction caa2, Changing modus of contract account. When you make changings on this screen and klick on the button "save", you can see the message "this contract account is changed succesfully".

But when you want to see the changed settings, you see the old settings. And everything in Display modus. If you try to change the same contract account again, you get the message, "this contract account is locked" although no other user changes this contract account.

So summarized, you cannot do any changings on contract account.

Do you have any idea, why?

Can a mandant copy be the reason? Because I made a mandant copy from this system to another target system before.

Thanks in advance.

3 REPLIES 3

murtuza_chhatariya
Active Participant

‎07-08-2011 6:28 PM

0 Kudos

I am not sure if this is related to COMMIT WORK but seems the same issue. When we save something and COMMIT WORK is used, it displayes that everything is saved, but it takes time to reflect the changes as COMMIT WORK runs parallely after SAVE.

Also it locks the account and immediatly, it will not allow changes on the same account.

Please close the session and open a new one in display mode. Check if this helps!

Also you checked if there is any user exits or something on CAA2?

Former Member
In response to murtuza_chhatariya

‎07-08-2011 9:34 PM

0 Kudos

Hi,

Please check ST22 logs and SAP inbox (in case of data inconsistency, you may receive mails in SAP inbox).

Regards,

Avinash

AmlanBanerjee
Active Contributor

‎07-09-2011 6:17 AM

0 Kudos

Hi,

There can be two possible reasons of the problem that you are facing-

(a) First one is what is explained by Murtaza..On pressing save, COMMIT WORK is used, it displays that everything is saved, but it takes time to reflect the changes as COMMIT WORK runs parallely after SAVE. In this whole process, the system locks the account and will not allow changes on the same account, until the COMMIT WORK is complete.

This scenario normally happens when the system is slow like you are running the SAP system under cloud environment.

(b) Go to transaction code-CAS7 and look through the events DSAVE and DSAVC.

Check any customised FM is assigned to this events or not, which is creating this problem.

Hope it helps.....

Thanks,

Amlan