Channel

Production & Capacity Planning

Showing 00 of 00
Customer Service
Demand Planner
Materials Manager
Production Planner
Production Scheduler
Purchasing Buyer
Supply Planner
Warehouse Administrator
Warehouse Manager
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Available Capacity
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CR01; CR02; CR03
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, I'm Martin, and in this video we will focus on how to take advantage of SAP's capacity availability capability. When used correctly, capacity availability check provides real-time visibility of an organization's production work centers or resources and their availability, therefore enabling more informed planning decisions and the opportunity to optimize utilization. So Eacliffe, tell us more about capacity evaluation. Sure Martin. Capacity availability check is a powerful feature when used correctly and in this demonstration I'm going to show you three things to focus on. How to maintain capacity for your capacity category. Recognize that available capacity can be maintained for different capacity categories. And finally, we will validate the results using capacity load transactions in daily, weekly, and monthly time buckets. Here we are in the capacity plan transaction CM01. To aid with defining available capacity for work centers and resources, regardless of which solution we're using via PPE, Repetitive or PPPI, the concept is the same. The goal is to reflect the correct amount of available capacity regardless of the time horizon we are looking at. So that could be looking at it in terms of daily, weekly, monthly, or even at a shift level. So let's take a look at the standard overview and we can see by default we are looking at capacity in weekly buckets. And our focus on this here is on this column here, available capacity. So for each week, how many hours of available capacity do we have and we can see that it's 40 hours per week. Where you see that 32 hours per week means it's a 4 day work week rather than a 5 day work week. So how is this information coming here? I'm going to switch over to the change mode of the work center. So that would be transaction CR02. So we can see that this is transaction CR02 and we specify the work center that we want to maintain their available capacity and click here on the capacity icon. Note, if we are working on a resource we would be going through transaction code CRC2, change mode for that resource. Basically given the premise that the work center or the resource already exists, the goal was just to maintain or update that available capacity. So here we can see we have two different capacity categories, 001 and 002. Where zero zero one represents machine capacity and zero zero two represents labor capacity. In terms of available capacity, we would maintain it, basically, hey, how much capacity do we have from a machine perspective? And then how much capacity do we have from a labor perspective? So let's take a look at the machine capacity, I'm going to double click on the 001 which brings me to the screen and just go to some key fields for defining available capacity. The first field I'm going to call out is this field here called pooled capacity. Just be aware that we can define available capacity from a pool perspective. We have a separate, video for this. If you think there is a need for this please keep an eye out for that video. The next field is the factory calendar. There's two ways the system, uses factory calendars. One is what you see here, where we said, look, we are going to create a calendar, that calendar is specific to how the operations run. You know, they could be like a 5 day work week, 7 day work week. We take holidays into consideration or we don't take holidays into consideration. So that's the type of information we would define in the factory calendar, and that's what we have reflected here. The alternative is there is a calendar associated with the plant, this plant being 1000. And if the belief is that the calendar that's associated with the plant is good enough we could have left this field blank and the system would then use the factory calendar that's associated with the plant. So be aware that this is not a mandatory field rather it's an optional field and if it's left blank, the information is then derived from the factory calendar assigned to the plant. The next field is active version. The question is for this work center, which version of data do we want to maintain? And what I mean by that is let's do the dropdown and we can see by default which version of data do we want to work with, is it normal, minimum, or maximum available capacity? Okay. So in this case we are going to work with normal. But if by chance we say, look, we want to alter the information in terms of available capacity and we want to reflect, let's say, maximum, where maximum is we are running a 3 shift operation, 7 days a week. Yes, we can come and modify this information and says that look, this information represents a maximum available capacity rather than normal available capacity. Okay, now come to the next field with the base unit measure in terms of the time that we are maintaining. So when we look at CM01, let's come back here briefly, what we will see is we can see that the timing it is H which is, look, when we present the information, please present it in hours and that's what, we are referencing on the other screen here. So this could be any time unit, it could be minutes, seconds. But again, when looking capacity, especially looking at it in weekly buckets and monthly buckets it's much easier to interpret when working with hours rather than minutes or seconds. But at the end of the day what is your business requirement? And that's what you would reflect here. And then finally, coming down in this last section here, what are the standard values of available capacity? In this particular case we're seeing based the available capacity, using a start time of 8 o'clock in the morning. We finish the line is shut down at 5 o'clock in the afternoon, and by the way there's a one hour break. So the total duration here is 9 hours but because of the 1 hour break, It says the operating time for that piece equipment is 8 hours. Okay. In terms of capacity utilization I reflected a 100%. We recommend that you use a 100% but you don't have to. By using 100% it says, look, my operating time is 8 hours, and by the way, it means that I have 8 hours of available capacity. It's not uncommon for some folks to say, look, we know production lines are not perfect and because it's not perfect I don't want to reflect a utilization of 100%. We would recommend that you reflect that in the production rate rather than here in the capacity utilization. But again, it comes down to, what is your business requirement? And recognize that if I came here and I am going to put 90 and hit enter you could see the number of hours per day has dropped from, 8 hours a day to 7.2 hours a day. Again, you could definitely work with this but it does make it a little more difficult to sometimes interpret the information you're looking at, and for that reason we strongly suggest that you keep this at a hundred percent and that then says, look, my capacity is 8 hours a day and then like the production rate says, hey of this 8 hours I need maybe 16 hours or 4 hours. And then of course we have H here to again show that the information we're looking at is being looked at in terms of hours. This could also be minutes, seconds, what works best for you but again we recommend hours. Finally a screen I want to take you guys to is the intervals and shifts and basically want to show that the information from the previous screen was then brought over to this particular screen where we could see that we are looking with version one, which is a normal available capacity. We can now see additional information where it says, look from now to the end of time we are working with start times. You can see the start times is reflecting in the 8 hours. The end times the default is 5 with a length break of 1 hour. The utilization is a 100% and in this case the number of individual capacity is 1. Let me just talk a little bit about this number of individual capacity where if this work center had represented 2 machines then ideally the number of individual capacities would be 2, to show that by defining it 2 the number of available capacity per day would then be 16 hours. In this particular case we are saying look, this work center represents an individual or single machine hence that's why we're using 1 capacity and that then says look, that machine is running only 8 hours a day. It's a good habit to come into the screen only because as you start maintaining things like a shutdown for example, or downtime for that particular work center, you would come in here, create a new entry and say, look, this start date to this end date, the work center is not running it's done for maintenance for example and we will then reflect that there is 0 capacity available during that maintenance time. Okay, so, that's it for this topic. I will say be aware that in terms of available capacity, required capacity, this information can be rolled up to a higher level. So at, at the beginning in the capacity evaluation, yes, we should be looking at it for a single work center, but if it makes sense to look at 5 work centers together for example, we can take this information and roll it up. We will demonstrate that in a feature video. So in summary, we have covered. How available capacity allows the business to define each work center available capacity. The business to define available capacity for different capacity categories, such as machine and labor capacity. And finally, how the business can validate the available capacity defined for each work center using the capacity load transaction in daily, weekly, and monthly time buckets. Thanks, Ecliffe. Using this feature provides information and tools needed to optimize production resources and improve operational efficiency. So for all of you out there that want to know more about how to get the most out of the SAP system, please check out our other videos and if you can find the video or the answer that you're looking for, please submit a suggestion.
Capacity Backlog
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CM01; CM04; CR02; CR21; CR22
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, I'm Martin, and in this video specifically, we're going to focus on how to take advantage of SAP's capacity backlog capability. When used correctly, capacity backlog provides a clear view of all the production orders and process orders, allowing organizations to better understand the production and equipment capacity utilization. So Eacliffe, tell us a little bit more about SAP's capacity backlog capability. Sure Martin. Capacity backlog is a powerful feature when used correctly and in this demonstration I'm going to focus on two things. How to retrieve capacity data for the work center experiencing the backlog. And, how to modify the capacity load transaction settings to identify when that backlog will get resolved. The intent here is to illustrate how to use transaction CM01, capacity planning, to identify when you will get out of a production backlog situation due to capacity constraints. So here we are on the initial screen of transaction CM01. Going to click on standard overview and we can see that the first three weeks is over capacity, significantly over capacity. So the question is how many weeks will it take to produce all this inventory using this current production rate? So we start by coming into planning, actually, you're going to go into settings, general, and we are going to click on this icon and do a green check. And we can see that all the weeks over capacity. Basically it's doing accumulation where it's adding up the available capacity so you could see the available capacity increasing as well as the required capacity. Comes up to 640, hours and that's the max. So let's take this and move it into the future by coming back to the settings general. I'm going to increase this to, let's say 180 days, I'm going to hit enter and now we can see that, the capacity situation, we are in a over capacity situation for several weeks before we finally get into the clear. Now, this is based on the current demand so of course this, most likely will not represent the worst case scenario because there's a high probability of added demand coming within this time horizon over these many weeks. So it's about 17 weeks, it will take the credits so this is the way we get to do a quick evaluation to say, hey, that existing demand, how quickly can we get out of the situation? It's at least 17 weeks. This is from a machine perspective and then of course what happens is if we come down to labor, yeah, there's definitely a lot of labor requirements. So the point is that we would also need to see what we can do from a labor perspective to address the production requirements. So, depending on your manufacturing circumstances you might be able to add labor to resolve the issue, great, otherwise you would've to say okay, what else do we need to do to resolve the situation or to resolve the backlog? So on that it's a wrap for how we perform a quick assessment of a capacity backlog situation. So in summary, we have covered. How capacity backlog allows us to retrieve capacity data for the work center that's experiencing that backlog. Plus, the business to modify capacity load transaction settings to identify when that backlog will get resolved. Wow, thanks Eacliffe. I can see how this will be super helpful for planners and schedulers, making informed decisions, optimizing production lines, and managing customer expectations. So if you want to learn more about how to get the most out of your SAP system, please check out our other videos and if you can't find a video or need an answer to a question that doesn't exist please submit a suggestion.
Capacity General Settings
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CR02
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in the SAP system. Hi, I'm Martin and in this video we're going to discuss an overview of the business rules needed to help us set up our capacity evaluation settings within SAP. When utilized properly these settings and these business rules benefit the organization by providing a comprehensive view of production capacity, which enables more accurate planning of production processes and helps avoid overloading and underutilization of capacity. So Eacliffe how about you tell us a little bit more about these general business rules that we need to apply? Sure Martin. Capacity general setting is a powerful feature when used correctly and in this demonstration I'm going to focus on three things. The different fields that influences both required and available capacity. Educate on how to apply the settings to the different capacity category. And educate on screen required maintenance for capacity evaluation to work properly. The intent here is to review and demonstrate some of the key settings in the general settings of transaction CM01 capacity planning transaction. These settings can be applied from either the selection screen, which is where we are sitting at right now, or within the transaction which you'll see later on. So let's go to the menu, get the settings, click in general and what we are going to do is start with the first option under general which is a cumulative over period. So I'm going to select that, the other thing I'm going to do is to show that I'm going to change it to minutes so that you can see the information in minutes rather than in hours. Screen checked. I'm going to bring up the information here and what you can see here is the available capacity is now displayed in minutes. Okay, as well as the required capacity. The other thing I want you to see is that you can see that the available capacity is cumulative, in other words it's increasing over time. Likewise, with the required capacity, there is one business scenario which is basically trying to clear backlog. So if you have a backlog of orders for example and you want to determine how soon you can clear that backlog. In other words, you have insufficient capacity, let's say in the first three weeks by taking this approach you will see that basically have an idea of when that backlog can be cleared. So let's go back into settings, I'm going to come here, go back into general, what I'm going to do is, I'm going to no longer do cumulative, I'm going to do what we typically do and I'm going to say derive the unit of measure from our master data or orders rather than using the min. Provided the min is not what on the documents. So green check, you could see that it switched over to hours, you could now see it's no longer cumulative, rather we are seeing the hours, we have 40 hours per week and here we can see the capacity requirements in hours for each week. Okay, so let's go back and look at other options within this pop-up. Again, settings general, I'm going to leave this on in this section here, the default is G, which is number of calendar days and you could basically say, start from the current date, that's what you have with a 0 and in this case up to 60 days into the future. You can change this to 90 days, for example and if I do a green check this did extend. We are going to come back here, do general, we are going to see is that it went from April to May when I changed it from 60 days to 90 days. The point is that you can work in daily buckets, there's a whole slew of options here in terms of do I work in calendar days, factory days, posting periods and so forth. It's typically easier just to work in days, but if there is some requirement where you need to use some alternative, like maybe you want to do it in monthly that's an option. Okay, so moving on one option, which is used a lot is in this section here, the period. So with the profile I'm using it defaults in to weeks you could easily look at it in terms of months. So by coming back here now you can see the information is presented in monthly buckets and this is especially true if you want to look at things like one year into the future, two years into the future. So if you maintain demand that far into the future, you can do a quick capacity analysis and monthly buckets to see, huh, do I need to make some key decisions now in terms of outsourcing to another plant or outsourcing to a vendor, et cetera. The point is you can really have vision not here as well as in long-term planning so long-term planning is other functionality the point is that regardless of which side of the fence you're working on you would use the same approach in terms of looking at the general setting. Okay moving on I'm going to come and look at the hierarchy. So there is the option to work with what we call a planning hierarchy. Typically I don't maintain things like available capacity and the planning hierarchy and if you don't the thing is you want the information from multiple members or multiple work centers to roll up to the superior work center for evaluation. So this is definitely another key field that you would use I know I do have a hierarchy out there let's take a quick look here and if I do this, let's see what happens. Okay, we're still looking at the work center. So here with an S this is the superior work center and the point is by maintaining that hierarchy it did pull in the superior work center and as a result of that, it then took information from the previous work centers CHEM_PK1, CHEM_PK2 and is now displaying it but a different capacity category, if I came down to 2 you can see there's information there. Okay and with that let's go back and see what are the options, e do have this option of distributing the capacity information so if the information spans over, let's say multiple days you would display the information in daily buckets for example you could use a formula on the work center to do the disaggregation. So it says, hey put so much capacity on the final day, the day before, basically do backwards scheduling, so that option is available. Otherwise, it would just pick up the distribution from the profile and that would be maintained down here. So if he came down here, you can see for the different capacity categories, so 001, you'll use SAP060 if you had a different rule, that different rule is sitting on the work center it would employ that otherwise this is how you would alter the distribution of capacity inform. Okay and then finally you have this here where in the intervals and shifts you can maintain three different type of available capacity, you can see what is normal capacity versus what's minimum capacity versus what's maximum capacity. So normal might be, let's say two shifts, minimum is one shift, maximum is three shifts. So you can do by picking one of these, the default is one and the point is that this information here at available capacity is based on the normal, and you can also see which profile is used to do this evaluation? Okay, so that's it for this illustration of how to use the general settings in CM01 to alter how this transaction behaves. So in summary we have covered. How capacity general setting allows the business to define settings required for required and available capacity. The users to apply the correct settings for the different capacity categories. And the users to maintain the work center type and screens required for capacity evaluation to work properly. Thanks Eacliffe. Using this feature allows a centralized real-time view of production capacity to quickly identify potential bottlenecks and take appropriate action to avoid disruptions. So if you want to learn more about how to get the most out of your SAP system please check out our other videos and if you can find a video looking for please submit a suggestion.
Capacity Overloads
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CM01; CM05
The best way to learn is by doing. Welcome to the video series that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin, and in this video we will focus on how to take advantage of SAP's capacity overload reports. When used correctly, capacity overloads can help organizations better utilize their resources such as machine and labor, and detect when the capacity requirement exceed the available capacity. Eacliffe, how about you tell us a little bit more about capacity overloads? Sure Martin. Capacity overload is a powerful feature when used correctly and in this demonstration I'm going to focus on four things. Distinguish capacity overload from capacity backlog. How to perform capacity valuation using capacity load and capacity load transaction. Distinguish the difference between capacity load and capacity overload. And why you may not want to just use capacity overload transaction. The intent here is to discuss working with capacity planning to identify where capacity overload is taking place within your manufacturing plant. Typically capacity or throughput analysis is done based on mission capacity. Basically how much output can we process, so generate in a 24 hour day for example. Then the next step is to determine is there sufficient labor for the amount of production that's assigned or scheduled for that production asset? So let's go into transaction code CM01 and I'm going to bring up work centers that's starts with CH in plant 1000. So let's go into the standard overview and in a weekly bucket, before we get into the details here let's first take a look at things in the monthly bucket. So I'm switching over to a monthly view and we could see for this work center CHEM_WK1, both machine capacity category 001, we have sufficient capacity in the month of February and also from a labor perspective, we also have sufficient capacity. So let's go back into the weekly view because we did see some red. Every time we have a red row it means we are overloaded for that particular week. So first year we are looking for week 7 and right now there's 0 capacity available in week 7. So the point is that we need to take just 10.66 hours and move it into the future. We know that the sufficient capacity, because from a monthly perspective it told us look for the month of February, we can cover these capacity requirements, hence we can move this into the future. However, when we just look at this from a label perspective 002, what we are seeing is, again there's 0 capacity available for week 7. Okay, so 14 hours we need to move into the future, and even though we could move, if I come to week eight I more than have ample capacity from a machine perspective, but from a labor, I'm already over the amount of labor I have available for week 8. So this is where we have a conversation with operations to determine, hey can we address this issue here by adding more labor, and typically based on how that conversation goes, it dictates whether or not we add additional labor here, or do we need to reduce the amount of available capacity so that when we do schedule production, we are not having so many issues from a labor perspective and of course you can see which orders to move. We can take from a machine perspective, you could drill down, see all the orders, which is contributing from a, from a machine perspective. So let me arrow back, you know, and if I came down to, from a labor perspective and drill down, we will see the same orders. Each one of these orders, you can get to them from, either from a labor perspective or from a machine perspective. Make the change, so I can take this for example, come into the plan order, and I can change the timing of this. So let me come here, I'm going to drill down and I can say, look I'm going to move it to like week 24, I'm going to reschedule this. I got a warning, okay it calculates the new timing. I can click save and what you can then observe when I do a refresh this one line item is going to move and by moving into the new timing it also takes the required capacity, both from a labor and machine perspective. So refresh and the line did decrease. I can then come back here, I can do a refresh and we should see these numbers up here adjust. The point is it already adjusted. So that's one way of addressing capacity overloads. What I'm going to do is take you into another transaction, this is CM05. The selection screen looks exactly the same, and the options are also the same. So what's the difference between the two, CM01 versus CM05? The difference is that, let me go in here, CM05 only brings up those weeks or months that has over capacity. So yes, I can come settings general, you know, you can also look at it from a monthly perspective so we can see here from a monthly perspective it is highlighting some issues the issues based on what I had initially retrieved, so the work centers category one, category two, they disappeared. Why did it disappear? Because of the fact that when we looked at it from a monthly perspective there was sufficient capacity. So the information we are seeing here is only based on remaining work centers in the facility that has a bottleneck or capacity overload. If I come back and I switch back to weekly bucket, then the initial work centers that we were working with will then come back. So you can see now this is the work center we are working with capacity category 001, week 7 versus 002, which is week 7, 8, 9, and 11, and week 10 is not here. So with week 10, we do have sufficient capacity but the fact is that with transaction CM05 it only focuses on the weeks and work centers that has capacity overload. We saw that when we went into the monthly bucket, this work center for this labor category, it did not have any issues, hence it was not presented as an issue. So you can really zero in on, hey, where do I truly have capacity issues, depending on if I'm working on daily, weekly, or monthly buckets. Okay, so that's the concept of capacity overload, doing analysis, identifying where the overloads are located within your facility. So in summary we have covered how capacity overload allows users to. Perform capacity evaluation using capacity load and capacity load transaction. Uses to understand the difference between capacity load and capacity overload transcation. And users to appreciate the value in using capacity load transaction. Thanks Eacliffe. Using this feature will provide the planner and schedule with greater visibility on when the capacity overload will happen and allow them to prevent it and therefore increase production efficiencies. So if you want to learn more about how to get the most out of the SAP system check out our other videos and if you can't find what you're looking for please submit a suggestion.
Checking Rule for Created Process Order
SAP® ECC
New
Production Scheduler
Production Planner
Production & Capacity Planning
PP
COR1; COR2; COOHVPI
Hey folks, welcome to the video service that unlocks and reveals the hidden value in your SAP system. Martin here and as we know the best way to learn is by doing, so let's get going here. In this video, we want to identify how the system determines which checking rule to use for each component required to create a process order. As we migrate through the maturity of a manufacturing order from planned order, to create a process order, and finally to release process order. We typically want to apply different business rules into which inventory supply elements we want to include in our checking rule to be able to make sure that we know that in the process order or production order for the scheduled and production timing. So once again, Eacliffe you're the best guy I can think of to help explain this, take us away. Thanks Martin. This is a process that is automated in SAP with configuration. The key to getting the desired results is ensuring that the scope of check configuration aligns with the business rules regarding which inventory elements to consider. Too often, many clients do not use this functionality because they don't understand what the system is doing or it is configured incorrectly. By demystifying what the system is doing and having the correct configuration, this functionality improves scheduling, productivity, and eliminates guesswork. So let's look at how process order component availability check determines which checking rule to apply for each component needed. Do all components use the same checking rule? By default, the checking rule for each component is based on the material master setting for each one of these components on the MRP3 view and the business process that is triggering the check. In this case, it is the process order and it creates status that is triggering this check. In this session, we're going to take a look at component availability check for a process order in create mode. So here's my process order, let's go into it and here you can see that looking at the system status, it is sitting in a create status, and we can also see that ATP was ran previously where it had missing parts. So the question is, do we still have missing parts or not? So we're going to come here, click on this icon to determine if there are any missing components, and this pop up is telling us that yes, we still have missing components. So let's go into this pop up and we can see that we have two components where they each have insufficient inventory. We need a quantity of 78.75 units of each and it is needed by the 19th of April versus the commitment date of 12/31/1999, indicating that we don't know when that supply is going to be made available. So what's being taken into consideration, at least for this first component? So we're going to select it, come in here, and what we can see is that for this item, the first component, again, we can see the requirements, how much is needed. and we see the date it's needed and the confirmed quantity is 0. So whether or not we see a confirmed quantity is dependent on things like what supply elements have been taken into consideration, as well as taking a look at a replenishment lead time, for example, again, depending on the settings. To see what settings is being employed, what we're going to do is take a look at this scope of check, and here we can see things like, in create mode we can say that, hey, take a look at safety stock and whether or not to take in transit, quality stock, and so forth. In this case, this check mark says do not take replenishment lead time into consideration, rather we want to look at more firm source of supply, things like a purchase order for example. If we were making it we know that it's a produced item, so, semi finished material, so in this case, we're not even taking process orders into consideration. So depending on what you are trying to accomplish, or what rules you employ to say whether or not you have a sufficient source of supply this is the area that you would take a look at to say hey if I'm doing this manually, which elements do I take into consideration? What inventory supply elements do I need to compensate for some of it? Looking at some demand, maybe demand for shipment to another plant, for example. So these are the things that we then reflect here in the scope of check. And then what happens is when you click on this icon here you can then see, hey, is there any inventories, like what receipts are we looking at? What sort of issues or goods issues that we can expect? And what's being confirmed in terms of if any of these demand elements were confirmed, we would see a quantity sitting here. Sometimes you want to see this because the fact that look, something may have reserved inventory and the point is you no longer wanted to reserve inventory. So again, this is just some of the insight you can gain by coming into this screen for that particular component to say, can I get inventory or not? Can I juggle things around so that I can run this specific process order? Hey, welcome back. In this demo, we showed. How to identify which checking rule was applied to each component in the process order with a create status. For a process order in this status, inventory elements are considered to say yes, no, or partial in terms of component availability to meet the demands of the process order. Checking each component for inventory availability should be the same as if you were making this decision manually. Wow, that's extensive Eacliffe, thank you so much. The last thing we want users to do is guess the results the system is providing. What's probably worse is duplicating work that the system should be doing for us. So as a manufacturing order goes through the different stages of planning a production run, going from planned order to created process order to finally to be a released process order, we typically want to apply different rules for the checking component of the availability of that component and the reliability of that availability. So folks, if you want to learn more about checking rules, ATP, and even just process orders, generally speaking, there's a whole bunch of other videos you can check out and of course if you have a burning question please submit it below.
Create Hierarchies
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CM01; CR01; CR21
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin, and in this video we will focus on how to take advantage of SAP's capacity hierarchy capability. When used correctly creating these hierarchies can really help organizations roll up their capacity requirements that will provide planners with greater visibility across their capacity constraints. Eacliffe, how about you tell us a little bit more about how to use this capacity hierarchy? Okay Martin. Create hierarchies is a powerful feature when used correctly, provides summarized capacity information for multiple work centers or you can use it to retrieve your subset of work center information or work centers themselves in various transactions. In this demonstration I'm going to focus on three things. How to set up a superior work center needed for a work center hierarchy. How to set up a work center hierarchy itself. And how to use the work center hierarchy in capacity evaluation. Here we are in transaction CR02 work center change to review a superior work center, which I created to work with the work center hierarchy. The superior work center is a light version of any other work center required to define a works of hierarchy. So looking at the basic view what we can first notice is, yes, we have some of these fields maintained but observe the standard value key 000, the point is we don't need any standard values parameters. Okay, the other thing I'm going to call out is when we go to the capacity view, this is during the interview which I've maintained for this work center and all I'm really doing is identifying which capacity categories I want to report on using this work center, superior work center. So we have category 001 machine time, again no formula needed and when I go into the details, you could see there's no calendar, no start finish time because this information from a reporting perspective is going to come from somewhere else. So this observation can also be applied to capacity category 002 label, again I drill down and literally we don't really need all these settings is irrelevant, we don't need these settings. And then finally I have a third capacity category, so let me scroll down, page down and now I can see I created a pooled capacity category and also with this again, if you go into the details, there's nothing maintained. So now that we have this understanding, what I'm going to do is go into the work center hierarchy, create transaction, so this is transaction CR21 and what I want to do is identify the name of the hierarchy I'm going to create. So with the superior work center I basically use the same name but I put an S just so we can make the distinction of, am I looking at the superior work center versus am I looking at the hierarchy? Okay, and so I have the H to represent the hierarchy and I'm going to hit the hat, go to the header and then give it a description, so I'm going to use the name it's two packing lines that this hierarchy is going to represent, packing line 1, packing line 2. Okay, and I am now going to say, okay, let's do some work center assignment, so you maintain your parameters that will bring up the work centers of interest, I know with me I can use this as an example and here we will get a listing of all the work centers that began with the letters CHEM. Okay, so I'm interested in the superior work center and then packing lines 1 and 2, not the last one. So I'm going to come here, do a select all, I'm then going to deselect the one not of interest since this was the fastest way of getting what I wanted and before I save it it's a good idea to come and look at the graphics of this. So looking at the graphics, what you can see is we have the superior work center again the one ending in S and the goal is to take information from packing line 1 and pack line 2 accumulated together and presented against the superior work center and that's why I call this work center lite because all the details we need from a reporting perspective will come from these two work centers. Also, please be aware that the superior works and must sit on the top when you do this graphing. If it's not on top you need to fix that and make sure the superior is sitting on top. So I'm going to come here now, hit save and that's it. I have now defined this hierarchy, so what I'm going to do is return to transaction CM01. So let's do this /ncm01. Okay, which is capacity planning transaction and if I want to bring up information I'm going to get rid of that work center. I can now retrieve my reporting based on under work center hierarchy, so click on selection, work center, I'm going to come here and do it through this transaction, so you could see I have the hierarchy again it's the object name ending in H. So here we can see again there's the representation of the hierarchy where we have the superior work center and then the individual work centers. So with that said I can then green arrow back, we could see it listed here, these are the objects I'm going to retrieve the data for and then go click on standard overview. So here we have the superior sitting on top. Currently, everything is sitting at 0 in terms of requirements and available capacity that holds true for machine. Just to aid with visibility I'm going to present the data in monthly buckets, and by doing that I can now get more information presented all at once. So again, machine capacity, everything is 0 at the superior level, same thing with label. Let's go down one page, I am now looking at the pooled capacity again, this is also at 0. Now we get to the individual capacity and you can see packing line 1, there's 50 hours needed out of availability of 96 hours, and let's scroll down again, we could see the pool, the red means it's over capacity I need 225 hours I only have 192. And then for parking line 2, similar situation, there's also 50 hours required out of 96 and the pool issuing, it's also over capacity which makes sense because the pool is really sharing a labor force between packing line 1 and packing line 2. So what I'm going to do is do one more thing by going to settings general, and you can see my hierarchy, in this case it defaulted in. If it ain't default in you can find it with a dropdown and I'm going to say, look accumulate the requirements, capacity requirements, and also the available capacity, green check and you could now see again we had a superior resource and now we could see, remember we had 50 hours coming from parking line 1, 50 was coming from packing line 2, so that summation of that is 100. We had an available capacity of 96 on both machines so that also got reported here and we could see for the other months the available capacity in terms of labor, there was no labor defined that's why everything is 0 and. I am going to come here and scroll down slowly so we can validate this and then we could see that the pool, even though we said to accumulate the information, because this is a pool it did not accumulate because that logic has already been taken into consideration saying, look, you don't double up the requirements and you don't double up the available capacity. Okay, so this is how we go about defining a work center hierarchy, this is how the functionality works and this is how you can use it to retrieve work center information within the capacity planning transaction, for example. So in summary we have covered. How to create work center hierarchies, which allow users to create a superior work center which is needed to create a work center hierarchy. It allows the users to set up the work center hierarchy itself. And it allows users to perform capacity evaluation using the work center hierarchy. Thanks Eacliffe, a very underutilized feature for sure. However I can see how this feature can allow users to aggregate the data to better support their decision making. So once again, if you want to know more about this particular feature or other features in your SAP system please check out our other videos and of course if you don't find what you're looking for please submit a request.
Create Pooled Labor Capacity
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CR11; CR12
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, Martin here and in this video we will focus on how to take advantage of SAP's pooled labor capacity capability. When used correctly creating pooled labor capacity can help organizations more effectively manage and allocate production capacities and resources. Eacliffe tell us a little bit more about this pooled labor capability. For sure Martin. Pooled labor capacity is a powerful feature when used correctly and in this demonstration I'm going to focus on three things about pooled capacity. Define what pooled capacity is used for. How to create pooled capacity. How to assign pooled capacity to a work center. Here we are in the pooled capacity transaction, CR11, to provide a perspective of what pooled capacity is and how to apply it to work centers and resources. We use the same transaction regardless of which manufacturing solution is being used in SAP. The solution could be PP, repetitive or PPPI. Before maintaining data it's good to know what we're using the pooled capacity for. The typical business scenario is to reflect more than one work center or resources that share a common labor pool. I will illustrate the scenario with 2 work centers. So I'm already sitting in the initial screen of transaction CR11, I'm going to maintain a pooled capacity in the manufacturing plant 1000, the pooled capacity I'm giving it the name labor pool 1 and because it's a labor capacity we are going to use capacity category 002, where 002 is labeled. So I'm going to head enter and here we can give it a description, I'm going to cheat a little bit I already have predefined a description, packaging labor group 1. Again it's being done for labor capacity, I'm going to put this indicator on to indicate that it is pooled capacity that we are defining and then the factory calendar, I'm going to use the same factory calendar we use for the machine capacity which was in category 001. So this one is 01, something that I know ahead of time. Okay, and the other thing I'm going to change is, the machine capacity says that the line starts at 8, we expect the people to start working at 8, so I'm going to modify this 7 to an 8. Okay, so the labor force is going to start at 8 o'clock, they're going to finish at 5 o'clock, there's a 1 hour break. So when I hit enter, what we'll see is operating time is 8 hours and we are going to say the number of people that reside in this pool is 10 people. Okay, so my capacity is going to be 80 hours and the interpretation of this is 80 labor hours. I am going to turn off the relevant to finite scheduling since we are not doing any kind of finite scheduling on the labor force, rather we just want to do capacity evaluation. Then finally, like what we did with maintaining capacity for an individual work center, we are going to take a quick look at the interval and shift only because this is where we would come and maintain the labor force over time. So for example, if we know that starting 6 months from now the pool is going to go from 10 individuals down to let's say 5 individuals, we can reflect that change here so that when we do capacity evaluations 3 months out, 6 months out, 1 year out, we can pick up the correct labor capacity as part of our evaluation. Okay, so I'm going to click save here and now we have the labor pool. I'm going to copy this, so highlight it, control C, let's go into maintaining the work center, so transactions slash 0 for a new session, CR02. Okay, I'm going to bring up the first packing line, which is PK1, I'm going to go to the capacity tab, right now there's only 1 capacity category, so what I'm going to do is scroll down, click on create, I'm going to enter capacity category 002, and I'm going to do a control V here and then we should have formulas. This should be SAP007 for working with labor hours. Hit enter and you can see this information is now sitting here and this is how we now link the first work center to that pooled capacity, and I'm going to save. I'm going to go now to the second work center that shares that labor pool, so that's packing line 2. Again, I'm going to go to the capacity tab, there's no capacity category 002, so I'm going to scroll down, create a new capacity, maintain 002. Again, I'm going to maintain the labor pool and I'm going to maintain the formula for calculating labor hours. Okay, and with that I'm now going to hit save. So these two work centers, packing line 1 and packing line 2, when we create a plan order or production order that puts requirements in terms of labor hours against these work centers, the goal is to do an evaluation against a common labor pool. So let me illustrate that, at least from an available capacity perspective, so I came here what I'm going to do to bring up both my work centers, I'm going to use a wild card, so I'm going to get rid of the one, put an asterisk and click on standard overview. Okay just to provide better visibility I'm going to go to settings, general, let's look at it in monthly buckets and what we can now see is we have packing line 1, we have the capacity, available capacity in terms of machine hours. So January has 16 hours left versus when you come to capacity category 2 which is labor, we can see that because we said there's 10 people available under labor pool, you can see available capacity is down at 160. You can also see clearly called out that we are dealing with a pooled capacity situation here. So if I come down to the packing line 2, it has its own individual machine hours. Basically doing the same profile as packing line 1 but in this case, we can also see the 160, which is also coming from the pool and again this allows us to say, look, when I have labor requirements, that labor requirement, let me compare it to the pool of people rather than comparing it to available direct labor on that work center. So in summary we have covered how pooled capacity allow users to. Understand what pooled capacity is used for. It allows the users to correctly create a pooled capacity. And finally to allow users to correctly assign pooled capacity to work centers. Wow, once again thanks Eacliffe much appreciated. A powerful feature for sure. Something that I can really see benefit the planner in their job. Once again if you want to learn more about this feature and others please come back to our other videos in our catalog and of course if you don't see what you're looking for please feel free to submit a suggestion.
Drawing Insights From Capacity Evaluation
SAP® ECC
New
Customer Service
Demand Planner
Production Planner
Production Scheduler
Supply Planner
Production & Capacity Planning
PTM; DM; OTC
CM01; CM04; CM05
The best way to learn is by doing, so welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hello everyone, Martin here, and I'm thrilled to engage with you on some of the information insights that you can draw from capacity evaluation in SAP. This powerful area of SAP is often underutilized. So today, we'd like to show you some ways that it can be used to help with answering questions in your organization. To lead us through this walkthrough today is Tom, who has a ton of practical information and experience in this area. So, Tom, take us away and share a lot about capacity evaluation. Hey, Martin. Well, when we think of capacity evaluation, it's often around the challenge of either being over capacity or figuring out a run plan for a work center or resource that are not fully booked out. Both are good uses of this functionality. But today, I want to take it a little further and hopefully show something that is new to you. First, we'll go in and look at our work centers that have a current backlog that needs addressing. Next, I'll show you how to accumulate capacity and requirements to see what the planned recovery date or next bookable date for that work center looks like. And lastly, I'll extend the time horizon and change to monthly buckets for a longer term outlook. Let's go in and take a look. Now we're going to dive into SAP and look at capacity planning and how we can understand our current state of what's happening, and also future state of what's going to happen. We'll begin our journey today by looking at CM04. CM04 is going to show us any backlogged production that we have on a work center. So this list, if we come in here, I'm going to put in my work center, which is already limited in my plant. When I look at this work center in this plant and select the overview, it's going to pull up any backlog work that's on this work center for me to see. Now as I click deeper into this, just by double clicking in, I can see the requirements of what's out there that what my production is behind on. This allows me to focus on these orders first, knowing that we're behind in its tying up capacity that we did not plan for today because these are past due orders that have not been completed. So using this CM04 tool, we can understand where we're truly behind and what specifically the orders that we're behind on to get caught back up in production. Once we understand and know where we're behind and what's affecting past dues for capacity, we can now turn our attention to looking at a current state of capacity. For that, we'll go in and look at CM01. CM01, again, gives us the same sort criteria as we can look at a work center in a plant, or we can look at all work centers in a plant, just to know that is also an option. As we look at the standard overview for this one, we're going to see a much different picture. So instead of just showing us what we're past due on, it's going to show us current and future requirements as well. So as we can see here, clearly anything that's red shows that we're over capacity. That's a concern for the shop floor. We need to understand why we're over capacity and how we can overcome that situation. Whether that's going in and looking at the details again and understanding can I move any of these orders out to lighten the capacity load. Or do we need to work overtime to overcome those capacity requirements? The other thing I can do inside of CM01 is I can break it down into different buckets. Currently, we see we're looking at it in a weekly bucket. However, if I were just to go up to the general settings, I have the option in here to change the capacity into any buckets that I prefer. I can see right down here I have a selection of different periods. First we'll look at it in a daily bucket. If I look at it in a daily bucket, this allows me to understand on a daily basis how am I utilizing my capacity. It could be that I'm over capacity on Monday, but fine on Tuesday and Wednesday, which then I know I can smooth those requirements to the other days of the week. In this current example, we can see here we're over capacity on most days in the current periods, but I can go out and look and see, okay, what's the next day I can actually put orders in where my capacity is open again? And in this example, I can see out on 12/9, I have 88 percent of my capacity remaining. So again, I can possibly move orders out into these dates, or new orders can go in those dates because I have capacity. In the short term, if I can't move orders out, I'm going to need to work some significant overtime or possibly hire more employees. But this gives me a picture of when I can recover and when I can actually add new orders into my production. The other thing we'll look at now, as we look at longer term planning, we may want to look at this again in weekly buckets, which we already saw an example of, but if now I pull it up in monthly buckets, I can start to look out to the future to see, okay, how are my monthly buckets of capacity looking in the future? This allows me to have more of a long term planning picture of what's going on in my production environment. As I can see here I only have three months showing with loaded requirements. So when I go out to the third month, I've got plenty of capacity and I can add tons of orders and lots of production in that, and I'm getting a little tight in the month of December, but my current month is way over capacity and I need relief. But this allows me to have a picture as far out as I'm holding a forecast or customer orders, any requirements I can see in the system, I can evaluate how that looks on a long term basis. So when we look at capacity in SAP, we not only have the ability to look at past due requirements, current requirements, we can also look at it with future requirements to understand our capacity situation and what we have to do about it and what we have to do to resolve any issues. So I have to confess, today we only hit three features on my favorites list. There are more, but this is a good start. With the features we looked at today, we can start to draw some insight of capacity evaluation. Are we ahead, or are we behind? What is our current lead time to put more work on that work center or resource. And we can proactively identify challenges or opportunities as we look across the broader horizon. There's a lot here, and I hope you'll go back and see what you can find. Thank you, Tom. That's such good information, and it's really easy to navigate. But folks, the challenge is making sure that we have the right rules to give us the right information. If capacity evaluation isn't SAP's part of your process, there a number of other videos that you should explore. This is a great gateway between S&OP and S&OE. So folks, if you're looking to maximize the value in your SAP system, please check out our chatbot that will share with you what recommendations can provide, specifically on capacity evaluation as an example. Or if you have a specific question, please submit it below.
Leadtime Scheduling
SAP® ECC
New
Production Planner
Production Scheduler
Supply Planner
Production & Capacity Planning
PTM
MD01; MD02; MD03; CM01; CM25; MD01N
Martin: Hey folks, welcome to the video service that unlocks and reveals the hidden value in your SAP system. So the best way to learn is by doing so, let's just get straight into this. This video in particular, we're going to be focused on using SAP's production planning lead time scheduling to generate machine and or labor capacity requirements to produce the required inventory. So I'd imagine I'd be preaching to the choir if I rattled off some statistics around related to being able to provide a quality promise to your customer. Making and keeping that reliable promise to a customer in many areas is a right to play and in others just purely a competitive differentiator. This of course, strengthens the integration between ATP, order fulfillment, procurement, and of course even product costing. So that's a lot. So how about we get into it and of course, tell us more about this Eacliffe, love to hear more about scheduling. Eacliffe: Thanks Martin. This topic allows production planners to aggregate capacity data to perform a relatively quick evaluation of manufacturing assets, for the short, medium, and long-term time horizon to make key decisions in honoring the commitments to providing manufactured materials in a timely manner. Production planning often occurs outside of SAP, given the existing solution needs to be fixed or takes too much effort in SAP. Unfortunately, this approach does not work well when integrating with other supply chain activities such as exception monitoring, purchasing, and finance, just to name a few. Why, of course, you should be able to promise against what you have. Why would you not be able to do that? If you are in this situation, don't worry, we are going to walk through what you need to be doing about it. Let's get into SAP. Let's explore how lead time scheduling works and let's understand its impact.What I've done is I've taken this material, put some demand in SAP or MRP as generated plan requirements. And when I ran MRP, I did not tell it to generate or use lead time scheduling. The results of that is when I double click on the plan order, I come into change mode, we can see that there are only three tabs, the header assignment, and master data. When I come to the master data tab, we can see that there is nothing related to the routing or master recipe. So that's issue number one. Okay the way this shows up in capacity evaluation is when I come over to the capacity evaluation transaction, the expectation is in this particular demonstration, we would expect requirements against this particular resource. So let me click on standard overview, and right now what we see is just 0 requirements. So even though we have planned orders out there over this time horizon the system is saying, look, don't need any capacity on the resource at this time. So I'm going to go back into the stock requirement list, and I'm going to rerun MRP using lead time scheduling functionality. So, the parameter of interest is this one down here, the scheduling parameter. When I do the drop down, there are two options. One is which is what I used before , is basically just give me timing. Based on other criteria I just need basic dates, but don't really give me capacity information versus option two. Option two says not only calculate the dates, the start and finish dates, but also tell me how much capacity I need to fulfill each of the planned orders for this material. So let’s select 2, I’m going to hit enter, enter to run MRP, come back over here, I'm going to do a refresh and now I'm going to take a look at the planned order. Let's come to this plan order, come in to change mode. What we can see is first, that there are now four tabs rather than three. But let's go to the master data tab and we can see that there's additional data now on the master data tab where the master recipe got pulled in. So this master recipe is now providing the production rate in terms of, hey, this is how many units we can produce over a certain duration of time. And then if I come to the scheduling tab we get the exact information in terms of basically what we will see is, let me scroll over or make this smaller so that we can see that basically 30 hours of time is needed. So 30.32 hours is needed to fulfill this particular, planned order. So when we convert it into a process order, that's how much time we would expect. And of course, when I come back to capacity evaluation, I'm going to do a refresh over here, and now we can see that we also have capacity information sitting over on this side. Okay, so you could see the impact of doing lead time scheduling and the fact that if the desire is to do things like work on the scheduling board, do capacity evaluation, we want to run MRP in lead time scheduling, regardless of if it's being done in background mode every night or it's being done online one material at a time. Hey, welcome back. In this demo, we have covered a few things. First, how to quickly perform capacity evaluation when performing lead time scheduling. Secondly, how to trigger lead time scheduling. And thirdly, the information required to perform lead time scheduling and strategic integration points. Martin: Eacliffe, thank you so much. Much appreciated. That's a lot of detail. So lead time scheduling allows for lengthening the runway on identified bottleneck challenges, and improving your supply chain integration. This is a topic often isolated in a spreadsheet that is poorly integrated with the remainder of the supply chain information in SAP due to data inconsistencies, et cetera. It's also going to be a journey to get us there. We have got to go from basics and kind of grow into maturity. But there's no question that this is a hot topic and can make a big difference in how we apply this to our supply chain. So folks, if you want to know more about this topic and other scheduling related issues related to SAP, please check out our other videos. And of course, if you have a particular question, feel free to raise it below.
Maintain Multiple Capacities
SAP® ECC
New
Production Planner
Supply Planner
Production & Capacity Planning
PP; PTM
CR01; CR02
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin and in this video we will focus on how to take advantage of SAP's multiple capacities capability. When used correctly maintaining multiple capacities can help organizations manage the capacity utilization of multiple resources such as equipment or personnel in a much more effective and efficient manner. Tell us how to make the most out of SAP's multiple capacities capability Eacliffe. Sure Martin. Maintaining multiple capacities is a powerful feature when used correctly, it'll allow us to look at different type of capacities for a single work center. In this demonstration I'm going to focus on two things. How to assign and maintain different capacity categories for a single work center. And how to evaluate capacity for these different capacity categories. The intent here is to discuss working with multiple capacities for a work center. Let's look at an example of what I'm referring to by looking at the capacity planning transaction CM01. So here I have this single work center. We are going to take a look at the standard overview. Just aid with visibility I will change my settings to look at things in a monthly bucket and so here we can see that for this single work center, I have this capacity category of 001 machine and I have a second capacity category ZLB which is a pool labor group. So the point is, it is possible to define different categories of capacity for a single work center. What I'm going to do now is jump into the change transactions for work center and add an additional capacity category. So I have this session queued up here is the work center we are going to modify, we are going to go to the capacities tab and here this is where the existing capacity categories are defined and the goal is to add a third capacity category. So scroll down, got these icons, click under create capacity icon, and here I'm going to create one for labor. So the existing labor capacity we have, ZLB, this is for a pool capacity which is covered in a separate, session, but the point is that the labor force here is shared among more than one work center versus 002, this is direct labor, in other words any labor that's maintained in the routing is dedicated to this particular work center. So I'm going to use 002 maintain the formula for calculating the capacitor requirements. You have to come in here, do some added maintenance, and that maintenance can be, using a calendar. If you don't do the calendar then it picks it off the plant. I am going to change this to, starting at 8:00AM so when I hit enter it comes down to eight hours per day and this is a default I'm going to work with for now. I'm going to save this. We have now defined an additional capacity category. So with that, coming back to the capacity evaluation, let's see if we could do a simple refresh, and by simply doing a refresh, this third line showed up down here. So let's scroll down and confirm that new capacity category of 002 is now included and if there were any orders that had that capacity category, which it wouldn't have at first, because the point is we first have to maintain the master data, then we have to maintain the routings and then the third step was that when we then create plan orders, production orders, it would pick up this additional capacity category and it would populate this column, the requirements. Okay, so this is how we go about defining multiple capacities for a single work center. So in summary we have covered how to. Maintain multiple capacities, which allows us to assign and maintain different capacity categories for a single work center. And how to evaluate capacity for the different capacity categories. Thanks Eacliffe. I can see how this feature will help us optimize resources and increase our overall productivity while reducing waste and downtime. If you want to learn more about this and other topics in your SAP system please feel free to check out our video catalog and if you have a specific question feel free to log it below.
Right Place, Right Time: Aligning Material With Pace of Production
SAP S/4HANA®
New
Materials Manager
Production Planner
Production Scheduler
Supply Planner
Production & Capacity Planning
PTM
MD04; CS02; MD02
Hey there, fellow supply chain superstars. We love getting questions from you. It helps us drive prioritization of our content, and today is one such video. Do you ever find that you're having trouble planning materials for the pace of production? Do you have particular materials that need to be delivered throughout the production run versus being a hundred percent available and in stock at the beginning of the production run? Well, we want your exceptions to mean something, and we don't want you to have to break down your delivery schedule manually. So who better to ask about this particular topic than Nicole? Nicole, this is an area that you are very familiar with. Why don't you share some more details on it? Hi Martin. This is such a great question. Anything we can do to make a planner or buyer's job easier, I'm in. SAP offers several tools that can help us refine the timing of requirements, and one such tool is called the distribution key. This is targeted for our longer runs of production where we may need to receive several deliveries of particular materials to properly feed manufacturing. Once this rule is in place, MRP understands what we're trying to do, and it splits the dependent requirement for that planned order. This then gives us a proper requirements date to align our deliveries to. It also helps us to get a more and meaningful material availability check based on our plan for replenishment. Let's get into SAP and take a look. Today we're going to talk about how we can use a distribution key within the bill of material in order to evenly spread a dependent requirement out over a period of time. As you can see in this example, I have a component and my stock requirements list is indicating that I need 20 million pieces of this component available on 04/10 for dependent demand. Now, that is a lot of material to use on a single day, especially if we look deeper at the dependent requirement, we can see that this planned production order is actually going to take place over a matter of years. Wouldn't it be easier if we were able to evenly distribute this dependent requirement over the period of time for the planned order? Well, we absolutely can, and we're going to do that by using the distribution key within the bill of material for the assembly. I'm going to navigate to the bill of material for the assembly, and I'm going to navigate to the line item details for the affected component, and I'm going to set a distribution key which will equally distribute that component over the dependent requirement. I'm going to save. Once the bill of material is saved, all I now need to do is rerun MRP for the assembly and re-explode that bill of material. Easy. Now, refreshing at this level is not going to show any improvement. However, if we navigate back to the component in question, we will see the dependent requirement coming from that assembly is now evenly distributed over the years of which that assembly is going to take place. This means instead of procuring a single incoming receipt of 20 million pieces, we can plan receipts across the time period that is intended for that planned production order, with just the click of one button. I love it when a good plan comes together. So let's go over a few key reminders. First, SAP and MRP in particular love rules. So the more rules that we know and can get into the system, the better MRP will do at giving us a reasonable plan for supply. Second, not only is this conversation around the right time, but also the right place. As we break down those requirements, we want to make sure we know the operation and the location where we'll be introducing that material into the process. And third, flow in parts productivity and manufacturing. Let's get the timing right so we can perform well and efficiently. Back over to you, Martin. Hey, thank you so much, Nicole. That was awesome. Love the walkthrough and I'll bet the Reveal TV folks and community love the idea of knowing how to use and align materials with the pace of production. So once again, thank you. Hey folks, if you can't find the video you're looking for and the AI is not giving you the recommendations you need, hey, please just submit the question below and we'll build some content for you.
Work Center Hierarchies and Superior Resources
SAP® ECC
New
Production Planner
Production Scheduler
Supply Planner
Production & Capacity Planning
PTM
CR31; CR32; CR33; CRC1; CRC2; CRC3; CM01
Martin: The best way to learn is by doing so welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin and in this particular video we'll focus on using SAP's work center hierarchy to perform capacity evaluation for a group of liked work centers. A debate may take place to define one work center to represent a multiple like machines, or create a work center for each physical like machine and use a group center hierarchy with a superior work center to perform capacity evaluation. So let's get into this. Eacliffe tell us more about how do we do this specifically in this grouping of evaluations of work centers, specifically in a hierarchy. Eacliffe: Hey, thanks Martin. I have set up a demonstration to. Illustrate the functionality of a work center hierarchy and a superior work center. So while it be easier to generate a single work center, or let it represent multiple work centers, this approach can sometimes be challenging when assigning a particular manufacturing order to a specific work center, for example. Regardless of the reason for having a one-to-one definition between a work center in SAP versus the physical, uh, machine on the production floor. By defining a work center hierarchy, capacity evaluation can be done for both the individual work centers and the superior work center. So let's get into SAP and look at how this functionality works. So this is a demonstration on how to aggregate production capacity information for resources or work centers. So you have the situation where you have like multiple, resources or work centers, and the whole point is you want to see, if I combine the capacity information for more than one resource am I able to do so? So the answer is yes, and you have the ability to do this either under discreet production and with production you would use a combination of work center master data setup along with hierarchy information or master data setup, as well as under the PPPI, you would use resources and also the hierarchy master data setup. So I've set up some data to illustrate exactly how this works. First, let's take a look at the resource that I created that basically represents the superior resource. I'll come into change mode, I called it this name here, and let's just walk through some of the views. So on the basic view it's a very light version of a resource. Basically what I'm doing is really creating this object to say, look, this resource represents a superior resource. And you could see that I don't need to maintain any kind of standard value information for this particular resource. Likewise, if I come to the capacity tab, yes I maintain the capacity category because I want to see information from a machine perspective. If I want to see labor, I would create a second entry here for labor category. But again, I would not maintain any kind of formulas. The whole point is that we would obtain the information from the, call it the children resources or work center. And finally, coming here to the scheduling tab, again, there's nothing maintained because again, the information that's needed or that is used by the system would be derived, from the, resources that’s actually doing the production. So with that said let's come back out and now I’m going to come to the hierarchy. So let's look at it in change mode, I gave it the same name as I did the superior resource, the names do not have to match. Okay? So it's your prerogative in terms of what name and convention works for you. You can use the same names or you can use different names. It all depends on what works for you. So with that said, I'm going to come and click on this icon. And it's basically saying, hey, I have this superior resource, you could see the first entry here, and then we have the, what I've been calling the children resource. So we have these two packing lines, 1 and 2. The thinking is that the materials which I produce on, let's say line 1, the majority, if not all of the materials on line one can also run on line 2. So it makes sense to do an evaluation with the two of them combined, just in case I have insufficient capacity on one line, then I can say, okayoverall, do I still have sufficient capacity? And if I do, then I'm not going to worry about it. I'll just move some of the production from line 2 to line 1. So what I'm going to do next is let's take a look at the capacity evaluation itself. So here I am in CM01 and I'm going to come in here. I maintain my plan, and on the planning I'm going to go to work center and I'm going to click on this icon to work with the hierarchy rather then the individual resources. So this is the hierarchy name. I'm going to do a green check here. It gives you a illustration of what the hierarchy looks like. So here's the superior resource, and then I have the individual. I'm not aware of any limitations of how many resources or work centers you can have attached to a superior resource. And of course you can also do multilevel. So I can have SP2, and SP2 could be something, you know, let's call packing line 4 and 5, and then you could have it all roll up into, hey, give me an overall SP network. Okay, so it could be multilayers from top to bottom, and I've got multi resources work centers. With that said I’m going to green arrow back and from here you could see the superior resource as well as the individual resources sitting here as part of the selection criteria. Here, I'm going to do a standard overview. You could see that right now I am sharing that there's 0 capacity required at the superior level and as well as available everything is sitting at 0. If I scroll down we can see that hey, we have a little bit of capacity requirements sitting down here. And then if I come further down, we could see, hey, this resource it does have capacity requirements, and the red lines indicate that I am over capacity. So what I can do from this point is then come here, click on settings general, and you can see in my case, the hierarchy ID, popped in here. And I'm just going to say, okay, you know what show me the capacity, the requirements only at this point. I mean ideally we’d look at two but I want to show the fact that just by turning this on I'm going to do a green check and we can see that, all the requirements capacity required is now sitting up here in the superior. Of course, everything is red because of the fact that we did not turn on the indicator for available capacity. So of course, all entries are over capacity of each week. So what I'm going to do is come back up here and I'm going to come back and let's go back to settings, general, I'm going to turn on the accumulation of capacity. This is the available capacity now we're looking at, I'm going to green check, and you can see that, suddenly everything is white. So the available capacity for the superiors, 32 hours for the first week because of the fact that we got 16 hours coming from packing line 1. And if I come into parking line 2, we expect to see 16 hours also. So you can see, look, still looking at the individual resources, I'm over capacity. But looking at it from a superior perspective or hierarchy perspective, I have more than sufficient capacity week after week. So this tells me quickly that I can move production from one line to the next. Hey, welcome back. In this demo, we covered. What capacity evaluation looks like when we use a work center hierarchy solution in the capacity evaluation. With this approach, a finite production schedule is done to a specific work center. Hence, we would schedule to that specific work center rather than a generic one. Plus, you can specify downtime to a specific work center instead of reducing the number of individual capacities with that generic work center. Of course, the work center hierarchy would pick up all these business scenarios I just identified. Martin: Thank you, Eacliffe, that's actually brilliant. It's good to know that these kind of options exist, right? When it comes to how to set up work centers in SAP, it's not uncommon to implement a solution that works for many business scenarios, but when it comes to finite scheduling, for example, the production planner or operations requires a lower level of detail that may be required creating additional work centers. Regardless of the need for the additional work centers, using a work center hierarchy could be the compromise to bridge the gap. So folks, if you want to learn more about capacity planning, generally speaking, or in the hierarchies, there are other videos for you to check out as well. And of course, if you do have a particular question for us, feel free to submit it below.

