Tom
Costs are accumulated by default into the material costs. This is
controlled in the EPDM control file. As an option, you can define one of
the user defined cost "buckets" as outside operations and accumulated them
in their own cost bucket.
Yea, no system works without data integrity. The biggest issue there is
managers lack of attention to process control.
Funny how manufacturing companies constantly give lip service to process
control (Lean, TQM, ISO...etc.) but have such difficultly applying it to
their overhead processes.
Kevin
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tom E Stieger
Sent: Tuesday, December 01, 2009 7:41 AM
To: mapics-l@xxxxxxxxxxxx
Subject: Re: [MAPICS-L] PO vs MO
Kevin-
Thank you for this well written example of using outside operations. We
looked at using this several years ago and ended up doing nothing to change
are current practices. One of the concerns we had was the change in where
the cost for the MO got accumulated. Currently we have the "service" items
as a part of the BOM and when we need a service we create a PO for that
service item receive that service item into stock and then issue it to the
MO. This places our costs associated to the service in the materials
section. With the Outside Operations configured where do the cost go, into
the operation or as a Misc. Charge to the MO?
The other concern we had was lack of data integrity so the automatic PO
creation wasn't going to be trusted therefore removing any benefit.
-Tom Stieger
Engineer
California Fine Wire
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Kevin Fox
Sent: Tuesday, December 01, 2009 7:18 AM
To: 'MAPICS ERP System Discussion'
Subject: Re: [MAPICS-L] PO vs MO
Todd,
There is a built in feature for outside processing with XA. As of R6 you
can download a PTF that will give you this function (called Outside
Operations!). If you have applied the latest PCM's and are at the latest PTF
levels for R6 it should be there. R7, R7.5, R7.7 and R7.8 have this
function already included in the code.
You can access it from EWP (or god forbid: green screen) by navigating to
Production Control and Costing (PCC), then select the outside processing
menu. There are two menu options. The first option "Work with Outside
Operation Details" allows you to set up the relationship between your
production operation routings and outside processing vendors. The second
option "Work with Outside Operations Cross Reference" allows you to work
with active open outside operations.
Here are the basic setup tasks.
1. Create a production router that includes a properly defined outside
operation.
For example.
Operation Seq: 0010 OP Laser Cut & Shape Facility: OP001
Operation Seq: 0020 Inspection Facility: IP010
Operation Seq: 0030 Form on Brake Press Facility: 78343
On the outside operation: (as above operation 0010) set the time basis code
to "C" = Outside Processing. Be sure to put the piece part cost into the
outside operation cost field.
Enter the number of move days required to pack, ship, process, return ship,
and accept the operation.
2. Create a service item for the Outside Operation Laser Cut.
For example:
We are going to make a formed metal part number: 123456
The outside process item "number" will be "OP Laser Cut"
Be sure to set the inventory code to "3=Service" Also, you should enter a
purchase price, and default unit cost.
3. Be certain to have a vendor master record setup for the vendor that
provides the laser cut service.
4. Now you are ready to setup the defaults using the "work with outside
operations details"
Site: = Site ID for your production facility (assuming EPDM)
Vendor: the number of the vendor in step 3
Warehouse: the production facility warehouse ID Finished Item Number: the
item that will be produced on the Mfg. Order.
i.e. 123456
Revision: the revision id of the finished item number.
Routing ID: The id of the production router defined in step 1 Routing
Version: the version of the routing defined in step 1 Service Item Number:
the item created in step 2. i.e. OP Laser Cut QTY/COST Update: Select the
option that supports your costing and variance calculations methods.
Preferred Vendor: Select the option that will default the preferred vendor.
P.O. Create at MO Release: Select the option that supports your processes.
(Just a personal note: if you don't select option 1 you are wasting a
tremendous opportunity at reducing non-value added time.) Release Time
Fence: Number of days in advance that you want to create the PO Lead Time
Purchase: enter the number of days the vendor quotes. Note that this should
be part of the move days added to the operation as in step 1.
Lead Time Adjustment: enter the number of days to go from dock to stock.
Note in my example you would NOT include inspection time as that is a
separate operation.
Auto Release Code: Select the code that matches your business process.
Again I like #3
Operation Status Completed.....: Select the option that matches your
variance accounting.
Additional Descriptions to PO Comments: Select this to print your operation
additional descriptions on the PO (WOW!).
Now...
Release an MO for 123456 and watch as you automatically generate a PO to
your vendor for OP Laser Cut operations.
Note you must receive against the PO AND the MO operation to effect good
count control.
A note to all on the list: This actually solved my problem submitted two
weeks ago. I just had to create an alternate BOM to list only the supplied
parts to the vendor. PERFECT!
Kevin
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Todd Ivy
Sent: Tuesday, December 01, 2009 5:33 AM
To: MAPICS ERP System Discussion
Subject: [MAPICS-L] PO vs MO
Hello All, A while back there was a discussion going on about outside
processing and inside processing. At the time, I didn't think it pertained
to me, but as always, it has come up. We have always had outside processing
for assemblies/weldments, but now we are using outside processing as well as
some inside processing to manufacture a single component. For instance,
when we cut parts from stainless steel, we send the metal out to be laser
cut into shape. Then we get the part back and send it through the press
brake at our facility to put a bend. Obviously we have to pay for the laser
cut, but dont want to execute a purchase receipt because we have a work
order for the bending that will also close out and add a qty to stock. Thus
giving a double receipt. How do you guys do this? I am almost sure this
was discussed a bit a few weeks ago, but I seem to lost the conversation
while purging my outlook. Any help is appreciated.
Todd Ivy
TYMCO, Inc.
225 E. Industrial Blvd
Waco, Tx 76705
T:(254) 799-5546 Ext:389
F:(254) 799-2722
www.tymco.com
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a
message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/mapics-l.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a
message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/mapics-l.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/mapics-l.
As an Amazon Associate we earn from qualifying purchases.