Redwood: Analyze and Manipulate Supplies and Demands Using Additional Capabilities

Welcome to the demo of the 25C Redwood Analyze and Manipulate Supplies and Demands Using Additional Capabilities in Supply Chain Planning's Supply Planning.

This feature allows you to analyze supplies and demands using the new Redwood visualization. Using this visualization, you can view supply and demand details and their relationship in the supply chain, make adjustments to proactively address supply chain bottlenecks, and release recommendations back to the execution system. This improves on-time demand fulfillment rates and enhances supply chain performance.

When you first open Supplies and Demands within a plan, a wide open search is performed. For this demo, I want to focus on the supplies and demands for a single item called MK-ENG-CPU. Let me go ahead and click on the Item Filter chip.

I'll key in CPU for my filter criteria. As I key in each character into the search field, the list of items is continually refined until, at last, I see the CPU item I'm interested in. When viewing supplies and demands within a plan, the system is retrieving data from a search index, which makes querying much faster. When querying against a search index, you'll see numbers next to each item in the filter chip.

The number 40 shown here represents the number of supplies and demands for item MK-ENG-CPU. When viewing supplies and demands in plan inputs or a simulation set, counts won't be displayed, because a search index is only used in plan mode. I could select multiple items. But for this demo, I want to focus just on the CPU item, so I'll click outside the box to apply the filter chip.

While the CPU item can be sold as an end item, it's more commonly used as a component into a computer system. Let me go ahead and filter so I'm only seeing planned orders. To do this, I'll click on the Order Type filter chip.

Now I see the list of planned orders for the CPU item. I want to demo the pegging-related capabilities of supplies and demands. Before doing that, I'll switch to a view that will be more relevant to pegging. I'll open the View menu in the right-hand side of the page. Earlier, I created a view called CB Demo View, which I'll now select. You can refer to the Supply Planning What's New for 25B for information on how to create your own views.

Now I can see the desired columns including pegged quantity. Notice that the current pegging mode is supply pegging. That means, when we expand on the rows, we're going to see the components that are pegged to the CPU items. I'm going to go ahead and expand the first node. Here we see the components that are pegged to the planned order.

Notice that, in some cases, we are seeing the same planned order listed twice but for different pegged quantities. This is because, by default, the system displays detailed pegging information, and each row represents the quantity pegged to a single end demand. To consolidate orders so that they only appear once under a given parent order, we can turn on summarized pegging.

To turn on summarized pegging, I'll open the More Actions menu. And then I'll select the Summarized Pegging action. The system refreshed the screen, so I'll need to expand the first node again. Notice how much shorter the list of pegged orders are after turning on summarized pegging. The pegged quantity now represents the total pegged to the CPU planned order regardless of the number of in demands the hard disk planned order is pegged to.

Summarized pegging stays on for the duration that the supplies and demands visualization remains open or until you manually turn it off. Currently, summarized pegging isn't saved as part of the view, so you'll need to turn it on each time after opening supplies and demands if you want summarized pegging. Let's go ahead and switch the pegging direction from supply pegging to demand pegging.

Let me open the Pegging menu. In addition to switching pegging direction, I could also select no pegging, which would remove the expand icons from the row header. For this demo, I'll go ahead and select Demand Pegging. The system refreshed the table, so I'll go ahead and open the first row again.

I see that there is a sales order and planned orders that are pegged to the CPU planned order. Let me expand one of the planned orders for MK-ENG-Computer to see the end demand. Now we are at the end demand. In this case, we have a sales order pegged directly to the CPU item as well as a forecast pegged to a planned order for MK-ENG-Computer that is pegged to the CPU planned order.

Before I wrap up the demo on pegging, I want to mention that in 25C, the child pegging rows aren't editable. This capability will be forthcoming. Before continuing, I'm going to Collapse the planned order to hide the pegged rows. Let's say I've been made aware of an issue that will cause a disruption in the production of MK-ENG-CPU item during the first couple weeks of February. As a result, I want to move some planned orders forward into January.