Try changing or clearing the filters

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

No results. Try changing your search keyword.

What Is a Scope of Check?

A succinct definition of SAP's Scope of Check

8 min
New
SAP® ECC
Order Fulfillment & ATP
OTC; P2P; PTM
MD04; CO09
The best way to learn is by doing so welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, Martin here, and in this video we'll be discussing checking rules as a part of ATP scope of check. Now this is a definition video on focusing on one key term within ATP process that holds a lot of power and is often misunderstood. This can lead to a lot of chaos and confusion as organizations work hard to begin their ATP journey, and understanding or believing in those results actually. Kristie, I know this is a really hot topic but checking rules, kind of the basics of ATP, take it away. Kristie: Hey, Martin, so great question. Sometimes it's good to take a step back to basics and make sure we're all on the same page with these different definitions. Today, I'm going to use SAP to bring the definition to light and walk through what exactly a scope of check is. What it influences, and how to check and see what scope of check is in [00:01:00] play. I'll also highlight some things that can cause hiccups in the process. Let's go take the tour. Alright, let's use SAP to help give this definition a little bit more life. ~Um,~ I am in CO09, ~um,~ which is the Availability Overview, and I really love this ~list.~ transaction because what it allows us to do is to go through and actually see what is available based on the checking group and the checking rule and it also lets us know ~kind of~ what the end of the lead time is for this item so we know that we should see the situation for planning if we're not running terribly behind we should start to see that even out and we should start to see recovery that should be the next available time to start to take in a customer order. So here's how I got to this transaction. I actually got here from MD04. So I'm going to go ahead and just navigate back and show you how I got here. So I went to Environment and I went to ATP [00:02:00] Quantities. So if you think about MD04 as being the place to be for our planners and buyers and our MRP controllers our schedulers, this is the place to be if you're checking availability, and that might be availability for sales documents, it might be availability for ~um,~ delivery, so customer orders versus deliveries versus stock transfer orders, or even for material that needs to be available for use in manufacturing. And the picture, the rule set that we're going to see is defined by the scope of check and that scope of check is the combination of the checking group and the checking rule. We will have a video that goes through the definition of the checking group and the checking rule, which makes up the scope of check. Now, if you're not sure how you got this particular checking group or checking rule as you were coming into this transaction, let me go back to MD04 and just show you one other thing, this is one of the hidden gems of the stock requirements list [00:03:00] that we highlighted in that video by the same name. So under Settings and Settings, if you come over here on General Settings this is what is controlling the checking rule that you are coming into that transaction, also for when you are doing your order report. So typically for an MRP controller, ~if it,~ if you're buying raw materials, your checking rule is going to be something related to production planning. I've modified that here because this is a finished good, and I want to take a look at it from the sales perspective to see what is going to be available and when. ~So,~ That's how it knew what to pull through, and the other thing I can do is, if you are on the ~um,~ customer service ~or,~ or customer excellence side of the house, you probably are coming directly into this transaction. So I'm just going to do a slash in CO09 and you'll see that it's actually going to prompt me for which checking rule I want to use. We'll talk more about the [00:04:00] definitions, but if you think about this, this is the progression through the process. So planned order versus production order, ~so~ a dependent requirement versus an order reservation, customer orders, a sales order versus delivery, so there's a progression there and that's how it knows what to bring in. And this is important because the combination of these two is what sets the rule for checking availability, so what is allowed to be included versus excluded. And you can see over here in your stock overview, this is the type of stock. This is the kind of stock that is eligible for consideration in the process. It tells us whether we're considering replenishment lead time, so if it's 15 days and we don't have any stock on hand, we know that we can make it and we will have it reliably in 15 days, so we're going to be able to go out and make that promise without any type of capacity constraint or consideration on material availability. We can go in and look at the storage location level information. And then also over here on inwards and outward movement, so [00:05:00] what other types of demand are competing with this particular requirement? And what do I need to factor in as I'm going through and seeing what is left over for this particular item? And then what am I allowed to include in terms of inbound inventory that's on its way in, as well as my certainty, the quality of my housekeeping, and the reliability of my information on what may be over and past due. And this is one where we do want to be really cautious, we want to be able to include receipts from the past and future. We want to be able to get our housekeeping in order and make sure that things are neat and tidy, we've got the correct over and under delivery tolerances. As soon as you start to exclude this, you really do have a significant chance of over planning. So only in very specific business situations should this rule be changed. And the other one that's really big is the replenishment lead time. So if you'd like to know more [00:06:00] about the checking groups and the checking rules that get us to this little playbook that tells us how we're going to determine whether inventory or inbound goods are going to be available for this order, how much we have available to promise, there will be other videos that go through specifically those definitions as well as the requirements for what you should or should not include. But the definition for today, for today's scope of check is the combination of your checking group and your checking rule gives us the rules for what can be included or not in your ATP quantity. Alrighty, thanks for exploring that with me. Being able to clearly articulate a definition can really help to ensure everyone is on the same page and talking about the same thing. One of the things we hope Reveal TV will do is promote a common framework of understanding, which enables critical thinking and excellent conversations. Understanding definitions for the big ticket terms [00:07:00] is essential for getting there. Today we learned. The definition of the scope of check. How we can figure out what scope of check is in play. And lastly, when and what some of the common hiccups may look like. Over to you Martin. Martin: Okay, great, thank you Kristie, much appreciated. This makes a lot of sense if you're thinking about it. We have different expectations for the state of our supply chain, depending on where we are in the process. We should have different levels of firmness and commitment and flexibility. So again, thank you for that, I appreciate that a lot. You know, a picture is worth a thousand words and the best way to learn is truly by doing. So folks, if you want to learn more about ATP and checking rules, please check out other videos related to this topic. And of course, if you have a specific question please feel free to submit it below.

