× 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: Order Status Bits ? Who, Why & When ??
  • From: Rob_Post@xxxxxxxxxx (Rob Post)
  • Date: Thu, 29 Apr 1999 15:49:48 -0400

     Roberto,
     
     My name is Rob Post, working for Bausch & Lomb in the Netherlands.
     
     The situation you describe I think has nothing to do with BPCS 
     Billing. Record-id's are changed by BPCS by at the moment of Pick 
     Confirm, taking backorder code settings into account. Only if an order 
     is confirmed to be completely shipped, or partially shipped and the 
     backorder code doesn't allow backordering, HID will be set to CZ. All 
     this is done prior to Billing.
     
     Rob Post
     Bausch & Lomb ELC
     Netherlands
     


______________________________ Reply Separator _________________________________
Subject: Order Status Bits ? Who, Why & When ??
Author:  Roberto_Sehringer@GM.cytec.com at Internet
Date:    4/28/99 1:35 PM


     To all you BPCS Experts,
     
     Here  is a mistery (due to my lack of BPCS knowledge) that most of you 
     can help me with :
     
     BPCS 6.02 after running our Billing Process we still find orders that 
     have been billed (invoiced) but the HID field in ECH hasn't been set 
     to contain a Z. The status bit for Closed Order has been set yet the 
     HID hasn't been changed to HZ... why ? Is this normal ?
     The order was succesfully billed and a record has been logged in 
     SIH/SIL yet ECH still has the Order as Opened.
     As the last part of the question what are all of the Status Bit 
     combinations, does someone have a document that explains the different 
     order status's.
     
     Many thanks in advanced.
     
     Roberto Sehringer
     Cytec Inudstries, Inc.
Received: from st.cytec.com (164.84.1.253) by stnt01.cytec.com with SMTP
  (IMA Internet Exchange 2.12 Enterprise) id 001258CF; Tue, 27 Apr 99 07:04:18
-0400
Received: from gw.cytec.com (igw.cytec.com) by st.cytec.com (4.1/SMI-4.1)
        id AA09038; Mon, 26 Apr 99 17:04:48 EDT
Received: by gw.cytec.com; id RAA05650; Mon, 26 Apr 1999 17:03:34 -0400
Received: from kitten.mcs.com(192.160.127.90) by gw.cytec.com via smap (3.2)
        id xma005604; Mon, 26 Apr 99 17:03:14 -0400
Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by
Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id QAA28167; Mon, 26 Apr 1999 16:01:29
-0500 (CDT)
Received: (from uucp@localhost)
        by uucphost.mcs.net (8.8.8/8.8.8) id QAA08438;
        Mon, 26 Apr 1999 16:01:27 -0500 (CDT)
Received: (from majordom@localhost)
        by midrange.com (8.9.3/8.9.3) id PAA10064
        for bpcs-l-outgoing; Mon, 26 Apr 1999 15:45:10 -0500
Received: (from uucp@localhost)
        by midrange.com (8.9.3/8.9.3) with UUCP id PAA10045
        for bpcs-l@midrange.com; Mon, 26 Apr 1999 15:31:03 -0500
From: DAsmussen@aol.com
Received: from imo18.mx.aol.com (imo18.mx.aol.com [198.81.17.8])
        by uucphost.mcs.net (8.8.8/8.8.8) with ESMTP id PAA06253
        for <bpcs-l@midrange.com>; Mon, 26 Apr 1999 15:16:08 -0500 (CDT)
Received: from DAsmussen@aol.com (7810)
        by imo18.mx.aol.com (IMOv20) id iDSHa28009
         for <bpcs-l@midrange.com>; Mon, 26 Apr 1999 16:09:35 -0400 (EDT)
Message-Id: <1c3aca73.245621fd@aol.com>
Date: Mon, 26 Apr 1999 16:09:33 EDT
Subject: Interesting Story -- _AND_ Timing...
To: bpcs-l@midrange.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 4.0 for Windows 95 sub 214
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)
Received: from blcofwo.bausch.com ([161.242.3.4]) by ccgate.bausch.com with SMTP
  (IMA Internet Exchange 3.11) id 0003B808; Wed, 28 Apr 1999 15:12:38 -0400
Received: by blcofwo.bausch.com; id PAA21971; Wed, 28 Apr 1999 15:12:36 -0400
(EDT)
Received: from kitten.mcs.com(192.160.127.90) by blcofwo.bausch.com via smap
(4.1)
        id xma018826; Wed, 28 Apr 99 15:09:22 -0400
Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by
Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id OAA15156; Wed, 28 Apr 1999 14:08:47
-0500 (CDT)
Received: (from uucp@localhost)
        by uucphost.mcs.net (8.8.8/8.8.8) id OAA21049;
        Wed, 28 Apr 1999 14:08:46 -0500 (CDT)
Received: (from majordom@localhost)
        by midrange.com (8.9.3/8.9.3) id NAA10922
        for bpcs-l-outgoing; Wed, 28 Apr 1999 13:32:44 -0500
Received: (from uucp@localhost)
        by midrange.com (8.9.3/8.9.3) with UUCP id NAA10757
        for BPCS-L@midrange.com; Wed, 28 Apr 1999 13:30:48 -0500
From: Roberto_Sehringer@GM.cytec.com
Received: from gw.cytec.com (firewall-user@gw.cytec.com [164.84.254.250])
        by uucphost.mcs.net (8.8.8/8.8.8) with SMTP id NAA18320
        for <BPCS-L@midrange.com>; Wed, 28 Apr 1999 13:12:34 -0500 (CDT)
Received: by gw.cytec.com; id OAA13353; Wed, 28 Apr 1999 14:13:40 -0400
Received: from stnt01-n2a1.cytec.com(164.84.2.16) by gw.cytec.com via smap (3.2)
        id xma013241; Wed, 28 Apr 99 14:13:16 -0400
Received: from ccMail by stnt01.cytec.com
  (IMA Internet Exchange 2.12 Enterprise) id 00127448; Wed, 28 Apr 1999 14:11:53
-0400
Mime-Version: 1.0
Date: Wed, 28 Apr 1999 13:35:39 -0400
Message-ID: <00127448.1879@GM.cytec.com>
To: BPCS-L@midrange.com
Subject: Order Status Bits ? Who, Why & When ??
Content-Type: multipart/mixed; boundary="IMA.Boundary.311323529"
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.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.