SAP SCM Info

About Supply Chain

2012-01-24T13:07:00.002+01:00

Operations Management 919 Slides Presentation

View more presentations from Hardeep Kumar

Theory of Constraints (TOC) Overview: A SAP Approach

2012-01-10T15:20:00.004+01:00

Key factors with respect to manufacturing are speed , reliability andcapacity.

Manufacturing normally suffers from:

· Poor on-timeperformance

· Longproduction lead-times ; big batch sizes1

· High WIPand/or finished goods inventory

· Highovertime due in-efficient labour utilization

· Excessiveexpediting and rescheduling

· Wandering orstationary bottlenecks

· Inability toabsorb additional market demand

The above deficiencies have a serious impact to a organization financialefficiency.

The Theory of Constraints maintains that every system is subject to atleast one constraint, which prevents the system from achieving infinitely highlevels of performance. In order to improve/optimize manufacturing efficiencythe Drum, Buffer and Rope (DBR) concept will be applied to:

1.IncreaseThroughput ; throughput KPI = Sales - Material costs

2.ReducingInventory ; raw materials , wip and finished products

3.Reducingoperating expenses.

The above 3 critical KPI have a major impact on Productivit

Process and TOC focus.

Anorganization main processes are Plan,source, make and deliver. Within theseprocesses there are constraints that if not exploited or synchronized willimpact productivity. This will be overcome by carrying out the following TOCsteps.

FundamentallyTheory of Constraint is mainly a strategy/approach/technique to focus oneattention to winning, maximize throughput resulting in higher productivity andprofits. Focus on what is critical, the rest is secondary.

The keypriorities to be managed:

1. Throughput;ensure the highest possible throughput of the system

2. Inventoryreduction; ensure optimum level of raw materials and work-in process as well asfinished products

3. Operatingexpenses

The focus wrt of the various posts and specifically around exploiting SAPwill be around throughput and inventory.

FIVE STEPS OF TOC

STEP 1:Indentify the constraint.

Find the one element of the manufacturing systemwhich limits the system's ability to achieve its goal. In most manufacturing.Basically identify what limits the system performance.

Very important to consider that a process isgoverned by:

· I Input ; components/raw materials

· C control ; policy , methods , shift, set-uprequirements; tooling

· M Mechanism; the actual manufacturing machine thathas a rated capacity

· Output the manufactured item (semi or finished product)

Refer to: http://sapscminfo.blogspot.com/search/label/Optimization

System constraints can beeither physical or policy. Physical constraints are relatively easy to identifyand relatively straightforward to break. Policy constraints are usually moredifficult to identify and break, but they normally result in a larger degree ofsystem improvement that the elimination of a physical constraint

STEP 2: Decide how to exploit the constraint .

Once the constraining has being identifiedunderstand how to exploit the constraint, that means squeezing the most out ofthe manufacturing constraint in order to attain maximum performance. Thereforeconsider all aspect around the process:

· Policy and procedure

Tooling, set-up equipment, set-up matrix

· Planning and execution system; ERP , APS ect...

This must be done without major system changes orcapital improvements with the primary objective of eliminating inefficiency from the constraint

STEP 3: Subordinate everything else to the decision in step 2.

Take the required steps to synchronize and alignthe performance of all other elements with the "exploited"constraining element. This may mean slowing down "faster" parts andspeeding up "slower" ones.. If you're constraint is broken at thispoint, go back to Step-1 and start looking for the next constraint (nextweakest link in the chain). If not, go on to Step-4.

Fundamentally make effective management of the existing constraint the top priority

STEP 4: Elevate the Constraint.

If the constraining element still remains thereason why the system's performance "tops out"; then"Elevate" usually means doing something to increase the capacity ofthe constraining element. Obviously, if your constraining element is running atmaximum efficiency (which it should be after Steps-2 & 3), the only wayto improve overall system performance is to obtain more of the constrainingelement. In a manufacturing environment, this may mean a capital investment inmore equipment, or hiring more people, or increasing work-ships.

STEP 5: Go back to STEP-1, but avoid "INERTIA".

This is the "repeat Steps 1-4" step.But the warning about "inertia" is important. It's designed todiscourage complacency, thinking that the environment doesn't ever change muchover time. Always consider that throughput increase can create other weakerlinks that previously were considered as secondary.

Subordinateeverything else to the decision in step 2 based On Bottleneck Drummer

When itcomes to subordinating everything to constraint, its bottleneck(s). In aproduction environment, the plant's constraint must be the driving factor inhow it is managed. In production, the productivity of the constraint is theproductivity of the entire plant.

A provenapproach to managing production through the constraint is known as"Drum-Buffer-Rope" and "Buffer Management."

· Drum - Theconstraint(s), linked to market demand, is the drumbeat for the entire plant.