What Is a Skip Lot?

Definition and purpose in boosting efficiency and performance focus

5 min
New
SAP S/4HANA®
Quality & Batch Management
P2P; PTM; QM
MM03
Hey there, fellow seekers of quality, Martin here. Managing a supply chain requires the right product, at the right place, at the right time, at the right price, and more specific, at the right quality. So let's talk through one of the key features SAP offers to support us in getting there. It's called skip lots in quality management. skip lots offer an incredible effective technique for building efficiency into the quality management procedures where demonstrated quality is in place. It allows us to focus time and attention on the areas that is the highest risk while permitting more flow where the risk is less. Today, Tom is going to talk us through skip lots. Tom, tell us more and help us understand what skip lots are. Hi, Martin. Let's start with a couple of quick things, and then we'll dive right into the system and see where the skip lot setup happens in the material master. So here's the deal. A skip lot is a sampling procedure whereby we are sampling only a fraction of the goods coming in. It allows us to keep an eye on things without checking everything and can be very useful when the demonstrated performance is high. Or, we don't have regulatory reporting requirements for a full inspection and the risk is not very high on the material that is subject to inspection. There needs to be a solid proven track record from the source and for the material. Let's jump into SAP and take a look at our skip lot procedures. It's important to remember a skip lot is simply a procedure that SAP allows us to skip inspecting certain lots instead of inspecting every single lot. This is particularly useful when the quality of the product is consistently high. So as we can see, we're in the material master in SAP on the Quality management tab. We're going to focus our attention on the inspection setup. When we go into inspection setup, down here it shows us skip lot allowed, which is currently checked on. The other important factor to this, when we're looking at skip lot procedures, is our dynamic modification rule. The dynamic modification rules are what actually dictate the procedure we follow with skip lots. So as we hit our drop down menu, we can see the available options for our skip lot procedures. We would focus our attention on skip lot procedure Z02. We can see we would inspect 1 lot, then skip the following 3 lots upon inspections. If we would shift our focus to the Z03 skip lot procedure, we would inspect 5 lots and then skip the next 10 lots. This is the procedure that SAP will follow when we set up skip lots. Setting up a skip lot in SAP increases our efficiency. It reduces the number of inspections required, leading to decreased inspection time and cost. It can also help us focus on risk management. It allows the quality team to focus their resources on the lots that are more likely to have quality issues based on our historical data. It'll improve our quality throughput. It speeds up the process, by minimizing inspection delays for lots that have high probability of meeting our quality standards. The key factors we have to remember when setting up a skip lot is our historical data. A skip lot procedure should only be based on a robust history of quality , to ensure the only lots with proven consistent quality are skipped. Using skip lots effectively can lead to a significant improvement in our quality management efficiency, but it should only be implemented with careful consideration of the quality risk involved. Thank you very much for taking the little walk through SAP with me. Let's take a moment to highlight the importance of what we just ran through. Skip lots are an effective technique to prioritize our time and energy towards the materials that represent the highest risk. Because we are only sampling some of the materials and not every good receipt. We need to keep up on the sampling, it must be timely. We also need to be vigilant in monitoring the results. If something comes back out of spec, it's very important that we take a decision on upping our inspection procedures for that material or supplier. We need to constantly monitor and stay on top of what's happening. This is a great technique when used correctly and offers flexibility to meet specific business needs. Hey Tom, thanks again. Much appreciated. Skip plots are an important tool in the quality management arsenal. I'm glad you were here to help us discuss it today. Thanks again. It really is going to help us focus our prioritization in both control and flow. Hey folks, if you want to learn more about quality management or even some of these additional features that we talked about today with Tom, please use the chatbot. And of course, if you have a specific question or suggestion for us, submit it below.

