We can do SAP-PP with the following Strategies:
- Make-to-stock production for mass production,
- Make-to-order production or make-to-order production
- as well as Production by lot size.
Depending on the production type, various production strategies are necessary. For each production process, you can determine optimum planning strategies. These strategies can be freely chosen and can be combined with each other. You can define the appropriate strategies per material and plant.
Processes in production planning and production control comprise the following main areas:
- Sales and operations planning for determining the quantities to be produced.
- Material requirements planning to calculate net requirements and component
requirements, taking into account scrap and lot sizes.
- Capacity requirements planning for detailed production planning, taking
into account available capacities.
- Production control to control and record the production process (create
production documents, record confirmations)
In my case, I am more immersed in Production Control .
A Maintenance Planner creates a Multiple Maintenance Work Orders with several Non-Stock items (i.e Carpentry Services, Civil Works, etc. )
Instead of releasing them one by one, the Maintenance Planner can use the SAP transaction code ME55.
From the report, just indicate the Release group, Plant, and the Materials Planner Controller. You can fill out the other fields if you want a specified number of Purchase Requisitions to appear.After filling out the fields, click on the execute button ( its the clock located on the upper left hand of the report =) ).
To release the Purchase Requisitions by clicking the release icon ( its the pencil with the check on top). Then click the back button and your done .
Its very simple, don’t you think so?
In a company’s Production Server, a Maintenance Planner wants to add a new Catalog in SAP Plant Maintenance using the Transaction Code QS41. But the Maintenance Planner was not successful because it is in Display Mode:
And when you try to check your Authorization using the transaction code SU53, the Authority Check failed even if the Authorization team already set it up in your SAP ID Profile.
The reason it failed because the Maintenance of selected sets specially in QS41 requires transport request. And in the Production System, All Configurations in SAP are CLOSED.
In order to solve this, we should apply the SAP Note 736920 to correct the problem.
A Catalog contains one or more code groups. A code group is a list of codes such as reason for repair codes or part condition codes.
A catalog contains both code groups and selected sets:
- A code group contains one or more codes. Since each code is assigned to a code group, codes are often referred to as “group codes” in SAP.
- A selected set contains a combination of different codes that originate from different code groups.
- Codes make up the lowest level of the catalog. Codes are used in both code groups and selected sets.
You define codes in code groups and use the codes in selected sets (for example, to describe characteristic attributes such as colors, shapes, surface characteristics), defect causes, or usage decisions.
Keep the following points in mind:
- You need the necessary authorization to perform these functions.
- The screens may vary slightly depending on the function you are using.
- The individual field names may vary slightly.
In SAP Plant Maintenance, Capacity requirements planning supports the detailed work scheduling for the individual maintenance Work Centers.
It aims at determining the capacity available at individual work centers and to use it optimally in view of daily requirement changes. They are maximized as far as possible in view of the changing daily requirements. Therefore, it can help us determine which Work Centers and individual persons are available and when assigning them to Maintenance Work Orders and Work Order Operations.
In Plant Maintenance with relation to capacities, we can do the following:
- You can assign the work of a whole order to an employee while you enter or process the order.
- This order-based assignment of work is an alternative to the method of allocating one or more employees to individual operations – although this method will continue to be supported.
- Responsible employee in the order header: With the partner determination procedure you can assign an order to an employee. You can choose different types of partners but the role must be that of a person.
- Automatic creation of capacity load for the employee: For partners of the type Personnel, you can determine in the partner determination procedure that capacity load records are automatically created for the employee. If an employee has already been entered manually for an operation, this assignment is not overwritten by the automatic assignment.
- Personnel planning functions for assignment in the order: The following functions are available via help for employee assignment:
– List of employees per work center
– Qualification overview
– Qualification and scheduling overview
– Qualification comparison with reason
– usage list per employee
– Scheduling overview including HR-attendance/absences (holidays, sickness)
Depending on the business requirement, in Plant Maintenance, we can use the Graphical or Tabular Planning Board or Multi Resource Scheduler ( MRS ) for Work Scheduling.
If this article is helpful, a small donation to my wallet address will be appreciated:
The reasons we used External Services or Third Parties are:
- Missing Qualification: A company’s own labor force is not always qualified to carry out every type of maintenance work. It is often the case that certain types of work will need to be given to external companies who have focused on this area (for example, lift servicing, the maintenance of air conditioning systems, process control etc.)
- Unavailable Capacity: External Services or Third Parties can be used to supplement the capacity of the internal labor force (for example during betterment projects, turnarounds, end of the year maintenance etc.)
- Costs: The question of whether external labor is more cost-effective than internal labor is not simply a case of primary cost comparisons( that is, the amount on the invoice) but also of the secondary cost comparison. That is, the administrative costs associated with managing external companies such as order planning, purchasing, service acceptance, invoice checking etc.
In SAP Plant Maintenance, we can do this by using Control Keys:
•PM01: The external service is handheld, via an internal order, like internal work
•PM02: the external service is processed with a purchase requisition and an individual standard purchase
•PM03: the external service is processed on the basis service items or service specifications and, later on, by service measurements.
In SAP Plant Maintenance, the features of a Maintenance Orders are the following:
- Flexible order processing
Ideally, the maintenance order must be capable of being opened with a minimum data entry (for example, in the case of a malfunction). On the other hand, there are some business processes in Maintenance, such as revisions, transfers or new constructions, for which the maintenance order should provide a wide range of functionality – working with external companies, network configuration, permit processes, cost statements, material reservations and others.
The Maintenance order either refers to one specific object or to a group of any number of objects which can be displayed in an object list in the maintenance order.
An individual order is valid for a specific piece of maintenance work only. In the case of standing order, however, you do not create a new order every time a new piece of work needs to be done. The standing order is valid for a certain period of time. It is created to cover minor repairs, and all times and materials are posted to it.
Maintenance orders are performed by internal company employees or are outsourced to external companies.
In SAP Plant Maintenance, A Maintenance Order can be created by the following:
- Scenario 1 : A maintenance order is automatically created in a maintenance item by the maintenance plan
- Scenario2 : The maintenance notification is entered at some remote location. A maintenance order is created for the notification by the person responsible
- Scenario 3 : In the maintenance order, several notifications are combined into one or more objects
- Scenario 4 : The Maintenance order is created directly = Malfunction-based Maintenance/Emergencies
- Scenario 5 : An activity report for an existing maintenance order is entered subsequently as a technical confirmation.
In SAP Plant Maintenance, when a Maintenance Plan is created, the cycle is assigned and defines the interval for the call dates and thus for the creation of orders.
In addition, different scheduling parameters can be assigned in order to adapt the call dates to various requirements.
– The Cycle Start determines the date from which call dates are to be calculated.
– The Shift Factor enables you to react to early or late confirmation. They are stated as a percentage related to the cycle.
Call Dates are calculated on the basis of scheduling parameters. For each call date, an order is created.
The changes in the schedules will vary depending on what you declare on the Early/Late Shift Factors and in the Tolerance Level of your Maintenance Plan.
A Maintenance Plan shows the shift of a planned date triggered by a late confirmation. The following parameters are taken as a basis:
– Cycle start: 01/03/98 – Cycle duration: 3 months
– Planned dates: 01/06/98, 01/09/98 – Tolerance for late confirmation: 10%
– Shift factor: 50% – Confirmation: 15/06/98
The tolerance always refers to the shortest cycle, so that in this case the tolerance is 9 days (10% of 90 days). The shift factor always refers to the total number of late days. As the confirmation date is outside the tolerance of 9 days, the shift factor of 50% of 14 days = 7 days applies. The newly derived planned date is therefore the 08/09/98 (instead of the 01/09/98).