RE: Status Codes jumping Print Process

GWaer

Member
RE: Status Codes jumping Print Process

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C050AC.398438DC
Content-Type: text/plain;
charset="iso-8859-1"

We have had status codes jump from 380 to 999. No logic or pattern. Could
not duplicate the error.
B733.2 SP9

Gary Waer,
Warehouse Supervisor
North County Transit District
 
You don't mention what type document these are ocurring on ... but I'll take a stab at it.

1) What are the Document and Line Types?
2) What are the Order Activity Rules you have setup for that Document/Line Type?

Most likely you have people running the wrong version of print programs that update statuses and/or you have very loose controls on these kind of programs. The print programs (such as PO Print) are really kinda stupid. If you print it initially using a version that advances status it will do so, to the next status per the order Activity Rules - usually 400 for P.O.'s. If someone then reprints the PO using the same version - one that advances status - it will again advance the status - to whatever is next per the Order Activity Rules. If your document is a PO that most likely is 999. So you see without the proper controls and most of all user education its easy in OneWorld for things to get screwed up.

Sorry if I sounded a little bit know-it-all above. I only know it because we've been through this same problem here. Even though people swore that didn't do this, the real story was that they did. If there's no logic or pattern to it thats another clue that its a people problem.

Hope this helps!

Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11.0, Oracle SE 8.0.5
 
Re: Status Codes jumping Print Process

--part1_54.c0948b6.27473db3_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

We had status codes appear to jump from 280 to 999 in the Purchasing Ledger
but in the Order Inquiry they were fine. We usually run a custom report to
batch but in this instance we used the "canned print batch program". There
is a SAR to correct this problem. Thanks for the input.

Roxanne
County Government

--part1_54.c0948b6.27473db3_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT SIZE=2>We had status codes appear to jump from 280 to 999 in the Purchasing Ledger
but in the Order Inquiry they were fine. We usually run a custom report to
batch but in this instance we used the "canned print batch program". There
is a SAR to correct this problem. Thanks for the input.



Roxanne

County Government</FONT></HTML>

--part1_54.c0948b6.27473db3_boundary--
 
Back
Top