What Is an IDOC Error?

Overview of IDoc errors covering what they are, where they occur and why

8 min
New
SAP S/4HANA®
SAP Optimization
OTC; P2P
WE02; WE09; VA03; ME23N
Hey folks, Martin here. Getting different systems talking with one another is often a challenge. Yet there are some great benefits to being able to send and receive information, particularly with communicating with our customers and our suppliers and just other systems in our landscape. Fortunately, there's a lot of standard best practices and communication protocols to lean on. When things are going well, we can manage issues as an exception. And today we have none other than Rutul to help us talk through IDoc errors and how we should think about proactively monitoring and managing them. Rutul take it away. An IDoc error lets us know that there has been a failure in processing a communication. This is very important because it's meant to make an update in your SAP system and it's failing, There's a load of important messages that can be sent back and forth. The errors really break down into three broad categories. Application errors. Syntax errors . And system errors. As a business team member, you are likely addressing a lot of syntax errors if you are actively monitoring your IDocs. Let's go in and talk about some of these places where you can see these IDoc errors. All right, here we are in one of those monitoring tools to catch, analyze, and resolve IDoc errors. There are several options in the system for example, BD87 or WE02, WE05, depending on your role and organization you might have different authorizations to these tools. One of the most common ones that we actually go through is the WE02 or 05. It will tell you by partner number or by specific IDoc messages and so on, there are multiple filtering options available in this transaction to see the errors or processing status of IDocs in specific areas, for example, you only want to look at for customer or vendor IDocs. You can filter those messages through the selection criteria and easily narrow down your search criteria. So what is an IDoc? IDoc stands for the intermediate document and IDoc is actually SAP specific terminology ortechnology or tool that is used to bring in the data in this SAP system. The flow is that there's EDI translation happening between the two partners and APO system is SAP. The translation that comes in or goes out to those partners or customers is an IDoc format. It may sound like a little technical and boring, but many of the IDocs errors are usually data errors or incorrect partner information, and so on and so forth. As I mentioned, the IDoc is an SAP terminology and the communication between the two partners happens through EDI, which means there are set specifications that SAP expects IDoc to be in and when that doesn't happen IDoc fails in SAP system and you have to use these tools to monitor and see those errors and correct those errors. It's very important that we not only address these errors in a one-off manner. We have to analyze and see the pattern, so to speak. When we talk about the IDoc errors and, resolve these errors long term. For example, a customer is sending you an order through EDI and it's failed in SAP system. So there could be a couple of very common issues related that, for example, a material number. What your customer is sending you is not matching up with what you are expecting in SAP system and IDoc will fail and say, hey, I cannot translate this material number. That's a very common error that you have to now work with the customer to say, hey, what are you sending? Are you sending the right part number? So on and so forth. And perhaps either change the settings in the EDI specification or within your SAP system communicating with them to say, okay, this is what I expect and then you can resolve this error for a long-term solution rather than changing or fixing in the one-off situation. One of the other common situations we get is where a customer order comes in and it has the SAP cannot find a ship to location, you know, ship to partner for that order that's coming in. And this is where a customer has lots of locations that you are shipping to and you are doing business with, and you are doing EDI with, but only some of them have been set up in the system. I. So now a new location automatically tries to send in an order but there is no ship to partner in your SAP system and IDoc will fail and say, hey, I cannot determine the ship to location. Or worse, it will attach an incorrect ship to location.Those type of situations are very common but this is where you can come in here and look at those errors and correct these errors. On the flip side, let's say you are doing business with your vendors you are sending the purchase orders to your vendor and they are sending you order acknowledgements or advance ship notices and so on from their side and it's failing. On the flip side, let's say you are doing EDI and communication and sending the purchase orders to your vendors. And your vendors are sending you the order acknowledgements or shipping notifications and those type of transactions back, and you see that it's failing. One of the common reasons these transactions fail is because they're sending you multiple acknowledgements for same PO or multiple advanced ship notices for same purchase orders again and again, and this is actually the bright side . We know in advance that things are coming in, we know that paperwork will be wrong, but at the same time, you want to also make sure that these occurrence are not happening again and again. We have to correct this at the transactional level as well, and communication level as well with your vendors so that it does not happen. We want these messages to constantly deliver to their destinations. We want the IDocs to flow in automatically. That is the purpose of it, so that it processes it without any issue, and being able to have these regular communications without any manual entry every time. It does help in removing the human struggle hours and allowsour teams to focus on what matters. IDocs provides us with an excellent opportunity. For communication and collaboration. When used effectively and monitored and addressed, they reduce the burden of actually the manual entry on our teams and lower the risk of data entry errors. Think about some of the examples, from today around sales orders and PO confirmations. That's a lot of manual work that can be alleviated with the proper use of EDI and resolution of IDoc errors. If we monitor these issues daily using some of the tools that we talked about today, we can achieve a good level of process efficiency. Hey Rutul, thanks a lot. That's a nice summary of benefits, balanced with necessary care and feeding. So again, thanks for the details. Hey folks, we don't always get into the technical topics specifically around how data is flowing from a technical perspective, but we do have a few others. If you're trying to find some of those, use the AI chatbot.

What Is the Purpose of MRP?

Find inspiration on why pursuing MRP is essential

