8.03.4.09A Order entry error Record has been modified by another

Yahoo Archive
1
Yes. 8.03.409B.



Sorry, couldn't resist.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
jilllopez1245
Sent: Wednesday, June 09, 2010 2:29 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: 8.03.4.09A Order entry error Record has been modified
by another user





We just loaded 409A last night and have been having the same problem. Does
anyone know if there is a fix for this?

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"pklein256" <pklein@...> wrote:
>
> Since we've gone up to 4.09A within order entry, we regualarly get the
following error message:
>
>
> Message: Record has been modified by another user and couldn't be updated.
Please press the Refresh button and re-enter your changes.
> Type: UpdateConflict
> Program: core/BizRuleEngine.p
> Method: Main-Block
> Table: OrderHed
> Row: 0x00000000026343af
> Field: TermsCode
>
> I know we normally get this message when someone else has updated the
record. NORMALLY you'd hit refresh, re-apply your changes, save the record
and move on.
> This is not the case.
> This can be a newly entered order, that no one has changed - we go back
into the order to make changes and get the error. the refresh button does
NOT work. I tried to update the record using DMT and still get the same
error message. It's like there's garbage data within the record, it thinks
it's been updated and can't update itself.
>
> Epicor says to do a dump and load. (which we did right before the 4.09A
upgrade... These orders are happening daily and we can't do a dump and
loload overnight.
>
> Has anyone else gotten this error message? Any ideas for solutions. Right
now our CSR's are having to delete the order and re-create it.
>





[Non-text portions of this message have been removed]
2
Since we've gone up to 4.09A within order entry, we regualarly get the following error message:


Message: Record has been modified by another user and couldn't be updated. Please press the Refresh button and re-enter your changes.
Type: UpdateConflict
Program: core/BizRuleEngine.p
Method: Main-Block
Table: OrderHed
Row: 0x00000000026343af
Field: TermsCode

I know we normally get this message when someone else has updated the record. NORMALLY you'd hit refresh, re-apply your changes, save the record and move on.
This is not the case.
This can be a newly entered order, that no one has changed - we go back into the order to make changes and get the error. the refresh button does NOT work. I tried to update the record using DMT and still get the same error message. It's like there's garbage data within the record, it thinks it's been updated and can't update itself.

Epicor says to do a dump and load. (which we did right before the 4.09A upgrade... These orders are happening daily and we can't do a dump and loload overnight.

Has anyone else gotten this error message? Any ideas for solutions. Right now our CSR's are having to delete the order and re-create it.
3
On Mon, Jun 7, 2010 at 3:01 PM, pklein256 <pklein@...> wrote:
>
> Since we've gone up to 4.09A within order entry, we regualarly get the following error message:
>
> Message: Record has been modified by another user and couldn't be updated. Please press the Refresh button and re-enter your changes.
> Type: UpdateConflict
> Program: core/BizRuleEngine.p
> Method: Main-Block
> Table: OrderHed
> Row: 0x00000000026343af
> Field: TermsCode
>

Have any BPMs running against OrderHed?

Mark W.
4
Yes, we have BPM's.

--- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@...> wrote:
>
> On Mon, Jun 7, 2010 at 3:01 PM, pklein256 <pklein@...> wrote:
> >
> > Since we've gone up to 4.09A within order entry, we regualarly get the following error message:
> >
> > Message: Record has been modified by another user and couldn't be updated. Please press the Refresh button and re-enter your changes.
> > Type: UpdateConflict
> > Program: core/BizRuleEngine.p
> > Method: Main-Block
> > Table: OrderHed
> > Row: 0x00000000026343af
> > Field: TermsCode
> >
>
> Have any BPMs running against OrderHed?
>
> Mark W.
>
5
We just loaded 409A last night and have been having the same problem. Does anyone know if there is a fix for this?

--- In vantage@yahoogroups.com, "pklein256" <pklein@...> wrote:
>
> Since we've gone up to 4.09A within order entry, we regualarly get the following error message:
>
>
> Message: Record has been modified by another user and couldn't be updated. Please press the Refresh button and re-enter your changes.
> Type: UpdateConflict
> Program: core/BizRuleEngine.p
> Method: Main-Block
> Table: OrderHed
> Row: 0x00000000026343af
> Field: TermsCode
>
> I know we normally get this message when someone else has updated the record. NORMALLY you'd hit refresh, re-apply your changes, save the record and move on.
> This is not the case.
> This can be a newly entered order, that no one has changed - we go back into the order to make changes and get the error. the refresh button does NOT work. I tried to update the record using DMT and still get the same error message. It's like there's garbage data within the record, it thinks it's been updated and can't update itself.
>
> Epicor says to do a dump and load. (which we did right before the 4.09A upgrade... These orders are happening daily and we can't do a dump and loload overnight.
>
> Has anyone else gotten this error message? Any ideas for solutions. Right now our CSR's are having to delete the order and re-create it.
>
6
Epicor was able to re-create the problem.
I just got an e-mail from Support for a fix. We're going to apply it tonight to see if it works. Call support for the solution. My tech support person was Ricardo Valdes.



--- In vantage@yahoogroups.com, "jilllopez1245" <jill.lopez@...> wrote:
>
> We just loaded 409A last night and have been having the same problem. Does anyone know if there is a fix for this?
>
> --- In vantage@yahoogroups.com, "pklein256" <pklein@> wrote:
> >
> > Since we've gone up to 4.09A within order entry, we regualarly get the following error message:
> >
> >
> > Message: Record has been modified by another user and couldn't be updated. Please press the Refresh button and re-enter your changes.
> > Type: UpdateConflict
> > Program: core/BizRuleEngine.p
> > Method: Main-Block
> > Table: OrderHed
> > Row: 0x00000000026343af
> > Field: TermsCode
> >
> > I know we normally get this message when someone else has updated the record. NORMALLY you'd hit refresh, re-apply your changes, save the record and move on.
> > This is not the case.
> > This can be a newly entered order, that no one has changed - we go back into the order to make changes and get the error. the refresh button does NOT work. I tried to update the record using DMT and still get the same error message. It's like there's garbage data within the record, it thinks it's been updated and can't update itself.
> >
> > Epicor says to do a dump and load. (which we did right before the 4.09A upgrade... These orders are happening daily and we can't do a dump and loload overnight.
> >
> > Has anyone else gotten this error message? Any ideas for solutions. Right now our CSR's are having to delete the order and re-create it.
> >
>
7
We want to restrict access to Part Duplication, which is a sub session from Part -- Can anyone provide info on how to restrict user access to sub session. We are on Vantage 8.00.811b



Vishal





[Non-text portions of this message have been removed]
8
8.03.407A

Use Process Security in System Management|Security Management folder.

Select the bo.Part object and then add the Duplicate Part method. From
there set security in the usual manner.

Ross

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Vishal Mehta
Sent: Thursday, June 10, 2010 4:27 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Restricting Access to Sub Session


We want to restrict access to Part Duplication, which is a sub session from
Part -- Can anyone provide info on how to restrict user access to sub
session. We are on Vantage 8.00.811b



Vishal





[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
9
This has happened periodically to us since we went to Vantage 8. We
sometimes have success by refreshing and saving before trying to make
any changes to the order, quote or whatever.



Hth,

Linda



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of pklein256
Sent: Monday, June 07, 2010 3:02 PM
To: vantage@yahoogroups.com
Subject: [Vantage] 8.03.4.09A Order entry error Record has been modified
by another user





Since we've gone up to 4.09A within order entry, we regualarly get the
following error message:

Message: Record has been modified by another user and couldn't be
updated. Please press the Refresh button and re-enter your changes.
Type: UpdateConflict
Program: core/BizRuleEngine.p
Method: Main-Block
Table: OrderHed
Row: 0x00000000026343af
Field: TermsCode

I know we normally get this message when someone else has updated the
record. NORMALLY you'd hit refresh, re-apply your changes, save the
record and move on.
This is not the case.
This can be a newly entered order, that no one has changed - we go back
into the order to make changes and get the error. the refresh button
does NOT work. I tried to update the record using DMT and still get the
same error message. It's like there's garbage data within the record, it
thinks it's been updated and can't update itself.

Epicor says to do a dump and load. (which we did right before the 4.09A
upgrade... These orders are happening daily and we can't do a dump and
loload overnight.

Has anyone else gotten this error message? Any ideas for solutions.
Right now our CSR's are having to delete the order and re-create it.





[Non-text portions of this message have been removed]