Menu
▾
▴
web-erp-developers
|
From: rfthomas <rf...@as...> - 2014-09-22 15:26:45
|
The BOM now carries a location and workcenter on each record. There should
be a header and detail for BOM's, so that the defaults for the whole BOM may
be set and maintained in one place.
Our business needs to maintain control on BOMs per US DOD, and other US and
foreign country traceability and configuration control requirements.
If by location a BOM differs, i.e. items utilized differ or manufacturing
method differs outside of certain strict parameters, then it is not the same
inventory item. The usual convention is to keep the main inventory code the
same and for this marginally different BOM, add a part revision code, a
routing code and a routing revision code. Inventory code example:
<part code>_<design revision>_<routing>_<Routing process revision>
BLISC_010_A_001
It is recognized that properly handling equivalent parts, i.e.
BLISC_010_A_001 and BLISC_010_B_120 are interchangeable items, i.e. all
BLISC_010. The customer would order BLISC_010 and higher level BOMs would
reference BLISC_010. The actual build/sale operation would then pull any
parts with a code starting with BLISC_010 irrespective of routing and
routing revision,
In any case the current BOMs.php does not allow for defaults for location or
workstation, but merely shows the first location and workcenter in
alphabetical order.
In order to have a reasonable default location, i.e. the
DefaultFactoryLocation, we have changed BOMs.php around line 705 as follows:
while ($myrow = DB_fetch_array($result)) {
if (isset($_POST['LocCode']) AND $myrow['loccode']==$_POST['LocCode']) {
echo '<option selected="selected" value="';
} else {
if($myrow['loccode']==$_SESSION['DefaultFactoryLocation']) {
echo '<option selected="selected" value="';
} else {
echo '<option value="';
}
}
The code should/could be further modified to use the loccode and code (field
name on BOM table for WorkCenter) of the first member of the BOM as the
default.
Bob Thomas
--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.
|
|
From: Dale S. <dal...@sh...> - 2014-09-23 03:45:30
|
> On Sep 22, 2014, at 9:27 AM, rfthomas <rf...@as...> wrote:
>
> The BOM now carries a location and workcenter on each record. There should
> be a header and detail for BOM's, so that the defaults for the whole BOM may
> be set and maintained in one place.
>
> Our business needs to maintain control on BOMs per US DOD, and other US and
> foreign country traceability and configuration control requirements.
Hi Bob, is your business required to meet specific formal standards? Which ones? I'm always interested in a good standards document to review! ;-)
Regards,
Dale
>
> If by location a BOM differs, i.e. items utilized differ or manufacturing
> method differs outside of certain strict parameters, then it is not the same
> inventory item. The usual convention is to keep the main inventory code the
> same and for this marginally different BOM, add a part revision code, a
> routing code and a routing revision code. Inventory code example:
>
> <part code>_<design revision>_<routing>_<Routing process revision>
>
> BLISC_010_A_001
>
> It is recognized that properly handling equivalent parts, i.e.
> BLISC_010_A_001 and BLISC_010_B_120 are interchangeable items, i.e. all
> BLISC_010. The customer would order BLISC_010 and higher level BOMs would
> reference BLISC_010. The actual build/sale operation would then pull any
> parts with a code starting with BLISC_010 irrespective of routing and
> routing revision,
>
> In any case the current BOMs.php does not allow for defaults for location or
> workstation, but merely shows the first location and workcenter in
> alphabetical order.
>
> In order to have a reasonable default location, i.e. the
> DefaultFactoryLocation, we have changed BOMs.php around line 705 as follows:
>
> while ($myrow = DB_fetch_array($result)) {
> if (isset($_POST['LocCode']) AND $myrow['loccode']==$_POST['LocCode']) {
> echo '<option selected="selected" value="';
> } else {
> if($myrow['loccode']==$_SESSION['DefaultFactoryLocation']) {
> echo '<option selected="selected" value="';
> } else {
> echo '<option value="';
> }
> }
>
> The code should/could be further modified to use the loccode and code (field
> name on BOM table for WorkCenter) of the first member of the BOM as the
> default.
>
> Bob Thomas
>
>
>
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
|
|
From: rfthomas <rf...@as...> - 2014-09-23 13:14:32
|
There are a number of standards and guidance documents. The following is an overview of the FAA requirements: https://www.faa.gov/aircraft/air_cert/design_approvals/media/CPI_guide_II.pdf http://www.faa.gov/documentLibrary/media/Advisory_Circular/AC%2021-43.pdf FDA Medical Device Quality Systems: http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/PostmarketRequirements/QualitySystemsRegulations/default.htm A search through Wikipedia for ISO9000 and AS9100 will yield links to many associated standards. The best practices are not industry specific. Traceability is required by all DOD, FAA, FDA and most tier 1 manufacturers. Our business deals across all of these. We need to maintain pedigree of all parts sold and have strict process revision control. You will see that there is a great amount of flexibility (hand waving), but one failure causes the customer to re-examine all documentation, process and quality and the vendor must generate an acceptable remediation plan to be implemented moving forwards. -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663p4657666.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |
|
From: ExsonQu <hex...@gm...> - 2014-09-23 04:02:26
|
*Hi, Bob*
I think the root reason is that we have no head data control like
PO, SO. Tim has provide a solution before although he have no time to code
it. But it cannot be found now.
I have interesting to develop it to make the BOM management more
feasible to most users' requirement.
Best regards!
Exson
--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663p4657665.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.
|
|
From: rfthomas <rf...@as...> - 2014-09-23 13:29:30
|
Exson, To implement a BOM header is straight forward. We can until the resources become available, leave the BOM table the same and add a BOMHeader table. Initially such would be used to provide static information that would be the default for the BOM table (BOMDetail) and used mainly in BOMs.php. Moving forwards, we need to put together a proposal to be reviewed of integrating concepts of traceability and revision control into WebERP. Currently, we can not readily determine which devices in the field contain items from batches or serialized items. There are times when a batch of material has defects and all items made utilizing such needs to be isolated. Examples would be faulty semi-conductors and material not conforming to material specifications, i.e. bad melt. We will investigate if there is sufficient information in the data base to answer such queries. We would like to differentiate product variations but still be able to use a minimal product code for quoting, shipping and invoice; but manufacture/purchase to a specific product revision. We recognize that there is a lot of capability and information in WebERP. Some of the items can possibly be accomplished by user discipline, proper set-up of the database, and well documented process. Bob Thomas -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663p4657667.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |
|
From: ExsonQu <hex...@gm...> - 2014-09-24 01:08:15
|
*Hi, Bob,*
Thank you for your reply.
Do you use the MRP in webERP? Do you keep the old version BOM and
know the product produced by which BOM version? Is the BOM needed to be
approved?
If these question have answers, we do not need to add a BOM
header.
Concerning to traceability purpose, webERP provide lots of
powerful traceability features. It is a piece of cake to solve the problem
what you mentioned since webERP provided lot/batch control, serial no
control even perishable control (expiry date control, there is a great
potential for this).
Currently, it's lack of a convenience script to retrieve the
outgoing lot/serial no via invoice no. But there is a workaround for this.
For a manufacturing company, the currently urgent issue is to make
BOM more controllable and traceable.
Best regards!
Exson
--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663p4657668.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.
|
|
From: ExsonQu <hex...@gm...> - 2014-09-24 01:16:43
|
*Dear all,*
According to the email from Tim, I've retrieved the discussion about
BOM enhancement. Following is the link:
http://weberp-accounting.1478800.n4.nabble.com/Bug-MRP-for-WO-at-reqdate-instead-of-startdate-td4651206.html#a4655134
<http://weberp-accounting.1478800.n4.nabble.com/Bug-MRP-for-WO-at-reqdate-instead-of-startdate-td4651206.html#a4655134>
It's a wonderful idea!
Best regards!
Exson
--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663p4657669.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X