Colin_Hugill
Reputable Poster
RE: Pick Slips Print (P42520) - did not print pick Back Ordered Quantity
Marsh and Simon,
Some basic clarification:-
a) Order next/last status values are governed by what you specify in the
Order Activity Rules. Oh, by the way this function is part of the Sales
order processing set up activity accessed from hidden selection 29 from
any Sales Order processing menu assuming the menu set up and security
set up allow you to use hidden selection 29.
b) The application of the order activity rules are also related to your
processing options for various programs in the Sales Order Process.
There are options that allow override status value allocation (provided
the Order Activity Rules allow it)
Please guys, read some of the standard JDE documentation!
Simon, you can't assume that what your company implementation definition
does is the same as every other JDE site. I don't have access to a JDE
site and source code at this time, and anyway I am a bit out of practice
at reading source code. None the less, in the absence of a claim that
JDE is hardcoded to use 902/540 I assume that order activity rules and
processing options rule the process, not hardcoded lines in programs.
Marsh, you need to recognize that you are dealing with a total "process"
and not one program. I know you may not like the prior and following
statements, however Pick Slip print is only one step in an overall and
integrated process (I emphasize the words integrated and process). You
need to understand the preceding "events" in the process and consider
them in context with the business requirement you are trying to satisfy.
You need to do some more analysis and provide more relevant detail to
the problem.
Marsh, and a lot of other JDElisters, may think this is contradictory to
an earlier post of mine a year or so ago. Sometimes it is necessary to
modify JDE code to meet your organization's specific requirements, but
only after some detailed assessment of both the requirement and JDE
functionality (you need to have a good understanding of JDE to evaluate
it). This may be one of those times but then again?
I do remember doing some senior consulting work /for a company about 7-8
years ago who wanted to show ordered, shipped, and, backordered,
quantities on Pickslips. The client was on A6.1 then A6.2. We ended up
making client specific modifications to the Pick Slip print program but
from memory they were pretty minor and revolved more around the printer
file format.
One of the best people to comment on the problem to hand would be Andy
Klee - are you there Andy? Andy is a bit of a Guru on Sales Order
Processing and is on the list. These days he also runs an independent
JDE Tips and consulting company so please don't expect him to give to a
definitive and specific answer with worked examples.
Regards
Colin Hugill
Consultant
(World A7.3 cum12)
Marsh and Simon,
Some basic clarification:-
a) Order next/last status values are governed by what you specify in the
Order Activity Rules. Oh, by the way this function is part of the Sales
order processing set up activity accessed from hidden selection 29 from
any Sales Order processing menu assuming the menu set up and security
set up allow you to use hidden selection 29.
b) The application of the order activity rules are also related to your
processing options for various programs in the Sales Order Process.
There are options that allow override status value allocation (provided
the Order Activity Rules allow it)
Please guys, read some of the standard JDE documentation!
Simon, you can't assume that what your company implementation definition
does is the same as every other JDE site. I don't have access to a JDE
site and source code at this time, and anyway I am a bit out of practice
at reading source code. None the less, in the absence of a claim that
JDE is hardcoded to use 902/540 I assume that order activity rules and
processing options rule the process, not hardcoded lines in programs.
Marsh, you need to recognize that you are dealing with a total "process"
and not one program. I know you may not like the prior and following
statements, however Pick Slip print is only one step in an overall and
integrated process (I emphasize the words integrated and process). You
need to understand the preceding "events" in the process and consider
them in context with the business requirement you are trying to satisfy.
You need to do some more analysis and provide more relevant detail to
the problem.
Marsh, and a lot of other JDElisters, may think this is contradictory to
an earlier post of mine a year or so ago. Sometimes it is necessary to
modify JDE code to meet your organization's specific requirements, but
only after some detailed assessment of both the requirement and JDE
functionality (you need to have a good understanding of JDE to evaluate
it). This may be one of those times but then again?
I do remember doing some senior consulting work /for a company about 7-8
years ago who wanted to show ordered, shipped, and, backordered,
quantities on Pickslips. The client was on A6.1 then A6.2. We ended up
making client specific modifications to the Pick Slip print program but
from memory they were pretty minor and revolved more around the printer
file format.
One of the best people to comment on the problem to hand would be Andy
Klee - are you there Andy? Andy is a bit of a Guru on Sales Order
Processing and is on the list. These days he also runs an independent
JDE Tips and consulting company so please don't expect him to give to a
definitive and specific answer with worked examples.
Regards
Colin Hugill
Consultant
(World A7.3 cum12)
