• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

problems with cross segment edit rule text

dkazinski

Member
Hi
I am having a large problem in the configurator and was wondering if anyone
else has this problem. ( We are running 7.3 cum 8) When the user is editing
cross segment edit rules, namely deleting or inserting rules, the text
associated with a rule will 'move'. The keys used to generate a serial number
are parent item, b/p, rule # and sequence number. The program is not
recalculating the serial number after a rule is deleted or a new one is added.
I have called Edwards and got the same old response of 'It doesn't do that in my
environment'. The gentleman on the phone was kind enough to e-mail me some
SAR's to apply since he was testing in cum 12 and I'm in 8. The ones he sent me
where for the assembly inclusion and not cross segment editing. I have lost all
faith in the support line and was hoping someone else has a fix for this
problem. Does this really not happen in cum 12? I welcome any help.
Thanks Debbie Kazinski
 

dherd

Member
Debbie -

There are definitely problems with CSER text in coexistent environments (I've
been struggling with some of these issues recently) but it sounds like you are
only running World. Is this correct?

When you say that "the text associated with a rule will move" do you mean that
it moves along with the rule that it was originally associated with, or that it
"moves" to a different rule? Also, I'm not sure what you mean by the "serial
number" which is generated by the "parent item, b/p, rule # and sequence number"
and how this relates to the error message text.

In World there are some issues with deleting rules and if it's not done
"correctly" (and I choke as I say that) you WILL end up with data corruption. I
can supply more details if you are interested. The SAR for this problem (as
well as a corequisite SAR for another data corruption issue) was written for cum
12 and we couldn't get it to work in cum 8 (which we are also on). Apparently
it relies on changes made in one or more of the 45 other SARs that have been
written for P3292 between cum 8 and 12.

If you can supply a bit more info about your problem I may be able to shed some
additional light on it.

Don Herd
JDE Sales Configurator System Process Analyst
Cascade Corporation
Portland, OR
e-mail: dherd@cascorp.com



\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/ \/
/\ Interested in CustomWorks or the JDE Sales Configurator? /\
\/ Check out www.egroups.com/group/JDE_Sales_Configurator \/
/\ /\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\











dkazinski <dkazinski@pentairwater.com> on 10/19/2000 10:43:18 AM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Don Herd/CASCADE)
Subject: problems with cross segment edit rule text ~~0:41





Hi
I am having a large problem in the configurator and was wondering if anyone
else has this problem. ( We are running 7.3 cum 8) When the user is editing
cross segment edit rules, namely deleting or inserting rules, the text
associated with a rule will 'move'. The keys used to generate a serial number
are parent item, b/p, rule # and sequence number. The program is not
recalculating the serial number after a rule is deleted or a new one is added.
I have called Edwards and got the same old response of 'It doesn't do that in my
environment'. The gentleman on the phone was kind enough to e-mail me some
SAR's to apply since he was testing in cum 12 and I'm in 8. The ones he sent me
where for the assembly inclusion and not cross segment editing. I have lost all
faith in the support line and was hoping someone else has a fix for this
problem. Does this really not happen in cum 12? I welcome any help.
Thanks Debbie Kazinski

--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=41
 

dkazinski

Member
Don,
The text moves to a different rule. If the text is associated with rule
number 4 and you delete rule number three, the text stays with rule number 4
although the old rule number 4 is now number 3.

The f0016 file uses a serial number as it's key (basically a next number). The
composite key that is used to generate the serial number for the configurator is
parent item, branch, rule and sequence. The file which contains the composite
key and serial number is the f00163. What is happening to us when we delete or
add rules, the rule and sequence number in the f00163 is not updated. I have
contacted Edwards again, and they suggest getting cum 12 and start 'cherry
picking' at the configurator until my problem goes away. Debbie






dherd <dherd@cascorp.com> on 10/19/2000 06:26:15 PM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Debbie Kazinski/FLECKHQ/PENTAIR/US)
Fax to:
Subject: Re: problems with cross segment edit rule text ~~41:72





Debbie -

There are definitely problems with CSER text in coexistent environments (I've
been struggling with some of these issues recently) but it sounds like you are
only running World. Is this correct?

When you say that "the text associated with a rule will move" do you mean that
it moves along with the rule that it was originally associated with, or that it
"moves" to a different rule? Also, I'm not sure what you mean by the "serial
number" which is generated by the "parent item, b/p, rule # and sequence number"
and how this relates to the error message text.