10 min
New
SAP® ECC
Procurement & MRP
PTM; P2P; DM; OTC
MD06; MD05
Hey there Reveal TV community. Today we're going to go back to basics and produce a quick video to sure up the foundational understanding on the planning engine in ERP called MRP. Now we have loads of videos around MRP, but this one is for those of you who are not really using MRP today and want a little level set. First of all, I want to clear up confusion around the acronym. MRP stands for Materials Requirements Planning. Second of all, we commonly hear organizations say that they don't run MRP. Most of the time, this is not true. MRP is merely running along in the background. You've just never had the opportunity to find the value in the results. This is an epic journey filled with value. And today we're going to start with some inspiration. It is in my opinion that there is no better human in this world to get you excited about MRP than my friend, Sean. He has helped dozens of organizations come to grips with the journey and quality of MRP and has seen the outcomes for the business and for the people time and time again. So Sean, please tell us more about the definition and the purpose of MRP. Like many things we encounter in life, getting MRP up and running and delivering great value can be challenging. However, at the core, it's very simple. MRP's purpose is life to the supply, the demand, and it does so by determining what is needed. How many are needed. And by when they are needed to be there. It's time and quantity, it's primary school math, at scale, running on a set of rules, which are discussed in some of our other videos. It's a plan for every part in each location. Now then, let's go and we take a look. Well, welcome to the demo on what is the purpose of MRP. Now, in his introduction, Martin addressed MRP as an acronym and acknowledged that MRP stands for Material Requirements Planning. This is important because it is a good descriptor of what MRP does. However, what we want to do this morning is to use a transaction called MD06, and we are going to look inside of a plant at what does the MRP list look like in terms of the last run when MRP ran. And we'll take a look at that out there and you can see here there is a date at which the last MRP ran, which tells us this is the last time that MRP went to work to produce a plan for replenishment. Now we already know that MRP is responsible for determining what materials need replenishment, how many, and by what date. And that's all according to the rules that we've set. Now, most organizations run MRP on a regular cadence. And so even if you don't trigger it yourself, it's out there producing replenishment plans and managing the balance of supply and demand. It's a really, really good communicator. So let's look at our find in lists, which is really a material finder. Let's just focus ourselves for a moment on the group 4 messages where MRP is telling us what has happened. And we'll notice down here are my group 4 messages on the side. The first one, it's telling us is that these are the new proposals that we might want or need to review and to act on. It then also tells us that these are proposals that have been changed and we might want to look at that in case we've already acted and sent out an inquiry, whatever the situation might be, but we may want tolook at that because it has changed. It can even tell us that the replenishment has been triggered by the explosion of a bill of materials. Now, this last one is important to mention because MRP came about to allow companies to scale effectively as product assortments became more diverse, BOM's became more robust, and with more changes MRP could follow the rules and start letting us know if we had inconsistencies or if there were any other challenges that were out there. Now if you've ever wondered about these messages here that MRP is sharing with you and want to get some more background, I'll close this for the moment, you'll see here's an information tab. Inside of that information tab we get to see the groups, the messages, and what their definitions are. And I would encourage you to go and watch some of our other videos where we've done a ton of work around specific messages in terms of understanding and giving you insight into what they are and how you might want to respond. But if we go back to the Group 4 that we were dealing with, maybe let's just see from the highlights some of those exceptions that are coming out against those materials. You'll notice that it highlights them for me and if I go in to take a look at each one, I start to see my Group 1 messages. Here they are down here. This is a new requirement that came about from the last MRP run. And I get that opportunity to look, here's a good one, it's got plenty. All these new requirements have suddenly hit us, and we're going to have to respond to this, and make sure that we bring those materials in on time. Because often these messages , they get neglected. And we really need to guard against that. We spoke, for instance, earlier on about the message 42, which is the second one. So the proposals have been changed. Likewise, we allow the system to do the heavy lifting, we can get in and we can find a material that has now been changed, where the message is telling us it's been changed and we may want to act on that. And as we just go through, we'll just look at a few of those and you can start to see where these changes are and determine whether that's going to have an issue for us. Now, lastly, what I want to do is just to go back to all the exceptions and look at what's known as Group 8. So we look at these Group 8 messages. This is really telling us that MRP was unable to run, and you'll see there's quite a few of these that are out there, that it was unable to run and we need to fix or address the issue or the master data that is preventing MRP from running these materials. If we were just to take a look at it, here's an example for us, this one says it's in status blocked for procurement, warehouse does not allow for planning. So there's a rule that's put in place, but we still have an MRP type that wants to be planned, and therefore there's a conflict, and we need to take a look at trying to resolve that. Okay, so once more, if we go back to our exceptions, and we just look at a couple of materials, and I'm going to pick one or two. I'm going to pick this material, 1417. I'll say find that material, there it is. And when I start to look at it, here I start to see all of these new requirements that are out there. So I can see a number of new requirements which is message 01 for replenishment. So it's seeking supply for the demand and it's following certain rules. And so we don't have to do the math ourselves. Instead, we can focus on managing the process and then proactively intervening with exceptions as they occur. We saw it earlier on with some of the message 42, the new proposals. That is exactly the same thing that we would want to take some action and make sure that we stay ahead of the game as far as looking at business operations Now, the truth is there are probably tens or maybe hundreds of thousands of parts of several locations to plan across. And we quickly lose the ability to scale when only people are involved. And so MRP, it really is our next best friend, provided we have the right rules set in place to enable accurate replenishment proposals. And so folks, I would encourage you to explore what MRP has to offer. It can be a bit of a hill to climb initially but it gets easier as we go and the view from the other side, I can tell you, is great. MRP is a highly effective approach to managing replenishment at scale when it's set up and running well. It requires the discipline of daily cadence to stay relevant and move from the theoretical to the practical and operational. To recap our conversation today MRP is a rule based engine that produces a proposed plan for replenishment. Its job is to supply the demand. And when it's really humming, it puts us in a position to proactively manage by exception, alerting us to deviations from plan so that we can make decisions on how to best move forward and assure quality of supply. I'm a fan, Sean, that is amazing. Thank you for telling us more about MRP and thank you for showing us the power and the purpose of this particular functionality. Thanks again. Hey folks, if you want to learn more about MRP, there is an entire video catalog on MRP and all the exceptions and results related to that. And if you have a specific question, please feel free to submit it below.

What Is the Ripple Effect?

Seeing is understanding: discover the Ripple Effect visualized in SAP

8 min
New
SAP® ECC
Demand & Supply Planning
DM; P2P; PTM; OTC
MD04; MD13
Hey, hey, welcome back supply chain superstars, Martin here. We've got a good one today. Did you know that there is a tool in SAP that will allow you to visualize the connection between a supply element for a component at the lowest level of the bill of material and the final demand element that is planned to serve? Now, we'll acknowledge that it's not the prettiest graphic that you'll ever see, but for the purpose of impact and analysis and connection, it's a very powerful tool. We have two videos on this topic. One on the visualization end product, and the other goes into detail around the pegging report. What we're talking about today is the end result known as the ripple effect. To take us through this excellent feature in SAP, Sean's going to be sharing with the team about how this specific report can actually help us. Sean, take us away. Well, well, well, Martin. How the tables have turned, my friend. Usually, it's Martin who talks about the ripple effect. Today, I get to put my own spin on it. This is exciting. In our walkthrough today, I'm going to focus on three key things. First, I'll carry on the definition Martin started to frame up on what we mean by the ripple effect. Second, I'll show you how to navigate to it and zoom in and out once you're there. And lastly, I'll give you some insight as to why this is so useful. As they say, a picture paints a thousand words. So let's get in and take a good look. Right folks, so here we are and what we're going to do is we're going to go into a transaction called MD04, which is your stock requirements list. And in this stock requirements list, I've chosen a material PLA-BLK, so this is 3D black printing and it is for plant 1000 and it's going to open up the stock requirements list for me and we can see the details that are currently in there in terms of the requirements and so on. And what I want to do is I want to select one of those supply elements. So here is a planned order at the top and we'll look at that planned order and go to what's known as the pegging report. If you notice down the bottom here is a button called pegging requirements. It has the upward arrow. So I click on that and what it does, is it opens up the pegging requirements for me that's related to that particular planned order. And what I then want to do is I want to say, well, show me this geographically , how does this look from a graphical point of view that portrays what's happening in the pegging report. And on the top button here, there's a graphic. So if I click on that, there it opens it up. And what it's doing, and just simply put what the ripple effect is about, is having a visible view that sees the connection and the links from the supply element component, which is here, all the way through to the intended purpose to which it is supplying and supporting. In this case, it's a forecast. So the intended outcome here, or the support that it's for, is for this forecast, but it could just as well be for a sales order or for a delivery. And in between it, we notice all the layers and levels of production in between where that requirement is coming from and what the supply is trying to supply to. Now, one of the neat things inside of this report is that when you get a much more complicated view than the one that I've got here, which is pretty straightforward, it's pretty simple, it's a great example to show graphically what this looks like. You have this functionality of zoom in and zoom out. And so let's just assume if this was a very complicated and dense, you can hardly read it. If I was to hit the zoom in button, see what happens? It increases the size to the point that I will get to, to say, I can see now what these other elements are in terms of the links between the elements from the supply all the way through to where that demand is coming from. So in this case, as I said, it is a forecast. Now we get to stages very often that it's far more complex than this graphic and that's why we need the zoom in capability. So let me show you a quick example of that ripple effect, now take a look at this one. How detailed is this? Oh my goodness, it really does have multiple layers. There are multiple drivers of demand in between the supply element and the demand element. There's all these different production pieces that are part and parcel of the process. And so what this is showing us that where it is way more complicated, it's very useful for us to be able to use that zoom in functionality so that we can understand the ripple effect. We want to understand inside of this, what is it that these are all touching? What is that ripple effect so that we can get to the point of having debate and really looking to improve things. So if I go back to my example, in this case, now I was going to zoom out. There I have, in this case, fortunately, the entire example. And I can then look at what are all of these pieces of the puzzle that make it up. Now, here's a really cool thing that one can look at as well. The real value of doing this analysis and seeing this graphically is when it comes to the quality of the conversations that are going to direct us towards what that outcome looks like. That's really what the whole notion is about. What is the quality of the conversations that we can use these graphics for? And it's going to help us to uncover issues relating to, say, good or bad forecasts. It may be overdue sales orders. Maybe there's missing materials, incomplete production orders, deliveries, and so on. But it really helps us unpack that. And just by way of a quick example, if I look at one of these planned orders in between. If I was to double click on that planned order, look what happens. It opens up the details that are behind it. And so when I get into that conversation as a team, when I get into that conversation as a production team or as a purchasing team, whatever it might be, I can start to look at really what's going on. I can understand the links that are inside of that and it makes things so much more easy for me to understand. And I can see now from the links, from the supplier all the way through to that demand picture. So it really is a phenomenal opportunity for us to have those conversations. And I want to encourage you, that as you get out there, take a look at the ripple effect that you're seeing on your business and use this graphical functionality to enable you to get to a point where you can have good conversations. And with that, we're back in the studio. I hope you found that walkthrough helpful. Today, we wanted to give you a little bit of how you can be curious and explore in your own system. A few key things to keep in mind. One is the visualization of the ripple effect helps us to get a picture of the magnitude of the impact when we're dealing with a wrinkle in the supply or we're working on changing priorities. Two, this is a visual infographic that can be quickly brought up in meetings to answer questions and demonstrate concerns based on that magnitude of impact we just mentioned. And three, this is the visual representation of the pegging report. We have a lovely video on that for you to check out and it walks through the full anatomy of that report. So there's more to come. Thank you, Sean. And thank you for taking one of my favorite topics on the ripple effect. This is just one of those areas that actually just help us with cross functional understanding and just really understand the impact of up and downstream supply chain challenges. So folks, if you want to learn more about how to apply some of these tools, please use our chatbot that will actually help recommend some videos based on your specific questions. Otherwise, if you have a question for us, feel free to submit it below.

What Is the SLED Date?

Shelf life expiration decoded: acronyms simplified for easy understanding

6 min
New
SAP® ECC
Quality & Batch Management
QM; PTM; P2P; OTC; WM
MD04; MM03; MIGO; BMBC
Hey folks, Martin here. So good to see you guys again. Are you ready to dive into SAP and put it to good use? Well, let's get going. Is your organization challenging itself with ESG performance goals? Well, the good news is that there are many, many ways SAP can actually be a helpful vehicle of enabling achieving these goals. Today, we're going to explore a simple but effective example. We'll be dialing in on SLED and BBD. This is one of the many tools to support making the best use of our available inventory, keeping us and our customers safe and reducing waste. Our guide today is Ed, and he's going to introduce us to SLED, or S L E D and BBD, and show us where and how they are determined. Ed, what would you like to tell our audience today? Thanks, Martin. A lot of good can come from a simple concept, and the SLED and BBD dates are just that. The SLED, or the Specified Limited Expiration Date, and the BBD, or Best By Date, can be tracked at the material and batch level. Tracking these dates in SAP also produces another very important piece of information called the Remaining Shelf Life. This requires a few simple settings, which we'll review today. With these key pieces of data in hand, we now have a few of the foundational building blocks to ensure that we're rotating and moving through our inventory efficiently. We're able to meet customer specific requirements through batch search strategies. And, we can monitor, prioritize, and make usage decisions with our list displays. Let's dive in and go find the places where SLED and BBD live and review how the remaining shelf life is calculated. Where is that shelf limited expiration date, or SLED date? How is it calculated? What does it mean to us? Well, we can answer two of those questions with a look inside the Material Master. These settings live on a tab you may not visit very often. We're headed to the Plant Data Storage Location 1 tab. You can see a bunch of settings at the top around rules for storage. Let's say you're not running full warehouse management, and you need some basic things in place at the storage location level to manage the storage of that inventory. This is where that data lives. Now, if we look a little further down, we have a section on shelf life data. Let's walk through some of these fields. The first one we want to concern ourselves with is the total shelf life. This is the total time the product can expect to be of best quality and eligible for use without restriction. This is measured from the date of manufacture, and that could be our own production, or in this case, it's our supplier's date of manufacture. The next field we would want to consider is the minimum remaining shelf life. This is the rule the system will follow when receiving the goods. A supplier may have shipped us a lot from a while ago. That's okay, so long as we have the designated amount of time remaining. This would also apply if we transferred goods if the information was set appropriately in the receiving plant. Another important field is the period indicator. Here, we can set days, weeks, months, or even years, depending on the nature of the expiration and the associated storage requirements. We can also set a max storage period, restricting the amount of time that we would want to let the material age from goods receipt without review. Interestingly, the time period for the max storage period can get quite finite, down to minutes, seconds, even microseconds. Okay, let's see how this is applied. Let's go into MIGO and go through the receiving process. So here, we'll enter the manufacturing date and tick the item, check it. Okay, and now let's try to violate the rules and change the date. It's not within the allowable time, so we get the message and can work with that. We have several clients in the food and beverage industry that work with the byproducts of other processes. When the milk is coming, ready or not, or the harvest is coming, ready or not, you have to be very smart in what you choose to do with those products to maximize shelf life and meet different requirements for different customers. I'd say no one likes moldy cheese except for when they do. All right, now that we know where these settings are set and referenced, we have some of the foundational building blocks to reduce waste, prioritize use, and support customer specific requirements. Simply tracking this information and reviewing it consistently gives us a jump start, which opens up options and opportunities that we would not have without this additional visibility. SLED and BBD are useful for both procured material and manufactured goods. And through regular monitoring, which we'll explain in another video, we can proactively work to review expiring material and reduce the number of decisions required around disposition of expired materials. Thanks for joining us and I appreciate your time today. As do I. Thank you, Ed. There's no time like the present to put additional focus in this area and explore how SAP can help us meet our ESG performance objectives. This is but one of many pieces of functionality that can help set us apart and set us up for success. Thanks again, Ed. Hey folks, if you want to learn more about these particular topics or other ESG performance goals, please check out our videos or submit your questions below.

What’s the Reason? Exploring Reason Codes

Using reason codes to track root cause and resolve recurring issues effectively

5 min
New
SAP S/4HANA®
SAP Optimization
OTC; P2P; PTM; WM
MD04; MB51; MIGO
Hey there Reveal TV community, Martin here. Do you ever find yourself looking at a transaction in SAP and wondering why somebody did what they did? Possibly even asking yourself why you did what you did. As time marches on, it's harder to unpack those deviations from the expected outcomes. The good news, we have a tool in the toolkit to help you with this challenge, reason codes. Reason codes gives us a quick and easy way to identify, explain, report on the reasons why we took a particular course of action and the difference in the normal expected process and outcomes. For today we're going to have Jason tell us more about it. Jason, tell us more about how to use these reason codes and why they're so important. What was the reason? Thanks, Martin. Chances are reason codes are being used or at least have been set up in some part of your business. They help us with a quick explanation of the course of action that we've chosen. Today we're going to work through a few examples of good use cases for reason codes. And as we do, I'd challenge us to think about how reason codes could open up the door for better reporting and analytics to drive corrective actions or process improvements or cross functional visibility for decision making. Let's dive in and take a look. So why reason codes? Well, if you have well thought out reason codes, and we have a quick and easy way to record the why, here's some examples . Why was this material moved from unrestricted use stock to quality inspection by block stock ? We expect material to move from quality to unrestricted, but to move back to quality and might need a little more information on the why. And if we're moving from unrestricted or quality to blocked, we would definitely not to know why . Was the material damaged, that happens. If we saw a pattern, we might find you need to up our incoming inspections then for a while until we see improvements. Or perhaps we aren't storing this material in the best place for it's survival and we need to think about a different storage strategy. Or maybe it's just not there. We really don't want that one, but sometimes it happens. We don't know where it is, so we block it to make sure that MRP and ATP won't see it as available for use. With a reason code, it makes it easy to quickly review and also spot patterns. Let's take this material, for example. If we look in the stock requirements list, we see three little golden cubes by our starting inventory position. Whenever we see these golden cubes, SAP is telling us we have inventory sitting somewhere other than unrestricted use. So I know there's something going on here. If I'm planning my replenishment, chances are this move to block stock was not on my bingo card for today. Now it's blocked and I don't know why. Wouldn't it be nice if I could just run MB51 for this movement type and see the reason code? Oh, and look right here. I've got three moves due to the material not found. Think it's time to call the warehouse and ask for a count . Things are getting a little out of handout there. Reason codes can help us a ton with reporting and analytics. We can use them in sales orders to help further define blocks. We could use them in production reporting if an activity was not completed or an order was completed short of the requested quantity, and we can certainly use them for unexpected movement or reclassification of material . Keep the list short and intentional. You'll make it easy to get quality information with minimal effort. Now, I'm a curious person and I like to know the why. Knowledge is power, and when you see the same issue popping up over and over again, it's a great opportunity to dive in. Now, a word of caution, require reason codes only when necessary. If you over do it, chances are good that the team will just go on autopilot and that is not what we want. We want quality reasons that drive activities. The choice of reasons should be well thought out and intentional. The goal is to drive transparency on the why. And cross-functional visibility that supports quality decision making. That's awesome Jason. Thank you. You clearly had some good reasons for bringing this topic to Reveal TV. Hey, those are great examples, but as we work to improve service levels and reduce downtime, reason codes would be very helpful in unpacking and resolving the myriad of issues that we deal with every day. Hey folks, I know there's a lot of these little tips and tricks that you could probably find in some of the videos we have, but if you can find one specifically to what you're looking for, feel free to submit it below.

