× 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.



We chose U's & T's over P's & N's based on our requirement/opportunity to 
bypass inbound barrier inspection for a large percentage of our purchased 
materials, this is a function of supplier qualification programs and the 
application of practical inspection protocols.  In a 6.0.04 environment we use 
an IREF field to specify inbound routing as either of DOCK[to stock] or 
INSP[-ection] both of which are also defined locations within our main storage 
warehouse although we exclude INSP as a non-allocatable location, this 
differentiation is exercised as the default receive-to location during a U 
transaction in PUR550 and is printed on our ever so slightly modified/enhanced 
receiver ticket.  Our material movers use the receiver ticket as a put-away 
instruction [in the case of inbound routing DOCK] and the receiver ticket 
"suggests" a hard storage location based on the last ITH location from the 
warehouse for which the purchase order was issued, the actual put-away location 
is recorded by the stockroom in conjunction with any required quantity 
verification and the receiver ticket become a source document for a transfer 
via INV510 [augemented by reason codes differentiating such a put-away 
transaction from all the other really exciting transfers].  In the case of an 
inbound routing of INSP, the receiver ticket now serves as the template for the 
inspection process [did I mentioned the receiver ticket has been modified?] 
being as it contains instructional text and requirements which have been 
codified by our quality assurance group and associated with respective item 
masters also via the use of an IREF field. The quantity of items passed are 
then forwarded to the suggested hard storage location and processed in the same 
fashion as materials whose inbound routing was to DOCK.  The count-verified 
receiver ticket confirming the put-away location effectively replaces the 
supplier's documentation [packing list or whatever] for the purpose of our 
payables match [which is kind of a <3 way match].  In the unlikely [for the 
sake of 
whatever criteria are exercised against it then options are selected [based on 
the nature of the discrepancy] to reverse the receipt directly from the INSP 
location or transfer the discrepant materials into a 
non-allocatable/non-nettable MRB warehouse for further 
consideration/disposition.

Receiving is typically viewed as a painfully simple process, usually receives 
that level of attention and becomes simply painful.  Something about getting 
off on the right foot...

TJ
>>> fupingren@yeah.net 06/15 4:53 PM >>>
Dear All,
    Envoironment: BPCS 6.0.02, AS/400
    How to process the purchase receipts procedure. ??
    Example, I Create a Po for raw material, Order qty: 1000, and when
vendor delivery, we need inspecting, so inspecting qty is 1000,stock qty
is 0,but the IQC result is rejecting qty 200,and stock qty is 800. How
to tracking the sequence procedure in BPCS, and how many transaction to
record it and what transaction code to record it.

Best regards!
FP Ren
China



+---
| 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 
+---

+---
| 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-Ups:

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.