× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Drop Ship & Purchase Orders
  • From: MacWheel99@xxxxxxx
  • Date: Thu, 23 Nov 2000 02:24:41 EST

We do not do drop shipments & are on 405 CD so some clues here that may be 
helpful but not fully solve your problems.

> The "bad" ECH field HSTAT is an "E" (have not found a list of valid codes) &
>  the "good" ECH has a "7".
>  The "bad" ECL field LSTAT is an "E" & the "good" ECL has an "8".

The ones you mentioned
E means ENTERED & not done squat with yet
7 means partially invoiced but not yet finished
8 means partially invoiced but no quantity left to do

You also have to look at the codes for active or closed order.
There are some activities that flip the status codes & "close" the order but 
there are still quantities open to be posted, because it is in the middle of 
a series of steps

Locating your ECH & ECL status code meanings.
Check BPCS_L archive search 
http://archive.midrange.com/bpcs-l/index.htm
for a post by Wendy H DeCair on "Order Status Codes" 
(on my bulletin board at work)

She had gone to the trouble of transcribing what they all mean from BPCS help
(I am lazy by comparison) & you might check SSARUN04 documentaiton

Easier for me, since I have BPCS source code is to look at the help source 
for ORD300 in QPNLSRC of BPCS405CDS & scan a few F16 times for Status, and up 
pops the full chart of what the status codes mean in the ECH & ECL files.

I don't have handy dandy quick & easy access to all status code rule charts 
in BPCS but I am hoping this much is helpful

I took a look at our HPO file.
All line #s are positive numbers
no zeros in there

PO status appears to mean
0 when no transactions yet
1 when parital receipt and costed
2 when all quantity received but not yet costed
3 when quantity received and receipts costed

MacWheel99@aol.com (Alister William Macintyre) 
BPCS 405 CD Rel-02 Data Janitor on 400-170 OS4 V4R3 (pre-IBM e-Server 
i-Series 400)  @ http://www.cen-elec.com Central Industries of 
Indiana--->Quality manufacturer of wire harnesses and electrical 
sub-assemblies - fax # 812-424-6838



AS/400 V4R4M0 - behind one set of ptf's from the current set, groups & cum -
BPCS ver. 6.0.02 plf, full client/server, Mar'98 cum

When entering drop shipments, I have one order whose corresponding HPH/HPO
have invalid field contents & I cannot get to the order to finish the
billing process.  The po was receipted, a few lines here & a few there so
they never noticed the extra lines?????

I am comparing a "good" order & po set to the set "bad" I am having trouble
with.  They both are to the same customer/ship-to/item - just different
dates.

The "good" HPO purchase order detail contain the correct number of lines,
which is 40 & they are numbered 1 through 40.
The "good" HPO field PBUYC has a "7" & field PCLIN has "001".

The "bad" HPO purchase order detail contains an incorrect number of lines,
which is 55 & they are numbered 1 through 55.
The "bad" HPO field PBUYC has a " ".
The "bad" HPO field PCLIN has negative "029-" for order line 1.
The "bad" HPO field PCLIN has negative "028-" for order line 2.
The "bad" HPO field PCLIN has negative "027-" for order line 3.
The "bad" HPO field PCLIN has negative "026-" for order line 4.
The "bad" HPO field PCLIN has negative "025-" for order line 5.
The "bad" HPO field PCLIN has negative "024-" for order line 6.
The "bad" HPO field PCLIN has negative "023-" for order line 7.
The "bad" HPO field PCLIN has negative "022-" for order line 8.
The "bad" HPO field PCLIN has negative "021-" for order line 9.
The "bad" HPO field PCLIN has negative "020-" for order line 10.
The "bad" HPO field PCLIN has negative "019-" for order line 11.
The "bad" HPO field PCLIN has negative "018-" for order line 12.
The "bad" HPO field PCLIN has negative "017-" for order line 13.
The "bad" HPO field PCLIN has negative "016-" for order line 14.
The "bad" HPO field PCLIN has negative "015-" for order line 15.
The "bad" HPO field PCLIN has positive "001" for order line 16.
The "bad" HPO field PCLIN has positive "002" for order line 17.
The "bad" HPO field PCLIN has positive "003" for order line 18.
The "bad" HPO field PCLIN has positive "004" for order line 19.

 and etc. through line 39

The "bad" HPO field PCLIN has positive "025" for order line 40.

For  purchase order detail records 41 through 55, PCLIN has a -0-(zeros) in
the field.

The "bad" ECH field HSTAT is an "E" (have not found a list of valid codes) &
the "good" ECH has a "7".
The "bad" ECL field LSTAT is an "E" & the "good" ECL has an "8".

Any clues as to what I need to do so I can complete the drop ship process?  

Or any clue as to what the operator may have done to give us our mess? 

Or any clue where the negative 29 comes in for the line number?

Any clue how it can count right & get to 40 & leave the last 15 po detail
records unsequenced?

Rather confused this day before Thanksgiving here in the States & I was
trying to end the week without any more problems????

I hope the abover makes sense because I'm not sure what we need to do to
rectify this error before month end.

Dennis Munro

"I love deadlines.  I especially like the whooshing sound they make as they
go flying by."  Dilbert's Words Of Wisdom:

Badger Mining Corporation
www.badgerminingcorp.com
dmunro@badgerminingcorp.com
(920) 361-2388

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.