· Buffer -Time/inventory that ensures that the constraint(s) is protected fromdisturbances occurring in the system.

· Rope - Materialrelease is "tied" to the rate of the constraint(s).

The drum,buffer, and rope provide the basis for building a production schedule that ishighly immune to disruption, avoids creating excess inventory, and uses smallbatches to minimize overall lead time.

But evenwith "Drum-Buffer-Rope," (DBR) occasionally disruptions occur thatrequire special attention. "Buffer Management" is used to mitigateand often prevent those disruptions.

The DBR methodology is Theory ofConstraints that will be used to maximize production throughput and inventoryreduction based on the constraints (weakest link) being the DRUM, the BUFFERbeing the inventory needed for the constraint and the ROPE the timing forreleasing the buffer with the main aim of protecting the weakest link an thusmaximize thus overall effectiveness.

Benefits of TOC

The primary benefit of the TOC approach is its orientation toward the outputof the entire system to maximize throughput (sales, billing), rather than acompartmentalized look at components which may have little or no positiveeffect on overall performance because of that "elephant in theparlor"--the system

Traceability in complex Supply Chain structure

2011-12-02T18:13:00.022+01:00

Traceability within a Complex Supply Chain flow and Distributed System Architecture (multiple EWM systems) and multiple software platform (SAP ERP, TM, legacy ect…).

OVERVIEW:

Organization’s require traceability either due to legal requirements or due to quality control requirements.

Traceability normally consists of defining detailed characteristics of a handling Unit and it its product, batch characteristics (expiry date, certificate ect..) and as well tracking across their micro (within plant) and macro (extra plant) supply chain.

Furthermore, in most cases traceability data must be kept for a number of years and must be available even though data has being archived. Further complexity is to be able to track within the pipeline based on specific characteristics such as batch number, mould number to determine its location and its association (production order, sales order )

Most organisations have complex supply chain flows, they can normally be within plant flow where batches / Handling units are received and processed across multiple steps. The characteristics of the batch and Handling unit may change as they are processed through various nodes of the supply network. Typical example would be temperature controlled items, expiry date ect…In this physical flow from a Micro physical flow.

Micro Flows

Furthermore, a Handling Unit can also be processed externally across multiple Supply Chain Units, across many organisations units such as other distribution centres, customer etc..as show in the macro physical flow.

Macro Flow Physical Flow

The above Supply Chain flows may also be supported by distributed IT network that are managed by individual SAP systems such as ECC , EWM and TM systems as well as legacy system. In each of these system there are processes that are specific to their relevant supply chain and have to be tracked. There are further situation where macro flows jump from one system to the other. Typical example is a Handling Unit produced and processed in one plant that is manage in System X, it then is sent to another plant via ship, the shipping is managed by system Y and eventually received in relevant plant system Y.

These multiple system creates a traceability dilemma in that having a single point view with respect to traceability becomes a serious problem.

Traceability update

This can be resolved with a centralized traceability system where its update is based on update rule from the various system. Update rule must contain the relevant event’s that should update the traceability system. This can be when a handling Unit is received from production, the traceability system will then be updated with the handling unit characteristics , its relevant status and its process status. An update rule could apply if handling blocked by quality department.

The ability of updating characteristics allows tracing of handling units based on characteristics of the Handling unit. The traceability not only will provide a full history of its process events and the latest status.

SOLUTION

Having provided a view on Supply Chain complexity with respect to Traceability and technology elements that are present in a complex supply chain, the solution would be a single point of data storage and extraction (reporting). This can be done by using SAP BW whereby traceability data is stored in relevant cubes and can be updated via updates rules from multiple systems.

The traceability system will be updated from the various system based on common updates rules defined for relevant process events that are critical for traceability.

The fundamental design requires two critical definitions:

The characteristics of the Handling Unit. In the definition of the characteristics it is imperative to define the critical key data elements that need to be maintained in the traceability. The data elements will be critical for tracking and reporting. From a reporting perspective data elements such as batch number, usability of the batch, tool number, certificate ect..This will then allow searching for related HU, example; search for usage of HU that was manufactured by a specific tool, or search all semi finished product HU where in put product was part of a specific batch.

The update rules that will update the characteristics; only key saupply process need to be controlled and updated in the traceability system. Typcial update rule if when HU is born, when received from production, when shipped out to another manufacturing plant.

The update of the centralized traceability system will then provide a central repository system that will contain complete flows thorough supply chain. This system will also provide status of each Handling unit and will allow the relevant user to take the required action should need arise due to specific requirement. Possible example relates to pharmaceutical environment where due a specific batch all Handling Units have to be traced through its pipeline. The traceability system will also provide a multi dimensional flow from raw materials, to semi-finished to completed manufactured item. This is critical should search for a specific batch of a raw material right through its usage up their final state (finished product).

