Sign in or 
Location: Oracle Utilities Customer Care
Discussion: Concurrency Error
Category:
Discussion Forum /
General Discussion
Share this
Showing 6 posts
|
eugeCba |
Concurrency Error
Feb 5 2009, 8:36 AM EST
Hi all! I'm working with BOs and I'm getting a Concurrency Error when I try to make an update. This is my code: invoke BO 'BOName' using "case" for read; for ($eachItem in "BSName/results") move 'CHAR_TYPE' to "case/+Char/charTypeCd"; move "$eachItem/fkValue1" to "case/Char[last()]/fkValue1"; end-for; invoke BO 'BOName' using "case" for update; The problem shows when I'm adding this characteristic to a BO that already have at least one characteristic of this type, otherwise works fine. I check the Error Log and I see the new characteristics added in my BO, but then I get the Error. I'm new at ETM!! Regards!! PS: I posted this issue also in Oracle Enterprise Taxation Management Do you find this valuable?
Keyword tags:
characteristics
concurrency error
ETM
update
|
jakarapu |
1. RE: Concurrency Error
Feb 5 2009, 4:45 PM EST
Hii.. Is there any Date field present in the table you are trying to add this char_type??
Do you find this valuable?
|
|
eugeCba |
2. RE: Concurrency Error
Feb 6 2009, 6:55 AM EST
Yes, there are two date fields, not in the table but related with my rows as a characteristic (in the characteristic table). I'm using a Case type not a BO, I misstype in the example code. Thanks for reply!! :) and apologize my english Do you find this valuable? |
|
arezki.halet |
3. RE: Concurrency Error
Feb 6 2009, 1:13 PM EST
We have encountered a similar problem just few days ago, I am happy to share the conclusions:This issue occurs when entering a date field. For instance, I believe the field for characteristics is: EFFDT. But other fields appy as well. If we are inserting a date stucture to this date field, like: sysdate, the system does not recognize the additioanalmin:sec and so on the sysdate. For example, if we are using a sysdate, then we need to insert or update with the following: sysdate -> to_date( to_char(sysdate, 'YYYY-MM-DD'), 'YYYY-MM-DD') However, not all ETM fields need to comply with this rule. For example, CI_ADJ, CI_FT, there are date fields ending with _DTTM. Let me know if this works. Do you find this valuable? |
|
eugeCba |
4. RE: Concurrency Error
Feb 6 2009, 2:06 PM EST
Hi!!! what i'm trying to add as a characteristic is a Foreign Key field, i don't change or add date field o characteristic. I have a case with an obligation asociated, when I launch a plug-in script i read the case, add a new obligation to it and try to update, this fails. If my case doesn't have an obligation asociated and the plug-in triggers, works ok; even if I'm adding two or more obligations at once. Thank you very much!!!! Do you find this valuable? |
|
arezki.halet |
5. RE: Concurrency Error
Feb 10 2009, 6:38 PM EST
"Hi!!! what i'm trying to add as a characteristic is a Foreign Key field, i don't change or add date field o characteristic.It does not have to be a characterestic, it can be any date field (few exception). So, the algorithm may be reading a characterestic or record with date field that does not comply with the described rule, and the error is triggered indirectly. Give it a try and verify if you see any pattern. Hope that works. Do you find this valuable? |
