SAP SD Down Payment for Sales and Distribution Course - Complete Process SAP S/4HANA | SAP EnTuIdioma | Skillshare

Playback Speed


1.0x


  • 0.5x
  • 0.75x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 1.75x
  • 2x

SAP SD Down Payment for Sales and Distribution Course - Complete Process SAP S/4HANA

teacher avatar SAP EnTuIdioma

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

    • 1.

      introduction to the SAP SD S/4HANA Down Payment Course

      2:27

    • 2.

      Process to connect to SAP Fiori

      7:41

    • 3.

      Create Sales Order for Down Payment scenario

      5:14

    • 4.

      Using the Post Billing Document app to create the Down Payment req

      6:40

    • 5.

      Discover the Down Payment Req using Manage Customer Line Items Fiori app

      6:32

    • 6.

      Convert Down Payment Request into Down Payment using Fiori

      2:47

    • 7.

      Display the Down Payment in the Customer Account

      3:32

    • 8.

      Check the Reconciliation Account in the Customer master record

      3:50

    • 9.

      Consequence to the Financial Statements

      3:05

    • 10.

      Failed attempt to create the first invoice and assign the Down Payment

      1:47

    • 11.

      Correction of the Sales Order problem

      3:31

    • 12.

      Create the invoice and assign the Down Payment at the same time

      5:12

    • 13.

      Update to the Customer account

      2:32

    • 14.

      Update to the Financial Statements

      4:06

    • 15.

      Remove the billing block for the last items in the Billing Plan

      2:43

    • 16.

      Billing the last items in the Billing Plan using SAP Fiori

      4:35

    • 17.

      Display the new invoice using Fiori

      2:14

    • 18.

      Post incoming payment considering the Customer Down Payment

      5:13

    • 19.

      Check the payment consequence in the Customer Account

      2:38

    • 20.

      Using the Display Document Flow Fiori app to check the history

      4:34

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.

54

Students

--

Project

About This Class

In this class you will learn about the Down Payment process starting from Sales and Distribution and we  will test the customizing settings using SAP Fiori apps such as the Down Payment Monitor. We will cover the steps to create a Business Partner and create a SO and then post the Goods Issue. We will also learn to create the Financial Invoice completing the Process. We will also post the relevant flows and examine the consequence in the SAP FI application module. The class also includes the process to create a Down Payment Request.

Meet Your Teacher

Level: All Levels

Class Ratings

Expectations Met?
    Exceeded!
  • 0%
  • Yes
  • 0%
  • Somewhat
  • 0%
  • Not really
  • 0%

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.

Transcripts

