SAP Process in Machine Shops: Issues and Remedies

Introduction:

This article deals with a case, which is believed to be resembling with SAP-Plant Maintenance implementations at some other places. This basically discusses the problems arise during and after implementing SAP, in Centralized Machine Shops of large manufacturing industries, where a legacy system (like CMMS ) existed,  the issues thereby and the possible solutions.

Background:

Machine shop process involves two main functions, namely

1. Spares Fabrication (like Fasteners, Sleeves, Bush Bearings, Flanges, Couplings, Gears and so on, for production unit maintenance.)
2. Repairs of Machine parts (Dismantled & brought from production unit to the Machine shop)

When SAP was implemented, SN1. above was identified as Production process and SN2 as Refurbishment Process.

Eventually, the machine shop process was  split into 2 modules, PP module for SN1., and PM module for SN2.

Process1: Initiated by Sales Document, then a PP order is processed and ends with Usage decision in Quality Module.

               Tcodes: VA01,2,3  CO1,2,3 , CO11n, MB11, MB1B, MIGO, COOIS, QA32,33 etc.

Process2:  Initiated by a Repair notification, then a Refurbishment Order is processed and ends with UD in QM.

                Tcodes: IW21,22,23,28,32, MB11, IW8W, MB1B , MIGO, QA32,QA33 etc

{Legacy system was addressing both these functions in a single  system.}

Issues:

1. The end-user (machine shop person) is having to deal with many Tcodes related to PP and PM modules.
2. He does not have a consolidated reports retrieving of factors like

          –     Total machine capacities booked for PP & PM orders in a single screen.

          –     Order status for both categories in a single screen

          –     Total Tonnage produced in a single screen

          –     Goods movement (start to finish) information against each order in a row.

                due to which, he had to

                  i. Go through too many commands (Tcodes) for retrieving information.

                  ii. Importing this data to Excel sheets and combining, to prepare consolidated report for administrative purposes.

and several such.

Remedies applied:

There was no option for the user, to have a single order system for both functions referred above. But the reporting part can be addressed to relieve him to a good extent. But there were technical constraints. The development of such PP-PM integrated reports, was demanding expertise in PP, PM and ABAP (also a about tables related to SD, QM and MM). During implementation, the consultants could not help in this area before they left.

After quite sometime, someone from ERP PM team of this organization, could develop himself, to reach these levels to address the above requirements.

Several PP-PM integrated reports were developed to serve the data required in a single ALV screen.

Few main reports are referred here, (several drilldown reports are not discussed)

Reports on Machine Capacities:

(Development based on tables  S024, S022, VIAUFKS, VIAUFK_AFVC, JEST, TJ02 etc.)

Selection-screen

ALV

Drilldown Report (Operation level)

Reports on Order Status, Operation Status, Goods Movement:

(Developments based on tables AUFM, AUFK, AFKO, AFPO, AFVC, AFVV, AFVU, JEST, TJ30, TJ02 etc)

Selection-screen

ALV

May notice DMS column (1st), where the icon, on clicking directly takes to the related drawing.

Drilldown Report (Operation level)

The screen-shots might be good inputs for the members who are in similar situations.

The Objectives of this post:

1. To give inputs to members who are in similar situations, pre/post-implementation.
2. SAP might take a call about this function (Machine shop process) and provide a sub-concept under Plant Maintenance (like Fleet Management).

        This would help reduce the end-user pain, in both, Data Entry and Reports areas.

Thank you

KJogeswaraRao