When Your Supplier Puts You on Allocation

Supply is short, and you're on allocation - explore strategies to manage the impact

7 min
New
SAP® ECC
Procurement & MRP
P2P
MD04; MD03
Hey, welcome back Reveal TV fans, Martin here, and I really hope you're thriving. Although I suspect that if you're watching this particular video, you have either trouble on the horizon or in the thick of it right now. If so, we're here to help. And you know that if you're dealing with constrained materials and facing being put on allocation is not a new challenge. Although, the cyclical nature certainly makes us feel like we're running an ultramarathon. As soon as we get one sector of the regional supply chain stabilized, it seems like we just have another one firing up. Now some of that is just normal supply chain life. But notice of allocation is certainly at the more extreme end of the spectrum. It's not fun for anyone. But there are some great tools to help us deal with the situation. And here to help us navigate the world of allocation today is Kelly. Kelly, you're quite the negotiator, I'm really interested to hear how you can introduce these tools to all of us. Thanks, Martin. No one likes to be told they can't have something, or that they are limited in what they can have, even if it's the best, most fair approach for the market served. For a lot of us, our response to the constraint of allocation has been alternate sources, often at a premium. Sometimes we've had to hedge our purchases and work with the burden of inventory carrying costs. Potentially expiring materials if we hedge too much or purchase from a less strategic source. And loads of other fun stuff. You're right. It's no fun. Even for someone who enjoys problem solving through negotiations like me. So here's a few things to know. We're on allocation when a supplier is managing priorities across customers in a limited or constrained environment. This can then limit sales potential to our customers and also result in a much higher cost to serve. I think in difficult situations like this, it is important to know that you're not alone. There are a lot of organizations going through this and comparing notes may be very helpful. For our demo today, I'm going to explain how three tools can work together to help you navigate the challenge of being on allocation. Let's go in and take a look. Sometimes it helps to bring the big picture together. I'm starting here in the stock requirements list. And if you look in the lower right corner of my screen, you'll see that I've asked SAP to show you the transaction code I'm in. This should help you as we go along. This is the current planning situation for a material that I've been told will be on allocation for the "foreseeable future". If you can't tell, I used air quotes for the foreseeable future part. I don't like that. I want a date. So here's what we're going to do. It's August right now, and my lead time is 90 days. I'm going to put a restricted plan in place for the next six months, and we're going to revisit this with the supplier monthly. My normal supplier has told me that to maintain the maximum allocation of X units per month, I need to guarantee a certain volume. I've pushed them, and we've agreed on a target quantity of the units you see here over the next 66 months. I've told them we will pull based on demand, but at a rate of no more than this many units per month. In addition, I am introducing a second source that will take my remaining volume, but at a price that makes us say, yikes. I'm going to have to chat with the sales, customer experience, and product management to see if we will weather the increase or pass some on. We hate to do that, but we may need to have that tough conversation to achieve customer tolerance time. To make this work, we're using several techniques. First, is a scheduling agreement that provides a forecast outlook for our supplier that has us on allocation. They have an idea of the pace of our demand and also an agreement that shows the total target quantity. In this document, I can also work with alternate master data related to lead time or pricing. I can update my source list to see this as the relevant source for the next six months, with a return to normal after that. I am also using firm and trade off zones for the commercial obligation of the information I'm sharing with them. Firm, they are cleared to produce and ship. Trade off, we will take it, but timing is not guaranteed and we've got a generous time horizon to meet our obligation. Second is a contract for my secondary supplier with specific information on the terms of the agreement. We've been eyeing this supplier for quite some time now. This may be an opportunity, if we can get them to give us better pricing and terms. I've asked for scaled pricing, which I will reflect in the price scales of the contract. This contract will also go into the source list as a valid source. Last but not least, I have a quota arrangement in place that's managing the split for me and restricting the volume that can go to my primary supplier. The one that has issued the allocation notice per month. I could base this on all kinds of different periods, but this month is good for now. The final product is in the system rules. That produces a balanced plan within the constraints. We have right now and a relatively easy exit to normal if normal arrives again. I can work with this. Today you were introduced to a few tools that can work together to help you manage the challenge of allocation. We have several other videos that go deeper into these tools and can help you get started. Without a doubt difficult situations require creative solutions. Sometimes people have great ideas for how to navigate rough waters, but the practicality of executing the plan can be daunting. I'm here to say that it can be made manageable. If you have an idea, let's explore how to get SAP to empower you to deliver it. Things change and when it's time, all of these tools we're talking about can be expired or discontinued , offering you a way out and back to business as usual or better. I love a good negotiation. Thank you, Kelly. Great insight. I too love a good negotiation and trying to turn what starts as a seemingly losing situation Into something good for the future. Out of a crisis comes innovation. So navigating tricky waters is a great time to see what you have to work with. This is a good starting point for a conversation. Well, folks, if you want to learn more about how to use some of these tools to be able to deal with suppliers and customer allocations, please check out our other videos as well.

When the Integration Breaks Down

Navigate cross-functional flows and fix breaks to keep SAP running smoothly

6 min
New
SAP® ECC
SAP Optimization
DM; P2P; PTM; OTC; WM
MD62; MD04; CM01
Martin: Hey, rock Stars Martin here. It's time for a chat around what happens when the integration starts breaking down. There's an inescapable truth about being a supply chain practitioner. The supply chain relies on integration and so does SAP. It is the beauty, the power, and the challenge. Getting it right isn't easy and it has both to do with people and a system. Here with the story to further explain is Steven. Take it away, buddy. Steven: Yes, Martin. Uh, the story has trials, uh, it has tribulations, it has people trying to do the right thing and a system that desperately wants to empower them to do those right things. The story revolves around the critical alignment of plan, schedule, and actual. We will seek to describe a scenario where the baton pass is, well, let's just say less than seamless. There's some confusion as to who's on first, and as we move through the process we have so much localized decision making. That we could definitely benefit from less. In short, we're not integrated, we're not aligned, and we can see that in SAP. So what should we do? Well, let's go in and take a look. The story I'm about to tell you is one that we've heard over and over again. It's a story about several individuals doing the best they can within the sphere of what they can control. It's also the story about frustration, confusion, and loss of value. Unfortunately, it's far more common than we'd like to believe. Our story starts with Rachel. Rachel's a demand planner who is the challenging job of painting a picture of what the company expects to sell over the next 18 months. She's a key player in the sales and operations process. She works with sales, marketing, product management to build an unconstrained consensus based plan. She keeps the system up to date with the best information she has and has a good process for monitoring the performance of her plan. Rachel also works with Chris. Chris is her planning counterpart. Chris provides feedback on whether it's feasible to supply the plan and attends the sales and operations planning meetings, and stays engaged with Rachel throughout the month. Now Chris knows that the demand plan is flawed and when product is not available, he feels like it's him and not Rachel that feels the heat. He constantly is fighting fires and he is rewarded for his finesse in crisis management. He works hard to align the schedule with what he sees as the priority needs of the customer, and sees Rachel's plan as information but doesn't really believe it's real. So he makes a plan based on what he thinks will actually happen. He also builds his plan in consideration of a balance of efficiency, service levels, and inventory investment. Not easy, especially since he has to redo Rachel's work in a spreadsheet, but he delivers quality plans to the shop floor every time. Now Dumebi is the recipient of the schedule. She's the supervisor for the first shift and sets up the other shifts as well. Chris's schedule is always changing and sometimes he even has scheduled downtime. He doesn't understand that her goals are all around OEE and absorption, and a lot of times his schedule doesn't prioritize those things. Plus customer service as a direct line to Dumebi and frequently asks her to intervene. Dumebi resequences a schedule and adjusts the quantities for more efficient runs based on what she knows they will need. Now meet Brent. Brent is the sorry soul who's making sure material is available to production. His suppliers think he's impossible. He is constantly making changes and asking for expedites . The things he expedites, production isn't running. Then there's unplanned consumption. For some reason, material planned for a particular run has gone elsewhere. Can't manufacturing make what they're just supposed to make? This team is actually a bunch of individuals. They're each doing the best that they can do, but when the baton is passed, they're looking at it and changing it and passing an entirely different baton onto the next person. What happens when this happens? Let's set the operational and business pieces aside. Each person, each well-intended individual is eroding the confidence of the prior person's work. There is no team, integration is broken down. We have to fix this. We have to get people engaged in conversations. We have to commit to a plan and collectively course correct. We can no longer make localized decisions the norm. We simply cannot win with that strategy. So let's engage as leaders and start making it possible for our individual superstars to become a well-functioning team. Imagine the possibilities. I wish I could tell you that this is a ridiculous overdramatized caricature of an integration breakdown. Unfortunately, it's not and examples like this are found throughout the functional areas of the supply chain. So what are our heroes meant to do? Well, first, if you see something, say something. Don't just go on your own way. But tell the person you take in the baton pass from what you're thinking and why. Let them challenge you and mutually agree on how to move forward. Second, inform SAP. Don't let the person receiving your baton pass wonder what's going on, or they'll come up with their own path forward. Thirdly, after you have a healthy debate, trust in your newly integrated approach and follow the plan until such time that another conversation is needed. Martin: Hey, thanks, Steven. Integration breakdowns are tough, and this is a good example of what happens when we let the problem fester and simply go our own way. We need to have a healthy conflict and figure out how to get back to the same page. Thanks again for the story and of course, the recommendations. Hey folks, if you want to know more about some of these Leadership Digest stories and videos, please check out our video catalog. And of course, if you're not sure or have a specific question, please submit it below.

Where are Exception Messages?

Optimizing demand with exception management strategies

9 min
New
SAP® ECC
SAP S/4HANA®
Demand & Supply Planning
DM; OTC; P2P; PTM
MD04; MD05; MD06; MD07
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin and in this video we are going to focus on where to find SAP exception messages. When used correctly. Exception messages can alert organizations to potential issues with the MRP results or other processes within the SAP. But where are they? Kristie, help us discover where they are. I think I can show you where Martin. Let's talk about where to find this powerful feature. As a buyer or planner, this is the feature that should be helping us most with our day-to-day work. Yet, for many of us, we struggle on how to get started, and in this demonstration, we're going to focus on three key things. First of all, what transactions will lead us to find these exception messages? Second, where the exception messages will actually appear. And third, how we should think about getting started when evaluating and resolving materials with exception messages. Let's learn about exception messages together. So this is a great question. Where do we find exception messages for demand? Have you ever noticed that when you look at where your exception messages are placed that they are not placed against your demand elements, they are only placed against your supply elements. The only one that's a little confusing is safety stock, because safety stock is a demand element, but it's letting you know that the stock is fallen below safety stock level, so it's related to your ability to supply it. So if you think about the purpose of MRP and our purpose as planners is to supply the demand and as buyers to supply the demand. It's our whole, our whole goal is to make sure that we have the right material in the right place, at the right time, the right cost, and the right quality, but our exceptions, because it's communicating to us as folks who are on the supply side of the house, only fall on our supply elements. You can see right here I have this scheduling agreement for this customer. It's actually in the past. Today is the 14th of February. We don't have enough inventory for it. There's no exception message. Where's the exception message? It's on the purchase order that is intended to provide the supply to supply that demand. Interesting, right? There is a lot of exception monitoring available though, for demand side elements. So the first is what I'm going to show you today, which is how we monitor our forecast to see how we're doing there. The second is, a good example would be VA06 for those of you who are on ECC or some of the Fiori apps, for those of you who have migrated to S/4, that let us know what is happening with our sales orders and gives us a lot of exception monitoring and insight into those arenas. Another good example for how we would find some exceptions would be around housekeeping. So we can always look for overdue MRP elements, in our exception monitor related to demand side items. But let's look at one of the exception monitors for managing our forecast, and I'm going to come in here first, and I just want to sum this up. So sometimes it's nice to be able to look at things summed up by periods, so days, weeks, or months, and in this case we happen to be forecasting in monthly buckets, so I want to come in here and take a look, this column here for planned independent requirements. So this is what we have, we can think of it as our open remaining to sell. So if we had planned for the month, this is the balance that we do not currently have a sales order or scheduling agreement pegged against. Our requirements are what we have sold for the month, and then the balance of that is the plans receipts. You can see we're planning perfectly in balance for these items. We're planning to replenish to the total demand, and we're not planning to keep any additional stock. Okay, so then the question becomes if we are starting to see exception messages like request to expedite what caused us to be outside of plan, did we place our purchase orders on time is definitely something we could look at. The other thing we can look at is we can see how we are balancing against our current forecast, and so to do that I'm going to come up to environment and I'm going to go look at this thing called total requirements display. So in the interest of full disclosure, I have a background in demand planning, so this is not blaming the forecast for all of our supply chain woes. I wish that that was the case or blaming the customer, if only the customer would place that order with the lead time that they were promised, if only, you know, the forecasting team would get it together on the demand plan. No, we, we work in supply chain our purpose in life is dealing with the variability and the volatility and the mixed issues that occur. So this is our world and what we're good at working through, but we can get some exception monitoring on how we're performing to the forecast. You can see here all the pieces that are out here, so what we have consumed and where we are able to balance against that forecast and it's easier to do this if we actually go in and we look at the customer view. You'll actually get a red, yellow, and green light here. So these items that are in red at the top, this is demand that does not currently have any forecast that it's able to consume against, and that's why we don't have any information over here to the right. Further down from that we have items that do have forecasts they're able to consume against, so a hundred and this is what's been assigned to it, and we can work our way through until we get out into the future, where we've got greens where there's plenty for us to peg against. So this is our planned quantity, what we're currently pegging against and then based on our consumption rules, how much of that forecast we're able to consume, and so in this case we can see that these sales orders don't have anything, they don't have a forecast that's within their consumption window and so this demand is actually in addition to our forecast. Now this happens in the current period so there's other considerations in terms of how we might be dropping or reorganizing that forecast for the current month, but this is very helpful in determining whether we're ahead or behind. The other piece of this around just rolling it up to these totals is if you can think about the planned independent requirements as you're remaining open to sell. When you exhaust those and the requirements, quantity starts to climb. If you are within your firm zone, your lead time for your suppliers, your firm zone for manufacturing, this is where we'll start to see those exception messages pop up because we aren't in position to be able to supply, so we are overselling plan. The opposite can also happen and we'd be able to see that here if we are underselling the plan. There's lots of plan that is open and we don't have anything currently pegged against it. You know, you can get a look out across the horizons. You can see here for October, we've already consumed the totality of our forecast, we have requirements of 210 pieces, in fact that may be larger than what the original forecast quantity was, and so we can use that customer view for help to determine that and then to be able to have good conversations with our counterparts in the sales and operations planning process, the IPP process, or just in demand planning to work through and resolve any of those exceptions as they occur. So really nice to be able to go through and see how the customer orders are stacking up against that demand and then be able to adjust accordingly and that's how we might be able to detect some of the exceptions that are occurring in our planning process. That and housekeeping are our two main ways to be able to do that because we housekeep both for supply and demand, and we have to push back on the demand in order to resolve the supply. So if we go through and we cancel something, or we delete something, which we should never do, we should close out. If we're doing those types of activities and there's still open demand, then all that will happen is the next time MRP runs, it's just going to regenerate for us, so getting a line of sight on some of these daily views and being able to have those housekeeping conversations with our counterparts definitely helps us to get this cleaned up. So that's where we find our exceptions for demand. So in summary we have covered how exception messages. Show up in key transactions. Highlight areas where our supply is misaligned to our demand. And become a critical daily habit for managing the overall supply chain. Super exciting! Thank you Kristie. We know that exceptions are the lifeblood of buyers and planners daily activities but finding exception messages is important because they highlight potential issues and this allows planners and buyers to proactively work to resolve them before they become larger and time consuming and more impactful into the business. If you'd like to know more about exceptions, finding exceptions and exception management in general, of course plus any other features and function SAP please check out our video catalog and of course if you've got some suggestions we are happy to listen please submit them below.

Where to Focus: QM Lots That Need Prioritization

Identify what's most critical when drowning in inspection materials