1. introduction to the SAP SD S/4HANA Down Payment Course: Welcome to the SAP S4 hana down payments for sales and distribution curves. We are a collective expertise if we consultants with decades of experience and we are eager to share our knowledge with you. In this class, you will learn from our experience not only how to set up the master records and just create the damping request, but also how to link the down payment to the process and later have to get the invoice and apply the dumping into it. Actually. But here we have the full content. The first is just a quick introduction to the SAP S4 hana, how to connect and use a theory. Then we'll start the process and we'll just create the sales order, setting up a new special general ledger transaction, which at the end of day the downpayment is special general ledger transaction, so well, we'll start with that. Then we'll just have a dumping in monitoring. We will create an see the consequence of the down payment even in financial accounting later. But we will pose the goods issue within sales and distribution and just run the bidding process so we can post the invoice at the end of the day. This is an account receivable that we have in a financial accounting. Because of that, the next step is to post the incoming pavement when we actually receive the payment from the customer. But of course, considering the first down payment, and after we pose that, the last step is just to check the update to the customer account because of course, everything now has to be a cleared, so well, we have covered that process. We will close the course and of course we invite you to keep checking our following courses on the platform. But well, without further ado, let's start with the first lesson. And again, you can contact us using our contact details at any point if you have any doubt, we can help you with any other topic. Just please drop a line using 123, learn ACP at gmail.com. So thanks so much and we'll see you in the lesson. 2. Process to connect to SAP Fiori: In this lesson, we want to show the steps that we need to follow to start using fury. And of course, this is really important and relevant because as we know, fury is one of the cornerstones of these new releases. So we will just show the steps to connect. That will be just the first thing. We will run an app. As we probably know by now, the theory apps are built using a technology that is very similar to the technology that most of the websites that we use everyday use. So for this reason, we need to use a web browser. So it most of the modern browsers can just work with theory just seamlessly without any issues. But then the decision is just pretty much a matter of taste. And we really like Safari, wheels like Firefox and Chrome. So in this run, now that we're in a desktop computer, we will use Chrome to show the steps. Actually, we already have one window of Chrome open and we will just open a new tab. Definitely as you can see, that ministers of the system have just also enabled quick link into your 11. So let's just click on that one. But of course, it just valid to say that at the end of the day, this is just a URL. And most of the times the users that will work with VRE every day, they just set up a quick shortcut. Just like in the desktop, like a shortcut that you can just double-click and they will take it. The computer will take you directly to this website. So we can start using theory. Of course, as you can see even from this first screen, we have a much nicer, more graphic and just user-friendly user interface. So well, let's start with the steps. Let's just enter our user. And of course, the buzzword. We could change the language to any of these available languages, for example. But right now what we have, we'll just go with English. So let's move on. And at first it will just load what we call the theory Launchpad. Just think of these as your homepage. And we could use these tiles just to click on them. And the tail will just call the underlying application. But actually, we will start with just something really easy, which is an inflammation of them report. But for that, we need also to discuss the objects that we have at the top. They seem like hyperlinks is just like texts. But actually, at the end of the day, this is just a group of apps. So let's switch to the group of apps for controlling. Because here we have the rubber that we went to run right now, which is the cost centers plan. Actually, this report will allow us to query the database. So the system can show the values for a given cost center and we can compare the actual implant column. So we can compare actual costs again against plans, plan costs. So let's run this app just really easy because we just need to click once on it. And of course, at first, just with the parameters that we need to complete to query the database shows up. So let's start with the fiscal year. We will also select a posting period for you. And it's important to maybe notice that we have this red asterisks for some of the fields. For some others, we don't have those. But of course, these are just the, a, like a way to point out that the field is mandatory. So well, also, it's important maybe to notice is that actually for all of these fields, we have this icon on the right-hand side, which is like two squares on top of each other. And for people who have been using the SAP system for a long time, even the previous graphical user interface. In the classical one. You are familiar with this because the much code, just in theory it looks a bit different, but it's the same principle for some of you that are maybe new to Sep. Let's just show how can we use it, it just by clicking on it. And the idea behind this, actually, as you can see, like a rapper in itself. Because the idea is that anytime a user has a doubt on which, like, what value should the user select for a given field. But they can do is just they can use the match code. And again, it's like a little rubber that will show all the permitted values for that particular field. So for us, in this example, we want the actual plan version, version 0. So we can just select that values, select that line and click Okay. And also all immediately will have the correct value for the field. So it's like what's a way to prevent errors? Just because we use only possible values. Because those are the only values that will be shown by the match code. So let's now continue with the company codes for these will enter the IV, which is what? D dash ten, and the cost center, which is for these example, a ten, 1200s. After we enter all these parameters, let's just click Okay. And as easy as this will have immediately the data in our report. The app is now executed it query database and just very quickly just show the results. Of course, this is just a, for example, we can see the GL account that was used for this posting. We only have one actually. It's the value is four, €90 with $0.91. Well, this is just a very simple example that are much more complex apps that well, depending on what we went for an up with was built. This was just a quick example. Just record. We have finished just comparing, for example, the actual against them out. It actually against that plan, which of course is actually the plan is completely empty. So the difference is the actual amount. That is just like a quick look to their report to the center. And of course just do one of our first few reps. So now we just want to show the steps to, hey, quit this up. For this video is really easy. We can just click the zippy logo at the top left and immediately will interfere lunch. But with this, we want just to finish this lesson. And of course, we just imagined to keep learning with all of the rest. 3. Create Sales Order for Down Payment scenario: We know that the ERPs and integrated system, and now we want to focus on integration between sales and distribution and financial accounting. Actually, we will focus right now on the down payment process. And for this we'll start with a new sales order. So we have these definitely saves group of apps. And we will use the create sales order fury. Yep. So let's start that one. Of course. I mean, we went for this scenario just a standard orders. So we will use the OR, or their type. And for the sales organization will use a double 0. Our sales organization right now for this scenario, the distribution channel is ten, just direct sales and the division is doubled zeros, we just cross division. Okay, with those values, we can just continue. Let's click Continue at the bottom just to get to the main screen. And of course, the first thing we need to set up is the salt party at the ship to party. So for both of the Buddy's, we'll just see just a example customer that we have set up here. So everything is correct. Now, we can proceed with the customer reference. For that, we will just type the customer reference directly, the 4711. Then what the customer reference date, we will just select today's date for that one. So now for the requested delivery date, we will switch these do in a month is just a human. But we will choose right now, seven, June 7th. So that's okay. Now we can proceed. And actually, this is for a service. So let's use the ID for the service which is 11. Just installation services. So that is the material codes for the service. Now, but we just want the quantity is one service were selling at the end. We're going to use a customer material number for this service. Actually, they the IV for that one is for dozens, 711. So similar to what we had in the customer reference. So that is that is correct. Let's just double-check that we have the correct blender. We can assign the plant, which is the double 0. And then we can just press Enter. That is to validate the data. First. Because we have been modifying the dates, we will have a just a warning here that the bidding date is to remind us, that's fine. We can continue. And first we will double-check the item category. We went for these, which is Milestone billings. So here we have it. That is correct. Actually, because of this, we can double-click just to get the full detail for the item for disease or the right them. Because we want to double-check them. They're building plan. So let's have a look here. As you can see, we have the first language is the most important thing right now for our process. Here we have it set up a down payment for ten per cent. So that's fine. It's not blocked, it for 10%. So €1 thousand. And that is something that, well, I mean, it's just the basic data that we need four years later using the same order as the preceding document for the down payment. So of course later we will have also the invoices that's coming in some of the next lessons right now, we will just go back so we can save. Okay, I'm might have some village in Boston, but that's fine for our scenario. Let's save these sales order. And let's just wait for the fury up to finish, because of course we need these ID for the document. We have now a new standard order. This one is 351. So let's write the number down. Of course, as you know, this is one of the most important values that we will have for the process. And it's fine now we have it. Let's close the fury up. With these. We finish for today, thinking you all. 4. Using the Post Billing Document app to create the Down Payment req: Right now, we have only created the sales order. And as we know, this is a document that is relevant for logistics, but it has no consequences yet. In financial accounting, even though we have a billing plan, we have done pavements and then milestone a bulk billings that then these documents have an impact, directly impact in financial accounting. That's going to come later. Actually, this lesson is probably the, one of the most important of these cycle because we will use a pose billing documents of urea to create the down payment request. And well, for these, jump into sales. And here we have the create billing document theory up. Of course, this app will always show the previous document we have been working with the same order that we created. So it's fine. We can just press Enter. And as you can see, a apa has found that it's important right now to create the actually the down payment, but it's a down payment request. How can we know that? Because at the top-left we have here down payment requests. Later, we will understand a bit better. What is the difference between a down payment request and an actual down-payment? Moving right now, what we see right now, this is just a down payment request for €1 thousand. If you remember, there's the down payment was for ten per cent and the value for this document, for the sales document, it's €10 thousand. So yeah, we have that correctly set up. The dates are correct. Everything is fine. So we can just proceed and save at the bottom right. And now they're coming back with this success message that the document has been saved correctly. We have the ID nine multiple zeros, 111. But what's important and we can accomplish that right now. It's just have a look at document, not only the logistic document, but also their fight document that was created according to or things to this scenario, these steps. So for this, let's click More. And within willing document, we can just click Display amble. Again, the latest document that we have been using, the one that was created as a billing document some seconds ago. Now it's defaulted here. So we can just continue at the bottom, right. We can click Continue. And here we have the detail. Of course this is just exactly what we were checking the previous screens. But now we have the difference because now instead of having just a temporary number here, a temporary ID for document, now we have the actual ID for this document, the net value, the payer, everything. But then again, we were saying that we want to understand a bit better what has happened for us in financial accounting. So let's click the accounting push button. And able, this is the document, but it's really super interesting document because most of their fight documents that a, you will see throughout your time using this API. They have at least two line items are most of the times three or even more. But right now, this one, we only have one line item. As you can see, it's just the f is this special year indicator for a pit down payment requests and it's only one line. Again, this document is not even part of the financial statements. Actually. The document is not even we didn't have a 0 balance. So it's not even complying with the most basic accounting rules. But that's correct because at the end of the day, this is not a financial document. It's not something that actually we can consider as part of the financial statements. So what's important then? It's the amount we have requests for 1100 considering also the tax, the 10, which is 10% tax when 1010%, 1100. And well, again, the important thing with especially general ledger transactions is that they use a different account, not the main account that we have in the master record for their business partners. So what we can do right now, what we can show right now, is there within more there? Oh, well, actually, we can just double-click the line-item. It was listed in the, but actually it's right in the screen. There's the push button or we can just double-click on it on the line item. And as you can see, the e-mail account that was posted two to 11, Nine, one triple 0. So that is exactly right. This is not the recommendation. And Canada we have in the master record for the business partner for this customer, this is an alternative recondition account, and actually this is the account for down payment requests. What's important is that later we will convert, will transform the down payment requests into an actual downpayment. And also when we accomplished that the account will change and then later when we assign the down payment to an invoice, also the account will be different. Either concision and Gamble be different. So it's just like a pile of course, in the process some steps, but every time we continue to the next step, we will have a different yield account, a posted too, because again, that is the magic, that is the main thing with the special GL transactions. So well, after we have seen this, we can just go back close and finish the theory up. And of course, we just wanted to thank you all for your attention during this lesson and invite you to keep learning with the next one. Thanks so much. 5. Discover the Down Payment Req using Manage Customer Line Items Fiori app: We showed in the previous lesson that the theory app create billing documents, actually created a new document, but this is not an invoice. Actually. This is not even a document that will show up in the financial statements. It is actually just a request, it down payment request, of course. So in this lesson, we will assume that we are just accountants working especially evils in account receivable. Because our job is just to go through the account of the customers multiple times a day at least and just find if there is something new that we should contact the customer for. Just the pressure, maybe it's a payment, something that is overdue or just even a down payment. Because if we don't receive the money, but if it's if it's an overview in both, then we can even start a legal procedure sometimes, or at least charging is some interests on the money that we haven't received yet. But if it's something more like a down payment, but sometimes it might be even worse because we haven't received the down payment, we haven't received the money. And because of that, we haven't even started working with producing the product that we are about to sell it or just the service. Actually, our scenario is more for services, but regardless, we have to receive the money or it's bad for us. It's bad for the customer because we don't, because then the customer might be thinking, Oh, they are probably working on the order right now and we're not, and then we lose the customer. So it's also bad for us. It might happen that, but again, for everyone. So because of that, Let's show the process. Again. Let's assume we are just accountants working in. Accountants working does in account receivable. And let's use the managed customer line items for Europe. So of course, the first thing is just to set up the ID for the customer. Which view? Remember it's like the EC double 0 and then the ID of the company code here. And then if we use the filters as they are right now, actually, let's try this. Nothing will show up. Because if you remember, we have been saying that this request is not even a normal item, is not even considered to be part of the financial statements. It has no financial impact, soap, no accounting impact. So if we leave the item type as normal items, nothing will come out of these query. But actually we can just delete the item type and then we can open the list of possible values. For example, if we select especially general ledger transaction and weekly go, again, nothing will show up because this is not even down payment yet. It's a down payment requests. And that is a big difference because a down payment request is what we consider just a note that item is again, it's not even showing the financial statements ever so. Well to understand the use of these and just to see the consequences. Customer line items, Let's click note that items and click Go. As you can see now, the result set is not empty, then the query is coming back with data with, of course, our downpayment requests. How can we know this is a down payment requests just immediately because of the F letter in this special year indicator column. This is again like the most the most especial of the special GL transactions because again, these one is not even part of the financial statements. What is also important? It's the net. So again, we should be contacting the customer because we haven't received the money. Journal entry type is interesting is RV AND amount, which is 1100. Well, again, just to double-check that this is not even part of the financial statements, just to be sure, we can click the Manage journal entries after clicking the number of the document. And immediately we have at the top this thing, item one out of one. So that is something that should call it like our attention immediately, should jump immediately for us. And we would have to say, Hey, how is this happening? For documents? In, for financial accounting documents, we need at least two items. So what is happening here? The document should be balanced, but then we just check that this is the down payment requests that this is posted to an alternative account, not to the main or confusion account that we have set up in the master record. Actually, we can click at the bottom right corner back to your journal entry. And again, it's obvious that this is not even a full document, that that is not even part of the financial statements because we only have one light night, nothing here after that one. So yeah, everything is correct as you can see now, we have the general your account correctly set up here. And what's important is that in the header, we immediately know that this is a note that item again, so we know it's fine if we don't have a 0 balance with the document. We have we also know that this is coming from is z because we have a billing document transfer type that the IDs RV. And we again, we know that this is du. So we have to contact the customer immediately. If we jumped to related documents, of course, we have access to not only the billing document a, What's great dignity, but also the sales order, again created in as D. So again, we always have the full access to the history of the value, so, well everything is correct. We can just click then the zippy logo. So we come back to your launchpad and we've finished with this, these lessons. So hopefully you can join us in the next one. 6. Convert Down Payment Request into Down Payment using Fiori: So far we only have a down payment requests, and now we need to transform this into a full downpayment. For this, we will jump into financials and we will use the post customer down payments fury up. Of course, we can use the down payment requests as just something to be considered as a previous document that for these Fool down payment. But well, the first thing is just to complete the document date. We went the same date for the posting date and the document date? That is correct. Now, then let's complete the IV for the company codes and equivalency. The next thing is the ID for the customer, which is the AUC 0, if you remember. And of course our special deal indicator, which lets have a look using the match code. We'll use the a, which is the full dump payment. So we can just select the value from the list. And then we can just about the next thing is just to continue with the bank data. Right now, we will set the main bank account. Actually, this is the GL Account that maps the main bank account and the amount which is 1100, if you remember. Now, it's important to check here at the top that we have their requests push button that will allow us just to consider the previous document as a base document for them for the actual downpayment. Just before we proceed. We can also assign these two separate center. We'll use our PCA. So let's click request. The app will check the account for the customer. And this comes up, of course, when only when dumping request, which is the one that we have. Of course, we can just select the line and click posts at the bottom. With this, the theory I will come back with this success message at the bottom in new document is posted. Now, of course, we will check the consequence in the coming lessons. So for right now we can just close the fury up and we finish for today. But again, just keep learning with all of our trainings and please join us in the next one. Thanks so much. 7. Display the Down Payment in the Customer Account: Now we have the down payment document and of course we just want to check how it looks like and just if there is a consequences to the managed customer line items fury up. So let's jump into financials. And here at the end we have our managed customer line items. Then let's just complete the ID for our customer and for the company goes. Okay, well, we know that the first thing we have to modify, just the item type. We don't want normal items. Actually, we want especial GL transactions. So after we have selected the other one, Let's click Go. And as you can see, we have now the down payment. This is of course, the document. As you can see, this one is still open ear. We have it is not clear yet, and it's for 1 thousand mile, 100 Euros. But it's also important just to double-check what happened to the down payment request. So actually we will switch to all items because that one is cleared. And we also need to select note that the items, again, remember that just dump him requests is always a note that item. It doesn't matter if it has been clear or not. So if we change those two values in the parameters, as you can see now, we have the two lines, the F, which is the down payment request, it has been cleared. And well, of course, it actually it was clear by the document, the down payment document. You can have a look at that. If you scroll to the right hand side using the clearing Andrew column, we have them document number for the actual dumping. So yep. Everything is correctly set up for the clearing of the dumping request and the creation of the down payment. And just quickly, if we check the document, we will with no with no window. Right now we know that the document is now a down payment. Now the down payment request. So what is important also is that the account is different. As you can see, this has been moved to the 21194 times 0, just the down payment customer account and it's for €1100. Everything that we have been a working with and expecting about the process. So everything is correct. We have the correct status now for the dump and requests the correct before the down payment and later, we will continue that process, have some billing using the billing plan, of course, having some invoices Actually. So that later we will apply the down payment to these documents. Actually, this is going to be the one of the most important things and especially things about the process. Because when we run the gray billing documents up again, you will see is something really interesting. Just the fact that the system will automatically assign to these efforts in both the down payment, so we don't even have to worry about that. But then again, this is something that is coming in the next lesson. So we'd definitely hope to see you there. Thank you so much. 8. Check the Reconciliation Account in the Customer master record: The reconstitution account that is used for just normal a items such as the ones that we were asking in the previous lesson just at the start of the bridge, Listen. All of those invoices, payments and all of those, they have a similar thing, which is that they use the reconciliation account that we have set up in the master record of the business partner. So in this lesson, we actually want to show that master record using the managed business partner, partner master data up. Because a later we will check the financial statements and we want to understand the consequences of using it just especially generic transactions and also using just normal transaction, normal items. So let's, let's just wait for the app to load so we can look for the master record of our business partner. And here we have it. Let's use the id, it, the AC. And we can just then click Go. The app. We'll come back with the result from the query to the database. And as you can see, we only have one. Of course when master record that has this id. That is totally correct. This is the name of the costumer EBIT of the address, but rose, but the most important thing is just to get into the details. So we can click at the end of the line exactly to double-check the details. And this is just because we want to understand again, the data is shown in the in the app, but also what is the reconciliation account? And this is a setting that is completely company called dependent is a company called dependent setting. So first we have to select the correct role. And as you can see, we have the customer role here. This is the one that we want to look for right now. So we can click at the end of the line just to get into the details of that role. And actually, as you can see now we have a company code section so we can just scroll down so we get to that section. And within that section will have all the company codes that really can we can have postings using them. Right now we want to look for the DAW 0. So let's double-click on that one. And again, this is just the company codes that we can have postings using these business partner muscle records within the details. For example, here for our company code, we will find out that here. Here we have the important field that we were just considering, the trade receivables domestic. The important thing is, let's double-check the ID number. It's one-to-one, five times 0. This is our traders who was domestic. Later, we will understand a bit better how this comes into play. But yes, this is the main reconciliation account for these business partner must record trade receivables domestic. So then again, this is something we have to set up when we create the master record for the business partner. And later when we have invoices, when we have just payments, that account is the one that gets posted to. Of course, the down payment, for example, which is a special year transaction, uses we'll use an alternative account, but that is also what we will start checking in the next lessons. So please join us. 9. Consequence to the Financial Statements: We now have a full downpayment and that just means at the end of the document, just a financial document. But the important thing is that this document has an impact to the financial statements. We have also check what is the account that we have set up in the master record for the customer. And now we just want to understand if using our financial statements, we will have access to that account or the down payment has been posted in an alternative account. So let's have a look at that. We will use our balance sheet income statement theory up. Okay, so here we have it. And the idea, of course is the first thing is just to complete the IV for our company code. And then just the statement version, which for this scenario we will use the 1010 data is correct. The ledger is correct because what? We want to check the leading ledger and we went to compare actual data against actual data. We can compare against plan data, for example, other scenarios. But right now, for our scenario, we went actually against actual period is correct. So we can then just click Go. And well, let's discovered this using the liabilities. So here we have payables. And within payables we have this section for them, payments and residual maturity less than one year at the end of the day, this is something that we received already from the customer. And later the customer can just say, hey, I want you to assign this to a next invoice. So we will receive less money for that image because we have the downpayment already set up. But again, the most important thing for this lesson for differential statements is that the €1100 is not being shown in the one-to-one five times 0 account, which is the main reconstitution account, the viscera up in the master record of the business partner. This one is the downpayment is being shown in an alternative reconstitution account which is the 211, 94 times 0, just the dump payments for customers. So everything is exactly as we were expecting. The main use of the especially year transactions is this. So after we have double-check this in the financial statements, we just finished the lesson. But just a quick reminder, please. You can contact us using help the SAP experts at gmail.com. So please help that SAP experts at gmail.com with any doubt that you may have, we are more than pleased to help you there. Thank you so much. 10. Failed attempt to create the first invoice and assign the Down Payment: We have been working to deliver the service or the other by the customer. And if you remember, even in the order we have the milestone billing. So actually, right now we have completed the first milestone. So it's possible now to create the first invoice. But let's have a look if we can actually create this using the create billing documents fury up within sales. So here we have it. And well, of course we have to have a reference to a word, Saints orders. So let's enter the IV for that one and then enter just to double-check if we can create these inputs actually, well, right now it's just have this status is partially invoiced, but at the bottom will receive this message that no billing documents actually were created. So let's have a look at the log. So here we have it locked in the More menu. And then as you can see what the message is actually super clear. We just have a blocking just in the novel implant. This date has been blocked for this first milestone two. So we cannot create the billing document right now for this data. Well, what do we have to do? Of course, let's just remove the block. That's something we have to complete in the change up. The change sets are there apps, so we hope to see you there in the next lesson when we complete this process. Thanks so much. 11. Correction of the Sales Order problem: After the confirmation of this first activities. Now, what we want to create this first invoice. But as we checked in the previous lesson, we have a block in the billing plans. So right now we will open the our sales order will double-check even the documents that have been created. Also, we will double check just the billing plant and remove this block. So it's an simple process, but it's important also for us to know that we can have some complications along the way, some problems along the way, especially if we don't have enough recessions and the correct permissions and other decisions for running the process. So this is also important. This is something that only specific users can actually complete. So well for these server, for us, in our present a scenario, we have the actually we have the sep all. So we have pretty much a full Lexis. But again, in a real-world scenario, we will have to double-check if for example, we can run the change sales or their fury up and just for this particular process, remove the block so well, right now, here we have it, change sales order. Let's click on it. And of course we have to just enter our sales order. So two, phi one, and continue. Now, urea will come at the bottom, just come back with this message that we should consider this subsequent documents. And if we have no idea what documents have been assigned, if we just want to double-check, we can come all the way to the top here and click the display document flow. So well, the idea here is to check that we have the dumping request, of course, and then we have the actual down-payment. So if you remember, we even have the correct documents, everything has been linked to the sales orders. So that is always the best thing about the main document that the sales order that we can always come back to it. Just have a reference to it and check them their subsequent documents that have been created. But right now, we just want to double-check the building plan as well. So let's double-click the item, just the first item, both the first and only item for these sales order. And we can just come directly to the regular here to the billing plan. And we have this first activity, the assembly. It's worth 4 thousand Euros. And what we want is just to remove the block. So it's as simple as this. Just come here, delete this block, and then of course, we have to save this. So let's just go back to the main screen. Click Save. And then they will just come back with this message just saying that the standard order has been saved correctly. So with this, we can finish the app. And actually we finish the lesson thinking you all. 12. Create the invoice and assign the Down Payment at the same time: In the previous lesson, we remove the building block. And now we just want to double-check the consequences running the billing process. But what's important is that we will just double-check if the image is created, but also if the damping is correctly assigned to this invoice. So this is going to be really interesting, just to notice, right now, we will jump into sales for this. Thank you. We have they create billing documents. Fear. Yep. So let's start that one. Will have the sales order correctly set up as the document as the reference documents. So let's continue the process that's presented. And here we have the important thing that is different from other times we have been running the bidding process because it's not only that the app is finding within the building plan that a an invoice should be created. These very app is also checking the account for the customer. He has found out that we have a down payment already created. So it's going to run a damping down payment settlement. As soon as we click save at the bottom right corner, we have the assembly activity a completed, so it's the 4 thousand Euros. And again, the app has also discovered these down payment for €1 thousand and it will actually assign, again the down payment to the image. So let's have a look at the consequences. But of course, for that we have to press save at the bottom, at the bottom right corner. So now we have the success message at the bottom. The document has been saved correctly. And well, of course we want to explore this further. So let's come all the way to the top billing documents display. That is the faulting the last document we created. So let's continue. And again, this is just a summary. The important thing also we have now a full document also for logistics. But then again, let's double-check the consequences for accounting. We will actually have these pop-up that we didn't have previously with some other processes because multiple documents were created. Let's have a look first at the accounting document. Can just double-click. And as you can see, we have the actual invoice for the 4 thousand Euros, but at the same time, we have the assignment of the down payment and of course the tax. But this is just the first important document. Again, this is the example at the top-left, the document number for this invoice and just the postings to the align items to the customer. And we will actually check this a bit later, just in a bit more, just more detail. But let's have a look. If we go back, we can just double-check the controlling document as well. This is relevant for controlling because at the end of the day, you have to remember that controlling. Most of the times, we think of controlling just as something has to do with costs. But truth be told, we also have our PhDs, which just means their profitability segments. And these €4 thousand has been assigned as domestic revenue for products and services. So the profitability segment was 21835. Okay. So that is correct for controlling. Let's go back. We went to exit the list. Then finally check also the actual profitability analysis posting. So we will discover the characteristics that were used to create these posting to the permittivity segment. So for example, the costumer, the actual product or service, which is the installation service, the company code, the plant, everything is currently shown here in the characteristics. And then if we move on to the value fields, will look, have a 4 thousand revenue posting here, and we'll just one hour of the assembly service. So, well, the theory app has created everything exactly as we need. So that just means we can go back, close even these pop up and finish. Now that we have the full documents, later on, we will check a bit more of the consequences of the process. But right now, we can finish the lesson. Thanking you all. 13. Update to the Customer account: In the previous lesson, we successfully completed the billing process and now we just want to double-check the consequences using the managed customer line items within Financials. So the most important thing actually, we'll just have a look if the downpayment is correctly assigned and just the balance that the customer has to pay. So what we know about these fury up, Let's complete the ID for the customer and then for the company codes. Now, if we use this parameter values, it's okay because the down payment at the end of day is not enough to clear the invoice. It is still an open invoice and it's a normal item. Just the image is a normal item so we can click GO. But if we ask the query, the database via the app to query the database with these parameter values, then nothing is found. Because, well, if you remember just the billing date was in the feature was pretty much in July. So we will modify the open-air. Actually, we'll select pretty much the last day of a July and we can go for again, and here we have it. The important thing, of course, is that we have the invoice. This is 4,400, but also we have the downpayment correctly assigned. That's also the reason we have the balance only for €3,300. So well, this is interesting. We have everything set up in the same document. So that is a reason in the previous lesson, we only had one document with so many around six line items because everything was posted only using one document. But that is exactly what we expect. That is exactly correct. And again, at the end of the day, the balance is correct. This is what we need to have the customer transfer back to us just to pay later on. So that's fine. Let's equate the fury of chicken this. And with this, we, of course, we finish the lesson. Thank you so much. 14. Update to the Financial Statements: In previous lessons, we successfully completed the building process and we also assign the down payment to the invoice. But now we just want to double-check the consequences to the financial statements. And we will pay special attention to focus will be on the actual account that was posted to the reconstruction account because this invoice at the end of the day is a normal item. And because of that, it should be the value should be showing up in the major condition account, which if you remember, has an ID of one-to-one, five zeros. And then we will also check about what's happening with the down payment. We'll have a look. It just using the balance sheet income statement app to understand what happened with that. But as a as a down payment now that has been assigned. So here we have the app. Well, let's just set up the ID for the company code and the ID for the statement version. And of course, we will switch right now to a July just to currently show that the values, so we have everything correctly set up. We can click Go. And if reopen assets, current assets, and our receivables here we have accounts receivable and everything that is less than one year with maturity less than one year. If we open the full detail here, we will have 4,400. Because remember, the webinar has been assigned to this variable just to them. Do they account, so the accounts receivable. So that just means we have a amount for €3,300. Now, if we explore this further, we will find out just what documents are being considered or maybe what document if it's only one, but what items of the document have been posted here. But what's also important for us to notice is that we have nothing else as down payments. We at least we have maybe just the taxes here at the bottom. We don't have anything else, of course, he, like in the capital and reserves. There is nothing else about the down payment because again, the down payment has been correctly like reclassified to this account. So there is nothing with that account anymore. That's the reason it's not showing up in the financial statements because again, they amount which was 1100, has been reclassified to the one-to-one five times zeros account. How can we double-check that? We just don't click the balance here for 3,300. And we will go for the line items. We want to double-check the line items for these accounts. So if we open the full path, as you can see, well, we will have these values, age in which we have the 4,400. This is the invoice. But again, what has been actually like reclassified is the 1100s because it's no longer a down payment, has been correctly posted to the trade receivables domestic account. But of course, this one is reducing the balance of the account. And that's the reason we have only €3,300 as the balance for the accounts receivable. So well, everything is actually correct. Everything is exactly as we expected, and that just means we can finish the app and finish for today. Just a quick reminder, please write a use. Our health SAP experts at gmail.com. Help that SAP experts at gmail.com, we are more than pleased to help you with any problem that you might have in any doubt. We are there immediately for you, so thanks so much. And we'll see you in the next. 15. Remove the billing block for the last items in the Billing Plan: Now we want to use this opportunity to remove the block for the items, remaining items in the billing plan. And also use the lesson to show the documents that have been created within the process. So let's use sales. Here we have the sales order fury up. So well, we just have to double-check that the sales order is correctly the fault, which it is. So we can just continue. Um, well, as we were saying, the first thing is just to listen to these warnings that we have at the bottom, this information message, actually, which is just to consider the subsequent documents. So let's click on display document flow. And as you can see, we have everything that we previously had, the down payment, then ping request, then we have the invoice. And finally, we have the a down payment applied to the inputs. So it just, they, they are not clear yet. We haven't cleared because we haven't received the full payment from the customer. But what's important is that it has already been correctly posted in the system. So we can just later, when we actually get the money, we can use them to clear just with the incoming pavement and the system will not show any error messages that we're missing money or something because their down payment, it will be considered so well, let's double-click the item. Because again, we also want to use this chance to modify the billing plan. And well, actually, as you can see, both of the bulge as the previous two items are now complete, we can even modify anything about them. They have been built, but let's remove the building block for the operation. This is the last one to deliver the service. And the closing invoice that actually has no monetary value. But just to close the process, so important the dates, of course. Right now, we will save the change. Let's just come back here, save it. And with this, we finish the lesson, of course, hoping that you can join in the next one in which we will continue the process. So thanks so much. 16. Billing the last items in the Billing Plan using SAP Fiori: We removed the block in the previous lesson. Now, let's run the billing process again. Let's have a look at the documents that the process will create. An actually, I see that in plural documents because it's, of course, it will create more than one. So let's have a look here at the create billing documents. Of course, we know that we have to double-check the sales order, which is correct. And we can just proceed, presenter. And that's it. We'll have the two documents. Even for logistics, we have the to the closing images for €0 and the final step is for the €6 thousand. So yes, we want both of them, both of them to be green right now. So we will select both lines and then just click save at the bottom right corner. Okay. The document has been created actually two documents. Let's have a look at them. Remember, we can use more the billing document and display, but they will default the last one. So let's click Continue. And this is just the inverse, just the closing invoice for the installation service. So again, 0, monetary value here is €0. So that's fine. Let's go back and let's let's just ask for the previous document. So the 1139 multiple zeros, 113. So the idea now is just to analyze, this is just the inverse, of course, for €6 thousand will have them a date for the service renders. So it's August, so we're assuming of course, that we are in that month right now. But it's just for the demo purpose. Let's have a look at the accounting are actually for this to work. The accounting period has to be open. So in this server, we have that open. But in a real-world scenario, most of the times that has to be close, but well, Let's double-click accounting to check these accounting documents so we know we have the account receivable. Then posting to the revenues account is the revenues from domestic sales and the output texts. Then again, this is just like a normal item, is not especially general ledger item or something. So we can use the general ledger view just to confirm that the recondition account that has been used as the one-to-one five times 0, which is which is correct. Actually. That is fine. So everything is correct. But they invoice even with the accounting for the rainbows, but we can just double-check the controlling document. If you remember this, probably. I mean, it has to be posted to a PSG to a profitability segment segment, which is the 21837. And again, just a posting for €6 thousand, similar to what we had previously, but the previous document was for 4 thousand, these invoices for 6 thousand. So we have like this. Then if we go back, yes, we want to exit the list. We can just double-check the profitability analysis document. So again, the characteristic values that were used to correctly set up the profitability segment are the same as before. So here we have the same customer, of course, same company codes in plants and everything is pretty much the same. And if we check the value fields there, The amount is just the thing that is different. If we compare this to the previous time, we discover these are posting to the segment because there's the previous time it was 4 thousand. Now of course we have it as 6 thousand. So yeah, everything is correct. We can then just quit the Fourier up. Now that we have all the documents correctly set up, correctly created. And with this, we finish the lesson thinking you all. 17. Display the new invoice using Fiori: Perfect. So now we have a new financial document and we just want to double-check the consequence in using the managed customer line items for urea is so we know about this process, we have to jump into financials. And here we have the managed customer line items for Europe. The most important thing is that we will set the ID for the costumer, the ID for the company code. But the date, we will select the correct date, which, if you remember. But according to this scenario, we want to use modify this for the last day of August. So again, this is possible just for our servers pretty much well in the real world, we wouldn't be running. The common thing is not to run a steps like this, like into the future. But right now we can do it. So the last day of August, and we will just go for the normal items. So if we click Go, because you can see we have the original limbo is 4,400. The one for the down payment for reducing the account for 1100 and the invoice now the new invoice, 46,600. So again, what is important is the downpayment is considered here. So later, when we receive the payment, we only need to receive 9,900 from the customer. And let's assume we actually receive the full amount. Then what's also important is that we will post that into the system, of course. And when we can confirm with the bank and the bank statement, for example, the electronic bank statement. The system can actually clear without any problem because the downpayment is also considered automatically, so well, either if we do it manually or if we do it with the programs, the SAP system will have no problem gluing these when we receive the €9,900. So that is coming next. So definitely we hope to have you there. Thanks so much. 18. Post incoming payment considering the Customer Down Payment: We have posted all the invoices according to the willing plan. And actually we have sent the documents to the customer. While this customer is just customer that as soon as they receive an invoice they pay. So we'll just show the process right now. We will use a theory right in here in financials that we can use just to post these incoming payments. But the important thing is we will double check, triple check if the down payment is considered correctly and if we can just posts so unclear, they open invoice. So for this, we have our posting coming pavements, fury up. Let's use that one. Amble. The first thing we have to set up the IV for the company code. Then let's just double-check the posting date, which is correct. And we'll use the same date for both the journal entry date and the validate. Okay. Now, for the bank section, we will use the ID For the general ledger account that we use to map our bank, our main bank account. For these scenarios, if you remember, what the customer has, what they need to pay to transfer the money. It's a 9,900, which we have it right here, actually euros. And after we have set that up, actually that is what the customer transfer. So let's find out if they're a value that €9,900 that we have now in our bank account can be used to actually clear the open invoices because we have multiple invoices. So for this, we have to click proposed items. And as you can see at the bottom left, we have all the open items. We have them both invoices and we have the a down payment. And what is really interesting here is that if we click either the invoice or the down payment, the system will automatically select both items. So we only have to click one of the items. The two options here of the two items that we have linked in the past, of course, because if we click the 146,600, the down payment will not be selected. This is just because if you remember, the DOM pavement has been assigned to the invoice for 4,400, but that's the point. If we choose these line items, the invoice for 4,400 or the down payment, it doesn't really matter because both items will be automatically selected and will be considered as items to be clear. So right now we have a balance of 9,900. Let's click to test all of these. Let's click the down payment. As I have been saying about the both items will be automatically selected. And well, of course now we still have a balance, but the balance is only for 6,600 Euros. So that is of course, the late, the last invoice. Let's select that one. And as you can see now, the balance goes to 0. So that just means we can actually proceed and posts. Just to be clear, Let's go full screen here in the section. The main section items to be clear. And yes, we have we're considering the invoice for 4,400 plus the down payment. So we have a value here of 3,300 and they're also considering the invoice for six times 6,600 and the customer actually paid completely paid everything. So we can just proceed and post at the bottom right corner. Let's see if we receive just the message with the document now that we have created this and it was successfully posted. So let's display this one is a simple document just just posting to the bank account and that is the debit, as you can see here. And the credit to the receivables is domestic. So this is important at the end of the day, it's a customer payment, but at the end of the album, this is a document that actually clears everything. So let's pay attention here to the journal entry number, just the number because we will have a consequence. Then we check the clearing. All the items will be clear using these journal entry as the clearing documents. So well, after we have seen this, we can just quit the app. No, we don't want to pose the new payment. So we can just create the theory up. And with this, we finish for today, but we definitely hope to see you in the next lesson. Thank you so much. 19. Check the payment consequence in the Customer Account: The customer transferred the €9,900 and we actually have already posted these incoming payments. So now we just want to double-check the consequence using for the a managed customer line items fury up. So let's switch to the corresponding group of apps. And here we have it. Pretty much. We are familiar with the press and we know probably what's going to happen. Just, the system will just show all the open items now clear. So actually they are no longer there. We don't have them open anymore. They are now cleared. But let's just double check if all the amounts are a match, if everything is correct and if the down payment has been correctly cleared as well. So right now we'll select all items, but we have to be careful because if we query the database with these parameters, only one item will show up, which is the payment. This is just because of the date range. So let's modify that they drink. We want these well, not from the start of December 2021. No, we want to go forward, let's say to the first day of the current period. Okay. And we want then just go forward the last day of August. So that will be the date range for the query. Let's click Go. And all the changes immediately felt, we have the all the items the renal three items via invoices, the 146,600, the one for 4,400, and the down payment for 1100. But now we also have the d set, this document which is the final payment for the 9,900. And of course, that results in a balance of 0. We don't have nothing to do with these are overdue with this customer anymore. And if we scroll all the way to the right-hand side, you can check the clearing entry column. And as you can see, for all the line items, the payment document has been set up as the clearing a entry, so everything is correct. Now with account for the customer, that just means we can create this fury up. And with this, we finish the lesson thinking you all. 20. Using the Display Document Flow Fiori app to check the history: Perfect, So now we just want to close the cycle using a theory that actually will just grant is a graphic depiction of all the documents created for the process, not only the logistic documents, but also the financial documents. Everything will be considered here. And for this, we have to use the search box here at the top. We will use a will just flow. Because actually the app that we want is the display document flow. So let's just click that one. And as always with this theory apps, especially the ones that are like recent view reps, they have these minimalistic feeling to them, just as simple as possible. And we only have one field, that document number field. So let's enter the ID for our standard order 351 actually will automatically complete the zeros there. And we can click Go. And we'll, as I was saying, this is like a fool, a graphic depiction of all the documents. Starting point is the initial thing here of course is the standard order. Actually everything is having a reference to the standard order table. Then we have the first document that was created with the billing processes. So the down payment requests. Then if we scroll down, we have the first invoice and the one for 4 thousand Euros, and then the one for €6 thousand. Well, if you remember ingredient text, this one is 4,400 and the next one is 6,600. Then the final image just for €0, just a closing invoice. Have a look that even using this view, we have like the summary of the full document. So that just means we have the two party, they have the billing date, we have the currency, and we even have the chance to explore further the documents. But if we go all the way down, then we get to the GL document flow here. And as you can see, these are just the documents that have been posted for financial accounting. The first one is just the the invoice. The one the first image, the one for, for a thousand. Then we have the second invoice, the one for 6 thousand. And finally, we have the payment, as you can see, these these set a customer payment. Well, that is just the journal entry type or document type as we also call this. So we can actually jump from this view to any document. We just have to click the details with regular document. Then we click the details. We're going to ask for the manage your journal entries. At the end of the day. What is shown is the actual document, but this is great because well, this is of course, the payment, if you remember the the the full payment that we received for the 9,900 posing as a debit to the a bank account and a credit to the residuals, domestic clearing them. They account for the eventual SMEs. Actually, that is a reason we will not show the consequences of the financial statements because right now we have nothing left as an account receivable. The full amount that has been cleared, and we have nothing for down payments because well, the down payment was even tier previously. So it makes not much of a point to show them. So we prefer actually to close the cycle using these display document flow theory, which again is great. It's really graphic nature. We know that with the classic graphic user interface was pretty much impossible to accomplish something like this. But with theory apps, actually it's simple just to achieve something like this. And the great thing here is that it's of course, a default app that we can just use right out of the box. So after we have seen this, let's finish the lesson, thinking you all as always, and invited you to keep learning with all of our trainings.