Have you ever heard about mis-communication between the production scheduler and the sales department? The availability check with its rules and conditions is the link. I am mainly talking about order entry here, but, of course, the forecast and setup of MTO vs. MTS are two more areas of friction between sales and production - unnecessary if the right strategies and configuration to support those are in place (an educated user who can execute the functions well, must be the most important part of the whole).
Now when you enter a sales order into your SAP system, it represents a demand for a sellable product. The sales order is looking to get product from somewhere, so as to fulfill a customers desire to increase your revenue. The sales representative can not possibly understand why the company s/he works for would not deliver the product right away or wouldn't do anything to fulfill the request asap. But there are other goals: a supply chain that is as waste-less as possible, low finished goods inventory, high production utilization, low production cost and a smooth, undisturbed production program. Unfortunately these goals - and the Sales Reps mission - are usually not in line.
In SAP the availability check is using a rule and may be different depending on the business transaction you perform. In other words: a Sales Order may check differently than a Production Order. The rule by which the check is performed can be assigned in the material master and therefore can differ from one product to another. This rule, together with the fact that you create a Sales Order, form the framework within which delivery dates with the customer are agreed upon.
As an example: if a customer wants 50 pieces but there are only 30 in inventory, the availability check finds out for you when the company is able to deliver the goods. In its simplest sense the additional 20 may be delivered after the time it takes to bring them back or at the date when we receive the next batch from production. This is the difference between checking with or without replenishment lead time.
In the checking rule you can identify what stocks - safety, blocked, restricted - are to be included in the check. It is also possible to specify whether planned orders (firmed or all), production orders, requisitions and/or purchase orders are used to determine the availability date.
As you can see the choice is ours what we let SAP automatically determine as the date we tell our customer, when they can expect the goods. But there seems to be a problem. At least I see that quirk everywhere I look: the sales rep is on the phone with the customer entering an order and the availability screen says "you can have 30 pieces today and 20 pieces next week Tuesday." "Great" the customer says and the sales rep saves the order without fixing the date.
Not fixing the date has no meaning for the sales rep but in MD04 the entire order of 50 pieces stands with a requirements date of today. That means a red light and a signal to the production scheduler to make 20 pieces... NOW ! And tomorrow it means Now! And the day thereafter too. And the customer does not expect the 20 pieces before next Tuesday and is quite happy with that (in the end he won't get them before next Tuesday anyway).
Would the sales rep have checked on the fixing, we would have seen a delivery for today and another one for Tuesday in MD04 and production would have executed that order, which the availability check saw. The customer would have received what they were promised and the world would have been a little bit better place to live.
It is incomprehensible to me why companies don't have a policy in place that supports better practices when it's so easy to do. Instead people fight you to the end to not fix the date. I have no clue why but I have customers with whom I have been discussing this issue for years and they still don't do it or only with much reluctance. "What if I have it available earlier ?" they ask. So you really want to have hundreds (if not thousands) of false delivery days per week disturbing your production program, in exchange for that one time chance to deliver on Monday instead of Tuesday? And even then... it's an exception... and those are meant to be handled manually - not the rule.
Of course, if your availability check produces false results because your basic data setup is incorrect or you mix up MTS with MTO, then you have to do something else and can't fix the date. However, in that case we have to take a couple of steps back and are not ready yet to have production and sales sing to the same song...
SAP Mentor, supply chain management enthusiast. Advocate for science as a basis to optimize the SAP supply chain. Active in Europe and North America. Sailboater, private pilot, motorbiker. At home in Tribeca, NYC. The opinions expressed in this blog are mine!
Tuesday, July 24, 2012
Friday, July 6, 2012
MTS, MTO, ATO, CTO, ETO… Strategies to connect Sales with Production
The interface between the Sales and Production departments
is a critical one. Very often the two departments work in silos. All strategies
discussed here, are at the crossroads between demand and supply. It is a goal
to be agile and fulfill every customers wish on time and on quantity, but it is
also important to minimize waste and enable smooth replenishment and
production. Proper use of the planning strategy helps achieving both goals.
A big problem, one that I encounter a lot, is that products
are not optimally set up for either one of these strategies. Either the wrong
assignment happens, or Production has a different idea than Sales, about what
the product assignment should be. Additionally there is the need to
periodically analyze the product portfolio because what’s MTO today might be
MTS tomorrow.
The ultimate achievement, one that both Production and Sales
strive for, is to have the right product at the right place in the right
quantity at the right time. Planning strategies are one of the most important
drivers to achieve exactly that.
Make To Stock Planning
When your product is a commodity that can be sold out of a
catalog and is defined and specified through a master record, it can be planned;
if it is somewhat predictable. A steady consumption in the past helps
predicting the future, however, there may be events in the future which require
a more forward-looking planning process.
In any case, if you can somewhat predict what will happen,
you may consider a Make To Stock strategy. Even if it is hard to predict the
future, but the customer does not accept long delivery times, you might be
required to make some of your product to stock.
Making to stock means production without actual
requirements. The Sales Order does not drive the production program but the
forecast does. Incoming Sales Orders use existing inventory for the delivery
which keeps the customer lead time to a minimum.
Once your product is identified as a ‘Make To Stock’ the
availability check in the Sales Order must
look for inventory and not place additional load in the production program. If
there is no stock your service level degrades and the customer needs to wait
for the next receipt from production.
Disconnect between
Sales and Production #1: the “customer is king” paradigm does not have
any validity in an MTS scenario. If you want to make the customer the king you
need to make your product to that customer’s order.
Make To Order Production
This strategy still is for standard products which have a
clearly defined specification. Other than MTS, there is absolutely no forecast
on products which are made to an order from a customer. You start production after the customer’s request comes in
and not, like with MTS, beforehand.
When you identify a product to be made to order, the availability
check in the Sales Order needs a lead time; the time it takes to replenish or
produce the product from soup to nuts. Therefore when a customer requests the
item, no freely available stock to fulfill the order can be found. Everything
is made from scratch and takes its time.
Disconnect between
Sales and Production #2: You cannot plan for a 100% (or more!)
utilization on the production line and allow for the free flow of orders, which
were set to MTO, into the production schedule. All too often there is pressure
to fully utilize the line; and that can only be done with orders resulting from
a forecast. If MTS fills the line and MTO orders drop on top, they fall into
backlog and the quoted lead time to the customer is a farce.
Assemble To Order or Finish To Order with placement of the Inventory/Order
interface
This type of strategy allows for a placement of a stocking
point, the inventory/order interface, at the most effective spot in the product
structure. What this means is that you can decide at what point in the BoM,
material is kept in stock readily available for further processing. Therefore upstream
of the inventory/order interface we are making to stock and downstream from it
we are pulling to order.
This also means that downstream from the I/O interface we
have lead time to the customer whereas the availability check does not need to
consider time for the processes upstream from the I/O interface.
ATO provides flexibility, speed and helps reduce waste.
Other people would say its agile and lean at the same time.
Disconnect between
Sales and Production #3: Assembly strategies have the capability to
generate a production order to assemble the finished product right out of the
sales order. As this happens, the system can also check on component
availability and if there is a shortage, it can provide a reasonable date for
when the finished product can be delivered. If that date is not fixed, and I
have not seen a Sales person fix a date yet, production scheduling is burdened
with a demand for today… and tomorrow for tomorrow… and so on and so forth.
Please take a moment to think about what is done here: the Sales Rep agrees a
date with the Customer who would be quite happy to get the product on that date
in the future. However, that same Sales Rep tells the Production people that
the product needs to be available right away. Consider how many orders there
are and that this pressure pops up every day from now on until the order is
delivered, you can easily see that there is room for improvement in the communication
department.
Configure To Order
When a standard product has variations in its specification,
one needs to answer the question whether to create a material master record
number for every variation or to make use of the variant Configurator. In case
the VC is used, an underlying structure will have to be build, which allows you
to configure a variation of one (configurable)
material number based on features and options. The underlying structure has optional
values and characteristics that have dependencies and limitations. Be cautious to know that In the same way that
there is a line where it becomes more efficient to use options and
characteristics to build a spec, there is also a line where it becomes more
feasible to use a whole new project to build a complex product which has never
been built before; or in other words: to build the underlying structure with
features and options and dependencies becomes far too complex.
So there is an upper limit as well as a lower limit in
complexity where Configure To Order has its right to exist.
Configure To Order is a strategy that closely resembles MTO
or ATO for the finished product and components can be made to stock using a
forecast based on probability factors maintained for options and features.
Engineer To Order
The Variant Configurator most always fails when that fine
line was crossed where ETO should have taken over! It is not the lack of
functionality and features of the VC which make it fail, it is mostly that the
VC is used for a structure where projects and work breakdown structures would
much better suit the handling of the complex product or structure in question.
Engineer To Order is used when complex structures are build.
In most cases these projects organize many tasks and follow a long timeline to
produce large, highly customized products to specific customer specifications.
The finished product, and also many components and subassemblies, have never
been built before and receive brand new product codes. Work Breakdown
Structures and Projects are used to structure and manage the procurement of
long lead-time purchased parts, the dependencies in production and procurement
and cost and timely delivery of the final product.
All of these strategies have many variations. What was
discussed above is just a generic description. A more detailed discussion is to
be had around SAP planning strategies where there are countless combinations
and opportunities.
…so here is a summary of my view on these strategies on a
very generic level.
MTS: standard
product made to a forecast before
any committed orders come in
MTO: standard
products not held in inventory and made after
a committed order comes in
ATO: standard
product where some components are held in stock and the finished product is
finished after the order comes in
CTO: The standard
product has variations; as many as not to justify the creation of a part number
for every variation but not as many as to make the underlying structure too
complex to handle
ETO: complex structures and customer
specified projects which were never built before and make it impossible to be
handled with standard variations
Subscribe to:
Posts (Atom)