One way to refine query results is to use column filters. I'm going to apply a column filter on the suggested due date column. When I Hover over the suggested due date column header, two icons appear. The arrow icon is used to sort the column, and the funnel-shaped icon is used to apply column filters. I'm going to go ahead and click on the filter icon.

I'll select On or Before operator and then key in a date of February 15. I'll press the Apply button. I see that there are two planned orders scheduled in the first two weeks of February. Let me firm those orders for January 18 to match the other two planned orders and avoid the disruption.

I'll use the Shift key to select the two orders to be firmed. Then I'll click on the Edit icon in the Toolbar. The mass edit drawer opens. The attributes that are available for editing is dependent on the order types I've selected. In this case, I've selected two planned orders, so I have several attributes that I could edit. In this case, I just want to edit the firm date. I'll go ahead and enter a date of January 18 and then press the Apply button.

The blue change-indicator icon is displayed for the changed rows, and the system displays a message confirming my changes. Let me go ahead and mark all five of these planned orders for release. First, I'll select the rows and then press the Mark for Release button. Oh, I forgot. I need to save the changes I made before I can mark the orders for release. Let me go ahead and do that.

Let me first dismiss the message. Then I'll press the Save button in the upper-right-most corner of the page. The system confirms my data was saved before refreshing the page. Now I'll reselect the five rows and mark them for release. I see my orders were successfully marked for release. However, these changes are pending until I press the Save button. So let me do that before I forget.

The next step in the process is to release the orders that were marked for release. I do that by selecting the More Actions menu in the upper-right corner of the page. Then I'll select the Release action. I receive a confirmation message asking me if I'm sure I want to release the plan. I'll go ahead and click on the Release button. The system submits the release plan scheduled process, and a confirmation message appears with the related process ID.

There's just a couple more items I want to show you before concluding the demo. Let's say I've received a notification that there is a big promotion being planned that will spike demand for item MK-ENG-Computer during the week of March 1, and I'm asked how it would impact the supply plan. To simulate the spike in demand, I'm going to create a manual demand.

First, I'll click on the Add button. The create order drawer opens. Let me click on the Order Type pulldown. I'll select Manual Demand. Then I'll enter the remaining details. When I'm done, I press the Apply button.

Notice that the manual demand is inserted at the top of the table, even though the item doesn't match the item I selected in the filter chip. Let's see what happens when I Save my changes. The system saves the manual demand and requeries the data. Since the manual demand doesn't meet the applied filter chips, it's no longer displayed in the table. Let's find the order I just created by searching for All Manual Demands.

First, I'll remove the item filter chip. Then I'll select the manual demand for the order type in the filter chip. The last manual demand is the one I just entered. Let's say I wanted this manual demand to persist across plan runs. Then I'd need to save the change to a simulation set. Let's go ahead and open the Actions menu.

I have two options when saving to a simulation set. I can select the row or rows I want to save and use the copy to simulation set action, or I can save all the manual changes I made to a simulation set. Note that only a small subset of order types can be saved to a simulation set. For this demo, I'm going to select the Copy All Changes to a Simulation Set action.

The copy to a simulation set drawer opens and is pre-populated with the plan's associated simulation set. All I need to do is press Copy. After pressing copy, the system evaluates the changed rows that are eligible to be copied to a simulation set and determines whether any of the rows already exist in the simulation set. If some of the rows already exist in the simulation set, then you have the option to overwrite rows in the simulation set or only copy the new rows into the simulation set.

I'm going to go ahead and select to only copy the new rows. Once the copy has completed, a confirmation message is displayed. Now this manual demand will persist across plan runs. This concludes the demo. Please check out the 25B and 25C Oracle Supply Planning What's New documents for more information on the Redwood version of supplies and demands. Thanks for watching.