RE: Shop base Manufacturing

> I>  From:     b_holden@csisystems.co.uk (Bruce Holden)
>   
> >  It does provide full traceability if you use the "Generate Shop
> Order"
> >  flag in Item/Facility Planning Master. 
> 
>          [Al Macintyre]
> Are you referring to CIC = Item Planning/Costing File which is
> maintained by 
> MRP140 Facility Planning Maintenance Update in which F1 Help
> inconsistently 
> labels CIC in places as Item/Facility File?
> 
> We are on 405 CD & I looked through CIC without success seeking such a
> flag.
> Is this V6 or an add-on to BPCS?
> 
        Al - I originally responded (before I saw your correspondence)
to a request from kcthai@nemic.co.,jp who is about to implement BPCS and
had some general questions. My reply was therefore succinct. The
"Generate Shop Order" flag exists in Item Maintenance (INV100),
IIM.IMGSOR, and Facility Planning Data (MRP140), CIC.ICGSOR. This
certainly exists in V6 but I don't know prior to this version.

> I did not see a single file called Item/Facility Planning Master
> I really wanted some way to list files by title(text) to simplify the
> search, 
> but settled for WRKOBJPDM OBJTYPE(*FILE) OBJATR(PF*)
> 
        Al - I was referring to 2 progs/files - see above. There is an
SSA internal support programme (Windows) called BPCS Database Viewer and
some Access/Excel programme and file lists that could help you here -
again I have them for v6. I do not know whether these are available for
4.05CD or if they can be released to users. It may worthwhile contacting
support.

> >  This automatically generates top level shop orders 
> >  as an automatic consequence of accepting the customer
> >  order for that item(s), and is cross-referenced back to it. It is
> then
> >  possible, according to the same setting for sub-assembly items, to
> >  generate multi-level shop orders down to the required level, all
> >  cross-referenced to parent shop order and original customer order,
> and
> >  complete with an enquiry to allow full visibility of the generated
> tree.
> 
> Our top few levels of items use the customer part number then same
> number but 
> some additions, for ease of correlating item identification with
> inquiries 
> from customers.  I could see value in doing this for some customers
> whose 
> needs are rather volatile, with short lead times (for the customers)
> in which 
> we have sufficient safety stock to support this behavior.
> 
> Lower sub-assemblies use number systems common to many customers &
> families 
> of products.  They make sense to continue via MRP.
> 
> 
> >  There will be some differences to your current working practice as
> the
> >  comon reference all the way through here is the originating
> customer
> >  order but I would not see that as a problem. MRP may be used
> alongside
> >  this routine for batch production items.
> 
> My interest is in performance, ease of flag throwing, seeing which way
> a 
> multi-level customer part is set for, and nothing falls through the
> cracks.
> 
> Right now we run full regeneration MPS MRP every week night for all 
> facilities & sometimes do net changes at mid-day for individual
> facilities.  
> I am thinking that we might want this feature for selected items for
> selected 
> customers, or use our own internal resupply orders to test the
> feature.
> 
> But if we tended to switch parts between normal MRP & this deal, we
> would 
> want inquiry to show full visibility of the tree of sub-assemblies
> that are 
> coded to be launched this way as soon as a customer order comes in,
> and any 
> non-common components that are not coded consistently with the other
> branches 
> of the tree.
> 
> Al
> 
        Al - The generate shop order flag cannot be varied by customer -
it is by item/facility. After accepting the customer order a top level
shop morder is automatically created. To generate further levels you use
SFC530. If the flag is not set on the top level item you can also create
the SO manually, then so long as lower levels have the flag set use
SFC530 as before. Note that it always creates the customer order
quantity and takes no account of inventory. The enquiry is SFC330 and
only looks at generated shop orders. To see the tree before SO
generation would be a 2 stage process i.e. enquiry to identify orders to
be generated then enquiry to see the tree on selected products say using
Indented BoM in BOM300.

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