• 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!

OW:P4210 ISSUE

Tricia_Rosas

Active Member
Below after this SAR code is our question. We are
B733.2/SP11.1/AS400/WNNT/SQL7.0 central objects


P4210 - Sales Order Detail Revisions - ER GRID - Row Exit & Changed -
Asynch

//
*************************************************************************
// SAR 3315391 - Begin ADD
// Clients using any of the User Reserved fields MUST load it into the
// various hidden GC fields provided for each User Reserved field.
// The following codes will have to be enabled up 3315391 - End ADD.
//
*************************************************************************
If GC UserCode is greater than <Blank> Or
GC UserDate is greater than <Null Date> Or
GC UserAmount is greater than <Zero> Or
GC UserNumber is greater than <Zero>
Or GC UserReference is greater than <Blank>
If VA grd_mnF42UI11WFLineNumber_LNIX is equal to <Zero>
VA frm_LNIX_Prev_WF_Line_Num = [VA frm_LNIX_Prev_WF_Line_Num] + 1
VA grd_mnF42UI11WFLineNumber_LNIX = VA frm_LNIX_Prev_WF_Line_Num
End If
F4211 Pre Process Values For Edit Line
GC Source ofData = "7"
End If
// SAR 3315391 - End ADD

We have found that once you enable this block of code, that this seems to
be the cause of numerous errors in P4210. Once enabled, you can no longer
perform a "Credit Returns from History". Additionally, we have issues when
you cancel a line in an existing order where various fields on the canceled
line get blanked out. And if you pass through other lines of the order
that were not canceled, if you pass through the canceled line, fields on
these lines get blanked out as well. Carrier number, business unit,
payment terms, tax information, etc.

JDE has stated in SAR 4212861 that they will NOT support any problems if
the client enables this block of code as it is considered a custom
modification, even though the block of code was supplied by JDE.

Does anyone have a workaround for this problem?


Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(Email) tricia_rosas@edwards.com
 

Larry_Jones

Legendary Poster
I assume your problem is how to stuff data into the cache area for user reserved fields so that later they can be updated to the database? Is this the reason you are enabling the remarked out code?

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
 

Tricia_Rosas

Active Member
Correct, we use the user reserved amount to handle our advanced pricing
issues.

Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(Email) tricia_rosas@edwards.com



Larry_Jones
<ljones@wagstaff. To: jdelistml@jdelist.com
com> cc:
Sent by: Subject: Re: OW:p4210 ISSUE ~~2872:2879
owner-jdelistml@j
delist.com


12/18/00 12:56 PM
Please respond to
jdelist






I assume your problem is how to stuff data into the cache area for user
reserved fields so that later they can be updated to the database? Is this
the reason you are enabling the remarked out code?

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=OW&Number=2879
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

Larry_Jones

Legendary Poster
Tricia,

Unfortunately this is not an area I have experience in - though we plan to use the user reserved fields in the future, hence my interest.

I suggest you repost the issue with the subject line specifying what you are trying to accomplish, e.g. "How to use User Reserved Fields in P4210?". This way you may get people with experience in this area who otherwise wouldn't read your post. As I said I have a vested interest in getting an answer to the correct procedure for this - so I'll be watching too.

Good Luck!

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
 
G

Guest

Guest
Hi Tricia,

I have been having fun and games with this bit of code for a while. There
are several issues around the use of pre-processor (F4211 Pre Process
Values For Edit Line) and I have managed to get JDE to repeat some of the
errors and therefore there are SARs on the way. I fail to understand why
this code is referred to as 'allowing user reserved codes' because the
pre-processor does a lot more besides as it is responsible for populating
the sales and purchasing report codes (SRP1,...PRP1..), the route, stop, Gl
& reason codes etc...etc... It is crazy in my opinion to suggest that this
is a modification because the code is an essential part of the order entry
process and should not be conditioned on user reserved code values being
present. If anyone out there can explain why JDE has done this then please
reply as I would like to know the reason. If anyone else has also
experienced the '078O' error in P4210, other than in the examples below,
then please reply as well.



1. Credit Memo from History.

Upon returning to the detail revisions screen from the Sales ledger
inquiry, you have already generated a F42UI12 cache record via the
'CopySODetailtoWorkfile' BSFN within P42025. So consequently when the
pre-processor within Grid Row & Exited Aysnch. is called you will get the
familar '0780 -Add to Cache F42UI12 failed'. The workaround is to
condition the pre-processor call so that it won't execute if the
cCreditMemo work variable is set to '1'. This isn't satisfactory however if
you need to populate user reserved codes or any of the codes mentioned
above.

I raised this on 12-12-00 and JDE have issued ESU 4769108 to fix it.

2. Repricing Error