8 min
New
SAP S/4HANA®
Quality & Batch Management
QM; P2P; PTM
QA33; MD07; MD04
Hey there Reveal TV community, Martin here. And today I believe we have a quality topic for you. One of my favorite things to see when we're out walking the floor is what's happening to the world of quality inspection. It's such a critical function and often so overlooked. Many of the times the challenge we see in quality isn't the actual defects. It's the efficient movement of material through the inspection process and having the right people, equipment and partners, et cetera, to keep it up. It actually turns into a physical backup on the shop floor, often exploding into exception messages, status confusion, and queue shuffling. Hey Jason, I know this is a tough topic, but such an important one. Tell us more. I completely agree that while quality is central to our processes and while everyone understands that it's a critical step, we really do struggle to keep tabs, keep up, and remain sufficiently resourced. So I can't wait to get into this. Today, we're going to explore how we as planners and buyers and MRP controllers can support our quality colleagues in prioritizing the inspection backlog. In today's video, we will. Identify some past due usage decisions and lock closeouts. Figure out which items have red lights by generating a work list. And use days of forward coverage in our exception messages to help prioritize a list to discuss with our partners in quality. Let's go in and take a look. You'll hear us talk a lot about integration and learning how to work collaboratively across the supply chain using exception messages to direct our actions to the most critical items. It often seems, though, that the quality team gets left behind a bit in this effort. They're off in their own little world, trying to figure out which inspections are most critical, often just taking them in order of start date without really knowing which ones are the most critical to keep the flow of production happening. Other than maybe getting an angry email or phone call when things go off the rails, they're pretty much on their own. Well, out of sight, out of mind is never a good approach to managing critical supply chain functions. So I'm going to share a couple of simple ways that we can help the quality team have better visibility to where they should focus their efforts. Here, you see the selection screen for QA33, which allows us to view inspection lots. We have a number of selection options here to choose from on the main screen, but I want to share a little inside pro tip to expand options. At the top left, you can see a red, green, and blue button. I thought surely this must be someone's flag, however my search proved to be frustrating and I was not able to find it. So, if someone knows out there, I'm curious. Can you send me an email and just let me know which country this belongs to? Or town, or county, I don't know. Whatever. Anyway, this is called dynamic selection options and, when I pop it up, you can see here that I get a bunch of different options that weren't there before. So for example, maybe I want to search QM Lots based on a specific purchase order number or specific purchase org. Those are options that I can use just by clicking here and then I can put my document in and run the list by that. So just a cool little tip that maybe a lot of people don't know about. You can explore this and take note that that button's available in a number of other transactions, so keep an eye out for it, and you might find it can help you refine your searches. Okay, enough of that, for this demo, I'm just going to keep it simple, I'm going to look at plant 1710, and I'm going to use only inspection lots without a usage decision. Now, this can sometimes run a little bit long, so I've already brought the information up on a different screen , and so here we go. First off, I have sorted these on the start date, earliest to latest. Now this is a perfectly logical way to prioritize the list and is often the approach when we're not collaborating as effectively across the supply chain as we possibly could. But how might we use other information in SAP to find out if there's a better sequence to support critical cases? So in this case, I'm going to use the old CTRL Y trick and highlight these guys and then I'm going to CTRL C to copy it to the clipboard and I'm going to pop over to MD07 and upload that list of materials. So I'm only looking at exceptions for those specific materials that I pulled from the QM monitor. So let's run that , and this is a pretty short list, but there's still some good info to be discovered here. If we just went by the dates in QA33, we would inspect one of the lots for QM001, then all four of the lots for this EWMS4-03 material. And then finally, FG129 and the final lots for QM001. But is that really the right approach? Take a look at the three columns that show here the stock days supply, the first receipt days of supply, and second receipt days of supply. What we can see here is that both QM001 and FG129 have red lights over here on the traffic lights, which means that they have a negative supply situation. While the third item is green, meaning that it basically has unlimited coverage. So in this case, if we just follow the dates from QA33, we'd be inspecting four lots of this material here that has no supply disruption and no current demand, while these guys that are having a critical supply situation wait. So that's most likely holding up production and could delay shipping to a customer, which is probably not the best plan. You can do this check very quickly in a daily stand up meeting and provide clear guidance to the quality team on what is most critical for them to complete right now to keep the process flowing. And this is even more crucial if, as we often find, quality is a bottleneck where optimizing the flow is vitally important. So there you have it. A simple way to use the red lights and days of coverage information in the MRP Exception Monitor to better prioritize quality inspections. And I am very serious about figuring out which country that flag belongs to. So help me out, send me an email, let me know what you find out. If it's not obvious, I am passionate about this topic. We so often see quality departments with good procedures that are just struggling to keep up. We need to partner well to provide some perspective on prioritization when there is a backlog. So a few points to take with you. First, Cadence keeps the chaos at bay. Trademark. Regularly review and help your colleagues to review delayed usage decisions or critical incoming inspections. Second, there are all kinds of work lists for status monitoring and QM. Make sure the team knows where to look so that all lots are appropriately addressed. And third, and I can't emphasize this enough, identify and feed your bottlenecks, but don't overfeed them. Work the constraint, look for the pacing that's possible, and adjust your inspection times to reflect reality, then improve that reality. That's what we do to make things better. Hey, thank you Jason. I knew that would get you fired up. Quality both feeds the processes on incoming inspections, and is the last leg in the relay before a product is ready for our customer. We focus on so many of the surrounding processes, but often quality inspection and how we work is prioritized and process is underserved. I'm really glad we're discussing it today. So thank you. Hey folks, you want to learn more about quality management just generally speaking or specifically, check out our chatbot, it will help recommend some videos for you.

Why Do We Call It the MAD Date?

Decoding material availability calculation and its impact

9 min
New
SAP® ECC
SAP S/4HANA®
Order Fulfillment & ATP
SD; MM; PP
MD04; VA03
The best way to learn is by doing so. Welcome to the video service that unlocks and reveals the hidden value in your system. Martin here, and today we've got a good one, in this video we're going to explore a material availability date, otherwise known as the MAD date. SAP has such a wide variety of dates which all have specific purposes and lead to a flow of information that drives our supply chain. The material availability date is no exception, as is what drives the required on hand date for MRP, traffic light, stock on hand, and exceptions. It's pretty important. We don't want to miss out on what exactly it is. So, Kristie, why don't you tell us exactly why the material availability date is called the MAD date? Because Martin, it's the date that the customers get mad if we don't have material available, and that might be our external customers, or our sister facilities, or even the manufacturing floor. Okay, before I jump into SAP for this demo, did you at least chuckle? That's it, folks. That's as funny as she gets. Yeah, okay. So what will we see in the demo today? We will explore how the MAD date gets determined. And some very important and often overlooked lead time considerations. How it shows up in the stock requirements list and what the impact is on the MRP run and exception monitoring. Off we go! All right, let's go in and see what this MAD date is all about. So, as we previously said, the MAD date is the date that the customer gets MAD if we don't have the product available. It's the date that the product is needed to be on the shelf so that all the other subsequent activities that are required in order to get it out the door to the customer on time based on when we made and are now trying to keep that promise. So, if you go into a sales order, and I'm going to show you an example of what I would call a flat schedule. I'll explain how this is actually working. You may see this a lot on your sales orders and what I want to do is explain what maybe should be happening instead. So let's just go in and we're going to grab the second item and I'm going to go in and I can see that there's a schedule line. So we ran an availability check. There's a schedule line in place and I can see the first date is the 2nd of December, that's when they're looking to get this product from us. And right now we can see that it was not able to be fully confirmed for the 2nd of December but instead has been confirmed partially for the 2nd and partially for the 4th. So this customer is allowing us to do two shipments. So multiple, partial shipments in this case, it happens to be two. Now, if we go in here, though, to the shipping tab, this is what allows us to get to that mandate, and this is so important because this is what drives the supply chain, right? This is the date that we're transferring over because it's the date we've committed to the customer and we're driving our supply chain to be able to meet this date. And if you look here, we have the delivery date of 12/2 and everything else is sitting flat to that date, right? So there's no additional time that is allotted for any of these additional pieces of the puzzle, and SAP has loads of dates and they're all based on lead time offsets. Lead time becomes very, very important, and the really nice thing about SAP is that it allows us all of these different lead time buckets so we can go through and figure out how much time we realistically need in order to accomplish each of these activities in order to be able to make sure that we get this to the customer on time. And so think about it as, you know, your quality inspection time, or your goods receipt processing, or dock to stocks time on the supply side, your planned delivery time, or in house production time, or the time on your routings. Same thing applies for a customer, so we've got a bunch of different things that we have to do. So we're shipping from a particular shipping point, we may have a route and a route schedule involved. The customer may have a receiving calendar that dictates when they're able to receive goods. Let's say it takes five days to ship to the customer and we're responsible for coordinating that delivery. So if the delivery date was 12/2 and we need five days for it to move and make its way to the customer, probably we're going to have a material availability date that is at least five days, if not longer before that in order to be able to make sure that that happens. So if you go into your sales order and you notice that this is really just a flat schedule, think about what kind of time buckets you need in order to be able to set yourself up for success because what you're trying to get to is that material availability date. So the delivery date offset by whatever time is necessary to get that product to the customer, so when do we need to issue those goods in order for it to hit that delivery date. Now for some of us, that delivery date represents the date it's leaving our facility, for others of us that will represent the date it is actually going to be reaching the customer. So you got to know your particular terms with your customer. Based on the date that you want to issue it, when do you need to start pick, packing, and staging for loading? That might be another day offset. If it's export and you have paperwork to do, it may be several days or even a week or two beforehand that's required. All of those things, calculating backwards, the delivery date minus the lead time for your route and transportation time minus the amount of time it takes to pick, pack, and load is what gets you to the material availability date or when that product would be required. And so as you run your ATP check and it's looking to see when inventory can be available, then you're flipping the schedule and scheduling from that material availability date forward for when it actually is ultimately going to get to the customer based on how much time you need to pick, pack, and stage, and load, and when you're going to actually goods issue and then the amount of time it will take in transportation. In addition to that, we have this transportation planning date and this is able to run in parallel, but what it does is it buys us additional time for things like the administrative work of setting up a shipment, going through the process of getting that booked and ready to go so you're able to actually start that process working on that transportation planning, assuming that you're going to hit that material availability date, which again, all has to do with how predictable and stable that supply is and how well aligned the ATP rules are to what it is that you can make and keep a promise against. So again, if you go into your sales order and you go to the schedule line, you look at the shipping tab and you notice that you have a flat schedule here, I really would like to challenge you to think through these different buckets of activities and make sure that you're setting yourself up for success so that customer is less likely to get mad because we will have the correct date in order to allow for all those other activities to occur in this material availability date or the MAD date. That's what's going to drive the supply chain, that's what you're expediting towards, that's what you're working your supply chain to try to achieve, is that material availability date because that's the date that we need to hit in order to make sure that we get the product to the customer on time. Welcome back from the demo, to summarize. The MAD date is the date that the customer gets mad if material is not available. We explored several lead time components that drive the correct date and the importance of getting this right. And lastly, we looked at how the state is driving MRP and exception messages. The date is the entry point for driving the supply chain. It drives all other dates and decisions related to how to best get that supply for the demand. And if we did all the other upfront work on lead time, so long as we meet this date, we have a really good chance of fulfilling our promise to the customer. Good stuff, Kristie. Thank you, once again. If we go to the trouble to really understand how the MAD date is determined, and then work hard to hit that date or manage the client's expectations, we'll be setting ourselves up for success. You know what I've learned today, Kristie? Most of us should not have flat delivery schedules in our sales orders. We really need to think about those lead times. SAP has a lead time bucket for all the different pieces of the process. So getting this right, neither too short nor too long, makes a big difference in efficiency of the flow of material to our customer. Well, I think that's a wrap today. Folks, if you want to learn more about MAD dates please check out our other videos and of course if you have a burning question please submit it below.

Work Center Analysis

Assess work center performance for improved outcomes

8 min
New
SAP® ECC
Scheduling & Shop Floor
PP; PTM
MCP7
The best way to learn is by doing. Welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin and in this video we are going to focus on how to take the advantage of SAP work center analysis. When used correctly, work center analysis can help organizations gain insight to how well we're able to run the schedule on the floor and identify where the bottlenecks might lay. It's a valuable way to improve performance and uncover opportunities for improved throughput. So Eacliffe, tell us a little bit more about work center analysis. Sure Martin. Work center analysis is a powerful feature when used correctly, how well a work center is performing and keeping its commitment to its schedule. In this demonstration I'm going to focus on three things. Provide an understanding of what insight this report provides from a work center perspective. How it goes about providing this insight on work center performance. And how to evaluate each work center performance. The intent here is the use transaction MCP7 to perform work center analysis. In this report the data is primarily captured by plant, work center, and month. So let's get into this transaction, and what I'm going to do is, because it's a test system, I'm going to run it for a couple of years. So let me execute this, I'm going to bring up all work centers within this plant that has information. Okay and here we can see that we got information currently sitting at the plant level. So basically we specified the amount of historical information we want to take a look at hence the amount of history was driven by that date range. Ideally we should have zero variances and when I mean zero variances just looking at my screen here, what we can see is we have target lead time, we have actual lead time. So based on our master data, this is how much late time we expect versus based on the production confirmation. The variance is then reflected in this column. In terms of execution time I don't have a variance, but we could see what the target is versus actual. If we want to see what the difference is we can do the quick calculation or you can select this column, come here to comparison to key figures, going to compare the target execution time, I'm going to compare that to the actual execution time. Okay, and here we can see the difference. So we'd spent just over 39 days difference between the two. So the question is, hey, is this something I need to take a look at? Okay. And then even queue time again, we have target queue time, actual queue time. This is the amount of wait we expected based on our master data, we're expecting only one day of queue time, we ended up with 23 days of queue time, so deviation of 24 days. So again, what's going on? And this is sitting at the plant level. So what I'm going to do is do a switch drill down, and I'm going to bring it down to a work center. Let's see what this information looks like. So we have the totals still sitting like before on top, but now we can see who's contributing to the variance perspective, so let's look at this the deviation. So I'm going to sort this. I don't see any negatives. So let's do this, we could see the biggest contributor is coming from this particular work center where we said, yeah, it should take us 9 days when in fact it took us only 1.4 days to fulfill that particular operation for that work center. So this is great, but recognize that, look any kind of deviation, positive or negative that could have a significant risk to our operation. if we are running too fast, like this is implying we may not have other components in a timely manner resulting in a shutdown vice versa, if we are not completing orders in time without operation in time we also run risk to the business. So ideally, our goal is to really bring these lead times into alignment. The other thing I'm going to call out is, notice we see these big numbers here, it's like, wow, this is a big deviation, I mean, the difference is 144 days. So how can this only be 14.4 days at the total level? And we have to recognize that the system is actually averaging these numbers at a total level, so because we are dealing with time we just can't simply add it up, so what SAP has opted to do is to take these number of days and just average them by the number of entries or in this case work centers that we have here. So this can be a bit misleading looking at it, and hence it's definitely good to come down to this work center view and actually look at the information at the work center level. And then just to take this one level further here we can see we had a big deviation the question is, okay, when did this happen? I can pick this single line item, I can then do what is called drill down by, which is this icon here, and we'll dive into that specific work center. I'm going to pick months and we could see we have 4 months listed here and for the most part, things were looking pretty good until we came into 2023. So in this case because there's just one entry we will try and get an answer for what's going on, but it definitely looks like an anomoly and for that reason there's a high probability we don't need to take any action, but still, we don't want to second guess this, we want to determinethe root cause of this. You know, was it a matter of something posted incorrectly, in this case did this order linger around for a couple of years, for example given the number of days, et cetera. So at the end of the day, yes we use this transaction, we focus on columns like lead time deviation, we can compare processing time between the two, like what's going on, actual queue time, and of course we can also take further information to consideration like operation data and so forth. Okay, so this is the type of insight that you can gain from doing a work center analysis to help determine which data set you should be going to, to improve the quality of your master data. So in summary we have covered how work center analysis allows you to. Appreciate the feedback that this report provides by work center. Identify which key figures to focus on in this report. And evaluate each work center performance. Thanks Eacliffe. Using this feature allows real-time information on work center utilization and performance allowing the business to improve production planning, optimize resource utilization, and enhance cost control. If you want to learn more about this topic and others in your SAP features and functions please feel free to check out our video catalog and if you have any specific questions feel free to submit them below.

Work Center Hierarchies and Superior Resources

How to evaluate capacity across similar resources using work center hierarchies

