Master Data in SAP MM | Introduction and Key Concepts — Transcript
Full transcript
- 0:00Hey everyone, welcome back to my
- 0:01channel. So today we are starting a
- 0:03brand new series on master data in
- 0:05SAPMM. As you know, master data plays a
- 0:08very crucial role in materials
- 0:09management and having a strong
- 0:10understanding of how to maintain it is
- 0:13necessary whether you're working as an
- 0:14end user or as a MM consultant.
- 0:18Master data is the building block of any
- 0:20SAP module and SAP MM is no exception.
- 0:24Without accurate and well-maintained
- 0:26master data, the entire procurement and
- 0:28inventory process can face challenges.
- 0:31That's why its knowledge is very
- 0:33important. This series will be your
- 0:35one-step guide to learning everything
- 0:37about master data in SAPMM. In today's
- 0:40video, we'll first talk about why master
- 0:42data is required, what all master data
- 0:45objects exist in SAPMM, and the
- 0:47significance of each of them. From here
- 0:49on in the upcoming videos of this
- 0:51series, we'll dive into each master data
- 0:53in detail covering both the end user
- 0:56perspective and the functional
- 0:57configuration side. You'll not only
- 0:59learn how to work with master data but
- 1:02also you will learn how to set it up in
- 1:04the system. So let's get started with
- 1:06today's topic that is introduction to
- 1:08master data in SAPML. So to learn about
- 1:11the master data first we need to ask
- 1:13this question that why master data is at
- 1:15all required in SAP. So to understand
- 1:17this, let's take an example. Let's say
- 1:20that your organization requires some
- 1:22laptops. So what you have to do? You
- 1:24have to basically place purchase order
- 1:27for this laptop on a particular vendor.
- 1:30So what this purchase order will
- 1:31contain? This purchase order will
- 1:33basically contain three sections. One
- 1:35will be the vendor information, then the
- 1:38material information and the purchase
- 1:40order information. The vendor
- 1:42information will basically contain the
- 1:44information about the vendor. that is
- 1:46what is the name of the vendor, what is
- 1:48the address of the vendor, what are the
- 1:50payment terms and other details. The
- 1:53material information will contain the
- 1:55details of the material that is what
- 1:56material you are purchasing and what all
- 1:59specifications are there for that
- 2:00material. That is what is the screen
- 2:02size, the RAM, hard disk capacity,
- 2:05processor, accessories, etc. These
- 2:07informations also you will have to enter
- 2:09in your purchase order. And then finally
- 2:12you will enter the purchase order
- 2:13information that is what is the unit
- 2:15price, how much quantity you are
- 2:17purchasing and what all other terms and
- 2:19conditions are there for that purchase
- 2:21order. So you see you have to enter all
- 2:24this information in your purchase order
- 2:27send it to your vendor based on these
- 2:29informations only vendor will supply you
- 2:31the material that is laptop in this
- 2:33case. Now let's say that you created a
- 2:36purchase order by entering everything
- 2:38manually in the PO. That is you enter
- 2:40the vendor information manually. You
- 2:42enter the material information also
- 2:44manually and you enter the PO
- 2:46information also. And after you prepared
- 2:49this purchase order, you sent it to the
- 2:51vendor and then vendor supplied you the
- 2:53material and that cycle was completed.
- 2:56Now let's imagine that another plant of
- 2:58your organization requires the same
- 3:01laptops. So what they have to do again
- 3:03they have to create a purchase order and
- 3:06again this purchase order will have to
- 3:08contain all that information and let's
- 3:10say that this time the plant is
- 3:12purchasing from an another vendor. You
- 3:15can see here this time the vendor is
- 3:17different. So the vendor address will
- 3:18also be different. The payment terms
- 3:20might be different and other details of
- 3:22the vendor will be different. The
- 3:24material is same. You have same laptop.
- 3:26You have same screen size, RAM, hard
- 3:28disk capacity, processor. But you see
- 3:31this time this person forgot to enter
- 3:34the accessories in this purchase order.
- 3:36He was preparing the purchase order. He
- 3:38was entering all the information
- 3:39manually. While entering the
- 3:41specifications of the laptop, he forgot
- 3:43to mention that the accessories are also
- 3:46required against this laptop and he
- 3:48placed the order with these PO
- 3:50informations. Now you see in both these
- 3:52purchase order you had to enter similar
- 3:55informations. You had to enter
- 3:56information about the vendor, about the
- 3:59material and about the purchase order,
- 4:01unit price, quantity and terms and
- 4:03conditions. And every time when a user
- 4:06enters these information, it is possible
- 4:08that some information is missed out by
- 4:10the person. And it is also possible that
- 4:13the same material is purchased at a
- 4:15higher price. Okay? Because you see when
- 4:18this person was creating this purchase
- 4:20order, this person did not have any
- 4:22option to search for the previous
- 4:24purchase order because this was also
- 4:26created manually. There was no entity in
- 4:28the system through which this purchase
- 4:30order could be searched. So this person
- 4:32asked the vendor to supply the material
- 4:34and whatever price was quoted by the
- 4:36vendor, this person had to enter in the
- 4:38purchase order. So you see you have
- 4:40these two purchase orders and basically
- 4:42we have these four limitations when we
- 4:45are dealing with these informations and
- 4:48we are entering these informations
- 4:50manually in the system. What are these
- 4:52limitations? First is you have lack of
- 4:54standardization that is you do not have
- 4:57standard specifications entered in your
- 5:00system. So every time a person is
- 5:02entering the information he has to make
- 5:04sure that he is entering the information
- 5:07correctly. Whatever specification the
- 5:10person is entering, he has to enter the
- 5:12standard information and it is totally
- 5:15up to the end user that what all
- 5:17informations are being entered. So you
- 5:20do not have standard data available in
- 5:22your system in this particular case.
- 5:25Then second thing is you have repetition
- 5:27of job. You can see every time the user
- 5:29has to enter all these datas manually.
- 5:32So earlier user entered these data about
- 5:35the laptop. Again user has to enter all
- 5:37this data. The third problem is that you
- 5:40have a difficulty to check the
- 5:42historical data. As I told you because
- 5:45you do not have any entity to search
- 5:47this purchase order. So this person
- 5:49whenever he's creating a purchase order
- 5:51for laptop, he will not be able to find
- 5:54the details of this purchase order. He
- 5:57will have to go through all the purchase
- 5:59orders which have been placed by your
- 6:00organization and then find out wherever
- 6:03laptop is mentioned what all screen size
- 6:06RAM hard disk capacity processor etc is
- 6:09mentioned and from there he'll have to
- 6:11see what all prices were there in the
- 6:13previous purchase orders. So the third
- 6:15problem is difficult to check the
- 6:17historical data and the last problem is
- 6:19inability to maintain the inventory. If
- 6:22you do not have any entity which stores
- 6:24the information of the material then you
- 6:27cannot have inventory in your plant
- 6:30because the inventory can only be shown
- 6:32against an entity which will contain the
- 6:34information of that material. So unless
- 6:37and until you have that entity which
- 6:39contains the information of the material
- 6:41you cannot maintain inventory. So you
- 6:43can see these are the four problems
- 6:46which you will face if you do not have
- 6:49any entity which stores the information
- 6:51of your material or your vendor. So what
- 6:54can be done to deal with these issues?
- 6:56So in SAP you have something called as
- 6:59master data. Okay. So let's understand
- 7:02the concept of master data and the
- 7:04transaction data. So whenever you create
- 7:07any transactional document in SAP, it
- 7:11will always contain a combination of two
- 7:14things. One is the master data and
- 7:16another one is the transaction data.
- 7:19Okay, in this case you see you will have
- 7:22to create certain entities which will
- 7:25store the information of the vendor and
- 7:27the material. And to achieve this in SAP
- 7:30what you'll have to create is master
- 7:33data for both these entities. That is
- 7:36for a vendor and a material you will
- 7:38have to create master data which will
- 7:41basically act as a container which will
- 7:44contain these informations. Okay. So
- 7:47whenever you want to enter the data you
- 7:50only have to enter the master of that
- 7:52particular material or vendor. system
- 7:55will take everything which is saved in
- 7:57the master data and will populate in
- 8:00your particular purchasing document that
- 8:02is purchase order in the current case.
- 8:05Okay. So you can see a master data is
- 8:07basically the building block in your
- 8:09system which you can use to build your
- 8:12transactions. Okay. So whenever you have
- 8:15to create a purchase order, you will
- 8:17have to use these master data and then
- 8:19it will solve all your issues which we
- 8:21discussed earlier. That is you will have
- 8:23standard data in your system. You will
- 8:26not be supposed to repeat your
- 8:28activities. You simply have to enter
- 8:30that master data and every information
- 8:32will be saved. And most importantly, you
- 8:34will be able to search the transactional
- 8:37documents which were posted earlier.
- 8:40That is if you have a material master or
- 8:42a vendor master, you can search for
- 8:45previous purchase orders which have been
- 8:48placed against that material or that
- 8:51vendor. Okay. So that is the most
- 8:53important thing that you get through
- 8:55this master data and that is indexing.
- 8:57That is you can search for the documents
- 8:59which have been created in the system
- 9:01against that master data. And finally in
- 9:04case of material you can only maintain
- 9:07inventory if you have material master
- 9:10available in the system without material
- 9:12master inventory management is not
- 9:15possible. So you can see these two
- 9:17information that is the vendor
- 9:19information and the material information
- 9:21is stored in something called as master
- 9:24data and this information that is the PO
- 9:27information that is the unit price
- 9:29quantity terms and condition this is
- 9:31called transaction data. Okay. So this
- 9:35data will change in every document.
- 9:38Whenever you create a purchase order,
- 9:41you may have different transaction data
- 9:44but you will have the same master data
- 9:46in all those purchase orders. So master
- 9:49data is something which is static that
- 9:51is which once created will not be
- 9:53changed or will rarely be changed and
- 9:56transaction data is something which will
- 9:58depend on each transaction document. So
- 10:01whenever you create a purchase order,
- 10:03you will enter a vendor master, you will
- 10:05enter a material master and then you
- 10:08will enter your transaction data. And
- 10:11these two combined together will
- 10:12basically create your purchase order.
- 10:15Okay. So I hope that you've understood
- 10:17this concept of master data and
- 10:19transaction data. A master data will
- 10:21rarely be changed. You will create this
- 10:23once and then you will keep on using it
- 10:26in every purchasing document.
- 10:28Transaction data is something which will
- 10:29depend on every case that is whatever
- 10:32purchasing document you're creating it
- 10:34will have its own transaction data and
- 10:37both these data are not created through
- 10:39the configuration route an end user only
- 10:41will be creating a master data and a
- 10:43transaction data but in the case of
- 10:46master data that end user will be
- 10:48basically from the core group that is in
- 10:51your organization certain people will be
- 10:54earmarked for maintaining the master
- 10:56data they will be responsible for
- 10:58maintaining all kind of master datas in
- 11:01your organization and they will only
- 11:03maintain the master data. Transaction
- 11:06data will be done by each user who is
- 11:08basically working in SAP ML. Okay. So
- 11:11any person who is creating the purchase
- 11:13order may not create the master data. He
- 11:16will only enter the master data in the
- 11:18purchase order and then enter other
- 11:20informations like quantity, unit price,
- 11:22terms and condition. But you will have
- 11:25certain core group members in your
- 11:27organization which will basically work
- 11:29as master data maintenance people. They
- 11:33will basically be responsible for
- 11:35maintaining the master data. But you
- 11:37have to understand that both these data
- 11:38master data and transaction data are
- 11:41done on application side that is these
- 11:43are not done through the configuration
- 11:45route. But the people who will be
- 11:46maintaining this master data and
- 11:48transaction data will be different.
- 11:50Okay. Master data will be maintained by
- 11:52core group people. transaction data will
- 11:54be entered by every MM user as
- 11:56applicable. Okay. So you can see here
- 11:58you have these two masters mentioned
- 12:00here. The vendor information we'll save
- 12:02in the vendor master and the material
- 12:05information we will save in the material
- 12:07master. And basically we'll be assigning
- 12:10something called as codes to these
- 12:12informations. That is you will have a
- 12:14vendor code and a material code
- 12:16available with you. You only have to
- 12:19enter these codes in your purchase
- 12:21order. Every information of these
- 12:23entities will be autopop populated or
- 12:25will be defaulted from their masters. So
- 12:28if you enter a vendor code in the
- 12:30purchase order, the vendor information
- 12:32will be defaulted in your purchase
- 12:33order. If you enter a material code in
- 12:35your purchase order, the information of
- 12:37the material code will be defaulted in
- 12:39your purchase order. And once you enter
- 12:41these two master data, then you will
- 12:44enter the transaction data that is the
- 12:46quantity, unit price, terms and
- 12:47conditions and other details. and then
- 12:50you will be able to create your purchase
- 12:52order. Okay. So this concept of master
- 12:54data is there in every SAP module. Now
- 12:57let's understand the various type of
- 12:59master data which are available in SAP
- 13:01MM. So as we discussed earlier we have
- 13:04material master and vendor master. Then
- 13:06we have service master as we have
- 13:08discussed in our service procurement
- 13:10video that you can procure services also
- 13:12through SAPMM. And there you can enter
- 13:15your service master that is you will
- 13:17enter the information about the services
- 13:19that are to be performed by the vendor
- 13:21and you will store that information in
- 13:23something called as a service master.
- 13:26Then you have purchasing info record.
- 13:28Now what is a purchasing info record?
- 13:30Basically this is a combination of
- 13:32material master, vendor master and the
- 13:34pricing conditions. that is you will
- 13:37create a master data in SAP telling that
- 13:39this material will be purchased from
- 13:41this vendor at this price. Okay. So
- 13:44basically you will combine material
- 13:46master vendor master and the prices in
- 13:49something called as purchasing info
- 13:51record. Then you have source list.
- 13:53Basically this master data specifies the
- 13:56allowed sources of a material for a
- 13:58certain plant within a predefined
- 14:00period. That is basically you will be
- 14:02maintaining a list of vendors which will
- 14:04be supplying you a particular material
- 14:06and based on that master list you will
- 14:09be preparing your purchase requisition
- 14:11and purchase order. Then you have
- 14:14something called as Kota arrangement.
- 14:16Now this master data type specify the
- 14:18proportion of a material that can be
- 14:20procured from a particular vendor. So
- 14:23here what we'll do we will combine
- 14:25multiple vendors and we will assign
- 14:27quotas for each vendor for supply of a
- 14:29particular material and based on that
- 14:32kota your required quantity will be
- 14:34distributed among multiple vendors.
- 14:37Okay. Then finally you have this
- 14:39condition master. So basically the
- 14:41prices that are quoted by the vendor we
- 14:44can also maintain those prices in a
- 14:46particular master data and that is the
- 14:49condition master. We will discuss this
- 14:51condition master when we discuss the
- 14:53pricing procedure in SAPMM. There we'll
- 14:56see how you can maintain condition
- 14:58records and how you can maintain the
- 15:00master data of your conditions based on
- 15:02multiple factors. Okay. So in SAP MM you
- 15:06have these seven masters that is
- 15:08material master, vendor master, service
- 15:11master, purchasing info record, source
- 15:14list, kota arrangement and condition
- 15:16master. We'll learn about all these
- 15:18master data in our upcoming videos. Now
- 15:20let's understand what is the meaning of
- 15:22organizational elements in master data.
- 15:24Now as we have already seen in the
- 15:26organizational structure in SAP MM video
- 15:29that in SAP MM you have these major five
- 15:32elements in the organizational
- 15:34structure. Now whenever you'll be
- 15:36entering information against any master
- 15:38data in SAP MM you will be entering that
- 15:41information on various levels. That is
- 15:44let's say that some information is
- 15:45applicable to the whole organization
- 15:48then that data you will maintain at the
- 15:50client level then some information will
- 15:53be specific to company code or plant or
- 15:56storage location or purchase
- 15:57organization. So those data you will
- 15:59enter at these specific levels. Let's
- 16:03say that you are maintaining your
- 16:04material master. Then the material
- 16:06specification will be entered at the
- 16:08client level because that material
- 16:10specification will be standard for the
- 16:12whole organization but the purchasing
- 16:14data will be applicable at plant level.
- 16:17Each plant will have its own purchasing
- 16:20conditions like it will have a
- 16:22particular purchasing group or it will
- 16:24have a particular purchasing value keys.
- 16:26So all those informations which are
- 16:28pertaining to the purchasing part will
- 16:31be entered at the plant level. Then
- 16:33every storage location in a particular
- 16:35plant will have its own storage location
- 16:37data. So for storage of that material
- 16:40you will have to maintain data at the
- 16:42storage location. Then if you talk about
- 16:45the vendor then the vendor's information
- 16:47that is the vendor name, address and
- 16:50other contact details you will maintain
- 16:52at the client level. But for posting
- 16:54financial documents against that vendor
- 16:56you will have to maintain data at the
- 16:58company code level. And to prepare
- 17:01purchase order for that particular
- 17:02vendor, you will have to enter the
- 17:05purchasing data at the purchasing
- 17:07organization level. So you can see every
- 17:11organization structure element is
- 17:13attached to your master data. Whenever
- 17:16you will be maintaining the master data,
- 17:18system will ask you to enter the
- 17:20corresponding organizational element and
- 17:23then only you'll be able to maintain
- 17:25that data. We'll see all these in
- 17:27details in our upcoming videos. But you
- 17:29have to understand that you have an
- 17:31organization structure in CPMM. And when
- 17:34you maintain your master data, you will
- 17:36have to maintain that master data
- 17:39against each element of that
- 17:41organization structure as applicable for
- 17:44that particular master data. So you can
- 17:46see at client level you maintain data
- 17:49for material and vendor. For company
- 17:52code and purchase organization, you
- 17:54maintain data for any vendor. And for
- 17:57plant and storage location, you maintain
- 17:59data for the material. In case of vendor
- 18:01also, you can maintain data at plant
- 18:03level. We'll discuss when we discuss
- 18:05about the vendor master. But majorly you
- 18:07maintain these master data on these
- 18:10particular levels which are shown on the
- 18:12screen. Okay. So in this way we have
- 18:15understood what is the meaning of master
- 18:16data in SAP MM and why it is required.
- 18:20In our subsequent videos, we'll learn
- 18:22about each of these master data. And in
- 18:25this series, I will cover the detail of
- 18:27every master data from the end user
- 18:29perspective and from the configuration
- 18:31side also. So I hope that you have
- 18:33understood this concept of master data
- 18:35in SAP MM. And I hope that you've liked
- 18:37this video. If you like my videos then
- 18:40please like and subscribe to my channel.
- 18:42Your likes and subscriptions really
- 18:44motivate me to create more content. In
- 18:46our next video, we'll learn about the
- 18:48material master that how you can
- 18:49maintain a material master and what all
- 18:51things you have to consider from an
- 18:53enduser perspective while maintaining
- 18:55the material master. So, see you in the
- 18:57next video. Till then, thank you so much
- 18:59for supporting me. Thanks a lot.
About this transcript
This page contains the full transcript of Master Data in SAP MM | Introduction and Key Concepts by SAP MM Learning Hub, generated from the public captions YouTube serves with the video. The transcript has 3,232 words across 494 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.