The above shows how the traceability system is updated via the update rule as a Handling Unit is processed through the supply chain.

Although RFID system may provide this kind of traceability, it will still have a narrow views and will not have the flexibility of a custom traceability that one can define characteristic unique to one’s business.

Supply Chain Performance Management

2009-09-22T14:40:00.003+02:00

This post is an extract of a project related to implementing BI at a Automotive Parts Manufacturing.

In order to effectively manage the Supply Chain, it is critical to obtain quality KPI in order to ensure that business objectives are being achieved, but more important required improvement’s can be identified and executed. Avoid the ‘so what KPI’.

Therefore SCM BI are fundamental to monitor and continuously optimize the Supply Chain, quality data allows for effective and rapid decision´s to carry out change.

In a manufacturing organization, just looking a inventory level and customer service on its own will not ensure that the specific weakness are identified so that relevant improvements can be initiated. In this scenario; taking factory capacity, manufacturing change-over rate, inventory levels, and customer service will provide a clear picture. Trends in high capacity utilization, high inventory and low customer service indicates that either the wrong product is being produced or the batch size produced is too big (low change over, because of large batch size not enough capacity available to satisfy customer requirements). With this information a more objective decision can be made for improvements which could result in improvements in planning methodology(IT and process problem) or modify factory tooling (physical problem) to allow quicker change over, or reduce batch size. Any one of these actions can actually worsen a specific KPI, example factory capacity, why ? Lower factory utilization capacity (capacity KPI on its own is own provide a poor KPI) means that manufacturing equipment are not churning out at its maximum, this could be due to higher product cut-over due to shorter batches, but the trade off would be lower inventory and higher service level. This means that one is getting higher cash throughput (capacity KPI, linked to inventory and service level provides a more realistic/value KPI). This is what business is about (The Goal). When this happens certain KPI become secondary by achieving total SCM benefit and not individual benefit like factory capacity.

If one had just Inventory and Customer service, one would be limited in trying to optimize stock levels without understanding the causes.

In order to define optimum SCM Performance Management KPI for a Business Intelligence System (BW) , the following cardinal rules apply:

• Define
Important to define the KPI that will measure performance in the Supply Chain, critical to understand performance versus plan and KPI’s that can provide meaningful data for rapid improvements.

The scope of KPI must provide required details to relevant BI Customer (Financial controller, Factory Manager , Supply Chain Manager ect..)

The scope of KPI relate to two key aspects:
 Width, how many KPI’s needed for BI customer, example for Factory Manager would require different KPI to SCM Manager, the SCM manager would look at the total integrated KPI of plants while the factory Manager a more limited picture, Factory Manager might be indifferent to Customer Service , but more on Factory Capacity
 Depth entails the meta data available to BI customer, a SCM Manager with respect to Inventory levels might require classification based on slow moving, expired, quality (certain products might be out of specification but can still be sold). This level of detail allows SCM Manager to initiate relevant actions to reduce inventory. A Marketing Manager might require classification based on brand, product introduction ect…

• Measure
In order to satisfy the KPI for the relevant Business Customer, data may be sourced from multiple system’s and applications. It is critical for the technical efficiency of a BI system to avoid duplication of extraction and update to the relevant info cube and multi cube’s. Obviously an organizing that has achieved homogenous (IT systems and process) ways of working will simplify data extraction. Knowing the bigger picture of scope of the KPI allows simplified and efficient extractors as well as the BW design (info cube, info sources ect..).

Dimension and time buckets must satisfy the BI customer. A Factory Manager is interested in a hourly view of critical bottleneck resources, while a SCM Manager interest might be limited to daily view (More SOP orientated)

• Analyze
The KPI must be simple and provide quality, better 10 quality KPI rather than 50 KPI. They must provide trends, graphs are critical, they must flag abnormalities based on specific baseline predefined by BI customer. The scope of KPI must enable decision that can improve efficiency and reduce costs. Graphical information is fundamental to provide view of data that enables better understanding of the situation. A graphical view to SCM Manager in a single graph containing Factory Capacity, Inventory Levels and Customer service provide an ideal snap-shot. A single view of Customer Service level provides the ‘so what KPI’

• Improve
The KPI provided can then be the stepping stone to initiate change and improvement by the relevant BI customer. Important that the BI tool allows for flagging the start an improvement/change/optimization so that benefits can be measured.

The difficulty of the above is to extract data considering that source can be R3 data or SCM APO platform consisting of BW Cube for demand planning, planning areas in SNP, order based data in gATP and PPDS versus simple tables in SAP R3.

Consideration must be give to multi-cubes to mesh data coming from SAP R3 and APO data sources (info cube) considering the interrelationship between the two systems.

Building a BI platform using APO PPDS as base will be discussed in a later post.

