This content has been marked as final. Show 4 replies
Wehave this error but its more related to charge account. If your error is related ot charge account then its not actualy an error, you can just ignore it, entre teh charge acount and get on with it.
Our users are entering the correct accounts. I do not believe this is due to charge account. It is intermittent, and that is what is very frustrating. Our users have to keep logging off and logging back in and try again and sometime, it clicks!!
The most unfortunate thing about this is that it is also difficult to get the log of the statement being executed by OAF at that time. We have to turn on the tracing on the screen and by the time we get to the point where the error appears, the log is some 600 pages and cannot be cut and pasted into a document.
The eror we had was related to charge account only. can oyu assign the charge account to one user and then ask them to eprform the operations. For another user, can you grant them privelge to create a pick list in iproc so when they do use charge account they are actuialy able ot pick one and use it.
DO you have some more infomation on this error. There should eb another page specifying which flexfield validation is causing the error.
please let us know how you were able to resolve the issue. if either the user logout and login, it works good, or clearing the cache from functional administrator will resolve the issue. we went live with R12 12.1.2 recently. your reply is greatly appreciated.