In World there are some issues with deleting rules and if it's not done
"correctly" (and I choke as I say that) you WILL end up with data corruption. I
can supply more details if you are interested. The SAR for this problem (as
well as a corequisite SAR for another data corruption issue) was written for cum
12 and we couldn't get it to work in cum 8 (which we are also on). Apparently
it relies on changes made in one or more of the 45 other SARs that have been
written for P3292 between cum 8 and 12.

If you can supply a bit more info about your problem I may be able to shed some
additional light on it.

Don Herd
JDE Sales Configurator System Process Analyst
Cascade Corporation
Portland, OR
e-mail: dherd@cascorp.com



\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/ \/
/\ Interested in CustomWorks or the JDE Sales Configurator? /\
\/ Check out www.egroups.com/group/JDE_Sales_Configurator \/
/\ /\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\











dkazinski <dkazinski@pentairwater.com> on 10/19/2000 10:43:18 AM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Don Herd/CASCADE)
Subject: problems with cross segment edit rule text ~~0:41





Hi
I am having a large problem in the configurator and was wondering if anyone
else has this problem. ( We are running 7.3 cum 8) When the user is editing
cross segment edit rules, namely deleting or inserting rules, the text
associated with a rule will 'move'. The keys used to generate a serial number
are parent item, b/p, rule # and sequence number. The program is not
recalculating the serial number after a rule is deleted or a new one is added.
I have called Edwards and got the same old response of 'It doesn't do that in my
environment'. The gentleman on the phone was kind enough to e-mail me some
SAR's to apply since he was testing in cum 12 and I'm in 8. The ones he sent me
where for the assembly inclusion and not cross segment editing. I have lost all
faith in the support line and was hoping someone else has a fix for this
problem. Does this really not happen in cum 12? I welcome any help.
Thanks Debbie Kazinski

--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=41





--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=72
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

dkazinski

Member
Don,
Sorry I didn't mention in my prior e-mail, but we currently don't co-exist
with One World. Debbie




dherd <dherd@cascorp.com> on 10/19/2000 06:26:15 PM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Debbie Kazinski/FLECKHQ/PENTAIR/US)
Fax to:
Subject: Re: problems with cross segment edit rule text ~~41:72





Debbie -

There are definitely problems with CSER text in coexistent environments (I've
been struggling with some of these issues recently) but it sounds like you are
only running World. Is this correct?

When you say that "the text associated with a rule will move" do you mean that
it moves along with the rule that it was originally associated with, or that it
"moves" to a different rule? Also, I'm not sure what you mean by the "serial
number" which is generated by the "parent item, b/p, rule # and sequence number"
and how this relates to the error message text.

In World there are some issues with deleting rules and if it's not done
"correctly" (and I choke as I say that) you WILL end up with data corruption. I
can supply more details if you are interested. The SAR for this problem (as
well as a corequisite SAR for another data corruption issue) was written for cum
12 and we couldn't get it to work in cum 8 (which we are also on). Apparently
it relies on changes made in one or more of the 45 other SARs that have been
written for P3292 between cum 8 and 12.

If you can supply a bit more info about your problem I may be able to shed some
additional light on it.

Don Herd
JDE Sales Configurator System Process Analyst
Cascade Corporation
Portland, OR
e-mail: dherd@cascorp.com



\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/ \/
/\ Interested in CustomWorks or the JDE Sales Configurator? /\
\/ Check out www.egroups.com/group/JDE_Sales_Configurator \/
/\ /\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\











dkazinski <dkazinski@pentairwater.com> on 10/19/2000 10:43:18 AM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Don Herd/CASCADE)
Subject: problems with cross segment edit rule text ~~0:41





Hi
I am having a large problem in the configurator and was wondering if anyone
else has this problem. ( We are running 7.3 cum 8) When the user is editing
cross segment edit rules, namely deleting or inserting rules, the text
associated with a rule will 'move'. The keys used to generate a serial number
are parent item, b/p, rule # and sequence number. The program is not
recalculating the serial number after a rule is deleted or a new one is added.
I have called Edwards and got the same old response of 'It doesn't do that in my
environment'. The gentleman on the phone was kind enough to e-mail me some
SAR's to apply since he was testing in cum 12 and I'm in 8. The ones he sent me
where for the assembly inclusion and not cross segment editing. I have lost all
faith in the support line and was hoping someone else has a fix for this
problem. Does this really not happen in cum 12? I welcome any help.
Thanks Debbie Kazinski

--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=41





--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=72
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Top