Advanced Inventory Optimization with SNP

2009-09-16T14:36:00.002+02:00

The optimum inventory balance would be managed via combination of the following key factors and elements driving the level of inventory and supply chain costs:

- buffer stock (safety stock) needed within the market to avoid potential Stock-Out caused by adverse effects of forecast errors and supply chain underperformance

- stock availability or customer service performance required to ensure customer satisfaction with their order fulfillment
- DRP planning parameters driven by manufacturing or 3rd party suppliers costs associated with the inventory (inventory value, storage costs, shipping costs, financial interest of holding inventory etc)

Safety stock is a function of all these factors. To make things more complex, all these factors are interrelated.

At the item level, there are some immediate obvious sources of error and uncertainty:

► Forecast error – the worse it is, the more safety stock you need to cover the uncertainty.
► Production batch size – the larger it is, the less often the stock will be low.
► Production reaction time – the longer this is, the greater the time over which the uncertainty has to be managed.

► Customer service level – the higher this is, the greater the safety stock needs to be.

The APO SNP provides a number of techniques to optimize inventory.

The current offering consists of:

► Standard Safety Stock Planning
► Extended Safety Stock Profile

Details can be found in http://help.sap.com/saphelp_scm2007/helpdata/en/1c/4d7a375f0dbc7fe10000009b38f8cf/frameset.htm

Should the above not be suitable, the custom approach can be adopted using advance marco functionality available within the SNP Planning Book.

A particular example wrt to inventory optimization is where SNP planning book was enhanced to manage a complex safety stock formula based on Robert G.Brown instead of using what is available in standard SNP.

The above formula shows safety stock is calculated based on:

Safety stock formula:
LT = Supply Chain Lead time (Total = Production + Transit , and expressed in months)
SR = Std. Deviation over production reaction time
BS = Batch size (Expressed in units as Production Minimum Order Quantity)
CS = Customer Service Level (shown as percentage)

Weighted forecast error calculation

F1 to Fn = Forecasts for weeks 1 to n (13 periods will do), for selected forecast types. The current average forecast over the next three months is.

 AF = Average Monthly Forecast = (Sum (F1 to F13)) / 3

An ‘average’ forecast error determined by SKU.

 WE = Weighted error

The previous 2 years Forecast accuracy percentages by SKU will be exported as 24 discrete monthly values.

The optimal inventory calculations require a single value of forecast error per SKU. The forecast error is defined as follows:

Forecast Error = 100 – Forecast accuracy Percentage.

That is an accuracy of 85% equates to a forecast error of 15%.

The functionality provided allows the error to be calculated on the last six months accuracy figures. The weighting is configurable. A higher weight is likely to be given to the more recent forecast error.

STEP IN BUILDING THE SNP OPTIMIZATION TOOL

The possible approach would be to use would be:

1. Copy standard SNP supplied Planning Books into Custom Planning Book

2. Add the required custom key fields, custom fields depends on how the macro calculation are carried. If standard macro functions are used then more custom key figures will be used. In the SNP planning, limit the additional field to Safety Stock only and use macro to calculate desired stock levels, other key figures like service level and forecast accuracy can be included for reporting purposes and for macro function to facilitate user mgt. Also handy for alerts. These key figures will be loaded from custom DP planning book which contains the guts of Safety Stock Calculation using Process Chain.