If you try to reprice (either manual, auto or batch R42750) the reprice
fails if you have invoked the pre-processor. The order reprice (ORPR) and
basket reprice codes (RPRC) are not populated onto the F42UI11 if the
source of data flag is set to a value of '7' . The peculiar thing here is
that the reprice codes exist in the data structure for the pre-processor,
which creates the F42UI12 caches record, but in fact ORPR and RPRC do not
exist on the F42UI12. They do however exist in the F42UI11 but there is no
mechansim for populating them ! The workaround is to unconditionally copy
the reprice codes from the item branch to the F42UI11 corresponding values
within B4200311.

I raised call 1971380 for this, JDE have not raised ESU yet.


3. Multiple Credit Lines from History.

This is different to case 1. and can be repeated with or without invoking
the pre-processor. If you select a line to credit from the ledger inquiry
and return to detail revisions screen and then again take the 'Credit Memo'
form exit and select another line to credit, when returning to the detail
revisions screen again and clicking OK to accept the order error '0780 -Add
to Cache F42UI11' occurs (Note: F42UI11 and not F42UI12!). This is less
serious than the other errors as usually you can select all the lines you
wish to credit within the one step.

I raised this on 15-12-00 and JDE have issued ESU 4784439 to fix it.

There are other examples of these type of errors on the KG, I know of
problems with Kit lines as well.



Hope this helps.

Technical Development Specialist
Developing World Systems Ltd
JDE Consulting Partner of the Year 2000 - SUMAH Region
+ 44 (0)1494 896600 Switchboard
+ 44 (0)1494 896603 Direct
+ 44 (0)1494 896611 Fax

andrew.holder@dwsystems.co.uk
Xe SP13, AS400 V4R4,

===========================================================================
=============================



Below after this SAR code is our question. We are
B733.2/SP11.1/AS400/WNNT/SQL7.0 central objects


P4210 - Sales Order Detail Revisions - ER GRID - Row Exit & Changed -
Asynch

//
*************************************************************************
// SAR 3315391 - Begin ADD
// Clients using any of the User Reserved fields MUST load it into the
// various hidden GC fields provided for each User Reserved field.
// The following codes will have to be enabled up 3315391 - End ADD.
//
*************************************************************************
If GC UserCode is greater than <Blank> Or
GC UserDate is greater than <Null Date> Or
GC UserAmount is greater than <Zero> Or
GC UserNumber is greater than <Zero>
Or GC UserReference is greater than <Blank>
If VA grd_mnF42UI11WFLineNumber_LNIX is equal to <Zero>
VA frm_LNIX_Prev_WF_Line_Num = [VA frm_LNIX_Prev_WF_Line_Num] + 1
VA grd_mnF42UI11WFLineNumber_LNIX = VA frm_LNIX_Prev_WF_Line_Num
End If
F4211 Pre Process Values For Edit Line
GC Source ofData = "7"
End If
// SAR 3315391 - End ADD

We have found that once you enable this block of code, that this seems to
be the cause of numerous errors in P4210. Once enabled, you can no longer
perform a "Credit Returns from History". Additionally, we have issues when
you cancel a line in an existing order where various fields on the canceled
line get blanked out. And if you pass through other lines of the order
that were not canceled, if you pass through the canceled line, fields on
these lines get blanked out as well. Carrier number, business unit,
payment terms, tax information, etc.

JDE has stated in SAR 4212861 that they will NOT support any problems if
the client enables this block of code as it is considered a custom
modification, even though the block of code was supplied by JDE.

Does anyone have a workaround for this problem?


Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(Email) tricia_rosas@edwards.com
 

Tricia_Rosas

Active Member
All,

FWIW, this is the answer I got from JDE on the support issue I raised in
regards to the fact that if you use the JDE supplied code to enable user
reserved fields, it breaks everything else about P4210. I've asked him to
contact Allred for us.

Since we have figured out a way to do this without using the user reserved
fields, this is no longer a priority issue for us, however the poor folks
that do need to use the fields are left out on left field!


Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(Email) tricia_rosas@edwards.com



Larry_Jones
<ljones@wagstaff. To: jdelistml@jdelist.com
com> cc:
Sent by: Subject: Re: OW:p4210 ISSUE ~~2872:2904
owner-jdelistml@j
delist.com


12/18/00 04:55 PM
Please respond to
jdelist






Tricia,

Unfortunately this is not an area I have experience in - though we plan to
use the user reserved fields in the future, hence my interest.

I suggest you repost the issue with the subject line specifying what you
are trying to accomplish, e.g. "How to use User Reserved Fields in P4210?".
This way you may get people with experience in this area who otherwise
wouldn't read your post. As I said I have a vested interest in getting an
answer to the correct procedure for this - so I'll be watching too.

Good Luck!

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=OW&Number=2904
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Top