wsellers
Active Member
RE: Finicky R42520
Angie,
Are you processing pick slips by next status through a blind execution of
R42520? Does the pick slip hard copy print out? I've seen instances, in
B7332, where the sales order will be at next status 540 and a user will have
the order opened into sales order revisions through P4210 as the pick slip
print program is executed. The pick slip prints and advances the next
status to 560; however, the end user then saves his changes in P4210 with
next status 540. Inquiry on the order through P4210 it would appear as
though the next status never changed even though it had. If you're logging
the status changes to the sales ledger, F42199, you can view these through
sales ledger history, P42025.
R42520 doesn't appear to verify that the sales order isn't opened by a user
in B7332.
Walt Sellers
Heil Environmental Industries, Ltd.
OW B733.2 SP10, Citrix, Windows NT TS2000, Oracle 8.1.6
Angie,
Are you processing pick slips by next status through a blind execution of
R42520? Does the pick slip hard copy print out? I've seen instances, in
B7332, where the sales order will be at next status 540 and a user will have
the order opened into sales order revisions through P4210 as the pick slip
print program is executed. The pick slip prints and advances the next
status to 560; however, the end user then saves his changes in P4210 with
next status 540. Inquiry on the order through P4210 it would appear as
though the next status never changed even though it had. If you're logging
the status changes to the sales ledger, F42199, you can view these through
sales ledger history, P42025.
R42520 doesn't appear to verify that the sales order isn't opened by a user
in B7332.
Walt Sellers
Heil Environmental Industries, Ltd.
OW B733.2 SP10, Citrix, Windows NT TS2000, Oracle 8.1.6