3. Create DP planning book with custom fields (key figures) to contain the fundamental fields needed for SS calculation. The number of Key Figures will depend on using SAP supplied macro’s functions or reducing Key Figures using custom built macro function (see http://sapscminfo.blogspot.com/2008/10/custom-macro-functions.html) The advantage of creating custom DP planning book is that it provides maximum flexibility and does not have the SNP constraints and simplifies the import from BW to the relevant key figures. Note it is possible to load data from DP planning book to custom SNP using the Process Chain mechanism to Load data from DP Planning Book to SNP planning on a regular basis. This custom planning book will import from DP planning books data such as forecast accuracy.

Concluding remarks: If implementing SNP with release SCM5.1 onwards, then priority would be to exploit the standard functionalities for advanced safety stock (ASS) planning. The ASS allows for the creation of profiles containing rules such as:

• Forecast Error : Percentage to correct demand forecast

• Determination of Replenishment Lead time rules

• Demand type, sporadic or regular demand

• Source determination

• BADI’s (very important to enhance logic) BADI for custom formula’s, replenishment lead time and forecast error.

SAP SCM Project Opportunities during economic crisis

2009-06-10T17:21:00.017+02:00

We are currently experiencing the worst economic crisis seriously impacting the IT SAP (basically all Software packages) consulting world. Some of the big five consulting companies have allowed a large percentage of their work-force to take a 2 year sabbatical, this implies that they only see a upturn in late 2010 early 2011 (most probable 3 quarter of 2011). This is also logical considering that IT projects lags’ 6-9 months the economic upswing.

This downturn implies over-supply of IT resources exceeding demand, rates have dropped to 50% of 2008, and some consulting companies are providing 2 for 1 especially the (small consulting companies). Even at these reduced rates IT investment is not taking off. The reasons for this are as follows:

1: Business is weary of IT, they see IT as cost builder rather than cost reducer, these continuous new acronyms (SOA/BPMN) do not really bring business benefits if they are not orientated towards business needs. See below the ‘Value Proposition Myth’
2: The over-supply of low cost consultants has resulted in many disasters, limited business benefits Having stated the above, are there opportunities for IT investment during this serious downturn?
In my opinion, YES.

These opportunities could be:

● IT RATIONILIZATION
● NICHE IMPLEMENTATION
● BUSINESS OPTIMIZATION

IT RATIONILIZATION
Rationalization of IT infrastructure;

How many multi-national companies out there have a disaster in place, many ERP systems (different types, SAP, ORACLE, JDE, different versions/release ect…) with costly interfaces and costly IT resources supporting these systems. I have even seen a SAP System Sales Order mgt, integrated with Oracle Delivery processing , integrated with a Catalyst Warehouse Management system integrated with a Transportation system (four system to manage Order to Cash) with complex custom interfaces, many support teams and many consulting companies.
Why is this? Very simple IT Managers approach in the past was the more complex, the bigger the budget, the bigger the power (parking space next to VP and personal secretary and nice office).

I recently worked on a APO Planning Project (DP and SNP) in a consumer environment whereby every time there was a roll-out to a new country a totally new project was started instead of making use of existing core template (actually most IT manager have no clue of what a template is) resulting in costly implementation and costly support (people and infrastructure). Even worse, the project was based on replicating a legacy logic built in EXCEL instead of really adopting a SCM optimization project.

Rationalization means getting rid of all the fluff and consolidating into one ERP/Planning System , single server architecture across all continents/countries. Cost saving is enormous. This actually contradicts SOA and adoption of the so called ‘Cloud Computing’

To make this a success the following are critical aspects to consider:

● Project ownership must be with business not IT (possibly a Finance VP)
● Strong project governance is needed (tools, control framework, methodology) with respect to managing the global rationalization. The rules of game must be clear.
● Manage project internally, use consulting companies or contract consultants to provide specialized resources on demand, using a consulting company to manage a IT rationalization normally has limited success, consulting companies objective is to bill as much as possible therefore strong conflict
● A system baseline is needed (template) of the ERP and SCM System, this baseline becomes the core for any global roll-out, rules for changes must be simple:
► Legal requirements (Country X requires that any delivery that cross regional borders requires certain financial requirements)
► Customer Service related, will the functionality result in poor customer service (obviously consideration of business volume is critical)
► Cost and Efficiency related, will it result in more people to pick pallets in my warehouse. Cost efficiency consideration must also look at cost of IT, no use in implementing a best of breed because you plan to save 2 forklift drivers but at the same time need to employ costly IT support people and costly interfaces
● Have a strong Design and Implementation Architects (people that know business and IT) that are able to link business needs with a solid IT solution. This means people that come from solid business background and have solid IT experience. People that can provide guidance to IT manager have to make smart decisions..
● To make the various VP interested (the ones that approve the project) IT managers will have limited success in trying to sell this, why? Simple, admission of their own failure. Best to use consulting companies (not IT) better Strategic or Auditing firms to approach the relevant VP. This is also an opportunity for SAP do some good solid marketing, it also in their interest to get rid of all the ‘Fluff’.

NICHE TOOLS IMPLEMENTATION
SAP has released over past couple of years within the Supply Chain Framework many new functionalities that could provide a business benefit. Typically to name a couple these functionalities:

► SCM Event Management
► SCM EWM (Extended Warehouse Management)
► SCM SPP (Service Parts Planning)
The problem with this is that IT must be able to sell this kind of project, success can be achieved if these functionalities can provide a perceived benefit in terms of IT rationalization or Business Optimization. A further problem is that most consulting companies have limited skills to implement these niche functionalities, you will not find the usual ‘low cost resource’ consultant.

BUSINESS OPTIMIZATION
This is more difficult to manage mainly due to lack of management skills, optimization from a IT perspective tends to fail because of trying to look at things from IT perspective only and not from a business perspective. Real optimization requires a good understating of Business and Mechanism needed to support a process (IT, manufacturing infrastructure ect..).

Optimization is like trying to fine-tune a symphony orchestra. Imagine trying to tune a violin without considering other instruments, or imagine sheet music for 1st violinist that in not in tune with a Cello.

Optimization in Supply Chain means doing things more efficiently (cost effectiveness).

● Right qty at the right place at the right time at lowest possible cost. (Planning, distribution and transportation)
● Supply Chain Network, most cost efficient network to deliver product to market. (centralized warehousing, multi-market warehouse), transportation methods, loading , route mgt.
● Producing more of the right product based on customer demand without increasing inventories (on time delivery, maximum manufacturing output at lowest inventory levels)
● Obsolescence avoidance.
● Inventory optimization; What is the optimal inventory policy that minimizes inventory holding cost while maintaining or improving serviceability and financial performance.

The fundamental aspect when undertaking a optimization project is to consider the above framework in order to ensure maximum success. Trying to focus only in System Optimization results in limited benefit. The ideal is to determine the correct synergy between Business Optimization and System Optimization so that the end result is a IT solution that totally supports business needs and achieves optimization objectives.

Some typical examples regarding the optimization framework;

Consider a SCM project whereby one of the possible optimization objectives is the rationalization of distribution center’s. This kind of work requires the following:

Business Optimization
This covers business strategy, understanding potential solutions and defining a TO-BE model.
The impact to the business with respect to distribution rationalization. This also includes opportunity assessment.
Business potential analysis from a cost effectiveness situation and other consideration such as tax implications, local Government benefits ect…
A conceptual TO-BE (Business Process Re-design, benchmarking) design Blueprint, organizational change, is needed to address location, type of warehouse, business model that leads to the desired cost effectives.

Implementation Consulting
This entails implementing and providing operational support for the conceptual TO-BE model with the ideal IT infrastructure.
Design , Build and implementation of the required IT tools, this could be the usage of existing functionality provided by the current ERP or SCM platform with the ideal hardware platform.
Operational IT system support.
I recently worked on a optimization project related production planning and execution, this was in the auto component supply. Reality was that business had very low confidence in the SAP IT solution, customer service was bad (50% on time delivery) inventories too high; too much was manufactured of the wrong product. Through the years, IT invested a lot of money bringing in consulting companies to try and fix the problem, but never succeeded because they always tried to optimize the IT part and never really understanding what was happening from a business perspective. Obviously IT and SAP was not well considered in the organization. This changed when the VP decided to personally engage the problem by using a consulting company specialized in manufacturing (not SAP or any IT system) to do a detailed work-study analysis and understand what exactly was happening within manufacturing, planning and execution and to identify a TO-BE situation, then based on the TO-BE model was the SAP System Optimized resulting in improved performance.

The above shows that there are different roles and skill set’s needed, the difficulty is to manage these task and clearly understand what skill sets are needed keeping in mind that during optimization process there are many role-players to consider. Not many organization have Change/Optimization champions that can mange an optimization project. Most IT managers lack ability to understand the grey area related to Business Optimization versus System Optimization.
The role of a skilled Design and Implementation Architect is also critical, this person normally not only has strong business skill but also has strong system expertise and help’s to bridge gap between Business Optimization and System Optimization and also provie guidance to what is technically possible.

CIF Management for eWM

2009-05-13T16:32:00.004+02:00

The eWM SCM platform is connect to the ECC system using CIF (qRFC) integration. The same integration technology used for APO.
The CIF is used both master data and transaction data.

Data is transferred using buffered qRFC technology:

Master data via standard CIF master data model, for eWM consideration/limitation must be made around vendor and customer replication as well batch managed products. Further consideration relates to managing batch determination in eWM. Critical to understand how characteristics and class are replicated and very critical to consider that it is not possible to use a SCM system for eWM batch management if set-up for configurable materials. This could be a problem if decision is made to use same SCM/APO development system for APO and eWM.
Changes are automatically updated for active models depending on Application Component (APO) flagged as well as change pointers set-up.
Transaction data, deliveries replicated to eWM system. From eWM delivery confirmation and goods movement. It is important that correct queue name is assigned to QIN scheduler.

One of the fundamental aspects regarding the CIF between ECC and eWM is related to monitoring and model management.

Queue must monitored for errors, job’s set-up to re-activate queue in error due to locking.

For active models, jobs must be set-up to de-activate a activate in order to include newly created master data objects. It is important in the CIF not to specify actual vendor or product codes but rather use other selection criteria such as plant / material types. For product material status is very useful to manage timing of replication in order avoid replicating a product that is still in the process of being updated in ECC.

SCM EWM Skill Set

2009-04-21T12:10:00.006+02:00

What is needed to manage a EWM project ?

R3 WM skills ?

In order to effectively manage a EWM implementation the following skill set is need:

1. Strong Core Interface (CIF). This is because EWM runs on the APO platform, all interface are managed via qRFC

2. Strong ERP Delivery processing, this is because interfacing between ERP and EWM is via Deliveries.

3. WM experience helps, limited benefit from WM considering that eWM is totally new solution, not an upgrade. Therefore you need Functional EWM resources that know eWM processes around delivery processing, RF, yard mgt, cross docking, Warehouse tasks/order, Quality Inspection engine and maybe interface PLC. This functionality is not present in std SAP R3 WM, totally new, 10 x more complex than old WM.

4. ABAP, BADI know how. Most EWM projects are enhanced. Must be able to provide guidance to ABAP developers.

5. SAP Architecture. Knowing how to manage distributed architecture, change request transportation, sizing ect…

The above defines the Functional EWM Consultant. For technical parts regarding developments, any senior ABAP developer will be OK. The EWM technical platform is no different to APO or R3. What is critical is that the Functional EWM Consultant must provide guidance to the developer in terms of which direction the custom development should go, it could be sufficient that a BADI will do the job. A weak functional consultant normally leads to excessive developments, complex developments and in certain cases modification to SAP standard resulting in excessive support effort.

Bottom line, a WM consultant without the above requirements will take some months to get up to speed. The training courses provided are quite limited.

Focus on strong functional EConsultant and good ABAP developer (don't look at the low cost, you pay for what you get)

A simple WM consultant is suitable for junior role, a person that can cover all above 5 requirements is ideal for project lead.

A logical approach to SAP Supply Chain Management

2009-04-09T03:37:00.005+02:00

The purpose of this blog is to provide and discuss various topics around Supply Chain Management within the SAP SCM platform. By placing Supply Chain Management into context helps do define a structured approach in covering various SCM topics and provides a framework on how to maximize and exploit the SAP SCM tool. My experience in working in the Sap SCM environment is that in certain cases limited success has being achieved with the IT investment when implementing a SCM platform. In most cases it is not due to a SAP weakness but rather poor implementation, lack of vision and in certain cases lack of expertise. I have experienced costly multi million investment projects whereby all we did was replicate a legacy solution (in most cases homemade or Excel driven) within the SCM offering.

A typical situation relates to a Parts Automotive manufacturer where the production planning and execution system had many shortcomings. This was reflected in two major indicators; 50% on time delivery and very high inventory: ‘Meaning, producing too much of the wrong stuff.’ This went on for many years whereby the typical IT approach was to maybe build a custom solution, a fancy report. Many external partners tried their luck, always same solution. The IT angle provided limited success.
Success was achieved by adopting a holistic approach between processes and the IT system in order to achieved the desired synergy:

o Re-design of manufacturing processes
o Lot size rules, change over tooling , sequencing logic. Processes and techniques that have nothing to do with SAP
o Modifying the SAP solution to consider critical process redesign:
o Modifying the logic around lot size rules
o Planning manufacturing considering key bottleneck resources in order to have realistic manufacturing scheduling (applying in the SCM solution Drum, Buffer Rope planning concept)
o Including buffer logic to protect key bottleneck resources
o Using sequencing logic that share similar tooling in order to minimize change over. Included building visual planning tables that allowed simple management

The above approach can be modelled within the modelling concept explained below.

In order to place SCM into context, I will adopt the IDEFØ methodology. Modelling SCM using IDEFØ approach help to organize the analysis of a SCM system. As an analysis tool, IDEFØ assists the modeler in identifying what functions/processes are performed, what is needed to perform those functions (mechanism/tools/resources), and what contols/constraints the process.

The basis of IDEFØ consists of the following when mapping processes:

o A process has inputs and outputs
o A process is constrained by controls. These controls could be constraints, legal requirements or o a business strategy, capacity. A IT system could be a constraint.
o A process is supported by mechanism (tools). Tools are resources (manufacturing, facilities and people) as well as a IT infrastructure. In certain aspect mechanisms adopted can become constraints on the effectiveness of a process.

Important to understand that process modelling plays an important role but has limitations, process modelling cannot optimize flow/movement. Optimizing flow and movement is also critical within the SCM, specifically in trying to optimize location (number of warehouse's) production process flow ect...

This blog's focus will revolve mainly around the SAP SCM system/mechanism (the SAP platform covering ERP and SCM)

The areas that are addressed with SCM area include: Planning, Execution and Control.

Custom Macro Functions

2008-10-29T14:39:00.012+01:00

SAP provides a number of standard Info Objects Functions that can be used within advanced advanced macros. There are situation whereby the standard functions within marco tool kit are not suitable. To overcome this problem it is possible to create a custom function:

A macro custom function is basically a function module that is created with transaction SE37.

What can you do with custom function ?
Basically anything, it is just ABAP coding, example:
Ø Doing checks across network and create orders without running heuristic
Ø Creating own safety stock logic
Ø Updating data to different custom key figures and different product / Location logic
Ø Triggering an event that in turn is associated to a process chain steps

What are the limitations?
None, other than performance. Careful testing is needed to verify performance impact.

What about error management?
In Interactive planning, if there is an error the custom can return a variable that is displayed in a pop-up. When running macro job in a process chain, it is recommend to create a log for any errors generated by user. This log can then be sent via workflow. Alternative alerts can be generated to identify technical problems or real alers that custom function generates. This log can then be sent via workflow.

Supply Chain Execution, WM, LES & eWM

2008-10-24T18:15:00.005+02:00

WM, LES and eWM

Purpose, usage and benefits.

The SAP platform offers a quite a selection with respect to Logistics Execution (warehousing, delivery and transportation)

It is critical to understand each one.

Warehouse Management WM:
The warehouse management module in SAP ERP is as we all know it since the days of R3 3.0. The warehouse management module is suitable for simple and low volume warehousing environment that is fully integrated with the rest of the SAP modules such as IM, PP, QM as well as SD. The module has followed an evolution whereby Handling Unit Management, Radio Frequency and in later releases Task and Resource Management (limited success) was included in its offering. The SAP ERP WM modules usage is also influenced by the SAP architecture. Normally a SAP architecture for a local single company environment.

Logistics Execution System: LES (decentralized platform)

The Logistics Execution System which includes WM, shipping, transportation is also available in a centralized SAP architecture as well as decentralized architecture connected via standard ALE (IDOC’s).
The decentralized architecture is suitable for multi-national organization that have central ERP environment and require high volume distribution in many countries. The benefit of the decentralized architecture is to have separate server in a country, example Japan where main ERP server is in Germany to manage 24 hours a day 7 days a week warehousing and distribution functions without disruptions and high system availability. A further benefit relates to radio frequency response time. A distributed LES server allows quick (sub second) response time.
One of the shortcomings to the decentralized architecture relates to close integration to other modules (example QM) and process autonomy is very limited. Inbound and Outbound in LES are only possible if they were replicated from main ERP system. Quality management only worked if HU assigned in Inbound delivery in ERP system limiting the system independence.

Extended Warehouse Management: eWM

SAP has progressed warehousing and distribution development with the development of Extended Warehouse Management with the introduction of SCM 5.0 (APO platform). This solution was developed within the Service Parts solution and enhanced.
The eWM operates in a separate platform (SCM server) and is integrated with ERP (from SCM51) via the Core Interface (CIF, same technology as APO) using qRFC Inbound and Outbound.
The key design feature with respect to eWM are:
Suitable for multi system, multi customer and multi partner technical landscape
True operating autonomy, allows processing inbounds in EWM without the presence of Inbound Delivery Notifications from ERP system
Quality Inspection engine to manage QM
Integrated with RFID
The weakness of Task and Resource Management has being replaced by a totally integrated design with respect to processing, movement and resource management assignment. The eWM support both layout or process orientated movements of pallets within the warehouse
Native integration with Material Flow doing away with costly middleware.

What now ?

Where to, what solution should be chosen ?

First consideration is the business requirement, complexity, volume and SAP environment.

If single client low complexity and low volume then choosing standard WM solution is more than adequate.

Where the requirements are for high volume, complex environment and distributed warehousing based on single SAP ERP system, then either LES or eWM should be chosen.
The eWM solution is the obvious choice if the ERP environment is based on SAP Enhancement Package 3 for SAP ERP 6.0. The eWM offering provides more advanced functionalities than LES and will be the main focus for technology investment by SAP.

Supply Chain Optimization

2008-10-24T18:13:00.009+02:00

Simply stated; Supply Chain Management is to ensure optimum time and place utility of a product.

Time and place: ensuring the availability right qty of a product at the right time:

1. Component at a assembly line to satisfy production sequence of a finished product
2. Semi-finished item needed for final assembly manufacture
3. Consumer goods at a supermarket
4. Spare parts for a an automobile/computer/aircraft

Optimum: ensuring time and place utility in a cost effective manner:

* Cost: ensuring lowest possible cost to store/move/transport an item
* Effectiveness: Ensuring correct product, correct quantity without any damages and correctly identified (packaging and labelling). Customer Service (internal and external) is a key measure of effectiveness.

To achieve the above, the following fundamentals elements related to time and place utility are critical for a Supply Chain Expert to apply the SAP SCM suite:

Production:
What , how and when to produce

Inventory:
How much to make and how much to store

Location:
Where best to do what activity

Transportation:
How and when to move product

Information:
The information need to make the above decisions.

The objective of the SCM blog is to provide insight regarding the application of the SCM suite provided by SAP in order to order to increase throughput while simultaneously reducing inventory and operating expenses at the desired customer service level. The following topics will be addressed within this blog:

► SCM in General
► SCM Design
► SCM Planning
► SCM Execution
► SCM Control/Performance