Now, we will go through the agenda of this course. In this course we are going to discuss about business partner concept and flow This is very important because you are going to understand how the flow moves and everything. The next is the transaction code for business partner configuration. There are lots of people who might say, okay, you know in s for HANA there is fury type and all those things are you don't have transaction code. That's not true. Sa p cannot live without transaction code and most of the people who use sa p also cannot live without transaction code.

Yes, they have given you have a wonderful look and feel through the fury apps. Those are again I'm saying those are for people who spent probably less than 30 minutes in, in SAP system. And that used to be a lot of people because you know, for approval and all those things. People used to just log into SAP, they pay, pay, they have other things to do rather than creating, you know, remembering the transaction codes. But for heavy users who spend more than more than one hour or two hours in s in SCP system, they have their transaction costs at the end of the day each fury app in the backend Khalsa transaction code. The next one is the business partner configuration.

The business partner configuration is similar to vendor and customer setup. So, in some cases, what you see, you can suppress some field you can make it mandatory, you can make it optional, you can make a display, the same thing that was there in vendor and customers is there in business partner, nothing is changing, but these there are some new transaction code and there's some new way to do configuration. And then we are also going to touch reporting related to business parts. Okay, so there's some out of the box reports that will help you to see all the business plans Partners how you can get rid of business partners you when we say what do we say by getting rid of business partners, hey this is as for HANA system, you just cannot load cartridge, okay? So if you are loading garbage and lots of people will lose load because you're moving from one or three system to s four and in r three, you do merge from different different software's different acquisition and you had garbage this of garbage in, garbage out, well, he has 400 you have a tool to take the garbage out after you have taken the current regime.

So, there are some features where, which we will discuss in detail some of the features are like, you can run a report where it will tell which are the business partners you have loaded in the system that doesn't have an activity for those previous three years. We can easily get rid of those. So you know And that by getting rid of those and getting rid of those means archiving those, your system will be running faster. The whole purpose of s for HANA is to run faster. And in order to make it run faster, it's just like a car. In order to make the car run faster or run well you have to put the oil change you need to change tires.

So doing oil change and changing tires is removing garbage from the system. So first you have to identify the garbage and then we are not really removing it. We are archiving it. We are putting it in the coast.