10 min
New
SAP® ECC
Production & Capacity Planning
PTM
CR31; CR32; CR33; CRC1; CRC2; CRC3; CM01
Martin: The best way to learn is by doing so welcome to the video service that unlocks and reveals the hidden value in your SAP system. Hi, my name is Martin and in this particular video we'll focus on using SAP's work center hierarchy to perform capacity evaluation for a group of liked work centers. A debate may take place to define one work center to represent a multiple like machines, or create a work center for each physical like machine and use a group center hierarchy with a superior work center to perform capacity evaluation. So let's get into this. Eacliffe tell us more about how do we do this specifically in this grouping of evaluations of work centers, specifically in a hierarchy. Eacliffe: Hey, thanks Martin. I have set up a demonstration to. Illustrate the functionality of a work center hierarchy and a superior work center. So while it be easier to generate a single work center, or let it represent multiple work centers, this approach can sometimes be challenging when assigning a particular manufacturing order to a specific work center, for example. Regardless of the reason for having a one-to-one definition between a work center in SAP versus the physical, uh, machine on the production floor. By defining a work center hierarchy, capacity evaluation can be done for both the individual work centers and the superior work center. So let's get into SAP and look at how this functionality works. So this is a demonstration on how to aggregate production capacity information for resources or work centers. So you have the situation where you have like multiple, resources or work centers, and the whole point is you want to see, if I combine the capacity information for more than one resource am I able to do so? So the answer is yes, and you have the ability to do this either under discreet production and with production you would use a combination of work center master data setup along with hierarchy information or master data setup, as well as under the PPPI, you would use resources and also the hierarchy master data setup. So I've set up some data to illustrate exactly how this works. First, let's take a look at the resource that I created that basically represents the superior resource. I'll come into change mode, I called it this name here, and let's just walk through some of the views. So on the basic view it's a very light version of a resource. Basically what I'm doing is really creating this object to say, look, this resource represents a superior resource. And you could see that I don't need to maintain any kind of standard value information for this particular resource. Likewise, if I come to the capacity tab, yes I maintain the capacity category because I want to see information from a machine perspective. If I want to see labor, I would create a second entry here for labor category. But again, I would not maintain any kind of formulas. The whole point is that we would obtain the information from the, call it the children resources or work center. And finally, coming here to the scheduling tab, again, there's nothing maintained because again, the information that's needed or that is used by the system would be derived, from the, resources that’s actually doing the production. So with that said let's come back out and now I’m going to come to the hierarchy. So let's look at it in change mode, I gave it the same name as I did the superior resource, the names do not have to match. Okay? So it's your prerogative in terms of what name and convention works for you. You can use the same names or you can use different names. It all depends on what works for you. So with that said, I'm going to come and click on this icon. And it's basically saying, hey, I have this superior resource, you could see the first entry here, and then we have the, what I've been calling the children resource. So we have these two packing lines, 1 and 2. The thinking is that the materials which I produce on, let's say line 1, the majority, if not all of the materials on line one can also run on line 2. So it makes sense to do an evaluation with the two of them combined, just in case I have insufficient capacity on one line, then I can say, okayoverall, do I still have sufficient capacity? And if I do, then I'm not going to worry about it. I'll just move some of the production from line 2 to line 1. So what I'm going to do next is let's take a look at the capacity evaluation itself. So here I am in CM01 and I'm going to come in here. I maintain my plan, and on the planning I'm going to go to work center and I'm going to click on this icon to work with the hierarchy rather then the individual resources. So this is the hierarchy name. I'm going to do a green check here. It gives you a illustration of what the hierarchy looks like. So here's the superior resource, and then I have the individual. I'm not aware of any limitations of how many resources or work centers you can have attached to a superior resource. And of course you can also do multilevel. So I can have SP2, and SP2 could be something, you know, let's call packing line 4 and 5, and then you could have it all roll up into, hey, give me an overall SP network. Okay, so it could be multilayers from top to bottom, and I've got multi resources work centers. With that said I’m going to green arrow back and from here you could see the superior resource as well as the individual resources sitting here as part of the selection criteria. Here, I'm going to do a standard overview. You could see that right now I am sharing that there's 0 capacity required at the superior level and as well as available everything is sitting at 0. If I scroll down we can see that hey, we have a little bit of capacity requirements sitting down here. And then if I come further down, we could see, hey, this resource it does have capacity requirements, and the red lines indicate that I am over capacity. So what I can do from this point is then come here, click on settings general, and you can see in my case, the hierarchy ID, popped in here. And I'm just going to say, okay, you know what show me the capacity, the requirements only at this point. I mean ideally we’d look at two but I want to show the fact that just by turning this on I'm going to do a green check and we can see that, all the requirements capacity required is now sitting up here in the superior. Of course, everything is red because of the fact that we did not turn on the indicator for available capacity. So of course, all entries are over capacity of each week. So what I'm going to do is come back up here and I'm going to come back and let's go back to settings, general, I'm going to turn on the accumulation of capacity. This is the available capacity now we're looking at, I'm going to green check, and you can see that, suddenly everything is white. So the available capacity for the superiors, 32 hours for the first week because of the fact that we got 16 hours coming from packing line 1. And if I come into parking line 2, we expect to see 16 hours also. So you can see, look, still looking at the individual resources, I'm over capacity. But looking at it from a superior perspective or hierarchy perspective, I have more than sufficient capacity week after week. So this tells me quickly that I can move production from one line to the next. Hey, welcome back. In this demo, we covered. What capacity evaluation looks like when we use a work center hierarchy solution in the capacity evaluation. With this approach, a finite production schedule is done to a specific work center. Hence, we would schedule to that specific work center rather than a generic one. Plus, you can specify downtime to a specific work center instead of reducing the number of individual capacities with that generic work center. Of course, the work center hierarchy would pick up all these business scenarios I just identified. Martin: Thank you, Eacliffe, that's actually brilliant. It's good to know that these kind of options exist, right? When it comes to how to set up work centers in SAP, it's not uncommon to implement a solution that works for many business scenarios, but when it comes to finite scheduling, for example, the production planner or operations requires a lower level of detail that may be required creating additional work centers. Regardless of the need for the additional work centers, using a work center hierarchy could be the compromise to bridge the gap. So folks, if you want to learn more about capacity planning, generally speaking, or in the hierarchies, there are other videos for you to check out as well. And of course, if you do have a particular question for us, feel free to submit it below.

Working With Forecast Bias

Ensure SAP supports your forecasts, optimistic or pessimistic, with the right setup

11 min
New
SAP® ECC
Demand & Supply Planning
DM
MM02; MD04
Hey folks, Martin here. Are you ready to tackle uncertainty and challenge? Are you comfortable with confronting the level of risk and uncertainty in your forecast head on? Well, today's the day. Today we're talking about forecast error and bias, and how to put the consumption horizon to work for you in managing your way through the risk that is inherent in your forecast. If this is a challenge for your business, you're in good company. Predicting customer behavior is a challenge for most organizations, and it's a topic that we're going to continue to build upon over time on this channel. In fact, if you search, you'll find other videos on monitoring forecast performance, working with consumption modes, and choosing a planning strategy that addresses different kinds of variability, volatility, and risk tolerance. Check them out. But specifically for this topic, we're going to be talking about forecast bias. To help us today on this topic of forecast bias, we have Kristie. Kristie, I know this is something that you love tremendously. This is something you deal with all the time. You may get even excited about this. So take us away. Yes, it's true. I do love a good demand planning puzzle. And while we may hit temporary plateaus in improving the quality of our forecast on some of our individual materials or products and in some of our segments. What we can do is get really great at managing the risk. And that is what I want to chat with you about today. I remember exactly when the shift in perspective hit me. I was in an IBP meeting that was well on its way to becoming a post mortem on forecast quality, and I remember hurting for my team as they tried to explain all the things that they were doing to try to get the forecast "right". And all the blame that was coming their way for our failures as an organization to deliver to the customer. Our cost to serve is ridiculous and our suppliers are tired of it. Forecast. The shipment was late and the customer is upset again. Forecast. Precious time, materials, and capacity gone because. Forecast. Now I'm a manufacturing gal at heart that also happens to love demand planning. So you know what? I know that SAP and supply chains salute all too well. It looks like this. And it's not helpful. So let's stop doing that. Baby steps are a good place to start. So let's focus the conversation. Supply chains are made up of quantity and time. So today, we're going to focus on time as an ally in dealing with the volatility in quantities. We'll also address our bias. Are we dealing with a bull or a bear? And then we're going to talk about the importance of differentiating where it matters and setting the appropriate rules in place as we consider our plan for every part. One of the tools that we have that can really help us is to understand the bias in our forecast and that is if we are consistently under or over predicting. What the demand will be for a particular item, and this is for those of us who are working on the supply side. We look at this at the material, the plant and potentially even the MRP area level. So it's very granular in terms of how we are observing that forecast. There are a ton of videos to help us to understand and unpack the different tools. I want to bring a couple of them together, though, today in the context of bias. And I'm going to talk specifically about consumption and the way that we can manage our consumption parameters to help protect us against some of the risks that's inherent in our forecast process. Here are a couple of other tools, though, before we go there. The first is we can take our average daily consumption. So that is what we have been using over the last X number of periods and compare it to our projections, our average daily requirement where those are wildly different, that gives us a great way to have a conversation with our counterparts. In demand planning and they can help us to understand the reasons for why that may be different. We want to make sure that we do respect the demand plan, just like when we say that we can't get production done by a particular date or we can't get supply in by a particular date the demand planning team the customer experience team has to trust that we are doing everything in our power to get it there when we see the demand plan and we have the conversation we ask the question at some point we have to say we've done everything in our power to get the best prediction that we can on this particular item. And it's good to ask the questions and certainly if you see something to say something. But at some point I do want to emphasize it is important that we start to work the process and commit. What we're talking about today can help us to manage through the inherent variability and volatility that we're going to experience with demand over time. One of the other things that we can get a quick line of sight on is how our forecast that is in the now is performing. So here's a good example. This is our remaining balance open to sell. It is December right now. We have nothing left and we have requirements for 45 units. Looks like that is a pretty typical demand. You can see November has 48 pieces remaining open. Looks like we might have had a timing issue there. The demand came in in a different time bucket than what we were expecting and we have 36 pieces projected for January. Looking like that's a little less than what we are seeing in the months that follow. So this is where we start to say, okay, what's going on? Are we over under forecasting? Is there some predictability to that? And if so, how can we set our consumption rules in place to help set us up for success? So, let's go in there and take a look. I'm going to go into the material master. This all lives on the MRP3 tab. Now my colleague and friend Patrick has put out a couple of great videos around consumption mode and forward consumption period and backward consumption periods. He's gone through and he's demoed as you change those settings what happens. So I will let him speak with you about that. What I want to address is the consumption based on bias. So how do you think about that depending on if you tend to over or under forecast? Now it's important to note that your consumption mode and the way you're consuming your forecast and what's eligible for consuming your forecast does tie back to your planning strategy. So there is a tight connection there and that is a big topic to explore. But when we're talking about consumption mode, think about it like this. So your sales orders, for example, are coming in and they're eating away at the forecast that is out there, the demand plan that's in the system. I think about them like Pac Man. It makes me less angry when things are wrong. So I think about it like Pac Man. We are coming in, that sales order is eating away at the demand plan. Now sometimes, that Pac Man gets too full and it just stops eating and then we end up with extra forecasts out there that's just hanging out like that November forecast we just saw. Sometimes, in a particular period, it may overeat. So, for example, the December time period that we saw that was completely consumed and now we're moving into January. When we know that we are maybe not right in terms of timing, but we are roughly right in terms of quantity, that is where the consumption mode can really help us. And really that's what it's saying. This is how much or how far out I am allowed to consume that forecast. So at some point, if I tend to under forecast, my demand plan is not high enough. I may want to allow those additional sales orders to sit on top of the forecast that we've put in. So it's going to stop eating away, it is additional incremental demand on top of the forecast. If I tend to under forecast, backward consumption and then controlling or not allowing, or controlling the horizon of forward consumption becomes my friend. So I don't continue to add to the problem. I'm not in a position where I allow it to continue to consume forward to January or February when I know I'm already over my forecast in December. I don't allow that problem to continue because I restrict how far forward I'm allowed to consume that forecast. If I am, over forecasting, so I am in a position where I am planning too much, this is where I really want to lean into that backwards and then that forwards consumption and I might allow myself to go a little bit further back and a little bit further forward in order to smooth that out because that might mean that I am a little bit off in terms of when that forecast is hitting. But if I'm roughly right and I'm confident that I'm going to consume it within the next couple of periods, then I might allow those days to go further out. Your consumption periods are in work days, they are subject to your factory calendar. So make sure that you're aware of that. A lot of times people come in, they put 30 days, they assume it's a month. Depending on your factory calendar, that may not be the case. So that's something really important to be aware of as you're going in and you're adjusting those dates, so you really want to think about whether you tend to under or over predict that demand and then use that to help you to choose the correct consumption mode and the period that you need for being able to smooth out that forecast. So look at your risk buckets and figure out what those bands look like and then adjust the timing so that you're getting the smoothest demand signal to your supply partners. Very, very helpful to be able to come in and fine tune this and make sure that we have the right rules in place so that we don't compile or add on or complicate the situation by allowing that forecast consumption to go too far out and allowing those sales orders to overeat into future periods when we really want to restrict that in if we do tend to under forecast. So whether you're overly optimistic or if you're pessimistic with your forecast, there is help for you here and it really surrounds the consumption mode and the consumption periods and how far out you allow that Pac Man or those sales orders to eat that forecast. You know what all good demand planners have in common? Radical candor, excellent storytelling, and intense curiosity. They live in a world where the good jobs are rare and the criticism is high. So to get better at all this, the first step is to know thyself as a person. As a collective that builds a consensus plan and as products, product families, customer and customer groups, whatever is the right level for you to get to a roughly right picture of demand. We have to be champions of risk and attack it heads on. If we can acknowledge and address where we're most likely to be wrong and historically how wrong without outliers and in which direction we tend to be wrong in, we can evaluate what we need to borrow from and how much time we need. Most importantly, the bias doesn't go away if we ignore it. So we need to work with it, rather than against it, and have SAP help us make it work. We are supply chain stewards, and good ones make it work with the cards that we have, while we are working on getting to a better hand. Much more to come on this particular topic. Okay, wow, Kristie. I mean, you were off to the races on that one. I can't imagine where this is going to go next. Hey folks, I'm sure there'll be plenty more videos to come if you're looking for those other videos we mentioned earlier use the chatbot, it will recommend them for you. If you have a specific question for us, please submit it below.

Working With the Release Date

Releasing requisitions on time ensures supplier success and reliable procurement

8 min
New
SAP® ECC
Procurement & MRP
P2P
ME5A; MD04; ME53N
Hey, welcome back fellow SAP explorers, Martin here. And today we're going to be looking and exploring a feature in SAP that has a strong value proposition, but is often overlooked. What we're chatting about today is the importance of the release date in driving the procurement process. What drives your PO placement today? Do you run off the release date or the delivery date? So today, Kristie is with us, and I know you love the process cadence, so have at it. Tell us more about the value of release date in procurement. Cadence keeps the chaos at bay, Martin and yes, the release date is one of the many dates in the procurement process. And it is one that is often overlooked. But it really represents a critical milestone. It is what helps ensure we're setting our suppliers and ourselves up for success by smoothly running through key process steps with the right amount of time to get them done. Today I want to show you how the release date is calculated and where we can find it. Let's go in and take a look. I love making a Reveal TV video on something that I have done wrong in the past and have found so much value in once I learned what it was for. And I remember in the early days of setting all of this up not knowing exactly when I need to get a purchase order to my supplier and being really worried that I could be past you and passing that ball to them and then not set them up for success and not get what we need when we needed it. So enter math on the part of SAP and enter this lovely field called the start or the release date. The start date if it's production, it is the release date if it is purchase orders or purchase requisitions that need to be converted into purchase orders. It is the starting line for the procurement process. It lets us know when we need to start moving that purchase requisition onto the next stage in order to be able to get that purchase order delivered on time based on all the master data that we have maintained in the system. So if you cannot see this column right now in your stock requirements list, it is hiding from you. And there are a number of columns here that are sometimes missing. Sometimes you'll be missing opening date. Sometimes you'll miss start and release date, and sometimes you'll miss rescheduling date. It's fiddly, but you just have to hover over the fields until you can see you'll see actually a double line arrow appear and then you have to drag that out in order to be able to get theparticular column exposed But this is a good one. And so it lets us know when we need to release. So in order to have this purchase order here on time, we have to start the process or get that purchase requisition converted into a purchase order no later than 08/27/2024 in order for it to get here on September 23rd. Okay, and if I double click in here I can even get a little bit more information without even having to leave my stock requirements list. So I can see the goods receipt processing time for this is 3 days, so the date that it is planned to be available. So the material availability date is the 23rd of September. That means we have to receive it from the supplier so that it can go through all of its stock to stock activities, receiving, quality inspection, etc. We have to have it by the 18th of September, okay? So that means that we have a weekend in there because those are our working days, subject to our factory calendar, and in order to make all of that magic happen so that the supplier can be set up to deliver on time, in order to start our process and get through it, get the purchase order out the door and over to them on time, we have to release this by the 27th of August. And if we go into the purchase requisition, we can further look at those details and see the planned delivery time. Okay, so all of that math is happening for us, we don't have to look at a calendar, it's right here and then all along the way it's letting us know if we have any exception messages. So you can see this is some old housekeeping that needs to be taken care of because not only is my start date in the past, but also my finish date is in the past too. So we really missed the boat on that. So how do you make sure that that doesn't happen? Well, you go to List Display of Purchase Requisition. So you might be using any of the ME57, ME58, ME59 transactions to move through your procurement process. You may be working in ME21N and pulling a list of requisitions. This is another great place to look. This is ME5A, you can see right down here. And when I was coming in here previous life, I would run this based on delivery dates and then try to estimate my lead time offset. Don't need to do that. Come in here, put in the release date. This is everything that you would want to go and work on. So your release date up to whatever the date is that you're working with. So you know, today, tomorrow, if you're about to be out of the office for the holiday break, you might reach out a little bit further than that, but it should be very, very near term. And then you would go in and pull a list of purchase requisitions that were standing out there that needed to go through, be released, and converted into a purchase order. This should not be reaching far out into the future. When we release things to our suppliers early, we can no longer get a good read on their performance or their ability to deliver on time and in full. Because we've released it to them early, we're giving them more lead time than what they asked for. And we also are limiting our flexibility. So the one thing we know about demand is that it changes. And so if we have trouble being correct in terms of time or quantity, we want to make sure that we maintain that flexibility for as long as possible. If you're struggling with that and you're trying to give your supplier more visibility, so maybe you're releasing really early, like this case, this is way out into the future. We don't want to do that. We want to have our dates be nice and tight to what we should be working on today, tomorrow, this week. If you find that you're needing to do that, then chances are you need to explore other options in sourcing such as scheduling agreements or other ways to get a good forecast to your supplier. So make sure you check out some of those other Reveal TV videos and they'll help guide you through that. But this release date is here and it's present in many of our purchase requisition related transactions. Extremely helpful for helping us to produce a list of purchase requisitions that we need to go through and work and get out to our suppliers in purchase orders. So, release date. It's a very, very helpful field available to you in SAP. Welcome back from the demo. As we highlighted today, Release dates represent the date we need to act to give our suppliers the time they need to successfully deliver to us. They can be a leading indicator of process adherence, improvement, or challenge. We can work with them in variants and we can use them to select our requisitions and convert them into POs. And we no longer have to do the math around lead time to determine if it's time to cut that PO or not. And I totally used to do this. I had a calendar at my desk and I was figuring out if it was 63 or 91 days of lead time and what date I needed to release it. Now we even have Google and other tools to help us get better, but why use those when SAP is already doing this work for us? Time marches on Kristie, thank you so much. The release date sounds like an asset to the process that gets us the right signal at the right time. Win win. Thanks again. Hey folks, if you want to learn more about other particular topics related to procurement, we have a whole section on procurement that you can look into. And if you're struggling to find a video, feel free to use the AI chatbot.