YouTube2Text

Master Data in SAP MM | Introduction and Key Concepts — Transcript

by SAP MM Learning Hub · 3,232 words · 494 segments · language en · Watch on YouTube

Full transcript

  1. 0:00Hey everyone, welcome back to my
  2. 0:01channel. So today we are starting a
  3. 0:03brand new series on master data in
  4. 0:05SAPMM. As you know, master data plays a
  5. 0:08very crucial role in materials
  6. 0:09management and having a strong
  7. 0:10understanding of how to maintain it is
  8. 0:13necessary whether you're working as an
  9. 0:14end user or as a MM consultant.
  10. 0:18Master data is the building block of any
  11. 0:20SAP module and SAP MM is no exception.
  12. 0:24Without accurate and well-maintained
  13. 0:26master data, the entire procurement and
  14. 0:28inventory process can face challenges.
  15. 0:31That's why its knowledge is very
  16. 0:33important. This series will be your
  17. 0:35one-step guide to learning everything
  18. 0:37about master data in SAPMM. In today's
  19. 0:40video, we'll first talk about why master
  20. 0:42data is required, what all master data
  21. 0:45objects exist in SAPMM, and the
  22. 0:47significance of each of them. From here
  23. 0:49on in the upcoming videos of this
  24. 0:51series, we'll dive into each master data
  25. 0:53in detail covering both the end user
  26. 0:56perspective and the functional
  27. 0:57configuration side. You'll not only
  28. 0:59learn how to work with master data but
  29. 1:02also you will learn how to set it up in
  30. 1:04the system. So let's get started with
  31. 1:06today's topic that is introduction to
  32. 1:08master data in SAPML. So to learn about
  33. 1:11the master data first we need to ask
  34. 1:13this question that why master data is at
  35. 1:15all required in SAP. So to understand
  36. 1:17this, let's take an example. Let's say
  37. 1:20that your organization requires some
  38. 1:22laptops. So what you have to do? You
  39. 1:24have to basically place purchase order
  40. 1:27for this laptop on a particular vendor.
  41. 1:30So what this purchase order will
  42. 1:31contain? This purchase order will
  43. 1:33basically contain three sections. One
  44. 1:35will be the vendor information, then the
  45. 1:38material information and the purchase
  46. 1:40order information. The vendor
  47. 1:42information will basically contain the
  48. 1:44information about the vendor. that is
  49. 1:46what is the name of the vendor, what is
  50. 1:48the address of the vendor, what are the
  51. 1:50payment terms and other details. The
  52. 1:53material information will contain the
  53. 1:55details of the material that is what
  54. 1:56material you are purchasing and what all
  55. 1:59specifications are there for that
  56. 2:00material. That is what is the screen
  57. 2:02size, the RAM, hard disk capacity,
  58. 2:05processor, accessories, etc. These
  59. 2:07informations also you will have to enter
  60. 2:09in your purchase order. And then finally
  61. 2:12you will enter the purchase order
  62. 2:13information that is what is the unit
  63. 2:15price, how much quantity you are
  64. 2:17purchasing and what all other terms and
  65. 2:19conditions are there for that purchase
  66. 2:21order. So you see you have to enter all
  67. 2:24this information in your purchase order
  68. 2:27send it to your vendor based on these
  69. 2:29informations only vendor will supply you
  70. 2:31the material that is laptop in this
  71. 2:33case. Now let's say that you created a
  72. 2:36purchase order by entering everything
  73. 2:38manually in the PO. That is you enter
  74. 2:40the vendor information manually. You
  75. 2:42enter the material information also
  76. 2:44manually and you enter the PO
  77. 2:46information also. And after you prepared
  78. 2:49this purchase order, you sent it to the
  79. 2:51vendor and then vendor supplied you the
  80. 2:53material and that cycle was completed.
  81. 2:56Now let's imagine that another plant of
  82. 2:58your organization requires the same
  83. 3:01laptops. So what they have to do again
  84. 3:03they have to create a purchase order and
  85. 3:06again this purchase order will have to
  86. 3:08contain all that information and let's
  87. 3:10say that this time the plant is
  88. 3:12purchasing from an another vendor. You
  89. 3:15can see here this time the vendor is
  90. 3:17different. So the vendor address will
  91. 3:18also be different. The payment terms
  92. 3:20might be different and other details of
  93. 3:22the vendor will be different. The
  94. 3:24material is same. You have same laptop.
  95. 3:26You have same screen size, RAM, hard
  96. 3:28disk capacity, processor. But you see
  97. 3:31this time this person forgot to enter
  98. 3:34the accessories in this purchase order.
  99. 3:36He was preparing the purchase order. He
  100. 3:38was entering all the information
  101. 3:39manually. While entering the
  102. 3:41specifications of the laptop, he forgot
  103. 3:43to mention that the accessories are also
  104. 3:46required against this laptop and he
  105. 3:48placed the order with these PO
  106. 3:50informations. Now you see in both these
  107. 3:52purchase order you had to enter similar
  108. 3:55informations. You had to enter
  109. 3:56information about the vendor, about the
  110. 3:59material and about the purchase order,
  111. 4:01unit price, quantity and terms and
  112. 4:03conditions. And every time when a user
  113. 4:06enters these information, it is possible
  114. 4:08that some information is missed out by
  115. 4:10the person. And it is also possible that
  116. 4:13the same material is purchased at a
  117. 4:15higher price. Okay? Because you see when
  118. 4:18this person was creating this purchase
  119. 4:20order, this person did not have any
  120. 4:22option to search for the previous
  121. 4:24purchase order because this was also
  122. 4:26created manually. There was no entity in
  123. 4:28the system through which this purchase
  124. 4:30order could be searched. So this person
  125. 4:32asked the vendor to supply the material
  126. 4:34and whatever price was quoted by the
  127. 4:36vendor, this person had to enter in the
  128. 4:38purchase order. So you see you have
  129. 4:40these two purchase orders and basically
  130. 4:42we have these four limitations when we
  131. 4:45are dealing with these informations and
  132. 4:48we are entering these informations
  133. 4:50manually in the system. What are these
  134. 4:52limitations? First is you have lack of
  135. 4:54standardization that is you do not have
  136. 4:57standard specifications entered in your
  137. 5:00system. So every time a person is
  138. 5:02entering the information he has to make
  139. 5:04sure that he is entering the information
  140. 5:07correctly. Whatever specification the
  141. 5:10person is entering, he has to enter the
  142. 5:12standard information and it is totally
  143. 5:15up to the end user that what all
  144. 5:17informations are being entered. So you
  145. 5:20do not have standard data available in
  146. 5:22your system in this particular case.
  147. 5:25Then second thing is you have repetition
  148. 5:27of job. You can see every time the user
  149. 5:29has to enter all these datas manually.
  150. 5:32So earlier user entered these data about
  151. 5:35the laptop. Again user has to enter all
  152. 5:37this data. The third problem is that you
  153. 5:40have a difficulty to check the
  154. 5:42historical data. As I told you because
  155. 5:45you do not have any entity to search
  156. 5:47this purchase order. So this person
  157. 5:49whenever he's creating a purchase order
  158. 5:51for laptop, he will not be able to find
  159. 5:54the details of this purchase order. He
  160. 5:57will have to go through all the purchase
  161. 5:59orders which have been placed by your
  162. 6:00organization and then find out wherever
  163. 6:03laptop is mentioned what all screen size
  164. 6:06RAM hard disk capacity processor etc is
  165. 6:09mentioned and from there he'll have to
  166. 6:11see what all prices were there in the
  167. 6:13previous purchase orders. So the third
  168. 6:15problem is difficult to check the
  169. 6:17historical data and the last problem is
  170. 6:19inability to maintain the inventory. If
  171. 6:22you do not have any entity which stores
  172. 6:24the information of the material then you
  173. 6:27cannot have inventory in your plant
  174. 6:30because the inventory can only be shown
  175. 6:32against an entity which will contain the
  176. 6:34information of that material. So unless
  177. 6:37and until you have that entity which
  178. 6:39contains the information of the material
  179. 6:41you cannot maintain inventory. So you
  180. 6:43can see these are the four problems
  181. 6:46which you will face if you do not have
  182. 6:49any entity which stores the information
  183. 6:51of your material or your vendor. So what
  184. 6:54can be done to deal with these issues?
  185. 6:56So in SAP you have something called as
  186. 6:59master data. Okay. So let's understand
  187. 7:02the concept of master data and the
  188. 7:04transaction data. So whenever you create
  189. 7:07any transactional document in SAP, it
  190. 7:11will always contain a combination of two
  191. 7:14things. One is the master data and
  192. 7:16another one is the transaction data.
  193. 7:19Okay, in this case you see you will have
  194. 7:22to create certain entities which will
  195. 7:25store the information of the vendor and
  196. 7:27the material. And to achieve this in SAP
  197. 7:30what you'll have to create is master
  198. 7:33data for both these entities. That is
  199. 7:36for a vendor and a material you will
  200. 7:38have to create master data which will
  201. 7:41basically act as a container which will
  202. 7:44contain these informations. Okay. So
  203. 7:47whenever you want to enter the data you
  204. 7:50only have to enter the master of that
  205. 7:52particular material or vendor. system
  206. 7:55will take everything which is saved in
  207. 7:57the master data and will populate in
  208. 8:00your particular purchasing document that
  209. 8:02is purchase order in the current case.
  210. 8:05Okay. So you can see a master data is
  211. 8:07basically the building block in your
  212. 8:09system which you can use to build your
  213. 8:12transactions. Okay. So whenever you have
  214. 8:15to create a purchase order, you will
  215. 8:17have to use these master data and then
  216. 8:19it will solve all your issues which we
  217. 8:21discussed earlier. That is you will have
  218. 8:23standard data in your system. You will
  219. 8:26not be supposed to repeat your
  220. 8:28activities. You simply have to enter
  221. 8:30that master data and every information
  222. 8:32will be saved. And most importantly, you
  223. 8:34will be able to search the transactional
  224. 8:37documents which were posted earlier.
  225. 8:40That is if you have a material master or
  226. 8:42a vendor master, you can search for
  227. 8:45previous purchase orders which have been
  228. 8:48placed against that material or that
  229. 8:51vendor. Okay. So that is the most
  230. 8:53important thing that you get through
  231. 8:55this master data and that is indexing.
  232. 8:57That is you can search for the documents
  233. 8:59which have been created in the system
  234. 9:01against that master data. And finally in
  235. 9:04case of material you can only maintain
  236. 9:07inventory if you have material master
  237. 9:10available in the system without material
  238. 9:12master inventory management is not
  239. 9:15possible. So you can see these two
  240. 9:17information that is the vendor
  241. 9:19information and the material information
  242. 9:21is stored in something called as master
  243. 9:24data and this information that is the PO
  244. 9:27information that is the unit price
  245. 9:29quantity terms and condition this is
  246. 9:31called transaction data. Okay. So this
  247. 9:35data will change in every document.
  248. 9:38Whenever you create a purchase order,
  249. 9:41you may have different transaction data
  250. 9:44but you will have the same master data
  251. 9:46in all those purchase orders. So master
  252. 9:49data is something which is static that
  253. 9:51is which once created will not be
  254. 9:53changed or will rarely be changed and
  255. 9:56transaction data is something which will
  256. 9:58depend on each transaction document. So
  257. 10:01whenever you create a purchase order,
  258. 10:03you will enter a vendor master, you will
  259. 10:05enter a material master and then you
  260. 10:08will enter your transaction data. And
  261. 10:11these two combined together will
  262. 10:12basically create your purchase order.
  263. 10:15Okay. So I hope that you've understood
  264. 10:17this concept of master data and
  265. 10:19transaction data. A master data will
  266. 10:21rarely be changed. You will create this
  267. 10:23once and then you will keep on using it
  268. 10:26in every purchasing document.
  269. 10:28Transaction data is something which will
  270. 10:29depend on every case that is whatever
  271. 10:32purchasing document you're creating it
  272. 10:34will have its own transaction data and
  273. 10:37both these data are not created through
  274. 10:39the configuration route an end user only
  275. 10:41will be creating a master data and a
  276. 10:43transaction data but in the case of
  277. 10:46master data that end user will be
  278. 10:48basically from the core group that is in
  279. 10:51your organization certain people will be
  280. 10:54earmarked for maintaining the master
  281. 10:56data they will be responsible for
  282. 10:58maintaining all kind of master datas in
  283. 11:01your organization and they will only
  284. 11:03maintain the master data. Transaction
  285. 11:06data will be done by each user who is
  286. 11:08basically working in SAP ML. Okay. So
  287. 11:11any person who is creating the purchase
  288. 11:13order may not create the master data. He
  289. 11:16will only enter the master data in the
  290. 11:18purchase order and then enter other
  291. 11:20informations like quantity, unit price,
  292. 11:22terms and condition. But you will have
  293. 11:25certain core group members in your
  294. 11:27organization which will basically work
  295. 11:29as master data maintenance people. They
  296. 11:33will basically be responsible for
  297. 11:35maintaining the master data. But you
  298. 11:37have to understand that both these data
  299. 11:38master data and transaction data are
  300. 11:41done on application side that is these
  301. 11:43are not done through the configuration
  302. 11:45route. But the people who will be
  303. 11:46maintaining this master data and
  304. 11:48transaction data will be different.
  305. 11:50Okay. Master data will be maintained by
  306. 11:52core group people. transaction data will
  307. 11:54be entered by every MM user as
  308. 11:56applicable. Okay. So you can see here
  309. 11:58you have these two masters mentioned
  310. 12:00here. The vendor information we'll save
  311. 12:02in the vendor master and the material
  312. 12:05information we will save in the material
  313. 12:07master. And basically we'll be assigning
  314. 12:10something called as codes to these
  315. 12:12informations. That is you will have a
  316. 12:14vendor code and a material code
  317. 12:16available with you. You only have to
  318. 12:19enter these codes in your purchase
  319. 12:21order. Every information of these
  320. 12:23entities will be autopop populated or
  321. 12:25will be defaulted from their masters. So
  322. 12:28if you enter a vendor code in the
  323. 12:30purchase order, the vendor information
  324. 12:32will be defaulted in your purchase
  325. 12:33order. If you enter a material code in
  326. 12:35your purchase order, the information of
  327. 12:37the material code will be defaulted in
  328. 12:39your purchase order. And once you enter
  329. 12:41these two master data, then you will
  330. 12:44enter the transaction data that is the
  331. 12:46quantity, unit price, terms and
  332. 12:47conditions and other details. and then
  333. 12:50you will be able to create your purchase
  334. 12:52order. Okay. So this concept of master
  335. 12:54data is there in every SAP module. Now
  336. 12:57let's understand the various type of
  337. 12:59master data which are available in SAP
  338. 13:01MM. So as we discussed earlier we have
  339. 13:04material master and vendor master. Then
  340. 13:06we have service master as we have
  341. 13:08discussed in our service procurement
  342. 13:10video that you can procure services also
  343. 13:12through SAPMM. And there you can enter
  344. 13:15your service master that is you will
  345. 13:17enter the information about the services
  346. 13:19that are to be performed by the vendor
  347. 13:21and you will store that information in
  348. 13:23something called as a service master.
  349. 13:26Then you have purchasing info record.
  350. 13:28Now what is a purchasing info record?
  351. 13:30Basically this is a combination of
  352. 13:32material master, vendor master and the
  353. 13:34pricing conditions. that is you will
  354. 13:37create a master data in SAP telling that
  355. 13:39this material will be purchased from
  356. 13:41this vendor at this price. Okay. So
  357. 13:44basically you will combine material
  358. 13:46master vendor master and the prices in
  359. 13:49something called as purchasing info
  360. 13:51record. Then you have source list.
  361. 13:53Basically this master data specifies the
  362. 13:56allowed sources of a material for a
  363. 13:58certain plant within a predefined
  364. 14:00period. That is basically you will be
  365. 14:02maintaining a list of vendors which will
  366. 14:04be supplying you a particular material
  367. 14:06and based on that master list you will
  368. 14:09be preparing your purchase requisition
  369. 14:11and purchase order. Then you have
  370. 14:14something called as Kota arrangement.
  371. 14:16Now this master data type specify the
  372. 14:18proportion of a material that can be
  373. 14:20procured from a particular vendor. So
  374. 14:23here what we'll do we will combine
  375. 14:25multiple vendors and we will assign
  376. 14:27quotas for each vendor for supply of a
  377. 14:29particular material and based on that
  378. 14:32kota your required quantity will be
  379. 14:34distributed among multiple vendors.
  380. 14:37Okay. Then finally you have this
  381. 14:39condition master. So basically the
  382. 14:41prices that are quoted by the vendor we
  383. 14:44can also maintain those prices in a
  384. 14:46particular master data and that is the
  385. 14:49condition master. We will discuss this
  386. 14:51condition master when we discuss the
  387. 14:53pricing procedure in SAPMM. There we'll
  388. 14:56see how you can maintain condition
  389. 14:58records and how you can maintain the
  390. 15:00master data of your conditions based on
  391. 15:02multiple factors. Okay. So in SAP MM you
  392. 15:06have these seven masters that is
  393. 15:08material master, vendor master, service
  394. 15:11master, purchasing info record, source
  395. 15:14list, kota arrangement and condition
  396. 15:16master. We'll learn about all these
  397. 15:18master data in our upcoming videos. Now
  398. 15:20let's understand what is the meaning of
  399. 15:22organizational elements in master data.
  400. 15:24Now as we have already seen in the
  401. 15:26organizational structure in SAP MM video
  402. 15:29that in SAP MM you have these major five
  403. 15:32elements in the organizational
  404. 15:34structure. Now whenever you'll be
  405. 15:36entering information against any master
  406. 15:38data in SAP MM you will be entering that
  407. 15:41information on various levels. That is
  408. 15:44let's say that some information is
  409. 15:45applicable to the whole organization
  410. 15:48then that data you will maintain at the
  411. 15:50client level then some information will
  412. 15:53be specific to company code or plant or
  413. 15:56storage location or purchase
  414. 15:57organization. So those data you will
  415. 15:59enter at these specific levels. Let's
  416. 16:03say that you are maintaining your
  417. 16:04material master. Then the material
  418. 16:06specification will be entered at the
  419. 16:08client level because that material
  420. 16:10specification will be standard for the
  421. 16:12whole organization but the purchasing
  422. 16:14data will be applicable at plant level.
  423. 16:17Each plant will have its own purchasing
  424. 16:20conditions like it will have a
  425. 16:22particular purchasing group or it will
  426. 16:24have a particular purchasing value keys.
  427. 16:26So all those informations which are
  428. 16:28pertaining to the purchasing part will
  429. 16:31be entered at the plant level. Then
  430. 16:33every storage location in a particular
  431. 16:35plant will have its own storage location
  432. 16:37data. So for storage of that material
  433. 16:40you will have to maintain data at the
  434. 16:42storage location. Then if you talk about
  435. 16:45the vendor then the vendor's information
  436. 16:47that is the vendor name, address and
  437. 16:50other contact details you will maintain
  438. 16:52at the client level. But for posting
  439. 16:54financial documents against that vendor
  440. 16:56you will have to maintain data at the
  441. 16:58company code level. And to prepare
  442. 17:01purchase order for that particular
  443. 17:02vendor, you will have to enter the
  444. 17:05purchasing data at the purchasing
  445. 17:07organization level. So you can see every
  446. 17:11organization structure element is
  447. 17:13attached to your master data. Whenever
  448. 17:16you will be maintaining the master data,
  449. 17:18system will ask you to enter the
  450. 17:20corresponding organizational element and
  451. 17:23then only you'll be able to maintain
  452. 17:25that data. We'll see all these in
  453. 17:27details in our upcoming videos. But you
  454. 17:29have to understand that you have an
  455. 17:31organization structure in CPMM. And when
  456. 17:34you maintain your master data, you will
  457. 17:36have to maintain that master data
  458. 17:39against each element of that
  459. 17:41organization structure as applicable for
  460. 17:44that particular master data. So you can
  461. 17:46see at client level you maintain data
  462. 17:49for material and vendor. For company
  463. 17:52code and purchase organization, you
  464. 17:54maintain data for any vendor. And for
  465. 17:57plant and storage location, you maintain
  466. 17:59data for the material. In case of vendor
  467. 18:01also, you can maintain data at plant
  468. 18:03level. We'll discuss when we discuss
  469. 18:05about the vendor master. But majorly you
  470. 18:07maintain these master data on these
  471. 18:10particular levels which are shown on the
  472. 18:12screen. Okay. So in this way we have
  473. 18:15understood what is the meaning of master
  474. 18:16data in SAP MM and why it is required.
  475. 18:20In our subsequent videos, we'll learn
  476. 18:22about each of these master data. And in
  477. 18:25this series, I will cover the detail of
  478. 18:27every master data from the end user
  479. 18:29perspective and from the configuration
  480. 18:31side also. So I hope that you have
  481. 18:33understood this concept of master data
  482. 18:35in SAP MM. And I hope that you've liked
  483. 18:37this video. If you like my videos then
  484. 18:40please like and subscribe to my channel.
  485. 18:42Your likes and subscriptions really
  486. 18:44motivate me to create more content. In
  487. 18:46our next video, we'll learn about the
  488. 18:48material master that how you can
  489. 18:49maintain a material master and what all
  490. 18:51things you have to consider from an
  491. 18:53enduser perspective while maintaining
  492. 18:55the material master. So, see you in the
  493. 18:57next video. Till then, thank you so much
  494. 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.