openSAP Gain Experience with SAP S/4HANA – Logistics Unit 1 00:00:06 Hello, and welcome to this new openSAP course, Gain Experience with SAP S/4HANA Logistics. 00:00:12 My name is Hendrick Luetjohann, I'm a product expert and present to you this first course unit 00:00:18 from Sydney, Australia. Various colleagues of mine from the SAP S/4HANA Regional Implementation Group 00:00:23 will present the content of this course to you. This course was designed with your feedback in mind. 00:00:31 You asked us to focus on one single area in a course. This course is focusing on the logistics topics 00:00:37 in SAP S/4HANA. You mentioned that you wanted to see examples 00:00:41 of processes, of functionality, which is different between SAP ERP and SAP S/4HANA. 00:00:47 00:00:53 This course will focus on logistics. Another ask was to give you the possibility to test the new features or functions on your own in a dedicated environment. 00:00:57 You will be able to experience the demonstrated features in your own SAP Cloud Appliance Library system if you want to. 00:01:06 00:01:12 00:01:16 Please note that this is optional and not mandatory to pass this course. This is a nutshell course, which means that the complete course content is available from the moment the course starts. The course consists of nine units. 00:01:22 After each unit, you'll be asked some self-assessment questions 00:01:26 00:01:29 to see what you have learned. At the end of the course, you can do the course assignment, which is based on all the content covered by the course. 00:01:35 Doing this assignment allows you to add points for your record of achievement and digital badge. 00:01:43 00:01:51 So, let's gets started. Let us take a look at the content of the course. In this first unit, I'm going to provide you with a short introduction 00:01:55 of each unit, and provide some guidance in case you plan to leverage 00:02:00 00:02:07 00:02:14 the SAP Cloud Appliance Library solution we're making available. My colleague Alexander will provide an overview of the changes in processing sales rebates in SAP S/4HANA compared to SAP ERP. He will provide an overview 00:02:19 of the condition contract management, which forms the basis for setting rebates with suppliers. 00:02:25 You will learn about the maintenance of these contracts and the business volume determination, 00:02:30 00:02:38 00:02:43 00:02:49 the settlement process, and basic reporting capabilities. In Martina's unit, you will learn about preliminary billing documents. These preliminary billing documents are intended purely for negotiation purposes. You can show them to your customers to align on exact details. If changes become necessary, 00:02:52 00:03:00 you can make these changes before you create and post the final billing document. In this unit, you will learn how to simulate future demand scenarios for the plant 00:03:06 to predict capacity and component demand across BOM levels, 00:03:10 00:03:16 analyze how the demand will impact the delivery performance, capacity situation, or the supply situation, and release the simulation results to the operative MRP. 00:03:22 You will see the MRP live, and the automated creation of procurement proposals for purchasing and production, 00:03:29 00:03:37 and monitoring of stock requirements, situation, and some further steps. In unit five, Kusiel will show you the main apps available in SAP S/4HANA 00:03:42 00:03:47 to monitor the production operations and quality inspections. You will gain some insights into apps, like manage production orders, manufacturing analytics, 00:03:53 and inspection analytic apps. We will stay in the plan to product area. 00:04:00 00:04:06 The focus of this unit will be on warehouse management. Diogo will present features supporting complex outbound processes inside a warehouse. You will, for example, learn about Fiori apps 00:04:13 for packing outbound delivery items on packing station, and how this is feasible, to have full visibility 00:04:21 00:04:25 of the warehouse activities and status until the loading of the product into the vehicle, and posting the goods issue. Advanced transport management has sophisticated capabilities 00:04:35 for carrier selection by the transport management optimizer. This can be based on freight cost and further criteria. 00:04:43 00:04:48 Philipp will show you a simple carrier selection, how it can be implemented with transport management functionality available in SAP S/4HANA. 00:04:54 00:05:00 00:05:08 You will learn about the required setup steps, default routes, and freight unit building, and then see a demonstration of the process which uses these settings. The last two units would take a look at the new flexible workflow in the procurement area. 00:05:13 00:05:19 00:05:24 Kim will introduce the new concept. The purpose of it is to simplify workflow configuration and give the business the opportunity to manage the setup on their own site. Documents in sourcing and procurement, such as purchase requisition or purchase orders, and others, 00:05:31 00:05:36 00:05:43 00:05:49 usually go for such an approval process. You will learn about the most important configuration settings. In the unit before we looked at the theory. In this last unit, Kim will demonstrate some of these functionalities in a live system. I hope the overview gives you a good impression 00:05:59 00:06:11 00:06:18 of the course content. I need to make you aware of some important information before we are taking a look at how to use an SAP Cloud Appliance Library solution. I mentioned earlier that we received the feedback from learners that they want the option to experience 00:06:24 00:06:28 the course content. We looked at various options, and the best way was to provide a dedicated environment as an SAP Cloud Appliance Library solution. 00:06:37 We are aware about the importance as a consultant to have hands-on experience. 00:06:43 00:06:47 00:06:51 00:06:56 Your knowledge and experience are key in your day-to-day business. At the same time, we need to make you aware that the exercise in the system is not mandatory to pass the final exam of this openSAP course. This is only an optional part of this course. In past courses, we have noticed that a lot of learners 00:07:03 focused purely on optional exercises and missed the deadline of the final exam. 2 00:07:09 Please make sure you plan your time accordingly. And don't wait till the last minute to take the exam 00:07:15 00:07:22 00:07:26 if you're interested in the record of achievement and the digital badge. We are providing an environment which will allow you to test the processes shown in the units of this course. It's up to you if you want to use this environment on your own 00:07:32 00:07:38 00:07:44 or shared with other colleagues. The actual system, the SAP S/4HANA system, is provided with a free trial license, which is valid for 30 days after the initial activation. You will need an account with one of the three cloud providers - 00:07:48 Amazon Web Services, Google Cloud Platform, or Microsoft Azure. Such an account comes at a cost 00:07:54 as per the cloud provider's contract terms. You or your company may already have such an account, 00:08:00 or you may need to create a new one. Please check what's applicable in your situation. 00:08:06 00:08:10 Please be aware that the latest information about the available cloud providers and links to the correct SAP Cloud Appliance Library solution will be made available on the Web page of this openSAP course. 00:08:20 While we are going to show demos as part of our course units, 00:08:24 we want to make it as easy for you as possible to walk through these processes in your solution 00:08:30 00:08:35 in case you want to do so. You can download dedicated PDF documents describing the processes step-by-step in the attachment area of the openSAP course. 00:08:42 00:08:47 Cost management is a very important factor when managing your cloud system. The storage of a system will generally incur a smaller fee, which will depend on your cloud provider. 00:08:54 Running a system often charged by hour, and the course is much higher 00:08:58 than just storing the system in a suspended mode. Make sure you manage the uptime of your system. 00:09:05 00:09:10 We have seen some instances where people had been presented with a very high invoice at the end of the month. Make sure this does not happen to you 00:09:14 00:09:22 00:09:29 and shut down or delete the system when not needed. This Cloud Appliance Library solution is based on the SAP S/4HANA 2020 Feature Package Stack 01 Fully-Activated Appliance. This means that you can run all the processes documented for the solution from all colleagues. 00:09:36 00:09:45 00:09:49 Please note that that we are using a different solution compared to our previous two courses. We extended the solution and added some additional configurations or activated additional business functions, allowing us to demonstrate processes in the system. 00:09:55 We recommend these systems for anyone wanting to try out the latest features in an SAP S/4HANA system, 00:10:02 and it's a good starting point for SAP S/4HANA projects. In the following, 00:10:10 00:10:14 00:10:21 I want to provide you with a short overview on how to create your own CAL solution and how to access it. Please note, this is an example to demonstrate the steps. We'll look at the four key steps to get the instance set up and delete it at the end of the process. 00:10:29 00:10:34 00:10:37 Step one, create an account with a cloud provider. If you don't already have an account, you need to create one. You can find instruction videos, for example, on YouTube. Use a search engine, type in the term 3 00:10:42 "SAP Cloud Appliance Library creating your own", enter the name of the cloud provider account. 00:10:48 00:10:57 00:11:01 00:11:07 Follow the instructions to create your own account. Here are the direct links. You may want to stop the video. Now to step two, create your own SAP Cloud Appliance Library user account. You will need to do that if you don't already have one. You can find instruction videos again on YouTube. 00:11:13 Use the search term mentioned here on the slide, follow the instructions to set up your own account 00:11:19 so that you can start your own instance and create it initially. 00:11:25 Here is a direct link. You may want to stop the video. 00:11:29 00:11:35 Now to step three, creating your own SAP Cloud Appliance Library instance. Note, this is only an example. You will need to start 00:11:40 on the SAP Cloud Appliance Library Web page, you can find some additional information. 00:11:45 00:11:50 You will need to log on with the account you created in step two. You will need to look up the correct CAL solution. So I'm using here a search term to find the instance 00:11:59 I'm going to use for this example. So this is a fully activated system, 00:12:10 00:12:24 00:12:30 00:12:39 and I searched for it and filtered it. So now we need to create our own instance. So I'm moving here to a different Web page in order for me to go through this process. So you need to click on Create Instance. You will need to give a name to the instance. This is up to you. I'm calling it "openSAP Course Demo". 00:12:49 00:12:56 00:13:04 You will need to assign a password, following the password policy mentioned below. This is an important password. You need to use it for accessing your solution. Now you can create it. So this process now starts. 00:13:10 Before we go further, you need to create a private key. You can just click on Store. 00:13:17 00:13:21 This is sufficient because we are not using a productive environment. If you have other privacy concerns, of course you can type in a password 00:13:27 and then download the key. Again, it's not required for this process. 00:13:34 Now, the solution instance will get prepared. It will take about 90 minutes, as mentioned here. 00:13:55 00:14:00 00:14:08 Now, we're doing a quick time jump. The system is now active. I filtered it with a name I provided in my own account and I can now connect to the solution. I'm using here the Windows Remote Desktop. I'm clicking on connect. 00:14:15 The file is downloaded. I need to open it. 00:14:22 00:14:31 00:14:43 Ignore the message, just click on Connect. Enter the password you created before, and click on the OK button. Accept the message. And the remote desktop connection is being established. You will log on to the system 00:14:53 00:15:02 00:15:09 and you will find a welcome message. If it's not visible, you can click on the icon Welcome at the bottom. Otherwise, you will find the SAP GUI log on information on the desktop. Please note that we are using here the client 100, 00:15:18 as you will see in a second coming up on the screen. So all activities are being done in the 100 client. 00:15:27 00:15:43 00:15:57 If you want to disconnect from the solution, make sure that you're selecting Disconnect. We're back on the SAP CAL account. Now, some tips around managing your instance. So you can find some additional information when you're following the error. 00:16:02 00:16:09 You can find information about potential cost. You can find also information about the getting started guide, which provides additional information about your solution. 4 00:16:18 Here, I'm just loading an example, just to show you a standard guide, which is provided, for example, 00:16:24 00:16:35 00:16:40 00:16:48 for the Fully-Activated Appliance, All the management information you find up there, you can terminate your instance. You can also manage other parts of it, same information here on this link page. If you're not using your solution, make sure you suspend it. So you're saving some money on that. 00:16:54 00:16:59 00:17:11 We're now suspending it. It will take a little bit for the system to come down, but in this case, it's just storage cost you would incur. Again, this process will take a little bit. In case you want to reconnect, you would need to click on the Connect button again. 00:17:16 As you can see, the button changes a little bit, depending on what activity is being carried out. 00:17:23 So if you want to activate the system again, click Activate and the system is started. 00:17:29 It will usually take 10 to 15 minutes. Here, you can terminate, for example, the solution 00:17:38 00:17:41 00:17:51 if you do not want to use it anymore. That's the last step. It is not something you can reverse. We hope the system will help you on your journey to SAP S/4HANA. So with that, just to reiterate a few things. 00:18:00 So we have additional information available, which you can download from the Web page. 00:18:04 And please note that with the system, we can only provide support 00:18:11 while the course itself is running. We will not be able to provide support, for example, 00:18:17 when this course goes into a self-paced mode. So I hope you got a good overview of the course content, 00:18:29 00:18:35 00:18:44 you're aware if you want to use the Cloud Appliance Library system, how that works, and I hope you will enjoy this course. My colleague Alexander will show you the next unit. Again, everything about settlement management. So please enjoy. 5 Unit 2 00:00:06 00:00:10 Welcome to unit two of this openSAP course. My name is Alexander Shipilov and I'm principal enterprise architect. After the introduction from Hendrick, 00:00:15 I will present to you Sales Rebates Through Settlement Management, 00:00:19 from Moscow, Russian Federation. What is Settlement Management and why do you need to switch 00:00:24 00:00:33 from classic SD rebates? SD rebates processing is no longer supported in SAP S/4HANA. The successor to SD rebate processing is condition contract management in Settlement Management. 00:00:39 This functionality contains several parts. First is customizing where you customize your system 00:00:45 according to your business requirements. Then we have data sources. 00:00:50 00:00:56 For sales processes, data sources are sales orders, deliveries, and invoice documents. Then we have condition contracts where you specify your rebate information like settlement calendar, 00:01:04 business volume selection criteria, and you specify rebate conditions. 00:01:08 Then you run settlement program, which determines business volume, which calculates prices 00:01:15 00:01:20 and which creates settlement documents. Settlement documents contain detailed information about your settlement, and also act as a reference to G/L account postings. 00:01:30 Why do we need to switch from classic SD rebates? With traditional ERP system, rebate indexes are very large. 00:01:37 You need to rebuild index in case of changes. You have inflexible business volume determination rules. 00:01:44 Rebate data is locked throughout the organization when rebuilding. And also, large data volumes affect system performance. 00:01:51 But thanks to the wind of innovation, we don't have such problems in SAP S/4HANA. 00:01:57 With SAP S/4HANA, you have the significantly enhanced functionality 00:02:01 of Settlement Management. It's a common functionality 00:02:05 00:02:09 00:02:16 for SAP S/4HANA Sales and Procurement. It's more flexible. You don't need to rebuild the rebate index in case of retroactive update or changes. Significantly reduced data footprint and memory. And no performance reduction in sales processes. 00:02:22 However, traditional VBO1 rebates are no longer available in SAP S/4HANA, with one exception. 00:02:28 If your landscape contains SAP TPM, Trade Promotion Management solution, 00:02:34 00:02:44 then you have a possibility to use classic VBO1 rebates with some restrictions. How do you create a condition contract for sales rebates? You use the Monitor Condition Contracts application 00:02:52 in SAP Fiori launchpad, or you can use WCOCO transaction in SAP GUI. 00:02:59 00:03:05 Mandatory data for a condition contract: contract type, validity period, sales area, business volume criteria like customers or materials, settlement calendar with settlement dates, 00:03:11 and each date can be of a particular type, we will look at that a little bit later, 00:03:17 and you specify rebate conditions for your contract. Once you create a contract, you need to release it 00:03:23 in the monitor condition contracts application. Which condition contract types 6 00:03:33 and settlement date types are available? The condition contract type specifies the rebate scenario 00:03:41 00:03:46 00:03:50 00:03:54 of the rebate agreement. It can be single customer rebate when you specify just one customer, it can be multiple customer sales rebate for multiple customers. It can be two-step rebate, where you have the ability to aggregate figures from several condition contracts. 00:03:59 00:04:05 00:04:11 And it can be goods-related rebates where taxes are calculated based on material items in a reference document. The settlement date type is a very important topic. So the settlement date type in a settlement calendar of the condition contract allows you 00:04:15 to specify intermediate steps in the settlement process. So these types are: partial settlement, 00:04:24 usually used for long-term contracts, one year or two year, when your customers do not want to wait 00:04:29 until the end of the validity period to get their payments. So with this settlement date type, 00:04:36 00:04:43 00:04:48 you can perform partial settlements every month or every week or even every day. Then you have final settlement. That's the final permanent settlement for the condition contract, usually at the end of the validity period to draw the line. 00:04:54 Then we have delta settlement used for subsequent corrections or late postings 00:04:58 to be considered for referenced final settlement. And we have delta accrual settlement. 00:05:04 This is used to post accruals of rebate amounts on special G/L accounts, and in this case 00:05:11 accounts receivable figures are not affected. How do you run settlement for condition contracts? 00:05:25 00:05:32 You can perform settlement either manually or you can schedule it in the background. As an optional step, you can check business volume for your contract before each settlement run. 00:05:37 So to perform settlement, you use the Settle Condition Contracts Fiori application 00:05:44 or you can go to WB2R_SC transaction in SAP GUI. You specify document criteria on the selection screen. 00:05:56 Then you specify run control options like logging or update type. You execute settlement program, 00:06:03 then you check the logs. You check generated settlement documents. 00:06:08 00:06:17 And you can check G/L account postings if any. Which reporting capabilities are available in standard system for condition contracts? You can monitor customer condition contracts, 00:06:24 you can display business volume, you can monitor settlement documents 00:06:28 00:06:38 and you have flexible reporting on condition contracts. Now it's time for the system demo. I will show you how to create a contract, how to settle it and we'll show you some basic capabilities for reporting. 00:06:46 First, we're logging into the system and we will not create our billing documents 00:06:52 00:06:57 for business volume, we will just check that something already exists within the validity period of the condition contract, which we are going to create. 00:07:03 So let's check our customer, specify some date range from the 1st of June till the end of June. 00:07:15 00:07:21 00:07:28 00:07:37 And we'll see two billing documents already available. The first is on the 1st of June and the second on the 4th of June. All right, let's go back and now let's create our condition contract. We go to the Sales Rebates section. We go to the application Monitor Customer Condition Contracts. Here you have some very basic reporting, 00:07:45 like contracts by customer, condition contracts by status, 7 00:07:49 by sales organization, and you have the list of condition contracts available with their statuses. 00:07:55 00:08:08 00:08:14 00:08:21 Now we press the button Create Contract. We will select the type, multiple customers. And we will maintain the contract. First, you specify validity dates from the 1st of June till the end of June. All right. Then you can put some extra fields like external numbers or whatever. Then you specify sales area, it's already populated. 00:08:33 00:08:37 You can maintain some header texts, it's not mandatory, so we'll skip it. Then we will specify business volume selection criteria. So we will use just one customer, the bill-to party 00:08:47 00:08:57 00:09:03 from billing documents, and we will specify a material just to make sure that nothing else will come to our business volume. All right. Settlement Data tab, it's not mandatory for population so we will skip it and we will maintain Settlement Calendar. 00:09:12 You can choose any calendar already existing in the system, like factory calendar of your country, 00:09:18 00:09:21 but we will not do that, we will create the settlement calendar manually. We'll specify several settlement dates. The first one will be delta accrual settlement 00:09:28 00:09:36 on the 2nd of June. Then we'll create another one that will be partial settlement. We will do that on the 5th of June, partial settlement. 00:09:47 Then we will create final settlement at the end of the month. 00:09:56 00:10:02 00:10:09 00:10:13 And just to be consistent, we'll create delta settlement for this final settlement. So settlement for delta will be somewhere in July. We specify that it's delta settlement and we need to specify the reference date from the final settlement already existing in this settlement calendar. Good. 00:10:20 So now we create conditions for this condition contract. So first we will create a rebate accruals condition, 00:10:26 00:10:32 as we have delta accruals settlement date type. We select rebate accruals. Let's put, for example, 2%. All right, now we'll create the rebate condition itself. 00:10:43 We will create scales also. We will also create scales for this condition. 00:10:47 So use rebate condition, let's specify 2% in the beginning, and then we will create scales with a special button. 00:10:59 So let's say we will have 1% for 500 United States dollars, and we will have 2% in case of 1,000. 00:11:22 00:11:28 Yeah, 1,000. All right, looks good so let's check what we have maintained. So basic data, we have contract type multiple customers. 00:11:35 Sales area, business volume selection criteria. Settlement calendar, and our rebate conditions. 00:11:46 00:11:53 Now we save the document. It's saved, let's remember this number. And let's check what we have in this overview transaction. So we have this number up here, it's inactive, 00:11:59 00:12:09 00:12:14 so we need to select it and to release. All right, looks good, it's active. Now let's get back to our Fiori launchpad and let's check the business volume for this condition contract. The number is already there, let's execute the transaction. 00:12:20 Now we see that something is already there. It's a cumulated figure but let's check that we have 8 00:12:28 those two billing documents from the beginning of this demo that they are considered in this business volume. 00:12:37 00:12:46 00:12:54 00:13:01 So we change the selection level and we see that we have those two billing documents. Okay, now let's settle our condition contracts. Settle Condition Contracts Fiori tile. So we have the number. We specify the first settlement date, which is 2nd of June and that will be the delta accrual settlement. All right. 00:13:10 We check and we change the run control for live run, change the logging option, and we'll put update mode to simultaneous. 00:13:21 And we execute the program. Successful, no errors. 00:13:28 Let's check what we have in the log. So we have settlement document created 00:13:33 00:13:40 with accounting document. Let's look into the settlement document. So you have these figures there, it's actually 2% from the first billing document. 00:13:44 If you calculate it, that will be this 7.02. Let's check the accounting document. 00:13:54 You see that no accounts receivable postings there, the postings are made for special G/L accounts 00:14:02 00:14:10 to accrue this rebate amount. All right, let's perform the second settlement. That will be on the 5th of June, and in this case we have the second billing document also considered 00:14:16 00:14:25 00:14:34 for this settlement run. Again, let's change the run type to live run. We change the logging option. And we change the update mode to simultaneous. That's not necessary in real life, we'll just do that for the sake of...I don't know. 00:14:41 So no errors, let's check what we have here in the log. So we will have a new settlement document. 00:14:47 00:14:51 We have a new accounting document created. And let's check accounting documents and settlement documents. So you see that right now we have 1% for the cumulated value 00:14:59 00:15:05 00:15:12 00:15:19 of two billing documents, let's check accounting. You will see that in this document, you have the accruals lines reversed from the previous settlement document, and you have a new line for our customer so to reduce the accounts receivable figure. And also you have tax here. All right, so let's perform the third settlement run, 00:15:29 00:15:37 00:15:43 00:15:51 that will be final settlement. We expect that it will be just a settlement document with zero values because we don't have any other business volume before the end of the validity period. So let's check that, so execute the program. Settled without errors, good. No journal entry is required for this settlement document 00:15:56 because we expect that it will be zero. Yeah, so zero figures, and if you press Accounting, 00:16:04 00:16:10 it will say that, no journal entries, no accounting documents. All right, that's all for this demo regarding the settlement. So you can also perform, yeah, 00:16:19 monitoring of the condition contract. There are two ways of doing that, like you press this little arrow. 00:16:26 00:16:31 You will go to the Fiori application to display condition contracts data. Here, you have some information. Another way to see what's inside the condition contract 00:16:39 00:16:48 will be, let's go inside the application. You press the hyperlink on the number and you press Change Condition Contract. So you have the WCOCO transaction open 00:16:54 00:16:58 and if you press Settlement Calendar, you will see that some of the settlement dates are already completed, but delta settlement is still pending because we didn't perform settlement for that one. 00:17:06 All right so you have options for corrections, reversals, and other actions for the contracts. 9 00:17:16 But let's see some reporting, Analyze Detailed Settlements. That will be flexible reporting for condition contracts. 00:17:23 00:17:28 So you have a transaction where we have dimensions, columns, and rows. You can pick some dimension, put it either to column, and you will have the screen recalculated on the fly. 00:17:38 When you put that into rows, it will be again calculated on the fly. 00:17:43 Let's pick some other dimension like bill-to party and we will see the report also considering bill-to party, 00:17:53 00:18:08 either in columns or in rows. Yeah, looks good. And that's the end of the demonstration. And with that, we come to the key takeaways of this unit. 00:18:17 So classic SD rebate processing is no longer supported in SAP S/4HANA, with the exception of scenarios 00:18:25 when we have SAP Trade Promotion Management. The successor to SD rebates processing 00:18:30 is condition contract management in Settlement Management. Condition contract management 00:18:36 00:18:42 provides a central standardized solution for administration of supplier and customer rebates. The concept of condition contract can already be implemented in an ERP system by activating the relevant business functions. 00:18:50 00:18:56 The functionality is very flexible. However, it requires investing some time to get familiar with this solution. Purchasing rebates management is similar to sales rebates, 00:19:04 only contract types and source documents differ. And with that, we come to the end of this unit. 00:19:11 Thanks for joining. In the next unit, you will meet Martina Reichert-Fischer 00:19:16 with unit three, Preliminary Billing Documents. Goodbye. 10 Unit 3 00:00:05 00:00:10 Hi, my name is Martina Reichert-Fischer, I'm a principal process consultant, and I present unit three from Berlin in Germany to you. Topic of this unit is Preliminary Billing Documents, 00:00:20 00:00:26 00:00:33 At the beginning, we want to clarify the question what is the preliminary billing document and what can I use it for? The preliminary billing document, abbreviated PBD, is an optional intermediary document between the billed reference document 00:00:40 and the final billing document. And that's important, it's not an obligatory document. 00:00:46 It is just for negotiation purposes, for example, aligning on details like prices, 00:00:52 00:00:57 payment terms with the customer. Or it can be used for internal reviews and approve it for critical invoices before they are sent to the customer. 00:01:04 00:01:09 The creation is based on single reference documents, or the billing due list, and the preliminary billing document is structured identically to regular billing documents. 00:01:17 The preliminary billing document is also relevant for output so you can check the layout of your invoice, 00:01:24 00:01:31 but it's of course not relevant for posting to financial accounting. The preliminary billing document can be changed as often as necessary, 00:01:36 following the discussion with customers. If changes become necessary, 00:01:41 you can make these changes in the Change Preliminary Billing Document app. 00:01:46 00:01:52 00:01:58 I will show this in the system demo later. In a preliminary billing document, you can work with different statuses, for example, reject or finalize. And in the final step of the lifecycles, you can convert your preliminary billing document 00:02:04 00:02:12 00:02:15 00:02:23 into the final billing document. What are the prerequisites for using this function? There aren't so many. The function preliminary billing document has been available since SAP S/4HANA 2020 and also in the current cloud release. You have to activate business function SD_BIL_PRELIMBILLINGDOC 00:02:29 to enable using the preliminary billing documents. To separate the preliminary billing documents 00:02:37 00:02:44 from normal billing documents, you have to maintain a new number range prefix and a new interval for the number range object RV_BELEG. You will find support in Note 2921988 00:03:00 It is possible, but not necessary to set up approval workflows for preliminary billing documents. 00:03:07 In certain situations it can make sense to ensure that a preliminary billing document 00:03:13 is approved by an approver before the billing clerk can create the final billing document. 00:03:19 00:03:24 00:03:30 Or you can, for example, define the preliminary billing documents with a net value higher than a specific value or those needed for a specific customer, must always go through an approver. For these cases, you find a detailed description behind this link. 00:03:41 Now we want to answer the question, how can I create and handle preliminary billing documents? 00:03:50 We did the prerequisites as explained, activated the business function, 00:03:56 00:04:00 maintained the number range prefix and the number range for preliminary documents and now we can use these four Fiori apps: Create Preliminary Billing Documents, 00:04:07 Manage Preliminary Billing Documents, Change Preliminary Billing Documents, 11 00:04:12 and Display Preliminary Billing Documents. With the app Create Preliminary Billing Documents, 00:04:20 00:04:28 00:04:34 00:04:41 you can create such documents from the billing due list items displayed in the app. Such billing due list items can be sales orders, deliveries, debit memo requests, and billing document requests. But you cannot create preliminary credit memos. With the app Change Preliminary Billing Documents, you can change different attributes 00:04:48 of an existing preliminary billing document to better align them with your customer's expectations. 00:04:55 You can also add items from suitable SD documents. With the app Manage Preliminary Billing Documents, 00:05:05 00:05:11 00:05:16 you can display a list of all preliminary billing documents in the system. Here, you can use filter, sort, and group criteria. You can also reject and finalize existing preliminary billing documents. And as the final step of the lifecycle, 00:05:23 00:05:28 you can convert the preliminary billing documents to billing documents. So far we have considered the theoretical part and prerequisites, 00:05:33 00:05:39 let's now look at the handling of preliminary billing documents in the system. You will see these four apps, Create, Manage, Change, 00:05:43 and Display Preliminary Billing Documents. We start with Create Preliminary Billing Documents. 00:05:49 00:05:57 With this app you can create PBDs from billing due list items displayed in the app. You have the same search bar like in the Billing Due List app, 00:06:00 00:06:08 00:06:14 and can use it for fuzzy search across all searchable billing due list item attributes. You get the billing due list items displayed and can fine tune the document creation process by making settings to decide how has the system creates 00:06:18 preliminary billing documents. And of course, you can customize your view of the list. 00:06:29 00:06:35 Now we choose one item from the billing due list and create a preliminary billing document. According to our settings, we switch to this view and see our first preliminary billing document 00:06:41 with the new number range and the prefix PBD. With a click on it, 00:06:47 00:07:01 we switch into this document and at first we want to check the document flow. As you can see, our reference document has the status invoiced. Therefore it is removed from the billing due list 00:07:08 even though no final billing document exists. Our preliminary billing document 00:07:14 is in status in progress because it's still unchecked. Another option to work with preliminary billing documents 00:07:25 00:07:31 is using the app Manage Preliminary Billing Documents. You can fuzzy search across all searchable preliminary billing document attributes. In our case I want a list with all existing PBDs 00:07:38 00:07:47 00:07:52 and you can see the different statuses in the Status column. Let me explain the different statuses. We have in progress. This is the default status after creation. It indicates that you are free 00:07:56 00:08:00 to make changes to the document, to reject it or to finalize it. You can also convert it to a billing document. Rejected, you can reject a preliminary billing document 00:08:07 to mark them as unsuitable for billing document creation. When this status is set, 00:08:13 the proceeding document can also be reopened and changed. Finalized, a user can manually finalize the PBD 00:08:23 to indicates that no further changes are required. You can convert it to a billing document. 12 00:08:30 00:08:36 Documents in this status cannot be changed. If further changes become necessary, you can set the document back to the in progress status. And we have the status completed. 00:08:42 00:08:47 That means the preliminary billing document has been converted to a billing document, therefore, the PBD can no longer be changed. If the successor billing document is canceled, 00:08:55 the in progress status is restored, meaning that the preliminary billing document 00:08:59 00:09:09 00:09:18 can now be changed again. You can set the status from this view directly and also switch between the statuses. But in our case, we want to check the PBD in detail. Therefore, we choose our PBD and go into the document. 00:09:26 You see the normal billing documents structure, with header and item and the button for output messages. 00:09:34 00:09:39 00:09:45 One of the advantages for preliminary billing documents is you can change certain attributes of preliminary billing documents to better align them with your customer's expectations. For example, you can add texts like billing info for customer. 00:09:57 You can change other header details like billing date, or payment terms, or input terms. 00:10:19 00:10:24 On item level I'd like to show you that you also can change prices if you recognize that they are incorrect because there are other agreements with your customer. 00:10:43 Another possibility is to add billing items for documents in the billing due list 00:10:47 to an existing preliminary billing document. Use the button for adding documents 00:10:53 00:10:58 to select an available SD document who's billing items you want to add. All items from the selected billing document are added. But you can only add items 00:11:05 from the document in the billing due list if the document header data matches 00:11:09 the header data of your existing preliminary document. You get a selection screen, can select it. 00:11:17 And now you can see that we have two items and, of course, you can change the price 00:11:24 00:11:36 of the second item too. And, of course, you can change the item text from the new document. Now we want to check the output document. 00:11:49 You can choose display document and you will see the printout, 00:11:54 the print preview from the preliminary billing document. It's marked as a PBD document 00:11:59 so you can't mix it up with real billing documents and, as you can see, our changes are still visible. 00:12:23 We save our changes in the preliminary billing document and go back to Manage Preliminary Billing Documents. 00:12:38 We select our PBD again, set the status finalize, 00:12:47 and now we can create the real billing document. As you can see, this billing document was created. 00:12:55 We switch into the document again and check the document flow. 00:13:00 00:13:08 00:13:13 As you can see here, we have two items from two preceding documents, they are all in status invoiced. Our preliminary billing document is completed. And the final invoice is blocked due to the customizing. Now I'd like to show you the system behavior with a different status. 00:13:25 00:13:40 00:13:54 We choose another preliminary billing document. We don't agree with this document, therefore, we set it to the status reject. And if I now try to create a final billing document, I get an error message, of course, because the status is not correct. 00:13:58 00:14:11 I rejected this preliminary billing document. As you can see it in the document flow, the proceeding document is still in status to be invoiced and our preliminary billing document is rejected. 13 00:14:21 00:14:27 That was a short system presentation on how you can with PBDs. Finally, I would like to summarize the most important points. 00:14:33 The functionality has been available since SAP S/4HANA 2020, and also in the current cloud release, 00:14:40 00:14:46 and it's an optional functionality. Only some prerequisites are necessary to use the preliminary billing documents Fiori apps, but the advantage is big 00:14:51 because you have, with the preliminary billing documents, a document before the final billing document is created, 00:14:59 which is identical in structure and can be changed due to customer's need 00:15:04 or internal requirements. You can also check the billing document layout 00:15:11 00:15:15 before you post the billing document to financial accounting. Therefore you can avoid complaints from your customers 00:15:19 and billing document cancelations. That's it for this unit. 00:15:25 00:15:29 Thanks for your attention. Stay tuned for unit four, with my colleague Karin Ruffenacht. 14 Unit 4 00:00:06 Hello, welcome to unit four of the openSAP course Gain Experience with SAP S/4HANA Logistics. 00:00:14 My name is Karin Ruffenacht and I would like to provide you some information on production planning 00:00:20 00:00:25 00:00:32 with demand simulation and finance scheduling. Therefore, I would like to discuss with you the following question. How can you manage to go from future demand scenarios to a feasible resource schedule in SAP S/4HANA? One possible process to go for that is the following. 00:00:42 Of course, first we need to know which products and which quantities we would like to produce. 00:00:52 Therefore, we need requirements in SAP S/4HANA. That could be customer requirements like sales orders 00:00:58 00:01:05 or schedule lines, or some forecast. In this unit, we will not focus on creating and calculating forecast but on the simulation and evaluation of forecast scenarios in predictive MRP. 00:01:16 This tool provides some functionalities to adjust forecast and to release your favorite 00:01:23 forecast scenario to the productive environment. Then material requirements planning will support you 00:01:32 00:01:39 to check the material availability across all BOM levels. And then finally, the planner can use advanced planning to create a feasible production plan, 00:01:46 considering constraints such as capacity, setup times, priorities, and so on. 00:01:54 00:02:00 In this unit, we will focus on the functionalities of predictive MRP and advanced planning. Therefore, we would like to start with the next question, how can SAP S/4HANA support you 00:02:09 to identify potential capacity and component issues for future demand scenarios and evaluate possible solutions? 00:02:22 Predictive MRP supports functionalities for mid- and long-term simulation. 00:02:30 Some customers also use it for short-term simulation, and it provides tools to check the situation 00:02:40 across all BOM levels and work centers, and provides functionalities 00:02:47 00:02:54 like clickable simulative key PIs, issues lists, solution proposals to the planner to adjust the forecast scenarios. Then if the planner is happy with the forecast scenario, 00:03:01 00:03:07 he can release it to the productive environment. On the right side, you see some screenshots of the functionalities of predictive MRP. However, I would like to go directly with you to a demo 00:03:15 to the Fiori launchpad. The functionality of the predictive MRP is provided by SAP Fiori apps 00:03:24 00:03:30 00:03:37 and is only available in the Fiori launchpad. First of all, I would like to show you the forecast scenarios we have created in the system. And therefore, I will go to the app Maintain Planned Independent Requirements, which gives you an overview 00:03:44 of all available forecast scenarios in the system. You see, we don't have any active forecast scenarios. 00:03:51 And I would like to show you the version 01. You see, we have got some forecast 00:03:58 00:04:07 on the finished product level for the plan 1710. I select these materials and I would like to go to the detail view. There we see that we have created some forecast 00:04:15 00:04:22 for the next 12 weeks and that this scenario is inactive. That means it is not relevant to the productive environment and to the productive MRP. Now I would like to check and evaluate 15 00:04:29 00:04:38 this forecast scenario with predictive MRP. It would be possible to define some constraints concerning material availability and for certain suppliers. However, we go directly to the app 00:04:48 00:04:57 Schedule Predictive MRP Simulation Creation. That means we create here a job for a simulative scenario. We use a template that of course you can use 00:05:07 in your system as well, it's the template openSAP Demo. And it includes when the job should be scheduled. 00:05:16 00:05:24 00:05:32 We go for immediate scheduling here. And in the step three, we define the selection criteria for our simulation scenario. You see, we define a name for the simulation scenario. We go for a weekly based bucket planning for a certain period. 00:05:37 And in the object selection, you can define which products you would like to check. 00:05:43 You can also define some limitations, like certain BOM usages, or you can include or exclude the stock transfer. 00:05:52 The most important setting is that you link one or more forecast scenarios to that simulation scenario 00:06:02 since we would like to evaluate that. Then we schedule the job, and that means that now 00:06:08 in the background, the system reads all the data, explodes the BOM, and creates a simulated scenario 00:06:15 00:06:26 for this selection criteria. After the job has finished, it provides a status and a log. And now we go directly to check our simulated scenario in the app process predictive MRP simulations. 00:06:36 There, we see a list of all available active simulations in our system. We select the first line, which we have created just before 00:06:47 00:06:59 and go to the simulation of this scenario. Now a list of all materials that we forecast is loaded and is displayed in the demand plan simulation overview. You see here a list of the materials with the forecast 00:07:09 for the weekly periods and the periods with some issues are highlighted in red. 00:07:17 On the top, you see a list of clickable KPIs, for example, the capacity issues. 00:07:23 There a list of resources with overload are displayed. We have also KPIs like delivery performance 00:07:33 or violated constraints. And we have several views available. 00:07:39 00:07:45 00:07:51 Now we switch to the capacity plan simulation, which shows us a list of the work centers we have selected for this scenario. And it displays also, for each work center and each period, two key figures. The first one is the capacity requirements for that period 00:08:00 00:08:07 00:08:13 in the first column. In the second column, there is the available capacity or the capacity overload. If there is a capacity overload, the key figure is displayed in red with a negative value and you can double click on it to activate the inspector. 00:08:20 The inspector supports the planner to solve capacity issues. And as you can see here for the assembly line one, 00:08:30 00:08:44 we have an overload for more than 30 hours. And now the system provides a list of materials, for which we could shift the forecast to other periods. So I select the first material and then I get 00:08:51 from the system a solution proposal. In this case, it proposes to produce all 00:08:58 00:09:06 00:09:16 or shift all the quantity from week 36 to 35. I adopt the proposal and apply it. Now, all the key figures are recalculated on the fly and the capacity list is updated. And we see that we still have a capacity overload, however, it has been reduced. 00:09:23 00:09:30 Now I go for the next material and adopt here also the proposal from the system and shift the quantity partially to another week. Now, after recalculating all key figures, 16 00:09:39 we see that we don't have any overload anymore on the assembly line one and on the finishing line. 00:09:46 00:09:53 However, we still have an overload on testing line one. I will accept this overload since we have got a second testing line, which we could use. And therefore I'm now happy with this forecast 00:10:03 and I would like to go back to the demand simulation view to check how my forecast has changed. 00:10:12 00:10:18 And we see that we have some changes. Due to the testing line, we still have some periods with red key figures, which are highlighted in red. And now I would like to see all my components 00:10:27 that I would need to produce during the next week. That's the components overview and I get a list 00:10:38 00:10:43 of all materials with the requirements quantity for each period. And if you would like to provide this information, for example to a supplier or to the management, 00:10:49 00:10:58 you can download it to the Excel spreadsheet. Now I'm happy with my forecast scenario and I would like to release it to the productive environment. So I return to the overview of the predictive MRP simulations 00:11:08 and release this forecast scenario to the productive environment. I activate the forecast scenario and release it. 00:11:17 00:11:24 Now the forecast is relevant to the productive environment. Now the next question is, how does MRP Live ensure material availability? We have got new requirements in the system. 00:11:34 Therefore, the MRP Live, which is executed directly on the HANA database and has got an increased performance, 00:11:44 will check the material availability across all BOM levels. It will create solution proposals like planned orders 00:11:53 00:12:00 for in-house production and purchase requisitions for external procurement to solve or in case of any material shortage. Then the MRP Live provides a lot of MRP analysis tools 00:12:09 and functionalities to the MRP planner in case of any issues. 00:12:15 00:12:24 00:12:35 So you have several alerting views. You get as well solution proposals and KPIs for the materials you are responsible for. After the MRP plan, the detailed scheduling planner faces the following question, which features are available for detailed scheduling 00:12:40 of production resources in SAP S/4HANA? With the planning tool embedded, PP/DS in S/4HANA, 00:12:53 00:13:03 we provide a lot of functionalities to the planner in SAP to solve any planning issues and to create an optimized feasible production plan. So we support, for example, 00:13:12 the switch to alternative resources, to alternatives plans, special planning scenarios, like tank resource planning, 00:13:20 considering shelf life, campaign planning, block planning, but also just some normal planning functionalities 00:13:31 00:13:43 like dynamic lots set up times, sequencing, backlog functionalities, and so on. PP/DS provides a lot of planning tools like the optimizer, which creates a feasible plan in the background, 00:13:53 considering priorities, delivery time, delivery dates, dynamic setup time, setup costs. 00:14:03 On the other hand, we have interactive planning tools, like a lot of planning ports, the alert monitor, 00:14:10 or the products view. In this session, we would like to show you 17 00:14:14 00:14:21 some functionality of the detailed planning port. And we switch back to the demo for the advanced planning functionalities. We assume we have executed the MRP Live 00:14:28 and the planner has maybe already checked the issues in the product view. And now we would like to check the capacity situation. 00:14:40 00:14:47 Therefore, we use the Fiori app Monitor Capacity Utilization, in PP/DS. It provides us an overview of all the work centers we have selected. 00:14:53 00:15:03 On the right side, we can see the utilization chart and you can also adjust all the information that is displayed in this overview by the user himself. So you can select certain columns and de-select them. 00:15:14 And the utilization chart provides you a certain overview on the capacity utilization and we see it's quite typical. 00:15:25 00:15:31 We have got a lot of peaks in some weeks. That's typical after releasing a forecast since the forecast is very often released for a certain day, and that's why we get an overload there. 00:15:40 00:15:47 00:15:54 We can also switch to more detailed information, to a utilization chart, which provides certain ways of analysis. One is this general utilization, another would be the possibility to check what materials are produced on this work center. 00:16:02 And of course, you can also check the list of operations and navigate to the detailed view of the operations 00:16:10 or the orders for this work center. Now, we would like to go to the detailed planning port, 00:16:17 to execute some detailed scheduling. You see, we have defined a profile for the openSAP course, 00:16:28 00:16:34 00:16:41 which includes a lot of customizing so you can select the buttons, the screens that are displayed in the planning port. We selected or we go for two screens. On the top, you see a list of the resources, which are sequenced according to 00:16:48 the production flow in the shop floor. The red resources are highlighted as bottleneck resources. 00:16:56 And in the graphical chart, you see the operations. On the bottom, you see the utilization chart 00:17:04 of the graphical planning port and now we would like to display 00:17:09 00:17:13 00:17:16 all the operations that are scheduled on the painting resource. And as you can see, we have got here an overload because we can only produce one operation at the same time in the painting. 00:17:22 00:17:29 Thus, we would like to reschedule the painting resource by the functionality rescheduling. And now the system has automatically resolved the overload, considering the strategy settings we have maintained. 00:17:40 And we do the same for the testing line. Here we have a special situation. 00:17:45 We have a second testing line, which we would like to use. And the system has rescheduled some operations 00:17:53 00:17:59 to the other testing line. We execute the same functionality for the next bottleneck resource, that's the finishing line one. 00:18:04 And again, here we have an alternative resource. However, in the planning meeting, 00:18:09 00:18:15 00:18:25 we have decided not to use it, that's why we changed the strategy profile and we do not allow to change the resource. That's why we set current modes to retain. Then we have a great functionality in the PP/DS planning port, it's the undo button. 00:18:31 00:18:39 So we can undo the last planning functionality and we execute the planning again. And now you see that the system has only used the finishing line one. 00:18:44 Now we have a plan, we have planned all bottleneck resources. 18 00:18:49 00:18:56 However, as you can see here, we can display the pegging information across all BOM levels, and then we see here that the testing is scheduled later than the assembly, 00:19:04 00:19:15 and that's not feasible in the shop floor. That's why we now use a second heuristic to consider the relationships, the pegging relationships, and to create a plan for a work center without any gaps. 00:19:24 00:19:34 So I select the operations for this week and execute a heuristic stable forward scheduling. Now, it rescheduled the whole BOM structure and tried to avoid gaps on these new resources. 00:19:45 And now we have colored the operations according to the product group and therefore, 00:19:56 we see now this order is produced in the right sequence. Now maybe we would like to schedule as well the second week 00:20:07 or the next week and put that a little bit more to the current line. 00:20:13 So we select also this week and execute a scheduling as well with the heuristic stable forward scheduling. 00:20:22 00:20:26 And then we would have a feasible production plan for these two weeks. However, we have decided to build some stock for the painted materials. That's why we would like to sequence this resource, 00:20:36 00:20:45 the orders manually, and to go for sequencing according to the setup group, according to the coloring from in two weeks' time. Because first we have to build up some stock for all the materials 00:20:56 and then we have the possibility to sequence them. Now, the planner has got here a heuristic 00:21:04 00:21:09 00:21:16 where he can, in a table view, change the sequence by drag and drop. There's also a clipboard available. And now I select some orders to the clipboard to the right to sequence them a little bit differently. I could also sequence them with drag and drop on the left side. 00:21:23 00:21:29 00:21:37 Now I sequence them according to the setup key and have now a new sequence. I put them back after the date I would like to sequence them. And now the planner can trigger the scheduling and the system will consider the sequence here. 00:21:48 00:21:54 You could also do that in the background by sequencing according to the setup key but the planner would like to see it here and to change it. And now we see we have a new schedule for the painting line. 00:22:04 And now I'm happy with this plan and I would like to save it. 00:22:09 00:22:13 00:22:21 And there are two possibilities, I can save it in a simulation version or I can just release it for a productive environment. So I would like to release it and then I will check the new situation in the app Monitor Capacity Utilization. 00:22:29 00:22:36 And we see now, and when I update it, that the painting resource has been leveled for the next four weeks. On the other resources, we don't have any capacity overload 00:22:45 within the next three weeks and we still have some capacity left 00:22:49 since we have just started with this product. So hopefully, you have got some idea about functionalities 00:22:58 00:23:04 of predictive MRP and advanced planning. Hopefully, you have got some incentive to explore more functionalities. Thanks for your attention. 00:23:10 00:23:16 And in the next unit, my colleague, Kusiel will provide some information on production execution and quality management. Thanks and goodbye. 19 Unit 5 00:00:06 00:00:11 Hello, and welcome back to week one, unit five of this openSAP course. My name is Kusiel Camargo. I am an SAP S/4HANA product expert 00:00:15 and plan to project team leader in the regional implementation group. 00:00:19 I'm talking from my home office in São Paulo, Brazil. And in this unit, I will present to you the topic, 00:00:28 00:00:35 Manage Your Production and Quality Operations with Transparency. So let's start. In unit four, you saw how powerful the production planning in SAP S/4HANA can be, 00:00:41 with tools to simulate future demand scenarios, to guarantee material availability, and to run detailed scheduling, 00:00:50 considering capacity load and constraints. Now, in this unit, we continue the business process flow, 00:00:59 00:01:06 00:01:13 00:01:20 and I will start showing you some of the improvements that SAP S/4HANA can bring when we are executing production operations. So assuming that I have already, my production orders created from production planning, our first question is how can SAP S/4HANA monitor the progress of production and measure operational performance? 00:01:30 00:01:35 In SAP S/4HANA, there are new SAP Fiori applications for production operations to monitor and manage your production orders or process orders. There are also several manufacturing analytics 00:01:43 embedded in the system. And analytic is related to production costs. 00:01:49 00:01:55 As an example, if the production supervisor wants to control the progress of production, we have an SAP Fiori app, called Manage Production Orders. This app helps us to monitor production orders, 00:02:05 to have an overview of the current situation. In this app, you can verify uncovered requirements, 00:02:12 real-time status of your materials, components, and milestones. You can also make adjustments in the order, 00:02:22 like editing quantities, dates, read master data. And now we have the option to see parallel sequences. 00:02:30 00:02:36 If you are working with process orders, you can navigate to the equivalent app, called Manage Process Orders. When we talk about measuring 00:02:47 the performance of the production operations, SAP S/4HANA provides you out-of-the-box analytics 00:02:55 through KPIs for key manufacturing figures, allowing you to quickly react with the necessary adjustments. 00:03:03 For instance, with the app Production Execution Duration, you can compare the planned and the actual operation durations 00:03:11 required for execution. The app Access Components Consumption, 00:03:16 compares the expected component scrap percentage defined in the BOM item 00:03:22 00:03:29 00:03:39 with the actual excess consumption recorded in the production confirmation. And we have other SAP Fiori apps for operational scrap material scrap, and scrap reasons. Another very important capability is to compare between planning and actual costs of production. 00:03:46 00:03:53 For that, the SAP Best Practices for SAP S/4HANA offers the scope item 2QW, providing the foundation to produce prebuilt finance analytics content 00:03:58 using Core Data Services views through the SAP Fiori apps, 20 00:04:03 Custom Analytical Queries and Query Browser. So let's take a look into the system to see an example of 00:04:12 00:04:21 00:04:28 00:04:34 how to monitor production orders. Using SAP Fiori apps in SAP S/4HANA. We start entering the app Manage Production Orders. In the upper side of the screen, we can see several options to filter the data. And in adaptive filters there are more fields that can be included. Below, on the same page, 00:04:39 00:04:46 00:04:52 we can see a list of production orders with the main relevant information like material, open quantity, start and finish dates. When we filter by material, we realize that the list is updated automatically without the need to leave the page, 00:04:58 including the progress of the operations for the production order in a graphical bar. 00:05:05 The icons in the column Issues make you aware of problems that occurred in the production orders 00:05:11 like quality issues, quantity deviations, 00:05:19 00:05:26 missing components, or delays. We can also change the dates and quantities, or edit the order directly from this app. In our example, we select an order to investigate further. 00:05:35 We immediately see more details about the issues and general order information. 00:05:43 00:05:49 00:05:55 00:06:04 In the section Components, we understand better the coverage situation. We see that we have three pieces of the component already consumed. Two pieces in stock, but five pieces are still missing. In order schedule, we check the progress of each operation, including now information about parallel sequences. 00:06:12 We can see the confirmations done in the order, and if we have quality inspection lots assigned. 00:06:20 Coming back to the operations, if we click in one of them, we go straight to the app 00:06:25 00:06:31 00:06:38 00:06:45 Manage Production Operations. In the Manage Production Operations app, we can have insights specific to the operation selected. This can be very useful, for instance to look closer at the operations that are delayed and the impact on other production orders assigned to the same work center. Because with a simple click in the operation, 00:06:51 the information in the work center schedule is updated. You can also verify the confirmations already done for this operation. 00:07:01 And from this app, directly make another confirmation 00:07:05 or even release an operation if you need it. And that concludes our demo 00:07:15 00:07:21 and also our explanation about how to monitor the progress of production and measure operational performance in SAP S/4HANA. Producing with excellence also means producing goods with quality 00:07:31 in compliance with industry standards, right? For that, SAP S/4HANA has embedded a very powerful 00:07:39 solution to ensure total quality management. So what are the advantages of using quality management in SAP S/4HANA? 00:07:51 The first advantage is that quality management in SAP S/4HANA is a very comprehensive 00:07:58 00:08:06 and integrated solution for all industries like machinery, construction, chemicals, pharmaceuticals, consumer products, and others. All to help organizations to comply with industry standards 00:08:17 and legal requirements more easily. Second, quality management in SAP S/4HANA can be applied 00:08:25 as a laboratory information management system or as a computer-aided quality assurance system 21 00:08:34 with advantages compared to having them as separate systems, like high integration into other SAP business processes, 00:08:43 00:08:54 no redundant master data, and no interface. By using QM with SAP S/4HANA, we can track quality from the design of the product, through procurement, production, through delivery. 00:09:02 And we meet customer expectations with transparency. Some of the key capabilities of quality management in SAP S/4HANA 00:09:10 00:09:17 00:09:25 include product development, to avoid defects and issues right at the beginning, for instance with a closed-loop inspection planning. Quality improvement. By managing complaints and problem handling through quality notifications, that enables you to define and perform 00:09:33 corrective and preventative actions. Quality analytics, to analyze data regarding 00:09:41 product and process quality, for making the right decisions based on quality KPIs. 00:09:49 And quality assurance and control. That allows data capturing and monitoring. 00:09:55 00:10:03 00:10:09 It also helps you to find the non-conformities and react to them right away. When we look closer, we realize that all main processes in quality management in SAP S/4HANA are now covered by modernized SAP Fiori user interfaces and embedded analytics. 00:10:18 00:10:24 To mention some examples, we have the Manage Inspection Plans app and the Manage Quality Levels app in quality planning. For quality inspections, 00:10:29 we have dashboards for the quality technician and the quality engineer. 00:10:35 We also have apps Manage Defects and Manage Quality Tasks for the nonconformance management. 00:10:44 And real-time analytics apps like Display Results History, Nonconformance Analytics, and Inspection Lot Analytics. 00:10:56 So let's leave the theory and move to the action. Performing a quality inspection process in SAP S/4HANA 00:11:04 00:11:13 00:11:20 to ensure streamlined inspections, quality planning, and execution supported by KPIs. We start with the quality technician role entering the app Quality Technician Overview. Here we have a dashboard with cards showing my tasks, open results for inspection lots 00:11:26 00:11:33 00:11:43 with or without special points, and inspection lots without the inspection plan. We can adapt to the filters with other fields if needed. In our example, we are interested in the inspections associated with the goods receipt from production. 00:11:49 So we only need one simple filter and the entire dashboard We visualized that there is one inspection 00:12:05 00:12:11 for this origin, pending, with status overdue. We click on the chart and we go directly to the Record Inspection Results app. In this app, we see that we have two characteristics without results. 00:12:22 00:12:34 00:12:40 And we add the production order number as a last double check before entering the results. We select the line and easily can enter the results by catalog or numeric format. According to the inspection object. The results are immediately valuated, so for instance, 00:12:57 when the value entered for the length was rejected because it is out of the specifications, 00:13:04 00:13:19 00:13:26 we have the option to attach a document or a picture with further details. After saving, we want to see the previous results for these characteristics that were rejected. And by clicking on the Results History button, we navigate to the app that shows the information to us 00:13:34 with a graph of the latest results and the limits assigned to the characteristic. 22 00:13:43 We can also see this information in a tabular view. The statistical information and general information related 00:13:51 00:13:59 00:14:06 to these characteristics. Now we are back to the SAP Fiori launchpad, and we play the quality engineer role. We enter the app Quality Engineer Overview. There, we have several cards showing us a 360-degree picture of the inspection management. 00:14:16 00:14:20 00:14:28 There are cards related to the usage decision completeness, if we have inspection lots with defects, the top defects, and the top defective materials. We also have cards related to the quality levels, quality for records, and quality tasks. 00:14:38 Back to the Inspection Lots Without Usage Decision card. We see that 13 inspections have no results yet, 00:14:46 six are in process, and three are completed. But what about to the inspection that we did right before? 00:14:55 Again, we filter by goods receipt from production, and we realize that that our inspection was completed. 00:15:03 00:15:10 00:15:16 But with violations. We click on the chart and we go immediately to the Manage Usage Decisions app. There we see better that we have one defect for the inspection and the usage decision is still missing. 00:15:25 We select the inspection and we enter in the detail page to verify general information of the inspection 00:15:32 00:15:41 like sample size and quantity to be posted. In results history, we have a clear view of the values inserted before, for each characteristic and below the defects created. 00:15:51 We can quickly check the history of the last usage decision results through the quality scores, 00:15:59 assign it to their respective inspection lots. We also see the material document number that generated 00:16:08 this inspection lot for further traceability. Now that we have a complete understanding of the inspection, 00:16:17 we can make our usage decision and save. We observe that a goods movement was done automatically in the background 00:16:26 00:16:34 00:16:43 with the three pieces from the goods receipt being transferred to unrestricted use. Back to the overview page. We realize that the cards in our dashboard were updated. As we had the defect generated for our inspection, let's look closer at the defects 00:16:48 00:16:54 assigned to this material. From the Top Defective Materials card, we go directly to the app Manage Defects. Here we can change the chart type for a better comprehension. 00:17:02 So we see that we had two defects for calendar week 22 and one defect for calendar week 23. 00:17:10 00:17:16 Of course, there are other options of visualization rather than calendar week. Below, we have the defecting formation in a tabular view. From the several SAP analytic applications available for QM, 00:17:32 we selected one quality inspection lot analytics to close this demo. Here, we decided to look at the usage decisions 00:17:50 00:17:58 made in the previous 365 days, and also display the graph by accepted and rejected lots by inspection type. We can show or hide information, 00:18:09 00:18:17 see the results in a tabular view, or even jump into other apps for further investigation. And this closes our demo. And also our explanation about quality management in SAP S/4HANA. 23 00:18:26 Let's close this unit with some key takeaways. There are SAP Fiori apps for production operations 00:18:33 to control the progress of production, measure operations performance, and prebuilt analytics 00:18:40 to compare planned and actual production costs. All main processes in quality management in SAP S/4HANA 00:18:49 00:18:58 00:19:05 00:19:11 are covered by modernized SAP Fiori UIs rich in embedded analytics. Check the SAP Best Practices for SAP S/4HANA and SAP Fiori apps reference library for a deeper understanding about how these apps are integrated in the process flows, their business benefits, and key features. And that's it for unit five. 00:19:20 00:19:25 00:19:30 Thanks for your attention. Please stay tuned for unit six, Leveraging the Outbound Process Using Extended Warehouse Management, presented by my colleague, Diogo Iran. Goodbye. 24 Unit 6 00:00:06 00:00:11 Welcome to unit six of this openSAP course. My name is Diogo Iran, I am EWM Senior Consultant, and I will present this unit from my home office in Brazil. 00:00:18 This unit covers the topic Leveraging the Outbound Process Using Extended Warehouse Management. 00:00:24 00:00:28 00:00:33 Our focus is to respond to the following question, what are the main features in SAP Extended Warehouse Management to support outbound process? Let's get started. Well, from the process perspective, 00:00:40 SAP Extended Warehouse Management is designed to perform basically three different main processes. 00:00:46 00:00:52 The inbound process, responsible for receiving the product into the warehouse, either from an external vendor, stock transfer orders, or a product from production line. 00:00:57 00:01:03 You can use additional functionalities, such as quality management, integration, serial number management, deck consolidation, and so on, until the confirmation of the putaway tasks at the storage bin. 00:01:13 The storage and operations, which represents the functionalities 00:01:17 to maintain the internal warehouse activities, such as replenishment, disloading, and physical inventory. 00:01:24 And outbound process, which gives the flexibility to plan the outbound activities into the warehouse 00:01:32 using functionalities like wave management, picking optimization, packing staging, and load management. 00:01:40 00:01:45 Performing the outbound process in SAP Extended Warehouse Management, you can easily note the business benefits, such as enhanced stock accuracy, 00:01:51 00:01:57 00:02:05 00:02:10 reduction of errors due to manual operations, increased service level agreement, and the monitoring and visibility of operation into the warehouse. Here are some features for outbound process in SAP Extended Warehouse Management. Let me describe some of them in a nutshell. Cartonization planning creates the number and size 00:02:18 of each carton needed to ship the order. The algorithm uses the planned shipping handle units, or PSHUs, 00:02:27 based on the information from product master data and the outbound delivery orders, 00:02:32 such as quantities, volume, and weight. The PSHU is very similar to our shipping handling unit, 00:02:41 00:02:47 describing a packaging material and the item it contains. But unlike the handling units, the PSHU does not exist physically in the warehouse. It's only used for planning the shipping handling units. 00:02:57 TM-EWM integration covers the end-to-end process, from the transport execution where trucks are planned 00:03:03 according to the orders in the route until the warehouse activities. 00:03:10 It enables a smooth processing of warehouse activities, increases business productivity, speeds up loading process, 00:03:18 00:03:24 improves utilization of the vehicles, and optimizes the total cost overall. A new and simplified TM-EWM integration called advanced shipping and receiving 00:03:31 00:03:39 was delivered on SAP S/4HANA 2020 FPS01. This new integration supports, for example, mixed and multi warehouse scenarios within one single TM document. 00:03:45 Direct integration without using the transportation unit, avoiding redundant documents. 25 00:03:53 00:03:57 Preallocated stock. You can register internal demands in a pre-allocated stock table. Once the stock is received in the warehouse, 00:04:03 you can forward the preallocated stock directly from the interim storage area for goods received 00:04:10 to the interim storage area for goods issued. In exceptional routing bypassing their regular putaway 00:04:17 in favor of moving the stock to the location where it is demanded. Automation can be delivered in different solutions 00:04:29 00:04:37 for all size and warehouse complexity. Let's start with connected devices. In order to enable the handheld device, SAP Extended Warehouse Management 00:04:43 00:04:50 has a native integration by activation of ITS mobile service. On the radio frequency framework, ABAP dynpros are defined, and after the service is activated, 00:04:56 ITS mobile renders the ABAP dynpro as HTML for display in the industry browser on the handheld device. 00:05:07 00:05:12 Warehouse automation is based on the future material flow system that can connect and control automation equipment, exchange the information with the control system 00:05:20 00:05:26 00:05:36 of the automated equipment in order to conduct them through the warehouse floor. The communication is based on TCP/IP and the information is transferred by telegrams. Another possibility is using a device that offers hands-free, using picking by voice technology, for example, 00:05:45 00:05:50 00:05:56 for optimization of the picking process. The pick by voice transaction uses SAP GUI dynpros whose fields have speech properties. Then the system generates HTML templates using the ITS HTML template generator mobile device 00:06:04 00:06:11 00:06:21 00:06:27 with speech input. These HTML templates contain the speech-specific tasks that are interpreted by the Web browser of the device. And finally, logistical robotics. This new generation of robots, also known as collaborative robots, give to the warehouse a different perspective to process automation. 00:06:32 00:06:38 00:06:43 These robots not only can store products, but also organize and transport products through the warehouse. The solution is based on cloud robotics, and can be integrated easily with extended warehouse management 00:06:47 00:06:54 by downloading the application software. It's an add-on in Extended Warehouse Management with three solution scenarios out of the box supported, cross docking, put away, and pick, pack, and pass. 00:07:02 And what about Fiori in SAP Extended Warehouse Management? Let's see our next page. 00:07:11 00:07:17 Using SAP S/4HANA, you can achieve the digital transformation by Fiori adoption. On the Fiori launchpad, you will find several apps available for SAP Extended Warehouse Management, 00:07:24 which support the outbound process steps according to the business scenario design. 00:07:30 On the left side, the tile Warehouse Task Confirmation, available to confirm warehouse tasks 00:07:36 by different warehouse process categories, such as picking, put away, and internal movements. 00:07:43 The app alone directly chooses one or multiple warehouse tasks 00:07:47 00:07:52 for confirmation or cancellation. Print warehouse tasks, view the details of a warehouse task, or handle an exception. 00:07:58 With picking by cart, this app you can optimize the picking process 26 00:08:04 00:08:09 by multiple orders in a single trip. Using a picking cart, warehouse workers walk through the warehouse, pick the products required by orders, 00:08:16 00:08:22 and place into the shelves. This efficient app can also eliminate the packing step, improve speed and efficiency, and reduce the human errors. And last but not least, pack warehouse delivery 00:08:30 is an app that allows quickly-packed products for outbound deliveries on a packing station. 00:08:37 00:08:41 You can choose different packing modes, advanced or basic packing mode, according to the one that best fits atop your process. Now, let me use the Fiori apps presentation 00:08:53 in our system demo. Okay, let's get started. 00:09:00 Our first step is logging into the system using the user and password provided in the exercise. 00:09:11 In this demo, we are going to perform a complex outbound process for Extended Warehouse Management 00:09:17 00:09:24 00:09:30 using the Fiori apps presented previously. The first step is to create the sales orders using the app Manage Sales Orders, available on the role sales order. Insert the order type and the organizational data needed, such as sales organization, distribution channel, and division. 00:09:41 00:09:49 And let's create two sales documents for different customers using the same product in both. The first sales document is for customer EWM17-CU01. Insert customer reference, and the products and quantities. 00:10:02 And save the document, repeat again the steps, creating the second sales document for customer EWM17-CU02, 00:10:13 00:10:21 using, again, the same products and quantity. At the end, two sale orders are expected. And the next step is the outbound delivery creation. For the outbound delivery creation, let's use the app 00:10:31 Create Outbound Deliveries from Sales Orders. An intuitive and friendly app to create documents, 00:10:39 which also allows processing massive documents. Select the sales orders and click on Create Deliveries. 00:10:47 00:10:54 Afterwards, click on Display Log in order to see the documents created. The expected result is two outbound deliveries and the distribution to SAP Extended Warehouse Management. 00:11:09 Okay. Now, using the Warehouse Monitor, 00:11:13 filter by ERP document numbers in order to see the outbound delivery order created automatically 00:11:21 once distributed with success to the warehouse number. In SAP Extended Warehouse Management, 00:11:34 00:11:41 00:11:48 00:11:53 you have the full monitoring and visibility of the warehouse activities in real time. You can also trigger different actions. Use the methods available to support the operation. Select all documents and click on Wave. The system displays the wave number created automatically for both outbound delivery orders. On the wave detail, you have several possibilities, 00:12:02 00:12:06 00:12:14 like simulate the wave, with which you can see possible issues before releasing the document for creating the picking warehouse tasks. Once the wave is released, let's see the picking warehouse tasks created and destination. 00:12:20 00:12:39 In our demo, it's the packing work center Y831. Okay, using the Pick by Cart Fiori app, we can confirm the picking warehouse tasks. Firstly, log in with the resource, 00:12:46 and selecting the picking mode. This friendly and intuitive app 27 00:12:50 00:12:55 displays the information needed to guide the warehouse workers to pick the product for multiple orders in a single trip. In this screen, two pick HUs are expected. 00:13:02 00:13:07 Create the first one and connect it to the position on the pick cart. In this case, pick HU 1234 on position 1-1. And the second, 5678, on logical position 1-2. 00:13:30 Following this step sequence, the products are picked physically 00:13:35 00:13:42 and placed onto the logical positions. Scan the search bin, and confirm the destination for the handling units. Once confirmed, the app updates the screen according to 00:13:52 the logical position used by the handling units and quantity remaining on the warehouse order. 00:14:03 Repeat this step until you complete the quantities and products required on the warehouse order. 00:14:17 On this last screen we have to unload the handling units. It means move the handling units 00:14:26 00:14:35 created and placed on the logical positions previously to the destination storage bin. In this case, there are two destinations storage bins at the packaging work center. 00:14:48 00:15:01 After confirming the picking warehouse tasks, log off from the app. All the picking handling units are confirmed. It's time to package the products 00:15:05 00:15:10 00:15:18 00:15:23 using the app, Pack Outbound Delivery. Connect to the work center, fill in the storage bin, and select the packaging mode. In our example, the basic mode. Start filling the reference number, which is the pick HU confirmed in the storage bin. The app automatically displays the picked product on the left side, 00:15:28 00:15:34 00:15:40 and creates a shipping handling unit on the right side. Click on products for packing into the shipping handling units. And close in order to conclude the packaging step for the shipping handling units. Repeat the steps for second picking handling units. 00:15:48 Change the storage bin on the packaging work center, and inform the picking HU assigned to this storage bin. 00:16:04 After you close the shipping handling unit, the packaging step is concluded. 00:16:11 New warehouse tasks for a stage are expected. Let's check the status of the warehouse activities 00:16:20 00:16:31 00:16:40 00:16:46 on the warehouse monitor. The statuses are up to date for the outbound delivery orders. Select all the documents in order to monitor the status. Picking is complete, but loading and goods issued has not started. On the bottom side, the list of all warehouse tasks created until this step. Picking and packing step has status C, which means completed. 00:16:57 But the stage step has the status blank, which means there are open warehouse tasks for confirmation. 00:17:06 For this step, we are going to use the Fiori app Process Warehouse Tasks. 00:17:14 This is the Fiori app for warehouse task confirmation. Filters are available to select the documents, 00:17:20 00:17:27 for instance, warehouse orders, warehouse task status, and warehouse process type. You can confirm or cancel massive documents, print warehouse tasks, or handle an exception 00:17:33 00:17:39 00:17:45 clicking on the document detail. Our warehouse tasks for stage are open and ready for confirmation to the intervening storage area for goods issue. Select the documents and click on Confirm. Now, to conclude the process, 00:17:55 00:18:05 we have to post goods issue for both outbound delivery documents. Finally, to close our demo, use the app Run Outbound Process. 28 00:18:11 We can conclude the process posting goods issue. Let's use the filter by the sales document. 00:18:21 00:18:35 00:18:41 These are the documents that started the outbound process in this demo. Once the documents are displayed, we can see the picking state of 100%. Select the first document and click on Goods Issue. Now the status for goods issue has changed to completed. 00:18:52 00:18:58 And again, to the second document, click on Goods Issue. And both documents have goods issued completed. Before we finish this unit, let's see important takeaways. 00:19:09 Using SAP Extended Warehouse Management, you can improve customer service productivity 00:19:15 and accuracy of operation in the warehouse. The solution is very flexible. 00:19:20 You can configure functionality according to the adherence of your process 00:19:24 and ready for handling large volumes. Achieve reduction in your order cycle time. 00:19:32 00:19:39 And scalability. I hope you enjoyed this unit. Thanks for your attention. And I will now hand over to my colleague, Philipp Bergthaler. 29 Unit 7 00:00:06 00:00:12 Hello, my name is Philipp Bergthaler and I am a business processes consultant for SAP Transportation Management. Today I will present to you unit seven of this openSAP course 00:00:21 00:00:27 00:00:36 00:00:46 from my home office in Upper Austria. The topic for this unit is Simple Carrier Selection with SAP Transportation Management. Before I go into the details, I want to show you what carrier selection actually means in a typical transportation process and how it fits into such a process. To do this, I have prepared this overview slide 00:00:54 00:01:03 00:01:07 showing a typical transportation process. It starts at the top with transportation demand. Then next, freight units are built. And, in the planning step, assigned to freight orders or freight bookings. To give you an example, 00:01:12 such freight order could be, for example, a truck in a load transportation scenario. 00:01:19 00:01:26 00:01:33 00:01:39 The carrier, which is responsible for the execution of the freight order of the transport, is determined in the subcontracting step, which is highlighted on this slide. For the subcontracting or carrier selection, there are multiple options, which depend on whether you use Transportation Management or Advanced Transportation Management. 00:01:45 00:01:52 And I will talk about this on the next slide. After carrier selection, the charges can be calculated for the freight order. And then finally, the freight settlement document 00:01:58 00:02:08 is created and posted. So, as promised next we will talk about how the options differ for the carrier selection, depending on whether you use Transportation Management 00:02:17 or Advanced Transportation Management. There are several solution capabilities 00:02:25 00:02:34 00:02:40 for transportation processes in SAP S/4HANA. There is basic shipping based on LE-TRA, which is available only for a limited period of time with the compatibility scope. Then there's Transportation Management and Advanced Transportation Management. 00:02:46 Both technically are based on the same code line, but the difference is that Transportation Management 00:02:53 is available with the SAP S/4HANA Enterprise Management License, but not all functionalities can be used. 00:03:02 Advanced Transportation Management, on the other hand, provides the full scope of functionalities, 00:03:09 but it requires an additional license. On the right-hand side, 00:03:15 00:03:22 we see what this means for carrier selection. Actually, many functionalities are only available with Advanced Transportation Management. Everything in the light blue area 00:03:28 00:03:35 is part of optimizer-based carrier selection, and the optimizer is only available in the advanced version. We see that manual assignment of a carrier 00:03:42 is possible in Transportation Management, and also that there are some automated options, 00:03:50 00:03:58 which I will talk about next. So, in SAP standard it is possible to determine the carrier for the freight order based on Transportation Management default routes. 00:04:07 This option I will talk about in detail on the next slides and also I will show this in a system demo. 00:04:16 00:04:25 For very basic transportation scenarios, it is maybe an option to have only one carrier per freight order type. If this is possible, 30 00:04:29 00:04:37 you can maintain the carrier in the partner determination profile assigned to the freight order type. A third option is to determine 00:04:45 00:04:50 the carrier already in the delivery, and then transfer it to the freight unit, and then from the freight unit to the freight order. If custom development is an option, 00:04:59 one way to do this is to create a custom process controller strategy, 00:05:06 calling a custom Transportation Management condition. If you need more information on this topic, 00:05:15 00:05:20 I recommend having a look at the SAP Transportation Management enhancement guide, which is available online. Finally, another option 00:05:25 for the custom implementation of the logic is the BAdI, which is available 00:05:32 00:05:40 00:05:46 for the partner determination profile in the freight order type. Now, in the remaining part of this unit, I will focus on option one on carrier determination based on default routes. I will first explain the concept of default routes 00:05:53 00:06:00 in SAP Transportation Management, and then show also in the system demo, how it can be configured and how the process then actually uses 00:06:05 those default routes to determine the carrier. Default routes can be used to predetermine a route 00:06:16 00:06:22 00:06:26 between a pair of source and destination locations or transportation zones. During freight unit building, the system actually can check if for the given source and destination location of a freight unit 00:06:32 00:06:38 00:06:44 a default route can be found, which matches those locations. And, if such a route is found, then it is applied to the freight unit together with all the information maintained on the default route. And you can see on this slide that 00:06:49 the carrier actually is one such piece of information, which can be maintained on the default route 00:06:59 Now on the last slide before actually going into the system demo, 00:07:04 00:07:09 I would like to explain the master data objects and customizing settings, which are required to set up carrier selection based on Transportation Management default routes. 00:07:17 00:07:22 00:07:28 I will start with the master data object on the left-hand side. Locations are required anyways if you want to use Transportation Management. At least the source and the destination of each freight order needs to be represented by a location. 00:07:38 00:07:44 Transportation zones are optional, but they are a really good way to group locations. A default route can either be maintained between two locations 00:07:49 or between two transportation zones or a location and a transportation zone. 00:07:55 00:08:00 00:08:06 This means if you use transportation zones to group locations, the number of default routes that have to be maintained can be reduced, maybe greatly. Again, of course, default route also need to be maintained. 00:08:14 00:08:18 In regard to customizing, I will now focus on those settings that are most relevant for carrier selection based on Transportation Management default routes. 00:08:27 The freight unit building for sure is the most important one. There you will find a flag called apply default routes, 00:08:35 00:08:40 and this flag needs to be set in order for this process to work. The logistics integration profile is relevant because there we define 31 00:08:44 00:08:50 the freight unit building rule. And the customizing for the delivery integration again in turn is important because there the logistics integration profile is maintained. 00:08:59 00:09:05 Now actually we will see exactly those objects in the system demo. I will first show the configuration and then I will show a process 00:09:12 that uses those objects to determine the carrier for the freight order. 00:09:19 00:09:24 00:09:28 I will need to jump a little bit between SAP GUI and the Fiori launchpad during the configuration part. And also during the process, I will create the delivery in SAP GUI just to give you a visual contrast 00:09:34 between the part that I do in SD or LE and the part that I do then 00:09:44 00:09:48 in Transportation Management. The locations actually are not that important for this scenario. So I will go directly, or they're not specific, 00:09:54 so I will go directly for the transportation zones. For the transportation zones, 00:10:00 just enter part of the name, and then you can display all transportation zones 00:10:05 00:10:10 with that pedal. Here we will see the transportation zone for the customer locations that I have created. And if we scroll down we actually see the locations. 00:10:18 Notice TM customer 10, which is the customer that we will use in our scenario. 00:10:26 Now go back to the master data part and navigate to the default route section. 00:10:34 00:10:41 The default routes also are shown or displayed in a work list. There's only one default route in the system and I open it up. 00:10:46 And here in the default route, we will see the sequence of stops 00:10:50 00:10:56 00:11:01 maintained in the default route. It always goes from shipping point 1710 to shipping point 1720, and then to the transportation zone of the customers, which I have just shown. Also, it's really important here 00:11:06 that we have maintained the carrier for each of the stages. So this is actually where the carrier information comes from. 00:11:20 00:11:25 Back, now we go to SAP GUI because now we will show the customizing that is required. We will start with the customizing 00:11:30 00:11:34 for the delivery integration. And in the delivery integration, we will see that the system decides, based on shipping point, delivery type, 00:11:40 and shipping condition, which deliveries actually are relevant 00:11:43 for Transportation Management. Here we can see the shipping point, 00:11:53 00:11:59 00:12:07 delivery type and shipping condition, and we see shipping condition Y7 used with logistics integration profile Y003. This is the setting we will use in the process. So now let's go to the logistics integration profile and have a look at this logistics integration profile Y003 00:12:15 00:12:22 00:12:25 where we see that freight unit building rule openSAP_01 is used. And as I mentioned before, the freight unit building rule is actually the most important part to apply default routes. 00:12:29 So I switch back to the Fiori launchpad, where, in the profiles and settings section, 00:12:36 00:12:48 00:12:53 00:12:56 I also, again, via a work list, show the freight unit building rule. So again, in the list, we will see all freight unit buildings rules that are maintained in the system. There are two. We use OPENSAP_01. We open that, and on the top right-hand side, 00:13:05 00:13:09 we can see consolidate per item. So we will expect one freight unit per unit per delivery item. And we see that the apply default route flag is set. 32 00:13:14 00:13:20 This is actually the flag that needs to be set in order for the default route to be checked during freight unit building. And this actually already was all of 00:13:25 00:13:30 the customizing that is required. And therefore we will now go to the process and I create a delivery based on the sales order, which I have created before. 00:13:35 There are two items in the delivery, so we expect to freight units, 00:13:40 00:13:48 00:13:54 and the delivery goes to the customer, the USTM customer 10 . In the shipment part, we see the shipping condition, Y7, you see it now. And this is the shipping condition 00:13:58 that we use to determine the correct freight unit building rule. We save the delivery. 00:14:05 00:14:12 And remember, the delivery number is 3597. So it's ending with 3597. Now, again, I go to the Fiori launchpad and in the Planning section, 00:14:18 there I do have a work list for freight units. I see all the freight units in this list, 00:14:26 so after the refresher I also see the new freight units, so I expect two new ones to be created. 00:14:32 00:14:38 00:14:49 And we see now, okay, there are two new ones created for the delivery ending with 3597. I open one of them and go to the General Data tab where highlighted in blue you can see that actually 00:14:52 the right freight building rule, OPENSAP_01 was selected, 00:14:56 00:15:01 and also the locations, the source and destination location, were selected as expected. It goes from the shipping point 1710 to the customer 10 location. 00:15:07 On the Stages tab, we see that the sequence of stops has been applied, 00:15:12 so it goes from 1710 to 1720, then to the customer location. And if we scroll all the way to the right, 00:15:19 we see that the carrier has actually been determined. So this is what's actually our goal, to get the carrier from 00:15:25 00:15:31 the default route to the freight unit. But now we need to do the planning. So go back to the work list, select both freight units for the delivery ending with 3597, 00:15:40 and create capacity document, which means the freight order, for those two freight units. 00:15:48 The error message you see there, this is just telling us that we don't have 00:15:52 00:16:01 00:16:07 the optimizer available here in this scenario. Now back in the freight unit after the refresh, we see that, yeah, after the refresh the freight unit is now assigned to a freight order. So this happened due to the planning. And we go to the freight order. 00:16:16 And in the freight order, again, on the General Data tab, 00:16:21 00:16:25 00:16:28 we see on the right-hand side that the carrier has been determined. So this was actually now our final goal, to have the carrier on the freight order. This carrier is responsible for the execution of the transport. Again, source and destination locations, 00:16:34 00:16:39 00:16:45 as expected, have been taken over from the freight unit to the freight order. Now to the Business Partner tab, there again you see the carrier has been taken over, so no surprises there. On the Items tab we see 00:16:50 00:16:56 00:17:00 that both freight units have been assigned to the freight order, each with one item. On the Stages tab we see that those are the stages tab have been copied over from the freight unit to the freight order. So yeah, as expected, 1710, 1720 then the customer. 00:17:09 And here on the Charges tab now, we see the charges have been calculated 00:17:13 for the freight order. This was possible after the carrier had been determined, 33 00:17:19 because then we could determine the freight agreement between our purchasing organization and the carrier. 00:17:25 And based on that, we will see the freight agreement now, and based on that freight agreement, 00:17:29 00:17:37 the charges were calculated. So this actually is already the end of the system demo. And I switch back to my presentation now, and to the key takeaways 00:17:43 00:17:46 00:17:51 that you should take with you. First, you should remember that simple carrier selection based on TM default routes is possible in SAP standard with Transportation Management. There are also some other options 00:17:58 and some of them require some custom development effort. Also, you should remember 00:18:05 00:18:11 that Transportation Management as a solution offers much more sophisticated functionality like tendering, which is available with advanced consultation management. 00:18:19 And with that, I am at the end of this unit. And in the next unit, you will meet my colleague, Kim Van Riet. 34 Unit 8 00:00:05 00:00:10 Hello, my name is Kim Van Riet. I'm a business process consultant, and I will present from Belgium the next two units to you. Let's get started with unit eight, 00:00:16 Flexible Workflow Configuration Options. The first question we will start off with 00:00:23 00:00:31 is, "What is flexible workflow?" So flexible workflow is a new concept which has been introduced with SAP S/4HANA with the objective to simplify workflow configuration. 00:00:37 00:00:42 Documents in sourcing and procurement, such as purchase requisition, purchase order, request for quotation, usually go through an approval process. 00:00:47 For example, the approval process for a purchase order could be as simple as 00:00:53 00:00:58 00:01:04 any purchase order exceeding a 1,000 euros requires the manager's approval and any purchase order exceeding 5,000 euros requires two levels of approval. The flexible workflow is based on a set of predefined workflow scenarios and tasks. 00:01:10 This provides a functionality to define condition-based workflows 00:01:15 00:01:22 for different processes in sourcing and procurement. It's possible to define a single or multi-step approval process. And also, all the relevant workflow items 00:01:29 00:01:34 00:01:39 are made available in the My Inbox Fiori app for the approvers. Manage Workflows Fiori apps are available for different purchase documents, and these apps allow the business process specialist to set up workflows 00:01:44 based on the business requirements. In the SAP ERP system, we use release procedure 00:01:51 or SAP Business Workflow to accomplish this process. And even though both the release procedure 00:01:59 00:02:05 and the business workflow are still available in S/4HANA, it is recommended that you use a new flexible workflow functionality in S/4HANA. So going to the next question that we will handle today, 00:02:15 00:02:21 "How do you activate flexible workflow?" So to configure the flexible workflow, you have to perform different steps in the system. Some of the steps are optional, others are mandatory. 00:02:28 As a prerequisite for using the flexible workflow, several customizing activities need to be done, 00:02:34 such as the activation of the flexible workflow scenarios. So if you use, for example, the agent determination, 00:02:43 00:02:47 so manager of the last approver, manager of workflow initiator, and the manager of workflow initiatives manager, to determine the correct approval, 00:02:53 00:03:00 you have to maintain the relationship between both the employee and their managers. So next to that, there are some optional steps that can be done as well, that you can take. 00:03:06 So when specifying the recipients for a workflow, for example, you can define users who have specific team functions 00:03:13 00:03:19 as the approvers of the work items. So these team functions need to defined, and you can define these in responsibility management. So you can also define, for example, 00:03:25 00:03:34 the accounting objects responsible, for example, the person responsible for a cost center can be set as the approver of the document. If the standard functionality doesn't fit your requirement, 00:03:41 00:03:48 there's also the possibility to include custom fields or your own custom logic. This can be defined into three groups. So firstly, you can define your own rules 00:03:52 for determination of approvals. You can also define your own preconditions 35 00:03:58 00:04:04 for the start of a workflow or workflow steps. And as a last point, you can also define your own logic to restart the workflow. The main activities for defining workflows 00:04:10 are done in the app Manage Workflows for Purchase Requisitions. So we here use the purchase requisition as an example. 00:04:20 00:04:26 However, this is also applicable for all other purchasing documents. So first of all, a workflow scenario needs to be selected. That's the most important thing. 00:04:31 00:04:37 So this can be the overall release or a release of the purchase requisition items. Afterwards, the start preconditions need to be defined. Then the approval steps with step preconditions 00:04:45 and recipients as well. And the order is also quite important. 00:04:49 00:04:54 It needs to be defined in which order the approval steps are executed because then the workflows need to be activated. And as a last point, 00:04:58 the order in which your workflows are checked for matching start conditions need to be defined. 00:05:04 As soon as the preconditions for workflow are met, this workflow is used. 00:05:11 00:05:16 Defining the order ensures that only one workflow is started even if several workflows have matching start preconditions. So then there are two more optional steps 00:05:22 00:05:27 00:05:34 that you can take as well. So you can also translate texts that were manually created for a workflow into several languages. So this includes, for example, the name of the workflow and its description, as well as the workflow steps - they can be also translated. 00:05:42 And you can also configure the system to notify approvers via e-mail about new work items in their inbox. 00:05:51 By default, the approvers are informed by means of notifications in the SAP Fiori launchpad. 00:05:57 00:06:02 00:06:08 So sending e-mails provides them with an additional notification channel. So you can also configure the systems so that the requesters receive e-mail notifications when a purchase requisition gets approved or rejected. So then we go to the next question today. 00:06:17 00:06:21 So the third question that we are going to look into is, "How do you add custom preconditions to the workflow?" As I already previously mentioned, 00:06:28 there are three groups where custom fields and logic can be used. 00:06:32 00:06:38 As a first point, own rules can be defined to determine the approvers. This can be done by implementing the BAdI determination of workflow agents for purchasing documents. 00:06:48 This BAdI can be used to, for example, define specific approvers for specific materials 00:06:55 or to define approvers for documents assigned to specific purchase organizations or purchasing groups. 00:07:04 The BAdI can be implemented via a SAP Fiori app, which is called the custom fields and logic. 00:07:11 00:07:19 00:07:25 You can also define your own preconditions for the start of workflows and for workflow steps. So for this, two BAdIs have been made available to use. So on one hand, you have a BAdI to provide additional conditions for scenarios. On the other hand, you have the BAdI value evaluation 00:07:33 00:07:40 of additional conditions for scenarios. So if you would like to define your own logic for restarting the workflow, you can create an implementation 36 00:07:45 of BAdI-defined conditions to restart flexible workflow. An example, where you can use your own preconditions 00:07:54 is when you create a new flexible workflow with an account assignment category as a condition, 00:08:01 it is possible to, as standard, choose from A, F, K and P, but it's not possible, for example, to select from Q or X. 00:08:10 The standard workflow app only provides those four mentioned account assignment categories 00:08:15 00:08:20 as a prerequisite. So from 1909, there are two BAdIs made available where you can add preconditions. So the next question is, 00:08:26 00:08:33 "Is it possible to retrigger the workflow?" So yes, it is possible to retrigger the workflow. And this is also possible by implementing the BAdI that we already mentioned in the earlier slide. 00:08:39 So define conditions to restart flexible workflow. This can be done via the SAP Fiori app 00:08:45 00:08:50 00:08:55 custom fields and logic. So you can go to the flexible workflow customizing for the purchase requisition. You go to the Exception Handling section, and in Action Results, you can set Restart Workflow. This way, the purchase requisition can be changed. 00:09:03 00:09:08 00:09:12 00:09:17 In case of a cancel workflow, the purchase requisition cannot be changed later. So note that it's not possible to edit a rejected purchase requisition when flexible workflow is active. It's very important to know. The only action possible in that case is to delete such a purchase requisition 00:09:21 00:09:27 00:09:31 and create new documents for approval. So if you're then talking more about a conversion to S/4HANA, a question that often occurs is, "Does the release strategy need to be changed?" So the answer to this question is no, 00:09:38 you do not need to change the existing release strategy, but you can change it to flexible workflow if you want. 00:09:45 00:09:52 This can be done in customizing, and by going to the activation of the flexible workflow for purchase orders. So the path is mentioned on the screen. 00:09:56 00:10:01 00:10:07 This way, you can also decide if you would like to keep on using the existing release strategy that you have implemented for, for example, the standard purchase order document type NB, and then change to flexible workflow for, for example, UB. So you can really define it per document type. 00:10:14 00:10:20 00:10:26 So with that, we come to the end of this unit. So we come to the key takeaways. So firstly, it's very important to understand that business process specialists can now set up workflows themselves with the flexible workflow. The SAP Fiori My Inbox app is available 00:10:33 00:10:39 00:10:43 and gives you an overview of all pending approvals that you have as an approver. And you can add custom pre-conditions to support your business requirements. The flexible workflow and business process allows you to synchronize and proactively deliver work 00:10:50 in the right sequence and based on the workflow steps, at the right time by defining the deadlines, 00:10:56 and by the right people by using agent determination, and with the right information and minimum efforts. 00:11:03 00:11:08 00:11:13 And also very important and lastly, without compromising in compliance. With that, we come to the end of this unit. In unit nine, we will end the course with the topic flexible workflow demo. 37 Unit 9 00:00:06 00:00:10 Welcome back to unit nine, which is the last unit of this course. We will end this openSAP course with the topic Flexible Workflow - Demo. 00:00:16 So, the question we ask ourselves in this unit is what does flexible workflow look like in the system? 00:00:22 To answer this question we will go through some demos. So we will first see how the flexible workflow is activated 00:00:29 and trigger the flexible workflow on the purchase requisition. 00:00:32 Secondly, we will see how we can restart the flexible workflow. Afterwards, we will dive into 00:00:38 how you can add custom pre-conditions to the flexible workflow. 00:00:42 00:00:45 And as a last point, we will show how to switch the PO from release strategy to workflow. So let's kick off and see how to activate the flexible workflow, 00:00:51 00:00:57 00:01:03 and how it can be triggered for purchase requisition. So firstly, activating the workflow. So for this we will need to go to SPRO and to the IMG. So then we will follow the path of first clicking on the SAP NetWeaver, then Application Server, 00:01:11 00:01:22 afterwards Business Management. Then we have the SAP Business Workflow where you can see Flexible Workflow and Scenario Activation. 00:01:25 You can also decide to go and exit it via the purchase requisition as well. 00:01:30 Here you can activate workflow scenario IDs. So for purchase requisitions, there are two scenarios, 00:01:36 00:01:41 00:01:46 one for the overall release and one for the release of the purchase requisition item. Scenarios will become visible in the Manage Workflows for Purchase Requisitions Fiori app once activated here. So if you want to do an overall release 00:01:50 00:01:53 00:01:58 of purchase requisition, you need to go and activate the scenario for the overall release, otherwise you can also activate it for the item release. In this example in the demo, we're using the configuration steps 00:02:02 00:02:07 for the workflows for purchase requisition. The steps to implement workflows for other purchasing documents are similar and the information provided here can also be used 00:02:12 as reference material. So for the release of the purchase requisition item, 00:02:18 00:02:24 the scenario ID is ending on the 471, which you see in blue on the screen. Next we're going to define step names and decision options to be used in the Fiori app My Inbox. 00:02:32 For this one, we stay in SAP NetWeaver in the IMG, but we need to go to the gateway service enablement. 00:02:40 00:02:48 So it's a little bit above, and there you can click on Content. Then we will go to the Workflow Settings. And there you will select 00:02:55 Maintain Task Names and Decision Options. In the Step Name overview screen, 00:03:01 00:03:05 00:03:12 you need to include the workflow scenario for release purchase requisition, if it doesn't exist already. Here you see that it already exists, so you will need to select to correct workflow ID, which is here to release the purchase requisition item, 00:03:18 00:03:25 and you will need to go to the left side of the screen where you can select the decision keys. And there we need to make sure that the correct decision keys are added, 00:03:30 so the approve and the reject. Here you see they are both added, 38 00:03:45 00:03:48 which is good. And next to that, the Icon MIME Repository Path and the Comment On fields need to remain empty. 00:03:57 00:04:01 Now that we've activated the flexible workflow, we can go into the Manage Workflow for Purchase Requisition Fiori app. So you see on top of the screen the workflow, 00:04:06 so there are different workflows that have been activated, so we will go for the release of purchase requisition item. 00:04:14 00:04:19 So you see that the automatic approval for purchase requisition item is there, so there are already two workflows in this screen. So what we will need to do is we will need to add an extra one. 00:04:25 00:04:29 00:04:33 So we'll click the Add button. And there the first thing we need to do is give the workflow a name. So we will give it a name the purchase requisition item approval. So then we will go to the properties section 00:04:40 where we will need to fill in the description and also the valid from and valid to date of the workflow. 00:04:48 00:04:53 So the purchase requisition approval for cost center, for example, as a description. And we will have valid from and the valid to date. 00:05:01 00:05:07 00:05:13 Then we will go into the start conditions. So the workflow will only start when the following preconditions are met. So as a first precondition, we are going to select the account assignment category. So the account assignment category 00:05:19 00:05:27 00:05:33 00:05:43 of the purchase requisition needs to be K, cost center. Then we will add a second condition, so the second condition we will add is a material group of purchase requisition item. There, we will select the material group, YBMM00, as an example. As a third condition we are also going to add the plant. The plant needs to be 1010 for the workflow to be started. 00:05:52 00:05:57 And as a last condition, we're also going to add the purchase organization. So the purchase organization we're going to include is also 1010. And then we will go into the step sequence. 00:06:05 00:06:11 00:06:15 So in a step sequence you see there's a step type, which can be the automatic release or the release of the purchase requisition items. So we will go for the second option. We're going to say that it's not an optional step. And as recipients you can add either a role or user. 00:06:22 00:06:28 00:06:34 So we will choose a role and we will state that the accounting object responsible needs to approve the purchase requisition. So here in our example, we have the cost center. So the cost center owner will need to approve the purchase requisition. 00:06:40 We are going to add an extra precondition, which will be the net amount is equal 00:06:46 00:06:55 to or greater than €1,500. And you can also decide, if you want you can add deadlines, so time constraints for when the approval needs to happen. We're not going to do that in this case. 00:07:02 But in the exception handling tab, we will say that if the purchase requisition item is rejected, 00:07:09 00:07:14 00:07:20 00:07:24 then the action result doesn't need to be cancel workflow, but it needs to be restart workflow. So we're going to change it to the restart and we're going to add this to our workflow. So now our workflow is ready. So we quickly have a review, okay, everything has been filled in correctly, and we're going to save our workflow. 00:07:34 00:07:37 Then the only thing we need to still do is activate it before it will work. So we will click the Activate button and then our workflow is ready to be used. 39 00:07:45 So then we will go and create a purchase requisition. So we will go to the Manage Purchase Requisition Fiori app 00:07:53 00:08:01 00:08:07 00:08:13 and there we will create a purchase requisition. We click the Create button and we fill in all the required fields to complete the purchase requisition. We use document type NB, it's just a standard document type, and we will add a material to our purchase requisition. Of course, based on the setup or the preconditions we have used in our workflow. 00:08:20 00:08:25 00:08:32 So we use plant 1010. We use cost center as an account assignment category. We will use the correct material group. We include our evaluation price and our quantity. Unit of measure. And then in the account assignments, 00:08:39 we need to select the cost center, so we will choose 10101201. 00:08:43 00:08:53 So we will apply these changes. Then everything has been completed except for purchasing organization and purchasing groups. So also there we need to include the 1010. 00:08:58 00:09:05 00:09:11 And as a purchasing group we use 001. And then we will check the approval details. And there you already see that the approval workflow has been calculated. So we see that the account object responsible needs to approve. 00:09:19 So you can see the details awaiting approval and Franz Musterman needs to approve 00:09:24 the purchase requisition. So what we will do now is we will go 00:09:37 and sign out of this user, and we will go to the user ID of Franz Musterman, 00:09:44 00:09:50 and we will see there, in his My Inbox Fiori app, where he can approve or reject. So we're logging out of here. And now we're logged in with Franz Musterman. 00:10:00 So you see this is a user ID Franz Musterman, and we will go into his My Inbox 00:10:08 00:10:13 00:10:18 because all the approvals of the workflow will fall into one My Inbox Fiori app. And there you see our approved purchase requisition that we just created. So you can either approve or reject. So in this case, we are going to reject, 00:10:22 because we also want to restart the approval flow. You can add a note if you want to, 00:10:28 00:10:37 so please check PR for incorrect details. And you can submit. So then this has been done. So what we do now is we're signing out of the approval user ID, 00:10:43 00:10:50 and we're going to log back in to the one where we created our purchase requisition. So we go back to the Manage Purchase Requisition Fiori app and there you will see that our purchase requisition 00:10:59 is still in awaiting approval. So when we click into it, 00:11:13 here you have the overview screen, and you can click into the approval details to see, 00:11:17 okay, how it's going on with my purchase requisition. And so you see that the item has been rejected 00:11:25 by Franz Musterman and that he has rejected it with comments. 00:11:32 00:11:36 00:11:41 00:11:50 Please check the purchase requisition for incorrect details. So we go back and we will go and check our purchase requisition. In this case, we're just going to change the quantity from 100 to 150. And we're going to apply these changes and save it again. So it's again in awaiting approval. 00:11:58 So if we go and have a look to the approval detail step, you see that it has been sent for approval 00:12:06 00:12:12 to Franz Musterman again. So what we will do now is we're signing out again, here we will go back into Franz Musterman, so in the approver user ID. 00:12:20 And so there in his My Inbox app you see our purchase requisition again. 00:12:25 And now we can just approve. Voilà, the purchase requisition has been processed successfully, 40 00:12:32 00:12:42 the approval has been done. So going back to our user and going back into our purchase requisition, we see the purchase requisition has been approved now. 00:12:49 00:13:02 00:13:06 So the release has been completed and our purchase requisition is ready and released. So next up we will add custom preconditions to the flexible workflow. So for this we go to the Custom Fields and Logic Fiori app. There are three different tabs, 00:13:12 00:13:17 00:13:21 Custom Fields, Data Source Extensions, and Custom Logic. Here we will click on Add and there you will see the business context. So you can go and scroll to P for procurements. There you will find all the custom logic that can be added. 00:13:29 00:13:34 So we will go and add, for example, for workflow, you have agent determination for restarting preconditions. So we select agent determination, 00:13:38 you can select the determination of workflow agent for purchasing documents 00:13:43 00:13:49 00:13:55 and add, for example, fixed assets because we want to have an approver for fixed assets. And there you can actually add your custom logic. So you can include the available fields that you require for your workflow, you can set the filter, 00:13:59 and you have also BAdI documentation. We are not going to go further into details 00:14:05 because this is really also user for development. You can just go and click on the radio button 00:14:13 and then you still need to publish your BAdI once. Next is switching PO from release strategy to workflow. 00:14:20 So you can decide to use flexible workflow per document type. So if you navigate also to the IMG 00:14:27 00:14:32 and then you go to materials management purchasing, then you have the purchase order and flexible workflow for purchase order. There you can activate flexible workflow for purchase order. 00:14:39 So there you can basically set per document type if you want to use the scenario-based workflow 00:14:46 or the flexible workflow, or if you want to keep on using the release strategy. 00:14:50 You can really individually decide per document type if you only want to use release strategy, 00:14:55 or if you want to start using flexible workflow. Okay, so these were the demos that I wanted to share with you. 00:15:02 00:15:07 00:15:10 00:15:15 So the key takeaways from this unit are that the configuration to set up flexible workflow has been simplified. Also we have an improvement of the user interface with the adoption of SAP Fiori in SAP S/4HANA. So with that we come to the end of this unit and to the end of this openSAP course. 00:15:21 00:15:27 00:15:31 00:15:34 I would like to thank all colleagues for contributing to this course, and of course you for your attention. We hope you enjoyed learning and we all wish you now good luck for the course assignments. Thank you and goodbye. 41 www.sap.com/contactsap © 2021 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distr ibutors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty s tatements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warran ty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or p latform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.
