0:05 Hello everyone, welcome to Zarantech. In 0:07 today's fast-paced business environment, 0:10 effective planning and budgeting are 0:12 essential for success. SAP BPC 10.1 0:16 offers a robust solution for financial 0:18 planning, consolidation, and reporting. 0:21 Let us dive into SAP BPC 10.1, a vital 0:26 tool in the realm of enterprise 0:27 performance management. SAP BPC 10.1 0:31 [music] stands for SAP Business Planning 0:33 and Consolidation Version 10.1. In 0:37 simple terms, it's a software solution 0:39 designed to streamline [music] financial 0:41 planning, budgeting, forecasting, and 0:43 consolidation processes within an 0:46 organization. SAP BPC 10.1 delivers 0:50 significant benefits. A 70% [music] cut 0:53 in budget cycle times and a 50% drop in 0:56 financial close [music] times. This 0:58 translates to enhanced efficiency with 1:00 real-time financial insights. Decisions 1:02 are made swiftly, driving strategic 1:04 [music] growth. In this course, we'll 1:06 cover everything you need to know about 1:08 SAP BPC 10.1 from its core 1:11 functionalities to practical 1:12 applications. We'll walk you through 1:14 step by step. Get ready [music] to 1:16 unlock the full potential of this 1:18 gamechanging tool. But before we begin, 1:21 please subscribe [music] to our YouTube 1:23 channel and hit the bell icon to receive 1:26 regular updates from us. Now, let us 1:28 look at the agenda. 1:31 Agenda one, overview of BPC. Two, 1:36 strategy and road map. Three, modeling 1:40 aspects in BPC. Four, versions of SAP 1:44 VPC. 1:46 Five, configuring environments and 1:48 dimensions. Let's dive in. 1:51 >> So, first of all, we'll understand what 1:53 is BPC, how BPC come into existence, 1:57 what are the predefined functionalities 1:59 available before BPC and why SAP has 2:02 taken BPC into picture. 2:06 Okay. [snorts] So, first thing first, so 2:10 we'll see BPC. BPC stands for our 2:12 business planning and consolidation. 2:15 So business what kind of business it 2:18 would uh ask for and how the business 2:21 will work in the BPC scenario. How the 2:24 plannings are work since in FI or if in 2:27 BW also you we will have some kind of 2:29 plannings and all interfaces. But why we 2:32 are choosing BPC not BW? Why we are 2:35 choosing means why [clears throat] BPC 2:36 is a superior as compared to other 2:39 planning modules and consolidation? 2:41 Consolidation will deal about my interco 2:44 company eliminations and journal 2:46 postings as well as my ownerships and 2:48 others. So why we are doing 2:50 consolidation as well in the BPC part. 2:52 So we will discuss this in our today's 2:54 session. Our agenda for today's meeting 2:56 is introduction to BPC and under this we 2:59 will expl understand understand how this 3:01 came into picture. What are the 3:02 advantage? What are the disadvantage? 3:04 How to achieve the our final goal with a 3:07 BPC point of view. Okay. Under this uh 3:11 one we have some we have included some 3:13 examples okay to provide a purpose in 3:16 purpose scenario. Okay. So though it is 3:18 not a 100% confirmed scenario so just we 3:21 have tried to provide you an example 3:23 okay of the via images and others so 3:26 that it will work in our perspective in 3:28 our direction okay so BPC stands for 3:31 business planning and consolidation okay 3:34 so I will provide an example okay 3:37 suppose tomorrow we'll have a forecast 3:41 or that tomorrow rain uh means 3:43 thunderstorm will be there or rainy 3:45 actually it's quite rainy Okay. And you 3:47 need to step out to market to purchase 3:49 your goodies or vegetables or something. 3:52 So what are the first what uh what what 3:55 are the first thing you will carry when 3:58 you are heading to market? Do you have a 4:00 forecast that it's a rainy season and 4:02 you don't have an umbrella or you don't 4:04 have anything to cover up? So what are 4:07 the things which you will carry or what 4:09 are the things which you will have in 4:11 your mind when you uh think that yeah 4:14 tomorrow I need to step out to market 4:15 and I need to purchase the goodies or 4:17 vegetables. So first thing first what I 4:21 told you is we don't since I don't have 4:23 an umbrella or anything okay to carry. 4:26 So what happened first of all the 4:27 forecast will happen. Okay. So once the 4:29 forecast will happen then means first of 4:31 all we have we have planned that 4:33 tomorrow I need to go to market and then 4:35 I will I check the weather and then the 4:37 weather the forecast that tomorrow is a 4:39 rain so first what I will do first thing 4:41 is like first we have planned first 4:43 planning will come followed by the 4:45 forecasting and since we don't have an 4:47 umbrella then what we will do is we will 4:49 allocate a budget that yeah I need 4:52 umbrella for like $20 $10 $30 how what 4:55 it is okay so first of all uh the 4:58 planning will come. So under this 5:00 planning we will do the planning for the 5:02 forecasted versions and under the 5:04 forecasted versions we will do the 5:06 budgeting. Okay. So these are the basic 5:09 three pillars of the BPC. Planning, 5:12 budgeting and forecasting. 5:14 So under this uh this is my planning, 5:18 budgeting and forecasting. Okay. So see 5:20 there are different kind of planning as 5:22 well. So if you are doing budgeting in 5:24 any domain like in Oracle, in UI, in uh 5:28 finance or in BW, in any domain, if you 5:30 are doing any budgeting, first first 5:33 thing what we need to see is our 5:34 historical datas. Right. 5:37 Right. Our historical datas, our 5:39 historical figures that how the 5:41 historical data, our historical figures 5:42 are different and uh what are our 5:45 predictions going forward, right? This 5:47 is what we are planning, right? based on 5:50 our historical data to forecast the 5:52 values and based on those forecast 5:53 figures we are doing the exact budget. 5:56 Okay. So this is how BPC also works. 5:59 Okay. So first the planning will take 6:02 place and after planning the budget will 6:04 come and the budget and then forecast 6:05 will be there. Okay. So it is a single 6:08 view of financial and operational data. 6:10 So when I say a single view so what does 6:14 this means? If you'll go from top up 6:16 approach or bottom up uh bottom down 6:18 approach, it is a one specified solution 6:21 to your input and output of the data 6:24 from one end to other end from or from 6:26 the last to the first. Okay. And the 6:30 second question is why BPC came into 6:32 existence? We have different different 6:34 modules as well. Okay. Where we are 6:37 using the data like Fury or BW or 6:40 finance then why BPC come into picture? 6:44 So since uh during introduction I heard 6:47 that some of you guys from finance 6:49 domain and record domain also. So we 6:51 have these things also in different 6:53 different system as well or different 6:54 different client interface as well. Then 6:56 why we are reading BPC on this one means 6:58 why BPC is different as compared to 7:01 other clients. So see there is a slight 7:04 difference mean BPC uh means why BPC is 7:07 like see everyone right now in front of 7:09 us they want to see the front end right? 7:12 We are not interested in our backend 7:14 system. If someone will say I want to 7:16 see uh something like a report or 7:18 something, I will not quickly go to BW 7:20 and log into GUI and say that boss see 7:23 this is my report how it looks like. We 7:25 have 10 different different buttons. 7:28 Okay, if you want to update anything, 7:30 you can press this. If you want to 7:31 reload anything, you can press this. If 7:33 you want to do a process chain work, you 7:35 can do this. Okay, so and this looks 7:38 very cozy. If you will see the uh one 7:40 where uh one screenshot which which is 7:43 there over here in the chat. 7:45 So in the chat also if you have uh 7:47 shared me the install software one. 7:49 Okay. So here if you could see uh the 7:52 component release splinding 7:55 up in a single frame. Okay. Means 7:57 everything is there and I don't want 7:59 this unusual information like SP level. 8:02 I don't have any ID on SP level. I don't 8:04 have ID on support packages. Okay. So 8:06 all thing are coming in a single gateway 8:09 and I don't need these things because 8:10 for client I don't need this thing. I 8:12 just want my values. I just want my 8:14 dimensions. I just want my module or I 8:17 was I just want my interface. Okay. So 8:20 BPC will provide you a flexibility that 8:23 what data you are having it will come 8:26 directly to your system. 8:28 Okay. So let's take an example. 8:32 So uh if you will go to different module 8:34 you will see a b c d. So we suppose a b 8:38 cde e and their values are suppose 100 8:42 and this value is 200 this value is 300 8:45 this value is 400. Okay but if you will 8:48 go over here the patch number also 8:50 written a1 and this patch number is b1. 8:54 Let's example path number is C1 followed 8:57 by this is G1 and different support 8:59 values means ABC is something some 9:01 values are also written in our uh BW1 9:04 okay or different different domain okay 9:07 but if you will see this is our backend 9:09 system or if you will see from client 9:11 point of view client doesn't require 9:13 these datas right so client is concerned 9:17 about this data only he don't want this 9:19 data that I want to see this data how 9:21 the patch version is working how the 9:23 client interface is working and how the 9:25 values are working. So what VPC will do 9:27 is BPC will put a filter that what data 9:31 you want to use. Okay, we will just 9:34 filter that data and we will show that 9:37 data to you according to your need. This 9:40 is how BPC is. Okay, if you'll go to ECC 9:44 and others, so you will have 10 9:45 different different columns. Okay, under 9:47 those 10 different different columns 9:49 there arely four to five columns which 9:50 are for our use not more than that but 9:53 we need if we need to uh open that and 9:56 if we need to hit the target it will 9:58 come like 10 different to 20 versions 10:00 like thousand of record thousand of 10:01 record and I don't have anything I don't 10:04 want to see all the thousand of records 10:06 at a time I just want to see like yeah 10:09 was for this XYZ cluster like APEC 10:11 cluster EMIA cluster or different XYZ 10:14 cluster so what I will do is just I will 10:16 filter APE cluster. So under this I will 10:18 see 10 different different reports 10:20 that's it from my side. If I want to see 10:22 EMIA cluster I want to see 10 different 10:24 things that's my side. Okay. So this is 10:27 how BPC will provide a flexibility. 10:30 Okay. So before introduction to BPC what 10:34 we are doing is we are doing reporting 10:36 and all in BW format only. So under this 10:38 BW format also we have variet kind of 10:41 reportings and everything. But the thing 10:43 is there is no flexibility. what is 10:46 there in the system that is what is 10:48 getting populated in our front screen 10:51 and we don't and to be frank we don't 10:53 want these values we just want the 10:55 values which we are using so after that 10:58 what happens so it will lead to like 11:00 data duplication as well means lot of 11:02 data different chunks of data and all so 11:04 then BPC come into existence and under 11:07 this BPC they say that yeah this is a 11:09 front end one though BPC don't have a 11:11 support system okay so it is fully 11:14 relying on our BW1 okay that's why we 11:17 are doing the mapping and all okay so 11:19 what we did is we like we have done the 11:21 transformation like mapping that boss we 11:24 want these datas only so bring those 11:26 datas so that it would be good for me as 11:29 well and for system as well so the 11:31 advantage of BPC is first would be my 11:34 memory okay so we we will use less 11:36 memory okay and second one is my 11:38 flexibility one is my time complexion so 11:41 these are the means more important 11:44 scenar scenarios while introduction to 11:46 BPC like the memory suppose if you will 11:49 see open any report it will take in BW 11:52 it will take like uh 10 MB or 5 MB 11:55 caches and all okay in BPC if you will 11:58 made a filter and open a report it will 12:00 probably take one or 2 MB of the values 12:02 memories okay so the remaining CPU load 12:04 will be get distributed as well 3 MB 12:06 that's why BPC is faster as compared to 12:09 my BW okay second one is my flexibility 12:12 it provide you an additional flexibility 12:14 to filter the values based on your 12:17 requirement. Okay. [snorts] Or filter 12:20 the values based on your requirement on 12:22 the columns as well. Time complexity. If 12:25 you want to make any changes in the 12:27 value with limited appropriate time, you 12:30 can just change the value in the front 12:31 end. And if you want to reload the value 12:33 in BW, then you can push the BPC value 12:37 to BW. Okay. So this is how BPC come 12:41 into and these are the advantage of BPC. 12:44 See uh under BPC in BW if you will go to 12:48 BW we will have lot of uh columns and 12:50 rows. Okay. So while hitting the rows 12:52 and columns so it will show me all the 12:55 existing values which are available in 12:57 the screen. Okay. There is no filter in 12:59 the data. Right? But in VPC while during 13:02 transformation only if we made a filter 13:05 that boss we need these XYZ values in my 13:08 report XYZ report. So what I can do is 13:11 if uh I put filter so BPC will pick up 13:14 only those values and it will show the 13:17 value with that combination only. Then 13:19 what will happen the memory uh power 13:22 means earlier in BW it is taking suppose 13:24 5 MB of data 5 MB memory. Okay. Then in 13:27 BPC it will take hardly around 1 or 2 MB 13:30 of memory. Okay. So that's why it is 13:32 faster and it provide me a flexibility 13:34 as well on the data mean if I want to 13:37 show the actual in a grade out version 13:39 that we can't input any values. So 13:42 actual would be in grade out version and 13:44 planned if I want to show my planned 13:46 value is in my uh edit ready version. So 13:48 we can do that also in the report as 13:50 well where different different formats 13:52 and time complexion here it will take 13:54 less time while executing the report as 13:57 compared to my BW. So that's the case 13:59 BPC is much more faster and flexible and 14:03 these are the advantage of BPC as 14:05 compared to different different modules 14:07 that's why we are using BPC as a front 14:10 end and BPC is that much popular over 14:12 here. So this is a technical one. Okay. 14:14 So technical guy will understand these 14:16 parts very clearly. But from business 14:18 point of view they will say I don't care 14:20 boss I just need this X by Z thing. So 14:22 how you are maintaining whether you are 14:24 maintaining in HyperD and Fury or BPC I 14:26 don't care. I just want to this simple 14:28 simple kind of data. Okay. So let me be 14:32 clear on this point in functional view. 14:35 If suppose business wants to lock any 14:38 version 14:40 locking we can't do any unlocking in our 14:44 BW version directly but in BPC we have 14:47 data locking version if suppose business 14:49 want a value business change the value 14:52 of a from 100 to 500 and business want 14:55 that yeah boss I I don't want anyone to 14:57 override this value so what business 14:59 will do business will go to a will sell 15:01 and he will lock the value like that so 15:03 that no one will able to make any 15:05 changes is whether any technical guy is 15:08 there available or any functional one. 15:10 Okay. So BPC will explain you this 15:13 locking functionality and that 15:16 difference different would be my 15:17 version. So BPC if suppose you want uh 15:21 XYZ version is there. Suppose there are 15:24 different different versions like actual 15:26 uh forecast. So what we will do is uh if 15:30 suppose uh we want to copy a version 15:33 from actual to forecast in BW what we 15:35 will do we will just go to actual we 15:38 will copy the value and we will paste 15:39 the value in forecast but in BPC with a 15:42 one click or one short we can copy all 15:44 the actual value to forecast and if 15:46 suppose business want all forecast value 15:48 business said that yeah I have posted 15:50 some 5,000 lines of my forecast value I 15:53 just want those 5,000 forecast value to 15:55 convert into my budget value. So 15:57 business will just go to forecast tab 15:59 and it will just click on the tab it 16:01 will just copy my forecast value to my 16:03 budget value. Okay. And third one is my 16:05 user point user perspective. 16:08 So under this user perspective how the 16:10 scenario is like business suppose 16:12 business want a cost center planning. 16:14 Okay. So under the cost center planning 16:17 in BW we have we need to go to the we 16:19 need to remember the characteristics or 16:21 key figures that both these are my key 16:22 figures. These are my characteristics 16:25 and these are my cubes. Under these 16:26 cubes, the data is coming upon and this 16:28 is how I am looking. But in BPC, we 16:32 don't need to go to three four different 16:34 different pages or understanding of 16:36 different different scenarios that yeah 16:38 this is my report manual or we just go 16:40 to a connection. We will go to a cost 16:42 center report and once we'll go to a 16:44 cost center report, we will able to see 16:46 the cost center report full picture in 16:48 the system. Okay. Okay. And if suppose 16:50 business want to look at in quarter 16:53 basis, monthly basis, yearly basis, 16:55 three-ear basis, they can just select 16:57 the time for Q1 for quarter month means 17:01 m y. So like that they will do it will 17:04 show the data in it will adjust the same 17:06 data in the same excel format which is 17:08 available in your screen from functional 17:10 point of view. So that uh business will 17:13 not dependent on the technical user that 17:15 boss I need to call a technical user so 17:17 that they can change the report from 17:19 month basis to year basis or year basis 17:21 to week basis or like that. So BBC will 17:23 provide this much flexibility to a 17:25 functional guy to understand how the 17:28 reports are working and if they want to 17:30 make any changes in the data they can 17:32 able to change the data and if they 17:35 don't want to post the data they say 17:37 that key boss I have a meeting at 1:00 17:39 and I don't want to show my end to end 17:41 data from ECC to BPC what it is coming 17:44 because I want to change my BPC figures 17:46 since these are not correct in BW then 17:48 what business will do they will just 17:50 edit the value in BPC and they can show 17:53 it to the business and they can push 17:54 back the same value from BPC to PW and 17:58 ECC forward as well. So this is the 18:00 functional understanding and it it 18:02 provide a simplicity and the 18:04 standardization of all kind of reports 18:06 with a proper channel and format. Okay. 18:09 So I hope I am clear on this technical 18:11 aspect as well as the functional aspect 18:13 of VPC. So uh what I mean is suppose we 18:17 have a meeting and right now I realize 18:19 that yeah boss the value of a which is 18:21 coming from BW all the way from ECC to 18:23 BW to BPC is not correct. It should be 18:27 in my record it should be 300 but uh 18:31 right now it is coming as 500 because 18:32 what the value is coming in BWBPC 18:35 showing that value only. 18:37 >> [snorts] 18:37 >> So what we can do is we can create a 18:40 posting means we can create a posting of 18:42 minus 200 in BPC only and we can just 18:46 execute the report so that in the report 18:48 it will show 300 to my one uh my 18:51 scenario and we can crossverify as well 18:53 with the system with the business 18:55 whether this is working fine or not. And 18:57 if they feel that yeah this is the 18:59 correct one then we can push back the 19:01 same data means we can export the same 19:04 data from BPC to BW and do the further 19:07 adjustments as well because we don't 19:09 have time to go to ECC and run the 19:11 process chain and once this process 19:13 chain will get complete then we'll go to 19:15 BW again run the process chain and do 19:17 the transformation in BPC via DMPS and 19:20 all. So we can do it like that also. So 19:23 these are the functional and technical 19:26 aspects of BPC. The difference between 19:28 BPC and Hyperion. So first and important 19:33 thing is BPC stand is a standalone 19:35 system. Okay. But Hyperion does Hyperion 19:39 is not a standalone system. Okay. So 19:42 what what do we mean by a standalone 19:44 one? under this standalone system what 19:48 we can do is 19:50 uh if suppose we don't have we have some 19:52 data in our BPC we can use that data but 19:55 in Hyperion it is very difficult to use 19:58 that data until unless it will not go to 20:00 the data library okay and BPC will have 20:04 more BPC will provide you a more complex 20:07 report scenario as compared to my 20:09 Hyperion in BPC if suppose we have four 20:12 members like A B C 20:14 And I want a report for one user to 20:18 exclude this A in my report means to 20:21 hide this A and uh means to hide this A 20:25 and show this report. But in Hyperion I 20:27 can't do this thing. If suppose a 20:29 dimension override like B come B uh 20:32 right now it is B for me but for you if 20:34 you want to change it from B to K we can 20:37 do a dimension override functionality in 20:39 Hyper uh in BPC but we can't do a 20:41 dimension override row override access 20:44 override functionality in Hyperion in 20:47 BPC we can use a drill down 20:49 functionality but in a Hyperion we can't 20:51 use a drill down functionality okay so 20:54 this is what makes VPC different from a 20:56 Hyperion as well though both are same 20:59 versions mean both are having same kind 21:01 of functionality but there is a upper 21:04 edge in BPC as compared to my Hyperion 21:06 scenario. BPC is more of user uh defined 21:10 one and Hyperion is more of technical 21:13 defined one. Okay. So if it will have a 21:17 user flexibility so it would definitely 21:19 have a technical fun flexibility as well 21:22 but in Hyperion is more of a technical 21:24 flexibility is not more of a functional 21:27 one. So I hope I am clear the difference 21:30 between Hyperion and Oracle. Let's come 21:33 back to the slide. Okay. So it provides 21:36 a single view of financial and 21:37 operational data and a unified solution 21:40 which supports performance management 21:42 process to adjust plans. Adjust plan is 21:45 nothing but the values which I told you 21:47 that if we can adjust those values in a 21:50 different version as well means for one 21:52 thing I am I was saying but we can 21:55 adjust the values and we can forecast 21:58 and we can budget and we can close the 21:59 cycle as well in BPC. In Hyperion we 22:02 can't close the cycle. So closing the 22:05 cycle we need to go to the interface and 22:07 then we need to apply the lock and then 22:08 we need to close the cycle. But in BPC 22:10 we can directly close the cycle. 22:13 So this is this is what BPC is all 22:16 about. BPC is having basic three pillars 22:19 budgeting, reporting, planning 22:22 [clears throat] 22:22 and this legal compl uh compliance is a 22:25 new one or we can say since it was 22:28 predefined in BPC so we can't count this 22:31 as a uses. So we can do budgeting and 22:35 forecasting in a ease way. 22:38 We can do the reporting and we can do 22:40 the planning. 22:42 So we can make a planning report also to 22:44 a report normal report as well in BPC. 22:47 If you want uh the suppose XYZ a 22:49 planning report I want what I can do is 22:52 I can create a version one V1 and I want 22:54 that V1 should be my report for view 22:57 only. Then we can also create a planning 23:00 report to a reporting tool as well. 23:05 So these are the advantages or uh 23:09 overview of BPC. You can see that it 23:11 will align the organization values and 23:13 it will increase the profitability. 23:15 It will improve the organization values 23:17 based on the technical and functional 23:19 aspects and it will strengthen the 23:21 productivity productivity as well. 23:25 So these are the inbuilt functionalities 23:28 in BPC. So we'll discuss one by one what 23:32 what uh are these different different 23:34 functionalities 23:36 in detail. 23:38 First one is my strategic planning. So 23:41 strategic planning defined 23:44 about the version and time that what 23:46 kind of planning we are into and how the 23:48 planning looks like whether it is 23:50 month-on-month level, year on year 23:52 level, day on day level, week on week 23:54 level or how it is flowing. 23:57 Okay. So under this strategic planning 24:00 we will have a cost center planning, 24:03 finance planning, revenue planning, 24:05 budget planning, forecasting. 24:09 Okay. 24:10 So under this strategic planning 24:12 different different kind of planning 24:13 scenarios will come. 24:16 Okay. So which will rely on M basis, YUI 24:19 basis, day on day care means weekly 24:22 basis. Okay. 24:25 or under this strategic planning we can 24:27 do a planning on granular level to a 24:29 broader scope as well. 24:32 So it depends if I want to show it to my 24:34 CEO one report to my CEO I will not go 24:37 to a granular level and show that boss 24:39 this is these are my values I will just 24:41 show the higher values that yeah these 24:43 are my value these are the allocations 24:45 and how these allocations are working 24:47 this is how uh we are working on this 24:49 interface so this is what about 24:51 strategic planning on a broader scope as 24:53 well and strategic planning on the 24:55 granular level it depends user to user 24:59 so this is about my strate strategic 25:02 planning and one more thing which I 25:05 forgot to tell you under 11.1 25:08 we will have a patch version which will 25:10 guide you as well that what are the 25:13 things which are important while doing 25:14 this planning as well if suppose for 25:17 cost center planning we will have GL 25:19 account cost center profit center then 25:22 he will guide you as well that if you'll 25:24 do y basis the report looks like this if 25:26 you'll do month-on-month basis the 25:27 report looks like this or if you'll do 25:30 week one bas This is the reports look 25:33 like this. So that uh business will have 25:36 an understanding that yeah if I will do 25:38 like this and the value will get uh 25:41 saturated by these values and value will 25:44 get accumulated by these values. So like 25:46 that. Okay. So these will come under my 25:49 strategic planning. We have operations 25:51 planning, business planning or XYZ 25:53 different different type of planning. 25:54 Suppose we have five six type of 25:56 plannings available. Okay. So these will 25:59 come under my strategic planning only 26:01 and it will depend how we want to 26:03 proceed a report whether it is on month- 26:05 on-month basis, year-on-year basis or 26:07 how it is. Okay. So for one planning we 26:09 can show report on three different 26:10 different format month on month, quarter 26:13 on quarter, year on year. We can show it 26:14 in a single frame as well, single report 26:17 as well or if we want to divide the load 26:19 we can show it in different different 26:20 sheets as well. So it depends. So going 26:23 forward we will see how we want to 26:24 create any report or how we want to do 26:26 any strategic planning. So today what we 26:28 will discuss more about the theoretical 26:30 part. Okay. So once I will get once you 26:33 guys will get familiar with the 26:34 theoretical part then we will start the 26:37 uh practical understanding and I will 26:40 again explain this part also that yeah 26:42 this thing what we have learned earlier. 26:44 So this is why we are utilizing this and 26:46 how we are utilizing this. Okay. So I 26:48 know uh so while while I was saying that 26:51 this is strategic planning these are the 26:53 things the things will come into your 26:55 mind that how these things will work in 26:57 my system right now in the theory part 26:59 it would be easy to understand but in 27:01 the system part how the values are like 27:03 that so no need to worry so I will show 27:06 you that as well that on month-on-month 27:08 basis on yearon-year basis how the 27:09 things will be okay the second one is my 27:12 budgeting so under this budgeting uh 27:15 what we are having we are having 27:17 different different budgets like P&L 27:19 budget, balance sheets uh and for cost 27:22 and the plan budget and different 27:23 different budget. So under this we can 27:26 do the budgeting on threeear basis, five 27:28 year basis okay and yearly one as well 27:32 reporting. So uh the budgeting uh 27:34 budgeting reporting forecast they will 27:36 also come into a planning perspective 27:38 only just the names are different though 27:40 the functionalities are different that's 27:43 why they are the different built-in 27:44 functions available in SAP BPC okay so 27:48 uh these are the key benefits which are 27:50 provided by BPC so it allow the user to 27:53 make better business decision okay by 27:56 supporting what if analysis and allow to 27:58 perform scenario based planning so like 28:00 I told so what are the bas Bas on the 28:02 scenario we can do the planning itself 28:04 on that time particularly in the BPC. So 28:08 BPC will provide me that much 28:09 flexibility to upload the value or to 28:12 change the value to reiterate the value 28:14 or to design the value on a proper time 28:16 frame. It allows you to collaborate data 28:19 and thus increase accuracy. So what it 28:22 will so the accuracy of BPC is more than 28:25 95%. So what it will uh do is it will 28:29 provide collective data what we are 28:31 using in the system and how we want the 28:33 system to looks like or how we want a 28:35 report to looks like or planning report 28:37 to looks like. Okay. It help in aligning 28:40 your plan with strategic goal and 28:41 decrease the cycle time. So decrease the 28:43 cycle time is nothing but my uh 28:45 month-on-month basis Y or year on or 28:48 week on week basis or day on day one. 28:50 You have an option to choose the 28:52 versions. See PPC is basically into two 28:55 versions. First one is my classic 28:57 version. What we are learning we are 29:00 going to learn on classic interface and 29:03 second one is my embedded version. So 29:05 under classic version what we are doing 29:07 is we are doing the transformation and 29:09 conversion. Okay. Under this 29:11 transformation and conversion we are uh 29:14 mapping the values from BPC to BW and we 29:18 are fetching the data from BPC to BW. 29:21 Okay. And if any conversion is there 29:24 then we are doing the conversion as well 29:26 to show that in the report. But in 29:29 embedded one since it's a runtime 29:31 system. So what is there in my uh BW 29:34 screen is the same in my BPC screen as 29:37 well. Okay. So in embedded one uh we can 29:41 use embedded while using RS plan. Under 29:44 this RS plan we will have a planning 29:46 scenarios. we learn different different 29:48 planning sequences and also while 29:50 running those we can use uh embedded 29:53 one. Okay. So right now what we are 29:55 dealing with is my uh standard one not 29:58 the embedded one. So the key benefit 30:01 that can be achieved by BPC is reporting 30:03 business reporting analytic report 30:06 forecasting budget planning predictive 30:08 analysis improved compliance 30:10 consolidation and BPF. So uh BPC um 30:14 since BPC uh till uh before introduction 30:17 to SACE BPC is a advanced go tool for 30:23 using predictive analysis. But as soon 30:25 as S sec introduced in the system, so 30:28 the use of predictive analysis in BPC is 30:31 becoming quite less because in SACE we 30:36 will have a flexibility to use 30:38 predictive analysis in our ways how it 30:41 would be and system will also recommend 30:43 in SEC but in BPC 30:46 uh the use is a very [clears throat] 30:48 less since it's a new feature if you can 30:50 compare in BPC but in SEC this is the 30:54 older one okay so BPF will basically 30:58 deal about your process owners and 30:59 templates so what it will give you end 31:02 to end picture though if you don't have 31:04 any technical guy available in your 31:06 available around okay so what you can do 31:08 you can go to the BPF BPF will have two 31:11 scenarios owner and receiver okay if you 31:14 are the owner you can you can make 31:17 changes in the report you can edit the 31:18 report you can do anything if you are 31:21 the receiver you can only view the 31:22 report then What what it simply tell you 31:26 that first you need to go to start open 31:28 XYZ report. Open this template. Under 31:31 this template you suppose it is in build 31:33 phase you can make the changes. If you 31:35 want to change the worksheet means plan 31:37 or if you want to change the font or 31:39 anything you can make changes in those 31:40 things as well. Okay. So this is how the 31:43 flow defines. Okay. So suppose that uh 31:46 uh report will connected to three 31:48 different reports. So what you will say 31:49 that once this uh process flow will 31:52 complete then only I will start the 31:54 another. So we can connect this four 31:56 five reports to one process flow and 31:58 then it will complete to us full 32:00 scenario report of the final output. 32:03 Okay. So this is how process flow works 32:06 in VPC. Like suppose we have a one 32:08 report like we have suppose 10 reports 32:10 for cost center planning and we have a 32:12 one bigger report for cost center 32:13 planning which we need to 32:14 [clears throat] show it to the director 32:16 or CEO or CTO for further approval. Then 32:19 we will not go and uh say that yeah 32:21 these are my 10 different different 32:22 report just do have a look. So what we 32:24 will do is we will just in the first 32:26 report we will check the cost and then 32:28 we will check the trail balances we will 32:30 check the values we will check the 32:32 administrative values XYZ for XYZ 32:34 scenarios we'll suppose have eight 32:36 reports so just we will use the while 32:38 BPF we will use the BPF and based on the 32:41 BPF we can accumulate all the values in 32:44 a single big report. So that is how BPF 32:47 works in BPC. So if suppose any step 32:50 will be missed the BPF will get failed. 32:52 Okay. So we can do it uh via uh means 32:55 cluster level as well or we can do it 32:57 via via version level as well or we can 33:00 do it via year level as well. Okay. So 33:02 this is about BPC. [snorts] So yeah this 33:06 is uh the capabilities of VPC we can say 33:10 unified planning and consolidation. 33:12 Okay. Second one is Microsoft office and 33:15 web reporting. So what we are doing uh 33:17 what we are reading in uh standard one 33:20 we will do it in MS office only and 33:23 we'll do the web reporting as well in MS 33:25 office only and the reports via web 33:27 console. Third one is my budget and 33:30 forecast. For budget and forecast values 33:32 we will do the planning as well in VPC. 33:35 Fourth one is my built-in financial 33:36 intelligence. So built-in financial 33:38 intelligence is nothing but my values uh 33:42 like suppose uh user security locks and 33:45 all. So this will come my this will come 33:48 under financial intelligence values like 33:50 security how the security looks like 33:53 like user team owner reviewer locking 33:56 work status. So work status is basically 33:59 we'll explain you about the lock status 34:02 of a report. Okay. Whether a sender or 34:06 receiver only need to unlock based on 34:09 the output what he is having. Okay. So 34:12 based on the output work status will 34:14 work. How the reports look like if you 34:17 make any changes in the entrant if you 34:18 log the value. Okay. Then legal and 34:22 management consolidation. Under legal 34:24 and management consolidation we will 34:26 have ownerships. We have intercomp 34:29 elimination. We will have uh 34:32 consolidation journal. We will have IC 34:35 allocations, we will have US 34:36 eliminations and different different 34:38 scenarios and then SAP S for 34:40 integration. So see what we are reading 34:43 is like BW for uh BPC. Okay. And we have 34:46 S for integration as well. So uh SAP 34:49 11.1 34:51 uh means BPC 11.1 will provide you 34:53 flexibility to integrate it via S for 34:56 HANA integration scenarios as well. And 34:59 then come hybrid planning by SACE. So 35:03 under SACE we will have a regression 35:05 testing. We will have a hybrid planning 35:07 for complex scenarios via story 35:10 creation, canvas creation and different 35:12 different data locking mechanism will 35:14 work under SACE. So SACE is like a 35:17 having an upper edge or you can say it's 35:19 adv advanced version of SAP BPC. So 35:22 these are the core capabilities like 35:24 planning, budgeting, forecasting, 35:26 consolidation as well as legal and 35:29 management reporting. So these five are 35:31 basically my uh core capabilities of 35:34 BPC. So we can plan the value, we can do 35:37 the budgets, we can use the forecast 35:39 figures, we can consolidate all 35:41 different different accumulated values 35:43 under one and we can do the management 35:45 reporting and analysis and for variance 35:49 calculation as well or reconciliation as 35:52 well we can use BPC in a broader 35:54 picture. See for this is for 10.1 35:58 uh means release plan. So uh 10.1 is 36:02 mainly comp uh compatible with PW for 36:04 HANA. Okay. BPC 11.1 also will come 36:08 under this scenario only. Okay. And this 36:11 is how the road map of release plan is 36:14 BPC. So what we are reading is like net 36:16 we one analysis uh service will be there 36:20 but analysis is unfortunately come under 36:23 advanced version means embedded one. It 36:26 will not come under my standard one. BPC 36:28 is my front end. There is nothing data 36:31 will not get stored in the BPC. BPC is 36:33 my front end. What data you want? We can 36:35 take the data from BW and we can show it 36:37 in BPC. BPC will not store any data. 36:39 What data is there in SACE or any 36:42 different different module as well. Now 36:43 Fury, SACE or different different 36:45 module. We can use BW only means HANA 36:49 only. Dimensional data means master data 36:51 will relate in BPC only. I'm just 36:53 talking about the transaction data. 36:55 Since master data is like a limited 36:56 data, right? It's not like a huge data. 36:58 So it's like if suppose you have created 37:00 10 master data if you want a change you 37:02 can just change two or three or five or 37:04 10 you will not change all the thousand 37:06 of records at one site. So the master 37:09 data is there in the VPC one web console 37:11 I'm talking about the transaction one. 37:13 So the transaction data what is there 37:15 you will take it from HANA only. We not 37:17 taking it from VPC or if you want in 37:20 analysis we even we don't have any 37:23 master data as well stored in analysis 37:25 for office. In analysis for office what 37:27 we will do is the what the data in uh 37:29 BW4 HANA system we can just take the 37:32 data we can just take the data via CDS 37:35 or via aggregation view via composite 37:37 providers and we can just use the data 37:39 and we can just do the calculation on 37:41 the fly and get the data give the give 37:43 back the data again to the S4 system. So 37:46 for analysis for off analysis services 37:49 what you are saying so we will use those 37:51 analysis service in our embedded one not 37:53 in the standard one. So in the standard 37:55 one we will use EPM. So under this EPM 37:58 we will have a connection server. So 38:00 under the connection server we can use 38:02 uh the master data while having 38:05 different different uh models and 38:06 dimensions. So strategy and road map. 38:09 Okay. So under this strategy uh BPC 38:14 strategy uh let me clear about this. So 38:16 right now since everything is moving 38:19 into cloud and other interfaces 38:21 right. So BPC will also have some uh 38:26 means uh scenarios which are moving into 38:29 cloud as well like what we are using in 38:32 SACE SAP analytics cloud. So there are 38:35 high chances that most of the BPC 38:39 functions or scenarios will get move in 38:42 SA cloud in coming 3 to four years time 38:45 frame. 38:46 There are high chances because cloud 38:49 will have at least right now cloud will 38:52 have something like 5 to 10% of BPC 38:54 acquaintance means what is there in BPC 38:57 that 5 to 10% will be there in cloud but 39:01 while the introduction of cloud or 39:03 patching of every 3 three months there 39:05 are high chances that most of the BPC 39:07 scenarios and process will get moved 39:10 into SACE SAP analytics cloud though BPC 39:15 Right now also BPC will have an upper 39:17 edge. BPC will provide more flexibility 39:19 and broader scope. Cloud don't have that 39:22 much broader scope but SAP is planning 39:24 to move all different different 39:26 scenarios in BPC into SAC. So BPC will 39:31 cater our two need. First one is my 39:33 business plans and second one is my 39:36 consolidation that is in central fin. So 39:38 what SACE has uh what SAP has did SAP 39:42 divided this BPC into two parts. This 39:44 consolidation and central finance will 39:47 move under group reporting and the 39:49 planning full end to end planning will 39:51 come under SAP analytics cloud. So SAP 39:54 also divided BPC into two parts and they 39:56 are doing their future ready for 39:59 planning and consolidation. 40:02 But right now as well BPC is a single 40:04 tech platform where we will use the 40:06 planning and consolidation under one 40:08 time frame and it will enable our 40:10 organizations to strategize and plan 40:12 different different scenario and analyze 40:15 the scenario as well as optimize and 40:16 close the results as well. But in cloud 40:19 we don't have this in cloud will become 40:20 like a da kind of scenario mean it's a 40:23 full box under box you need to play what 40:25 you will play around in the system but 40:28 BPC will have a broader scope so since 40:31 cloud is also developing so going 40:33 forward after 3 to four years the cloud 40:36 will also become a uh planning kind of 40:38 scenario same as the BPC this is what I 40:40 assume or SAP is assuming under it 40:43 latest press note in February 2024 40:46 so BPC uh will enable organizations to 40:50 better uh strategize and plan and 40:54 optimize as well as close uh and 40:57 disclose results to increase the revenue 40:59 and profitability. 41:01 Okay. So here in BPC the profitability 41:04 margin is bit higher as compared to 41:07 other different different scenarios. So 41:09 why it is because BPC is a single stop 41:11 solutions for my planning as well as my 41:13 consolidation need mean it will cater my 41:16 planning as well as my finance under one 41:18 roof. No other model in SAP will cater 41:21 these two things at the same time. 41:24 That's why BPC is having an upper edge. 41:26 Second one model in the moment model 41:28 future opportunities and update plan to 41:31 seize new opportunities collaborate in 41:34 context for better alignment and 41:36 accountability. 41:37 So it will collaborate with different 41:40 different versions and modules for 41:43 having a better uh means better 41:46 alignment for the system data and 41:48 configuration though we will have some 41:51 duplication as well in the system but 41:53 yet that will also get covered and 41:56 [snorts] base planning on live 41:57 transactional data. So live 41:58 transactional database planning is 42:00 nothing but in my BPC embedded one. We 42:04 we are not using the live transactional 42:05 data format in my standard. We'll use 42:08 the live transaction data in our 42:10 embedded only 42:13 guide the business. So it gain live 42:15 insight into financial and operational 42:18 metrics and simulate the impact of 42:20 potential actions like various different 42:22 different scenarios we can cater in the 42:24 BPC uh based on the potential how these 42:28 things are working on and how it will 42:30 get impacted in the system. Discover 42:33 what's profitable and what isn't 42:36 to improve the bottom line. So we will 42:38 think and uh we will understand that 42:40 what are the scenarios which are 42:42 important for us to work on and how the 42:44 scenarios will work going forward in the 42:47 BPC for a broader point of view 42:49 continuously account accumulate 42:51 consolidation and report to close faster 42:53 with fewer errors. So there is a 42:55 advantage of consolidation in BPC. So 42:59 what is that advantage? If you will do 43:00 an ownership or IC elimination, it will 43:03 reduce a few lesser error as compared to 43:06 your FI as well. If you go to FI or CO, 43:10 you you need to create latch items for 43:12 doing the consolidation process. But BPC 43:15 will not allow you to create any latch 43:17 item. They will do direct end to end GL 43:19 account IC elimination or consolidation 43:21 based on the ownership ratios or 43:23 ownership values. Provide realtime 43:26 visibility during the period to act 43:28 improve results. So yeah uh real time uh 43:30 visibility means it will provide you a 43:32 visibility of doing the uh values on m 43:37 and yi and to see the results uh during 43:40 that period and improve if we have any 43:42 issue in the scenario. Right now we are 43:44 in we are now entering into the tech 43:47 technical aspects of BPC. What are the 43:49 strategies? How the road maps are 43:51 defined? Okay capabilities. So it uh it 43:55 will streamline uh we have a streamline 43:58 planning uh the key capabilities of BPC. 44:01 So I discussed this thing earlier like 44:04 as well. So it is a streamline planning 44:06 forecasting consolidation and reporting 44:08 process in one environment. So how BPC 44:11 is looks like I will show a glimpse like 44:15 suppose this is my Excel. Okay I am 44:19 omitting this for time now. Like suppose 44:22 how the BPC functions. First one is my 44:25 environment that this environment we 44:28 will have different different uh 44:30 dimensions and models. Then we will go 44:32 to models. Then we will go to 44:34 dimensions. Okay. Under this model and 44:38 dimensions then we will go to reports 44:40 creation 44:42 reports planning and budget. Then we 44:46 will go for BPF 44:48 and work status. 44:51 And then we will go for security. 44:54 We'll go for security and then we will 44:57 go for Excel 44:59 uh for 45:01 transaction data. So in Excel uh we will 45:05 have different different things like 45:06 we'll go for package 45:10 and then uh transactions 45:14 uh means uh transaction files 45:17 transformation files. Then we will uh we 45:20 will have conversion file as well. Okay. 45:24 And uh after conversion file we will 45:28 have a list link list and then we will 45:33 have after link list we will have 45:37 reports reports. Okay. So I will 45:41 explain. So model is basically my 45:43 character uh means so this is my whole 45:47 BPC interface BPC plan. So this is what 45:51 we will read going forward in the 45:54 technical aspect as well as the 45:55 functional aspects as well. So uh here 45:59 uh for mapping from BW to BPC we will do 46:04 the mapping t from here only for 46:07 transformation file we will do BPC to BW 46:11 mapping version also BPC to BW BPC only 46:16 not BW 46:18 package is nothing but uh my we will 46:20 write process chains we will call the 46:22 process chains in list is nothing but 46:25 for my transaction data 46:27 transaction data process chain. 46:30 So this process chain will show me my 46:33 clear one my update you suppose any new 46:37 values are there clear update change 46:41 uh then refresh. So this is my package 46:46 one. So these are inbuilt 46:48 functionalities in the package. Okay. 46:51 This will come under my MD and under 46:54 link list transaction data. Okay. And we 46:57 we under transaction data we have run 46:59 package as well. The run package we will 47:02 have we what package we are running we 47:04 can able to view those package in this 47:06 one and those package will see whether 47:10 it will have a status as finished or not 47:13 and if it is finished then 47:15 [clears throat] we'll able to see the 47:16 data in the report or planning and do 47:19 the planning as well. So this is how 47:21 about BPC planning looks like. 47:23 calculation script will come after once 47:25 we'll complete this report then this 47:28 calculation will come if we do 47:31 calculation on this so this is uh I 47:33 didn't told about calculation because 47:36 right now I'm just doing a transfer mean 47:38 normal transfer from my master data and 47:41 transaction data and showing it in 47:43 report if you want to do any calculation 47:45 we will write logic script so what logic 47:48 script is there it will come after it 47:50 will come here only okay this will come 47:52 under this web console. I showed you 47:55 this thing uh the model dimension this 47:59 thing this will come under web console. 48:02 So BPC will have a web console. So this 48:04 will come under web console and what I 48:06 showed you this this thing. So this will 48:09 come under my Excel EPM for EPM. 48:12 [clears throat] 48:13 So this is how BPC structure looks like 48:16 here. Report means we can use the report 48:19 via web console as well. We can execute 48:22 it will show me the this report only. If 48:25 you want to open it in Excel, we can use 48:27 from here. But we will recommend users 48:30 to open those reports from here only. 48:33 Okay. So this is how a web console looks 48:35 like in a VPC. So VPC will provide you 48:39 enough flexibility and it will help you 48:42 for a streamline planning, forecasting, 48:44 consolidation and reporting process in 48:47 one environment. It will increase the 48:49 organizational agility like uh run 48:52 multiple what if scenarios in real time 48:54 and automate calculations allocations 48:57 manual process for shorter cycle times. 49:00 Uh it will have benefit from a 49:02 businessowned and managed own solution 49:04 and manage solution. It will leverage 49:06 best-in-class for Excel plugins. Excel 49:08 plugins is nothing but my uh EPM and 49:11 analysis. It will improve the accuracy 49:13 of plan and financial data reporting and 49:17 uh the plan and consolidation in single 49:19 application built-in finance. So we can 49:21 use this it will reduce the cost of 49:24 ownership with single platform with 49:25 realtime insight from S4 and BW4 HANA. 49:28 So BPC direct update method you can see 49:31 what we discussed. So what SAP has did 49:34 is SAP has divided BPC into two parts 49:37 planning and consolidation. The planning 49:39 part will go to this one SACE and the 49:42 consolidation part will go to group 49:44 reporting. So under this consolidation 49:46 we will have different different kind of 49:48 scenario for IC elimination, ICMR, US 49:51 elimination, GA, GAP, ownership ratios 49:55 and under this planning we will have we 49:57 will discuss we will have all the 49:58 plannings which is available in BPC to 50:00 SEC but the functions are very different 50:03 and I personally feel BPC is much better 50:05 as compared to SAC because I worked on 50:08 SA group reporting SA BPC as well but 50:11 BPC will have a broader scope but right 50:14 now SAP is a plan SAP are in a plan to 50:18 wind up this BPZ solution going forward 50:20 in 27 or 28 I guess I'm not sure because 50:23 earlier it was for 22 or 23 but uh still 50:27 it's running so it will be like 27 28 or 50:30 I don't know whether it will increase 50:31 also so there are four different 50:33 versions of BPC first one is my BPC 10.1 50:37 net fever standard on HANA or Oracle IBM 50:41 DB2 so BPC we can integrate BPC with 50:45 Oracle as well via Oracle SQL as well 50:48 via RFC connections. Second one is SAP 50:52 BPC 10.1 native or embedded on HANA. So 50:54 embedded is nothing but my realtime 50:56 system. Optimize as for HANA is my 50:58 native HANA. Fourth one is my 10.1 51:01 Microsoft version as well. So these are 51:03 the different different versions of SAP 51:05 BPC available in the system and these 51:09 are the advantages and disadvantages. 51:11 Planning, reporting and consolidation 51:13 solution based on BW technology. It uh 51:16 we can design it designed to be used and 51:18 maintained by business. BW and BPC 51:20 integration need to be established. No 51:23 full integration like same 51:24 transformation and conversion file. 51:26 Additional BPC software and license need 51:28 to be purchased for reporting purpose. 51:31 Embedded create a BPC flexibility to 51:33 BWIP. So we don't need uh uh means uh 51:37 means a connection. We just need a live 51:39 data interface. BW and BPC integration 51:42 is deep and real time. No interface 51:44 needed to be developed. We don't need 51:45 any interface for here. The embedded 51:47 version is ITdriven and required depth 51:50 technical understanding because see 51:52 right now what we are using earlier SAP 51:54 had decommissioned BWIP. IP is 51:57 integrated planning but again they came 51:59 they write it BPC embedded. So this is 52:01 nothing but my BPC BWP only. So they 52:04 just introduced it with a new name for 52:06 BPC uh embedded one. That's it. The 52:09 embedded version is strongly ITdriven 52:11 and required in depth technical 52:13 knowledge. Maintenance will be done by 52:14 IT but finance own and change some 52:16 objects like uh composite and 52:19 aggregations and other values. Planning 52:21 will be done with BW master data. So 52:23 what is there in master data? So it will 52:25 just check those data since it's a right 52:28 runtime real time value for 10.1 support 52:30 package 09 consolidation is supported in 52:34 embedded one it uses same consolidation 52:36 so we can use it RTC realtime 52:39 consolidation in uh embedded one 52:41 embedded is having a much upper as 52:43 compared to the standard reporting is 52:45 done using business object analysis 52:47 addition of Microsoft office and 52:50 additional BPC software also will be 52:52 needed. This is a comparison between 52:54 standard and the embedded one. So here 52:57 uh ask uh someone is asking about the 53:00 client one. So analysis for office is 53:02 dependent on this one analysis uh 53:04 embedded one only. So for net view we we 53:08 we do if we don't need HANA also we can 53:11 use it we can use okay but in embedded 53:14 we definitely need a HANA server or 53:16 system for a proper function. Excel 53:19 client would be EPM addin. We'll go to 53:21 connection server and we will uh just 53:23 log into EPM and do the work. Here in 53:26 the embedded will be analysis for office 53:28 modeling will be here for account model. 53:31 Okay. And here it is key figure model. 53:33 Uh BW connection is partial model key. 53:35 There is no not enough connection like 53:37 transformation conversion. That's it. 53:39 And here everything need to be mapped. 53:41 Modeling is web client. So here the 53:43 modeling would be web client and as GUI. 53:45 So mostly we are preferring GUI in 53:47 embedded one. Like we have a t as RS 53:50 plan. Under this RS plan, we can do the 53:51 different different planning. Local 53:53 master data and hierarchy not needed. We 53:55 need to create but here it it is created 53:58 by default since it's a realtime system. 54:01 Scripting here we are using script logic 54:03 but there we are using fox formulas. 54:05 Data locking is the last win concept and 54:07 here we have also data locking on the 54:10 pessimistic law. Pessimistic law query 54:12 is like MDX engine query and here we 54:14 have an analytical query which we call 54:16 asex query as well. This aggregation 54:18 will work only on BW1 HANA and ER 54:20 embedded it is work all time. So BPC 54:24 optimized version for S4 HANA. So under 54:28 this we have this is HANA multi-tenant 54:31 under this cash management accounting 54:32 BPC optimized for BW embedded one and 54:36 BBC standard for the net one. So this is 54:39 how BPC optimize version. 54:42 So we'll come to our version BPC 10.1. 54:45 So here planning, reporting and 54:47 consolidation solutions will be based on 54:49 my SQL server technology. How the SQL 54:52 will uh means work. The same scenario 54:54 will we will use for scripting and all. 54:57 This version is designed to be flexible 54:59 interface with different source system 55:00 can be established. Then different 55:02 source system can be established by RFC 55:04 connection and the application can 55:05 larely be maintained by business. So 55:07 here the more of most of this 55:09 application is maintained by a business 55:11 interface only. How the business will 55:13 work on this interface? So BPC decision 55:16 tree. So this is very important one for 55:19 BPC decision tree. So SAP platform 55:22 planning and consolidation running. So 55:25 BW net on HANA SAP BPC optimized for S 55:28 for HANA and net for HANA will have 10.1 55:32 netw standard and 10.1 net embedded. So 55:36 what we are using is like standard one 55:38 right not the embedded one right and 55:40 under no platform no SAP platform we are 55:43 using planning and consolidation so this 55:46 is 10.1 Microsoft so this is so we are 55:50 using very less over here uh means we 55:53 are not using BPC 10.1 Microsoft in most 55:56 of the cases okay so these are all about 55:59 the versions and others and then we will 56:02 now we will switch into the technical 56:04 aspects of BPC. So this is what I 56:08 explained you about the introduction to 56:10 BPC, how BPC is working, what are the 56:14 interfaces, what are the advantages, 56:17 what are the disadvantages, how BPC will 56:20 have its future ready, how the things 56:22 are going to be in BPC going forward and 56:24 how the values are yet to be performed 56:26 in the BPC. Okay. So if that is clear 56:29 then we will move into the technical 56:31 aspects of the BPC. What is inside BPC 56:35 standard? So, so we have different 56:39 different modelings in SAP BPC. First 56:43 [snorts] one is my environment. 56:44 Environment we can environment is 56:47 nothing but the plot or area you can say 56:52 where we are doing the where we are 56:55 starting our construction means we can 56:58 take an example of a baron land. Okay. 57:02 And there if I want to build a five-star 57:04 building means uh build a five floor 57:07 five-story buildings. So what we will do 57:09 the baron land we will first cover it 57:12 with concrete or make a proper 57:14 foundation. So that is my environment. 57:17 Okay. So the proper foundation is my 57:19 environment. So under environment we 57:22 will add some pillars for technical 57:26 support of that uh pillar of that 57:29 building. So that will that will be my 57:31 dimensions. So dimension is nothing but 57:34 my building block in a BPC. So under the 57:37 dimensions the collection of all the 57:39 dimensions will come under model. Okay. 57:43 So first one is my environment. 57:45 Environment is my basic plot. Dimensions 57:48 are my pillars and model are nothing but 57:52 the collections of all the dimensions 57:55 which are available in the system. Okay. 57:58 So yeah one uh so yeah one dimensions uh 58:03 different different dimensions can be 58:05 also used in one model or one dimension 58:08 can also be used in different different 58:10 models. So it is not specific that yeah 58:13 cost center will you we will use cost 58:15 center in cost center dimension only we 58:18 use profit center and profit center 58:19 dimension only. Okay. And models are 58:22 also with different different model also 58:25 can be get integrated into different 58:27 different dimensions or different 58:28 different models interfaces as well. 58:31 Okay. And in different environment we 58:34 need to create it from scratch. We can't 58:37 use the previous dimensions and model in 58:39 the another environment. If we are in 58:42 one environment, we can use that model 58:44 and dimension which is available in 58:47 respective environment only. So BPC road 58:50 map versions. So BPC uh see you can see 58:55 uh BPC 11X 11.1. See this this came in 58:59 2021. Okay. And right now this is the 59:01 latest one only. And this 10.1 it came 59:04 on 2018 or 17. So that's why I am saying 59:07 that key we can use uh 11.1 as compared 59:11 to 10.1. And uh this also we will use 59:14 till 2027. earlier in earlier time frame 59:18 it will be for 2024 or 25 since SAP has 59:21 increased the time frame from 24 or 25 59:24 to 27 because right now they are 59:27 shifting the scenarios from BPC to SACE 59:30 and GR. So this is how the road map 59:32 looks like basically we are in the first 59:34 one only. So under this net vaver 59:37 version so what the thing is like we 59:41 will uh so uh it will have an 59:43 integration with SACE right now means 59:46 after 2027 the plan for SAP is to 59:50 accumulate all the SACE features means 59:52 BPC features in SAS so that BPC will get 59:56 wiped out and we will use SSD for our 59:58 near future because right now the number 1:00:01 of users are getting lesser as compared 1:00:05 to the previous years. So that's why 1:00:07 they had a plan to remove this one and 1:00:10 use the uh SACE one. But I doubt that it 1:00:14 would be very difficult for them to 1:00:16 remove this BPC because most of the 1:00:19 business means high level business or 1:00:21 approaches are using the net one only. 1:00:24 So it would be very difficult for them 1:00:27 to get uh means go ahead to remove this 1:00:31 one till 2027. So it will get also 1:00:33 extended till 29 or 30. This is the BPC 1:00:37 road map and version. So BPC 10.1 1:00:41 Microsoft version is a successor of SAP 1:00:43 10.0. 1:00:45 So the version is relevant when SQL 1:00:48 server is your BPC platform. 1:00:50 Okay. So you know that what BPC why uh 1:00:54 in BPC also we are using JavaScripts as 1:00:57 well. And if anyone knows then can they 1:01:00 tell that where we can use the java 1:01:01 scripts while using logic scripts we are 1:01:04 using the java scripts in VPC. So it's 1:01:08 uh syntax would be like x dim member set 1:01:11 xyz for dimension xde this and that. 1:01:14 Okay where loop for loop in as if else. 1:01:20 So we are using the same uh in uh logic 1:01:24 scripts and the same we are uh the same 1:01:26 javascripts we are using in sec as well 1:01:29 but the name different as data actions 1:01:32 and they are pretty same means 99.99% 1:01:36 same just the uh means page uh flow will 1:01:40 be different apart from that everything 1:01:42 is similar this is what in between BPC 1:01:44 and sec for javascripts okay and in BPC 1:01:48 we will also have a BPC uh we will also 1:01:51 have a SQL server. So do you know how we 1:01:54 are extensively using the SQL server as 1:01:57 well while doing the integration we are 1:01:59 using SQL servers in our database 1:02:02 platform like for organized package link 1:02:04 list and all we will have SQL server 1:02:06 only we are which are connected by this 1:02:08 way we are using SQL server as well in 1:02:10 BPC database and you know one thing we 1:02:13 can use Hyperion as well inside BPC also 1:02:16 via SQL RFC connections. So if we can 1:02:19 make a RFC connection we can use uh that 1:02:23 uh Hyperion as well in the BPC 1:02:25 interface. Though the functionality of 1:02:27 BPC is not uh will not work but uh we 1:02:31 can view the same under one system only 1:02:33 means under one roof in the BPC uh one 1:02:36 we can use the Hyperion and we can use 1:02:38 BPC as well. But Hyperion functionality 1:02:42 will not work in the BPC means uh some 1:02:44 functionality will work but not the 1:02:46 whole one. So BPC 10.1 embedded is a pen 1:02:50 ultimate model. So it is the most uh uh 1:02:52 successful model we can say of a BPC 1:02:55 embedded one. So right now it's like uh 1:02:58 if um suppose we have a share of 100 so 1:03:01 out of 100 90% share of BPC will go into 1:03:05 go into embedded one only and remaining 1:03:08 10% will rely on my standard one because 1:03:11 it is a R3 ECC system. Okay. So what is 1:03:15 the difference between embed and 1:03:17 standard one is in standard 1:03:20 we need to upload the master data we 1:03:23 need to create everything we need to 1:03:24 upload master data and then we need to 1:03:26 do mapping and we need to create 1:03:28 packages and then we will what we will 1:03:30 do is we will go to report and do the 1:03:32 report creation in embedded what and 1:03:36 that also the data is like if suppose 1:03:39 data is available in BW then only we can 1:03:42 view that data only in the standard one 1:03:44 but In embedded we can view the realtime 1:03:46 data. What data is there in PW? Suppose 1:03:49 it's 217 AM. What data we are viewing in 1:03:51 217? The same data we can view it in 1:03:54 embedded in 217 only. But in standard we 1:03:57 won't. And the second thing is in 1:03:59 embedded uh we will not go and map 1:04:02 everything. We will just input the 1:04:04 reference from ECC where ECC and then it 1:04:08 will use our BP BW warehouse. Okay. We 1:04:12 will just use the integrated planning 1:04:14 package and we'll just integrate it from 1:04:16 package. And now my BWIP interface is 1:04:20 ready. So BWP interface will get ready 1:04:22 within 5 to 10 minutes. But for BPC 1:04:25 standard, [clears throat] it will take 1:04:26 like 1 day to make a connection. It's 1:04:29 not one day it will take something like 1:04:32 3 to 6 hour 3 to 4 hours at least 1:04:34 because we need to install EPM. We need 1:04:37 to see the flexibility. Then we need to 1:04:39 connect to the server and then create uh 1:04:42 and once connection we'll able to see 1:04:45 whether it is working or not. Then we 1:04:47 will uh check the log on screen and then 1:04:50 only it will get started. But in 1:04:52 embedded one. So once we have all the 1:04:55 credentials, we will just quickly go to 1:04:57 analysis for office. We'll just log in 1:04:58 and it will get start. What data is 1:05:00 there in the embedded one? We can use 1:05:02 that and we can view queries as well in 1:05:04 embedded one like what we are doing in 1:05:06 Eclipse like in BWE queries. So does 1:05:09 anyone have any idea on queries? So BEX 1:05:12 queries are nothing but query which are 1:05:14 creating different data source. So under 1:05:17 B query we have different different kind 1:05:20 of characteristics and key figures. 1:05:22 Okay, we call it directly in embedded 1:05:24 one but standard won't have that 1:05:26 physibility to use B queries and uh in 1:05:30 BPC 11 and in BPC embedded also we must 1:05:34 uh have as for SAP HANA component which 1:05:37 is underlying in the process of BPC uh 1:05:40 embedded one. Okay. So I personally 1:05:43 recommend BPC embedded one is a faster 1:05:45 one. and it's a growing age as compared 1:05:47 to my standard interfaces BPC road map 1:05:51 and version. So BPC standard version for 1:05:54 SAP net standard model it's it is a 1:05:57 successor of 10.0 net and prior version. 1:06:01 So the latest version which is running 1:06:03 is in BW 7.5 and it is relevant when SAP 1:06:07 ECC [snorts] R3 and BW 7.4 or higher are 1:06:11 already in place. SAP BCS BCS or BPS 1:06:16 need to be replaced. It is like business 1:06:18 process and simulation BPS. So earlier 1:06:21 it was process and simulation. So it is 1:06:24 replaced and right now they came with a 1:06:26 PAPM performance analysis and 1:06:28 profitability management. So they also 1:06:31 divided BPS into different parts. So 1:06:34 PAPM so that is what we are working in 1:06:38 means uh right SAP BPC 10.0 on net is a 1:06:42 current version used within the 1:06:44 organizations third party consolidation 1:06:46 software need to be replaced and SAP so 1:06:49 software so earlier what happened so SAP 1:06:51 will have a planning software but we 1:06:53 don't have SAP have don't have a 1:06:55 consolidation one so what they did is uh 1:06:58 with the introduction to BPC they will 1:07:01 uh have a consolidation as well uh means 1:07:05 relied under BPC only so earlier they 1:07:07 are using uh means a third party 1:07:09 software for consolidation for 1:07:11 management futures or management 1:07:13 reserves. Okay. But after introduction 1:07:16 to the consolidation one that things 1:07:18 become easy and it would be uh quite uh 1:07:21 important for them to use going forward 1:07:24 in the BPC scenarios. So that's it from 1:07:27 this one. So this is about the 1:07:28 introduction 1:07:30 glimpse of BPC. How this BPC will work 1:07:33 and how the BPC functions are like how 1:07:37 the BPC come into existence. What are 1:07:39 the advantages, disadvantages, 1:07:42 and how the scenarios are like to be? 1:07:45 >> All right, let's test your knowledge. 1:07:46 Here's a question for you. Which of the 1:07:48 following is a key feature of SAP BBC 1:07:52 10.1? Option A, real-time data 1:07:55 integration? Option B, mobile app 1:07:57 development? Option C, workflow 1:08:00 management. Option D, predictive 1:08:02 analytics. Take a moment to think and 1:08:05 when you're ready, choose the correct 1:08:07 option. Remember, each choice holds a 1:08:11 key to unlocking the answer. 1:08:14 Good luck. Type the correct answer in 1:08:16 the comment section. Hey there, ready to 1:08:19 dive into the world of SAP VPC 10.1? Our 1:08:23 course is your ticket to mastering 1:08:25 supply management all at your own pace 1:08:27 on our platform. In this course, we'll 1:08:29 unravel the mysteries of SAP BPC 10.1. 1:08:33 Think of it like a Swiss Army knife for 1:08:34 planning, ensuring we've got enough 1:08:37 goodies and getting them where they need 1:08:39 to be. From the basics to expert tips, 1:08:41 we've got you covered. Crafted by 1:08:43 seasoned pros, this course delivers the 1:08:45 goods. Your mentors, top-notch veterans 1:08:48 in the feed, ready to guide you through 1:08:50 and tackle any queries you throw their 1:08:52 way. And hey, [music] don't just take 1:08:53 our word for it. Our students are 1:08:55 singing their praises. Folks just like 1:08:57 you have found this course a game 1:08:59 changer. Best part, it's easy on the 1:09:02 wallet. [music] Learning doesn't have to 1:09:03 cost a fortune. Ready to become a SAP 1:09:07 VPC 10.1 [music] maestro? Enroll now. 1:09:10 For more details, visit Zarantex 1:09:13 website. 1:09:14 >> Yeah. So this session is basically 1:09:16 divided into two PPTs. First one will 1:09:18 will be our environment model and 1:09:20 dimension management. Okay. So under 1:09:24 this we are having different we will 1:09:25 study about the how what environments 1:09:28 are what kind of environment we can make 1:09:31 and what are the models how many types 1:09:33 of models are available in the BPC 1:09:35 [snorts] 1:09:36 and what are the dimensions what are the 1:09:38 basic prerequisites dimensions which 1:09:40 which is must in a model and how the 1:09:42 model will behave uh with or without 1:09:45 dimension okay so environment uh what 1:09:48 are the environment environment is 1:09:50 basically uh we we can consider 1:09:52 implement is a playground area where we 1:09:55 are uh creating a BPC uh where we are 1:09:58 creating BPC models and dimensions and 1:10:01 all kind of scenarios. Okay. So uh what 1:10:04 are all kind of scenarios? It will be 1:10:06 like our BPF flow, our securities, our 1:10:09 teams, our users. So uh it depends based 1:10:13 on the user. So how they want to create 1:10:15 they can they can create environment for 1:10:18 different different types of planning as 1:10:19 well separate environment or under one 1:10:22 environment also they can create 1:10:23 different different types of planning. 1:10:25 It [snorts] totally depends on their uh 1:10:27 u mean requirement how they want to 1:10:30 proceed since environment uh as per 1:10:33 environment. So environment will have 1:10:35 multiple kind environment will give you 1:10:37 multiple kind of options to create 1:10:40 different different models and different 1:10:41 different dimensions. Under that you can 1:10:44 create different kind of planning 1:10:45 scenarios. How the scenarios are going 1:10:47 to be how it will be work in your 1:10:50 existing reports, models, projects etc. 1:10:54 And how it will going to affect your 1:10:57 different kind of stories which uh was 1:11:00 earlier pre earlier you can preview it 1:11:02 in BW1. Okay. So an environment consists 1:11:05 of primarily of models and dimensions. 1:11:07 Okay. So since in I uh since we can say 1:11:10 environment is our playground area where 1:11:12 we will start our uh technical analysis. 1:11:17 Okay. So under environment we have 1:11:18 different kind of models and dimensions. 1:11:21 Okay. So models are a collection of 1:11:24 dimensions and dimensions are the basic 1:11:25 building block and dimension can be used 1:11:28 by any model within an environment and 1:11:30 uh the delivered environment is called 1:11:32 an environment shell. Okay. So uh 1:11:36 environment is there. So we we need to 1:11:38 create an environment and under the 1:11:40 environment we need to uh input the 1:11:43 model and dimensions. So once done we 1:11:45 need to activate that. So that we call 1:11:47 as environment shell. Okay. So once we 1:11:51 uh activate the environment shell. So 1:11:53 all the uh each environment will have 1:11:55 basically four models. Okay. By default 1:11:58 four models. We need to decide what 1:12:00 models we are looking for or what models 1:12:02 we can choose. Okay. The environment 1:12:04 shell has four models each with their 1:12:07 own associated templates and packages. 1:12:09 So these are predefined SAP scen things. 1:12:13 So which will be available while 1:12:15 installing the environment. So under uh 1:12:19 environment we will have uh four 1:12:21 different different we will have 1:12:22 different different delivered models. 1:12:24 Okay. So just pay attention in details. 1:12:26 So we have four different different 1:12:28 models. Okay. So here your uh technical 1:12:31 journey for BPC will start like first 1:12:33 will be our consolidation where we where 1:12:35 we will do our uh income statement and 1:12:39 balance sheet data consolidation. Okay. 1:12:41 So it will contain our income statement 1:12:44 and balance sheet data planning. So that 1:12:48 will also by default uh SAP will provide 1:12:50 you a report for income statement and 1:12:52 balance sheet format. So that it it 1:12:55 depends on you how you want to create it 1:12:57 across. Second one is our ownership. 1:12:59 Suppose one company had different 1:13:01 different ownership like 10% in India, 1:13:03 10% in UK, 30% in Japan, 40% this. So 1:13:07 for that all SAP will have a privilege 1:13:10 to create a different uh model as 1:13:12 ownership. Third one is my planning. So 1:13:15 basically planning is the most used uh 1:13:18 model. So under this planning we we will 1:13:20 use all different different kinds of 1:13:22 planning and scenarios. Okay. [snorts] 1:13:26 So currency translation also we can use 1:13:28 over here. And fourth one is our rate. 1:13:31 So rate will store the exchange rates 1:13:33 means forex exchange rates and it is 1:13:35 assigned to the financial and 1:13:36 consolidation model as a supporting one. 1:13:38 Okay. So the major models would be my 1:13:41 planning and consolidation only. But uh 1:13:44 right now what we are doing is we we are 1:13:46 doing all kind of scenarios in planning 1:13:48 only and if some IC uh and balance sheet 1:13:51 plannings are there then only we are 1:13:53 using consolidation. Okay. So basically 1:13:57 uh we are creating different different 1:13:59 dimensions. Okay. So there are basically 1:14:02 five dimensions which needs to be 1:14:04 mandatory that is C E A T R. C is for 1:14:07 category, E is for entity, A for 1:14:09 account, T for time and R for rate means 1:14:12 currencies. Okay. So these are the 1:14:15 basically five important dimensions. If 1:14:18 rate is also not there then we can 1:14:20 suffice but C would be the mandatory 1:14:23 four dimensions which should be 1:14:24 available in across all the dimension uh 1:14:27 all the models. C for category, E for 1:14:30 entity, A for account and T for time. 1:14:33 Okay. So, uh category uh would be like 1:14:37 your actual forecast, planning, budget. 1:14:40 Okay. Budget one, budget two, etc. Okay. 1:14:44 P is for entities like uh you suppose 1:14:46 you have multiple entities or multiple 1:14:48 company codes. So, that will come under 1:14:50 this. A is your account like your 1:14:53 account are basically four types. Asset, 1:14:55 liability, expense and income. Okay. and 1:14:58 uh non-financial [snorts] 1:14:59 account will also cater this one and uh 1:15:03 it is your time. So you can input your 1:15:04 time in Y mm format. Okay. So these 1:15:09 [snorts] are the basically means basic 1:15:11 four dimensions which should be 1:15:12 available across all the models. Okay. 1:15:15 And apart from that there are means some 1:15:17 add-ons also. So it depends on your 1:15:19 choice how you want to create it. But 1:15:21 these are the basically four dimensions 1:15:23 which should be available. So you can 1:15:26 add date as well. So y mm and dd as 1:15:29 well. So it depends how you want to 1:15:32 check it up. If you want to show it in 1:15:34 hierarchy format, you can make it in 1:15:35 hierarchy format as well. Means it uh 1:15:38 SAP uh means BPS will provide you enough 1:15:40 flexibility 1:15:42 to use dimensions based on your needs. 1:15:45 Okay. If you want to create time in two, 1:15:47 you can create in two. If you want 1:15:49 create time in 10 different dimensions, 1:15:50 you can create 10 different dimensions. 1:15:52 But in a model we generally prefer 14 to 1:15:56 15 standard dimensions uh which will 1:15:58 make our work easy means more than that 1:16:02 will lead to uh means the time 1:16:04 complexity time issues and other 1:16:07 scenarios. So it will be always better 1:16:09 if we could use like uh less than 15 1:16:13 mean 12 to 15 dimensions only. Uh once I 1:16:16 have system I will show you everything. 1:16:17 BPC [clears throat] will have all kind 1:16:18 of flexibility like uh if you want to do 1:16:21 it in period like in Q1 period Q2 period 1:16:24 so we have Q1 Q2 so under Q1 we will 1:16:26 have 1 2 3 4 5 6 so like that you can uh 1:16:30 easily uh make changes in the period 1:16:32 means you can easily do your planning 1:16:34 across that and under GL also we will 1:16:37 have GL we will have name [snorts] 1:16:39 description and uh GL account uh means 1:16:43 parent as well and afterwards means 1:16:46 account type. So these four field will 1:16:48 be mandatory for account. For category 1:16:50 we will have member ID and description. 1:16:53 For entity uh for entity also we will 1:16:56 have member ID and description. And for 1:16:58 time we will have uh as I told y Y mm as 1:17:02 ID only or if you want to create 1:17:04 hierarchy. So just go to SAP uh BP means 1:17:08 go to the time hierarchy only mean time 1:17:10 dimension and in the right side you will 1:17:12 able to see uh that create hierarchy. So 1:17:14 it will by default create header key for 1:17:16 2022 23 24 like that. If you want it to 1:17:20 create via period level just you can uh 1:17:23 select create via period. So it will 1:17:25 create via period for particular year. 1:17:27 If you want to create via days so we can 1:17:30 create for each one we will have one 1:17:31 hierarchy. For each two we will have one 1:17:33 hierarchy. So likewise as well mean it 1:17:35 totally depends on your requirement how 1:17:37 you want to proceed in the environment 1:17:40 uh in the main dimensions. 1:17:42 Okay. So under dimensions we'll have the 1:17:44 master data. Okay. So we will focus more 1:17:47 on the master data for [snorts] your 1:17:49 learning purpose and just uh once you 1:17:52 take the dump of the data create at 1:17:54 least six to seven basic dimensions 1:17:56 which you want that your model uh your 1:17:58 model should have. Okay. And first of 1:18:01 all create in planning one and then 1:18:04 create in the consolidation. Your 1:18:06 consolidation will deals with all kind 1:18:08 of balance sheet and P&L. So under 1:18:10 balance sheet and P&L you have cat will 1:18:13 be the mandatory one rate will be 1:18:14 mandatory or if you want to create any 1:18:17 uh asset uh different asset dimension 1:18:19 then you can create if you want to 1:18:21 create any userdefined dimensions like 1:18:24 cost element or profit group or profit 1:18:28 center or cost center uh or WBS. So you 1:18:33 can create as well under users user 1:18:35 defined dimensions as well. Okay. So in 1:18:38 VPCs the dimension types are used to 1:18:40 identify the role of each dimensions in 1:18:43 the consolidation engine. Okay. And the 1:18:46 entity uh dimension is used to determine 1:18:50 the local currency. So under entity you 1:18:52 will have a local currency. So this is 1:18:54 how your BPC page looks like. Okay. So 1:18:57 first of all in the right side if you 1:18:59 will go to right side we have a setting. 1:19:01 Okay. So after setting we will have a 1:19:04 name means username. Okay. And after 1:19:06 that uh if you will click on this one 1:19:09 scroll one so you will able to uh see 1:19:12 the environment name. Okay. So once you 1:19:15 will see the environment name just go to 1:19:17 the top left. 1:19:19 On the top left you will go to 1:19:21 administration. Okay. Under 1:19:22 administration we will have dimensions 1:19:24 and models. Okay. So [snorts] under 1:19:26 dimensions uh you can create dimensions 1:19:29 like uh what is there. Okay. uh so 1:19:34 actually they will uh there will be like 1:19:36 some dimensions available in the system 1:19:38 as well like predefined SAP prerequisite 1:19:42 okay and if you want to make any changes 1:19:44 in the data and everything you can do 1:19:46 that as well so suppose account so once 1:19:49 we'll go to account so under account we 1:19:51 will have uh means like five six excel 1:19:53 tabs are there means columns are there 1:19:55 under that we can input master data 1:19:57 [snorts] ID and description the uh 1:20:01 advantage The disadvantage of having 1:20:04 this dimension is we need to input the 1:20:06 values manually for master data. Okay. 1:20:09 Or we can copy or paste the data. There 1:20:10 is nothing as such flat file form. Uh 1:20:13 there is nothing as such this format uh 1:20:16 means I can say CDS format 1:20:19 to upload the data via uh means what 1:20:23 data is in S4 we can upload that data. 1:20:26 So every time if you have a new data you 1:20:28 just need to go to some part that 1:20:30 particular dimension in which dimension 1:20:32 you have a data you just need to go and 1:20:34 you need to add the data manually of 1:20:37 your own or you can copy the data. Okay 1:20:40 there are some cases. So uh when you are 1:20:44 running uh a package it will give you 1:20:46 error so that the uh means member ID or 1:20:50 member is not available in the 1:20:52 particular dimension. to make sure you 1:20:54 can have a regular check on the 1:20:57 dimensions that if any new data is pop 1:21:02 you can uh create that data as well in 1:21:04 the system. Okay. So member ID should be 1:21:07 must and description you can change it 1:21:10 once you are once you are done. So once 1:21:12 you are done with the uh dimensions so 1:21:16 you can just save. So once it will once 1:21:18 you uh click on save so it will state 1:21:20 that start processing. So once it will 1:21:23 start processing so the status will come 1:21:25 as processed. So once it is processed 1:21:27 means your dimension is ready. Okay. So 1:21:30 like like this you you can create. So 1:21:32 click on new and uh under new you can 1:21:36 input the ID what ID you want. So you'll 1:21:39 have these types account audit category 1:21:41 currency 1:21:43 entity subtables. Okay. So select your 1:21:48 respective uh mean type and under that 1:21:51 you can just create the dimensions. 1:21:54 Okay. So basically how many dimensions 1:21:56 are available uh means how many 1:21:58 dimensions you are planning to create in 1:22:00 this system. If you have a plan or that 1:22:02 ready then it would be uh good you can 1:22:06 check it via type as well and you can 1:22:08 create it as well the dimensions. Okay. 1:22:11 >> Okay. 1:22:12 >> So these are the dimension types like 1:22:14 account. 1:22:15 So type is A, audit is D, category C, 1:22:19 currency R, entity E, scope G, inter 1:22:24 company I, subtables is S, [snorts] time 1:22:27 would be T, U, uh, userdefined would be 1:22:30 U. So under user defined, you can use 1:22:32 cost center, WBS, profit center and 1:22:36 measures means uh if you have any 1:22:38 measures in EPM1 like amount, percent, 1:22:42 so you can add that as well. Okay. So, 1:22:45 account will contain your chat of 1:22:47 account values. Audit [snorts] will 1:22:50 audit will identify the origin of values 1:22:52 such as input, manual entries and 1:22:54 elimination. Category are basically the 1:22:57 version such as actual budget and so on. 1:22:59 Currency will contain the currency value 1:23:01 in which company does business. Entity 1:23:04 contain your business entities that are 1:23:07 included in the consolidation process. 1:23:10 Scope contain your scope. Scope will 1:23:13 contain consolidation group members. 1:23:15 Okay. Uh though we are not using scope 1:23:19 [clears throat] 1:23:19 actually this is out of scope only. So 1:23:23 scope we are not using uh inter company 1:23:26 will contain your IC ids uh for the 1:23:29 entities like trading partner and others 1:23:32 and flow as well come under inter 1:23:34 company. 1:23:36 Sub tables will refer to your flow or 1:23:38 dimensions. 1:23:40 Time would be your time period which is 1:23:41 where you want to store the data. User 1:23:43 [snorts] defined like additional 1:23:45 dimension for your understanding and 1:23:47 measure are amount, percent, weight, 1:23:50 anything what you want to input. So this 1:23:53 is how you can create new dimension. Go 1:23:55 to dimensions. We'll have a new. So 1:23:58 under that new you need to input the ID 1:24:01 then description and the type. You need 1:24:03 to select the type as well. So under 1:24:06 dimensions 1:24:07 uh under that dimension if you want to 1:24:10 use one dimension in different different 1:24:13 one user dimension link [clears throat] 1:24:14 with another uh type of dimension as 1:24:17 well you can do that as well. So go to 1:24:19 that dimension then ID and if you want 1:24:22 to input 1:24:24 use another dimension under that you can 1:24:26 use that as well under uh this options. 1:24:30 Okay. So we can do modeling options vary 1:24:33 with different different dimension type 1:24:35 as well. Okay. [snorts] Under user type 1:24:38 dimension we can add account type and 1:24:40 entity as well. But under entity you can 1:24:43 use account type user data like that. 1:24:47 Okay. So these are the basic properties 1:24:50 of dimensions like adding properties to 1:24:52 model adding properties. Okay. dimension 1:24:55 features and adding property dimension 1:24:57 in consolidation ownership and rate 1:24:59 models modifying properties. We can add 1:25:02 property values as well [snorts] and we 1:25:05 can remove dimension properties as well. 1:25:07 If we uh we can uh we cannot delete the 1:25:11 system generated properties. So some 1:25:12 dimensions will automatically by default 1:25:15 have system generated property. So we 1:25:18 will not able to delete those properties 1:25:20 in the system. configuring environment 1:25:23 and dimensions. So system generated 1:25:26 properties are like this like 1:25:28 description would be there calculation 1:25:30 if any calculations are there then we 1:25:33 can use calculation that hir will be my 1:25:35 header keys like it will uh it will 1:25:38 store our basic basic hierarchies for 1:25:42 particular dimensions. If there is no 1:25:43 hierarchy, we can keep it blank as well. 1:25:46 But hierarchy, I think in uh GL account, 1:25:49 if suppose hierarchy are there, so it 1:25:51 will be recommend to provide hierarchy 1:25:54 for a top- down view. Okay. So we can uh 1:25:58 use dimensions for property validation 1:26:00 also and account dimensions can only the 1:26:03 rate type such as AVZ for average. Okay. 1:26:06 If the rate exist in reference 1:26:08 dimension. So under reference dimension 1:26:11 what is happening means uh if suppose we 1:26:13 have a dimension and we have another 1:26:14 dimension so we can call one dimension 1:26:16 property from other dimensions okay and 1:26:19 validate as well. An entity dimension 1:26:22 can use a currency such as euro if the 1:26:25 currency exist in referent dimension 1:26:27 enter company uh dimension can be linked 1:26:31 to entity member if it exist in the 1:26:33 reference dimension. So these are the 1:26:35 different dimension like dimension 1:26:37 account will have a reference type 1:26:39 account property as a rate type and 1:26:42 validation as average rates or so on uh 1:26:46 category will have a time property is 1:26:49 year and validation is see not or 1:26:52 anything what you have entity would have 1:26:54 a currency property would be currency 1:26:56 and validation would be local currency 1:26:59 intercomp would have entity property 1:27:01 would be entity and validation would 1:27:03 have trading partner 1:27:04 So till this are you clear? Okay. So 1:27:07 this is how the dimension internal 1:27:09 structure of a dimension looks like. So 1:27:12 in the top in the uh top we have add 1:27:16 delete revert. We will have recent 1:27:19 deleted member. We will have apply 1:27:22 hierarchy order display and export to 1:27:24 CSV. Okay. So ID would be there in the 1:27:28 left followed by description. Account 1:27:30 type is much for account dimension. 1:27:34 Offset it depends on you. Input IP 1:27:37 depends on you. Inter company depends on 1:27:40 you. Rate type would be depend on you. 1:27:42 Means the rest these things are depend 1:27:43 depending on your requirement. If you 1:27:46 want to add you can if not no worries 1:27:48 and uh you if you want we can export the 1:27:51 dimension also in the CSV format. And if 1:27:55 you click on apply hierarchy order if 1:27:56 suppose any hierarchy is maintained we 1:27:59 can see the hierarchy in hierarchical 1:28:01 view. Uh we can see the dimension in 1:28:03 herical view. There is no uh there is 1:28:06 nothing as such to upload via flight 1:28:08 file. You need to create the you need to 1:28:11 copy or paste the values manually in the 1:28:13 system itself. 1:28:15 If you want to add something, you can 1:28:17 you need to go to add just you will get 1:28:20 a column uh row and under row you need 1:28:23 to input the values and click on save. 1:28:26 That's it. 1:28:27 There is nothing as such uh input or 1:28:30 flat file or anything. We can have just 1:28:33 copy and paste. Uh so this is how means 1:28:36 if you can copy five lakhs account as 1:28:38 well. So as BPC won't have any so it 1:28:42 will get copied for five lakh account as 1:28:44 well. So there is no worry about copying 1:28:46 and everything. You need to create a 1:28:48 sample of data like this and uh we can 1:28:52 copy uh the same account dimension type. 1:28:56 So under account dimension we have 1:28:58 different different properties. So uh 1:29:00 what you what you saw in the right means 1:29:03 after dimension after account type these 1:29:06 are our properties like offset account 1:29:08 type input type input type inter company 1:29:12 rate type scaling uh scaling and also 1:29:16 these are my rates or means these are my 1:29:19 elimination properties okay for a 1:29:22 particular dimension it depends on us uh 1:29:25 what kind of property if we are using or 1:29:27 if we want to delete we can delete as 1:29:30 The must have property which are 1:29:31 available in account type is uh account 1:29:34 dimension is account type. It is 1:29:36 required to input the account type. 1:29:38 Okay. So why we need account type? So it 1:29:41 will basically we can use account type 1:29:43 for having control in the sign display 1:29:46 and aggregation behavior. Okay. Like uh 1:29:48 asset liability will have a sign income 1:29:51 expense will have a positive negative 1:29:53 sign. So we can control like that. Dim 1:29:55 list. So dimish properties are used as 1:29:58 selection criteria in business rules. 1:30:00 Elimination account is basically used in 1:30:03 US elimination process to identify the 1:30:05 offset accounts. Group is used to 1:30:07 classify accounts such as P&L balance 1:30:09 sheet. Is input is used for report 1:30:12 filtering. Rate type is required in 1:30:14 input forms. Okay. What kind of rate 1:30:17 type it would be? Uh scaling is used to 1:30:19 display value in thousands or uh lakhs. 1:30:23 Okay. 1:30:24 uh like formula based scaling type ele 1:30:28 basically elimination account type 1:30:30 properties like uh means we have control 1:30:33 and prevent so we are not using this 1:30:35 control and prevent aggregation if we 1:30:37 have multiple uh account with having 1:30:40 quarter to date and year to date value 1:30:42 that this account we can use in QTD and 1:30:44 MTD or YTD then we can use this 1:30:47 otherwise we won't use this prevent 1:30:49 aggregation so account type properties 1:30:52 we are having basically four account 1:30:53 type properties available like [snorts] 1:30:55 asset, liability, income and expenses. 1:30:59 These are the sign, these are the 1:31:01 report, these are the aggregation using 1:31:03 periodic measure. So the dimension 1:31:06 structure will look like this. Okay. If 1:31:09 you want any differential integrity then 1:31:12 you can input uh fixed value as rate or 1:31:16 if you want to input any hierarchy then 1:31:18 standard or in uh then here they put 1:31:21 standard as parent H1 and enter company 1:31:23 as parent H2. So this is how your sub 1:31:26 table means flow type dimension looks 1:31:28 like like under H1 we'll have a flow 1:31:30 like F to under tot different different 1:31:35 scenarios for flow type flow type 1:31:38 properties. So under this flow type we 1:31:39 will have id and description and flow 1:31:41 type. So flow type is must while having 1:31:45 the property. 1:31:46 Okay. To make sure to input the flow 1:31:48 type property when you are uh when you 1:31:51 have a dimension as flow type. So it is 1:31:53 used to distinguish the opening and 1:31:55 closing flow. Okay. Like f__101 1:31:58 for opening f_02 for closing. So like 1:32:01 this you can use for flow type as well. 1:32:04 And f01 is my opening. F 02 is my 1:32:07 closing. So like that if you could input 1:32:10 if you could uh just uh put a filter on 1:32:12 opening and closing uh all the 1:32:14 calculation like sum or differences 1:32:16 would come directly in your report. So 1:32:18 no need to go and just check one one to 1:32:21 one to one mean. 1:32:24 So it will come directly over here. And 1:32:26 by the way we can create multiple 1:32:29 uh custom defined property as well in 1:32:31 the dimensions. 1:32:34 If we want to delete one property and 1:32:36 add different property, we can do that 1:32:38 as well in the dimensions 1:32:42 like maintaining consolidation dimension 1:32:44 like entity type. So we can maintain 1:32:46 entity type like ID, description and 1:32:50 currency and if you want uh we can input 1:32:54 owner and all. So why we are inputting 1:32:56 owner you know means uh if we have any 1:32:59 security okay where owner only need to 1:33:02 where admin only need to update the 1:33:04 entity then we need to input the owner 1:33:07 type as well that what uh for what owner 1:33:10 we are giving access to make the changes 1:33:13 read or write or both. So configuring or 1:33:18 maintaining the dimension as well 1:33:20 maintaining [snorts] consolidation 1:33:21 dimension for intercomp type. So this is 1:33:25 the id description and you we can input 1:33:27 uh entity as the property for the 1:33:31 company is the uh basic basically the 1:33:34 page page is same. So it depends on us 1:33:37 how we want to create the particular 1:33:39 dimension 1:33:41 like for category type dimension we have 1:33:44 actual budget forecast IFRS US gap 1:33:48 uh then draft final publish and 1:33:51 simulations. Okay. So category for OP is 1:33:56 used in the balance carry forward. Okay. 1:33:58 For uh difference it is effect 1:34:00 difference only. For source it would be 1:34:03 FX source category. 1:34:06 For rate it would be rate underscore 1:34:08 category. Period would be rate period 1:34:12 rate year and start month which are user 1:34:15 currency translation simulations. 1:34:19 Opening period is used to specify for a 1:34:21 particular month. Okay. EI is used for 1:34:24 planning scenario 1:34:26 to control user input. If year is not 1:34:28 used, the category n member can be used 1:34:30 any type. Okay. For group type [snorts] 1:34:33 uh means uh for group type also we will 1:34:37 have like uh this kind of scenario like 1:34:40 uh wild will uh have a parent under this 1:34:45 world we will have Africa, America, 1:34:48 uh Asia, Pacific and Europe. Okay. So, 1:34:52 so world will be a parent hierarchy key. 1:34:54 Under this we will have this member ids. 1:34:57 Under this member ids, uh we will input 1:34:59 the currency type since each one will 1:35:01 have different different currency type. 1:35:04 So like this how our group type 1:35:06 dimension will get configured in the 1:35:08 system for audit type dimension. 1:35:11 This is how it looks like. See this is 1:35:14 how time dimension look like. Y mm. 1:35:18 Okay. And if you input for uh quarters 1:35:21 so we can use like this. Okay. So we can 1:35:24 define the level as well like uh for uh 1:35:27 quarter it will be like quarter, year 1:35:30 and month in the uh report as well. So 1:35:34 hierarchies so hierarchies can be 1:35:36 defined for any particular dimensions. 1:35:38 They can be loaded automatically or they 1:35:40 can be created manually. It depends on 1:35:42 us how we want to proceed for different 1:35:44 different hierarchies in the system. 1:35:46 Okay. So they are used for basically 1:35:49 expansion, rollup and member selections. 1:35:52 We can create multiple hierarchy like uh 1:35:54 uh means uh BPC will have like uh we 1:35:57 will say will give you privilege to 1:35:59 create three different hierarchy only 1:36:00 for each dimension. 1:36:03 Okay like H1, H2 and H3 that's it and 1:36:06 then child. So uh it depends like for 1:36:10 time uh means for account I think we 1:36:12 will have multiple header keys but for 1:36:14 other BPC will give us privilege to 1:36:17 create only two or three header keys 1:36:19 only at once. If suppose we have like 1:36:23 five head suppose let's suppose we have 1:36:25 H1 H2 H3 H4 H5 okay if you will input H4 1:36:29 right then what it will happen H4 H3 H2 1:36:33 H1 and child will come okay then you 1:36:36 need to write that uh remove leaves node 1:36:40 then if you will remove leave node then 1:36:41 your particular hierarchy H4 will come 1:36:45 like how you are doing in Hyperion okay 1:36:48 so there are some time dependent 1:36:50 hierarchy as Well, so this is uh means 1:36:53 this this is a screenshot for EPM 1:36:55 report. I don't know why the input so it 1:36:57 will give you a confusion only. 1:37:00 [snorts] So don't focus on this uh one. 1:37:02 So we will discuss it once we will go 1:37:04 for EPM reports. So uh once you will 1:37:07 create we need to click on save and 1:37:09 process under save and process we can uh 1:37:13 it will ask do you want to say uh take 1:37:15 the environment offline. So what does 1:37:17 this mean? If you will click on yes. So 1:37:20 if suppose someone will work on the 1:37:21 environment so uh it will not work for 1:37:25 them. So it will make environment 1:37:26 offline. So what changes they are doing 1:37:28 so they will be stick to that only the 1:37:30 previous one. Okay. So always make a 1:37:33 habit when you are having when you are 1:37:35 creating a dimension uh if this message 1:37:38 popup will come do you want to take the 1:37:40 environment offline just click on no. So 1:37:41 that if suppose someone was logging into 1:37:45 your system or means in the BPC system 1:37:47 so they can also work and you can also 1:37:49 work at the same time otherwise uh if 1:37:52 you will click on yes then uh you and 1:37:55 they both need to wait 1:37:58 for like uh a minute or so. So once you 1:38:01 click on no then it uh then this pop-up 1:38:03 will come the dimension have been 1:38:05 processed and once you click so you will 1:38:08 see the status has processed. 1:38:11 So once it is processed means all kind 1:38:13 of master data or BW reports are 1:38:16 available in the system. So now your 1:38:18 system is ready to uh create reports or 1:38:22 various inputs. So these are basically 1:38:24 the dimension members 1:38:27 uh which are used in class. Okay. So we 1:38:31 will discuss this also once we'll have 1:38:32 system. So I will show this 1:38:36 how this will work as well. So I guess 1:38:38 this is all about your configuring 1:38:40 dimension and models. So uh uh if you 1:38:44 have different different kind of suppose 1:38:46 act for cast version as well available 1:38:48 in your system you need to create that 1:38:50 as well like f_sub_1 f_sub_2 f_sub_3 1:38:52 till f_sub_10 mean how many you have so 1:38:56 basic not have a userdefined dimension 1:38:58 saying that versions and under that I 1:39:01 have draft 1, draft 2, draft three and 1:39:03 when I load the data I'll use that uh 1:39:06 intersection to load. Is it not 1:39:08 possible? 1:39:09 uh it's possible but see as I told you 1:39:12 earlier only we have basic we need four 1:39:14 dimensions are mandatory 1:39:16 >> yeah 15 is limit right 15 1:39:17 >> 15 is a limit and four are mandatory 1:39:19 dimension under this category is the 1:39:22 main dimension also so we can't just 1:39:24 bypass the category and create a user 1:39:26 defined as version if category we are 1:39:28 using category in other dimension 1:39:36 as version and we can use like that as 1:39:38 well So under this what is happening if 1:39:41 suppose we have different different uh 1:39:44 mean suppose we are getting data from BW 1:39:46 to BPC okay so what it will do is if uh 1:39:52 we have two kind of things okay first 1:39:55 one is my transformation 1:39:58 okay and second one is my conversion for 1:40:01 time being just forget about conversion 1:40:03 so first we'll focus about 1:40:04 transformation okay so what are 1:40:06 transformation so transformation 1:40:08 information files are those files okay 1:40:11 where we need to uh map the figures okay 1:40:15 so here mapping simply specify 1:40:18 the left hand side would be your left 1:40:20 hand side would be BW dimension 1:40:24 okay and the right hand side would be 1:40:27 your BPC dimension okay so it will have 1:40:31 three columns first would be my options 1:40:35 okay 1:40:36 uh under options it's like uh there are 1:40:38 four five lines which are predefined 1:40:40 only. Okay. And after that we we will 1:40:44 have mapping. So it will divide into 1:40:46 three parts. Options, mapping and 1:40:48 conversion. 1:40:51 Okay. Under options we will have like 1:40:54 five to seven lines which are available. 1:40:56 The text size will be this. Delator 1:40:59 would be XYZ and like that. Okay. 1:41:02 mapping will have my BW to BPC functions 1:41:06 or dimensions and conversion. If suppose 1:41:09 in my BW my time would be like 20 uh 12 1:41:15 uh sorry 2 1:41:17 0 to 10 204. 1:41:21 Okay. But in my BPC the format would be 1:41:24 like y mm. Okay. Means y mm. 1:41:31 Okay. Then what we will do? We will just 1:41:33 input in the conversion we will input 1:41:36 time.xls. 1:41:37 Okay. Under here conversion suppose for 1:41:40 2024 you want to convert then you need 1:41:42 to write every means in conversion we 1:41:45 have internal 1:41:47 external 1:41:49 and value. 1:41:52 So under internal you need to write all 1:41:54 the time which you want to cop which you 1:41:57 want to uh make changes. 1:41:59 Okay. Like this one. So you can input 1:42:02 this like 0 to 10 1:42:06 20 1:42:08 4. Okay. And if you want to convert it 1:42:10 to like uh this like uh uh 2024 1:42:16 uh here you will write this y 1:42:20 dot 1:42:22 mm and here the value will come like 1:42:24 2024 1:42:27 dot 1. So like this you need to pick up 1:42:30 this value data transformation page will 1:42:33 also look like this only. So under this 1:42:36 transformation you can call it in uh 1:42:39 based on your understanding how you want 1:42:41 to call it in the system but uh most of 1:42:43 the cases these transformation values 1:42:45 are getting calculated. 1:42:47 In some cases these transformations are 1:42:49 getting called as well 1:42:52 and there are some users who they don't 1:42:55 want any transformation then what they 1:42:57 will do they will create a separate file 1:42:58 in BW and they will load it via process 1:43:01 chain only by DMP. DMP is nothing but my 1:43:04 data manager package. 1:43:07 So under data manager package we need to 1:43:09 input the name of the process chain. So 1:43:12 once the process chain will get 1:43:13 triggered automatically my data will get 1:43:16 triggered in the system that is advanc 1:43:18 BPC scenario. So yeah we'll see if that 1:43:22 thing suffice uh in this one because in 1:43:24 most of the BPC projects that will not 1:43:27 work but uh if that thing will work 1:43:30 under this then I will show that as well 1:43:32 but for that we need uh have a updated 1:43:34 version of BW and updated version of BPC 1:43:36 as well. If anything would be failed 1:43:38 then we will unfortunately not able to 1:43:41 do that. Let's see how what system we 1:43:43 will get and how the scenarios are. 11.1 1:43:46 is the most updated one and 7.5 [snorts] 1:43:50 7.5 would be my BW version. So under uh 1:43:53 the transformation so once I will create 1:43:55 the transformation and conversion then 1:43:57 what I will do is we will have a DMP 1:44:00 okay like uh like packages like organize 1:44:04 link list and then organize 1:44:09 master data 1:44:11 like organize 1:44:15 CC key. So we can what under this we 1:44:20 will have a scripts. Script means like 1:44:23 advanced formula that once uh user will 1:44:26 click CC hierarchy script. So what it 1:44:28 will do? It will replicate you to CC 1:44:31 dimension and under that CC dimension it 1:44:34 will search for that particular member 1:44:36 and it will input the hierarchy 1:44:40 by default. Okay. So those are mean 1:44:43 later stages once we will have system. 1:44:45 So it would be easy for you to 1:44:46 understand and I think this it for the 1:44:48 dimensions and now we'll proceed with 1:44:50 the another one. So once the dimensions 1:44:53 are completed then we need to uh assign 1:44:57 dimensions to a different different 1:44:58 models. 1:45:00 Okay. So how the model works is model 1:45:03 are basically the combination of 1:45:05 dimension. 1:45:07 Under this model we will have n number 1:45:10 of dimension but as per SCP 1:45:14 uh it would be good if you could have 14 1:45:16 to 15 dimension at once in a different 1:45:19 uh in a model. Okay, more than that also 1:45:21 won't have any issue but SAP will say 1:45:24 that it will lead to system complexity 1:45:27 or time complexity. Okay, we can add 20 1:45:30 as well or 30 as well. there is no issue 1:45:32 but yeah uh your time taking uh means it 1:45:35 will take enough time to open the report 1:45:37 because data loading will take enough 1:45:39 time so we'll start with this so can 1:45:43 anyone tell why we need flow type 1:45:44 dimension 1:45:46 it is basically for the opening and 1:45:48 closing ones so uh we can use flow type 1:45:51 in the planning as well and then how we 1:45:54 can use that flow type in the planning 1:45:56 planning means planning model I think 1:45:58 there are some guys for finance as well 1:46:00 like so They should have this answer if 1:46:03 they can speak. 1:46:05 Suppose we have a cost center planning. 1:46:08 Okay. So my FAB month got a closer. 1:46:11 Okay. So uh suppose I am doing month end 1:46:15 activity MEC activity for particular FAB 1:46:18 month. Then my closing I need to 1:46:20 transfer my closing balance to my cost 1:46:23 center planning opening balance. Okay. 1:46:26 So what I will do? I will go to flow 1:46:28 type. I will create a flow type or if 1:46:31 suppose a flow type is created then I 1:46:33 will just input the flow type entity as 1:46:36 opening and I will run the package. 1:46:39 Okay. So what what it will happen the 1:46:42 closing value uh of my flow type which 1:46:44 is earlier predefined so it can be 1:46:47 converted into the opening value. Okay. 1:46:51 So this is how I can transfer my flow 1:46:53 type closing balance to opening balance 1:46:56 in a particular planning model. Okay. So 1:47:00 what I am telling is suppose F 1:47:02 underscore 1:47:04 01 would be my opening. 1:47:09 F_02 1:47:11 would be my closing. Okay. So, so I want 1:47:15 to transfer my closing balance to next 1:47:18 month opening balance. F_03 1:47:24 would be again my opening. 1:47:26 So what I will do is I will create a 1:47:30 copy of f__02_1 1:47:36 as my opening 1:47:39 and I can write a logic uh where x dim 1:47:45 member set 1:47:48 flow 1:47:51 is equal to 1:47:54 f underscore _ 02 1:47:59 s_1 1:48:00 s f__03. 1:48:05 So what is x member set? So it will it 1:48:08 is saying dimension having a member set 1:48:10 flow 1:48:12 having ID as uh f021 1:48:16 as f03 means it will convert my 0201 1:48:22 value to my f3. So that my 02 means the 1:48:25 replica of 02 will get converted to my 1:48:28 opening one. 1:48:30 Okay. And once uh I wrote this so I just 1:48:34 need uh I just need to input it in my 1:48:37 package list. 1:48:39 So once I will just run the package 1:48:42 means the master data package. So it 1:48:44 will get refresh 1:48:46 and my closing balance for that 1:48:48 particular planning will come under 1:48:51 opening balance. 1:48:53 Okay. And uh there are uh and uh there 1:48:57 are some scripts as well where you can 1:48:59 create one flow and you can just uh 1:49:02 replicate that one only like how I did 1:49:04 right. So you do like that also. If you 1:49:07 can create one flow only you can use it 1:49:09 in opening and closing. You will need to 1:49:11 specify the particular time like for 1:49:13 January you need to specify that for 1:49:15 till 31st January the closing would be 1:49:17 my uh February opening. So like that 1:49:20 also it will work. So you just need to 1:49:23 uh write it in the logic and what will 1:49:25 happen you just need to uh mean put a 1:49:28 timer on the logic that yeah on that 1:49:30 particular time it will start like how 1:49:31 the process chain is working right we 1:49:33 can do as well this uh this will be in 1:49:36 script logic. So uh can can anyone tell 1:49:39 what is the difference between my entity 1:49:41 and flow because flow will also have the 1:49:43 entity. So why we are using entity? We 1:49:46 can use flow only to have entity because 1:49:49 entity is also a property of flow right. 1:49:52 So rather than using two dimensions it 1:49:54 would be easy right? If you can create 1:49:56 one dimension and use the property as 1:49:59 entity in flow. 1:50:01 See flow will have entities. I will tell 1:50:04 you this as well. So this is also a 1:50:06 technical one. Suppose we have a flow 1:50:10 as opening 1:50:12 and for entity like 1:50:16 uh we can say UK okay let's suppose UK 1:50:19 is an entity and let's suppose APAC is 1:50:23 an entity 1:50:24 let's suppose 1:50:27 uh IMIA 1:50:30 let's okay so for example flow one will 1:50:36 have opening balance 1:50:37 Okay. So if it is connected to UK, APEC, 1:50:42 I emaile and Latm. Okay. They're having 1:50:45 different different time zones, right? 1:50:47 Like suppose suppose uh it's like uh 1:50:50 2:00, 2:00 a.m. in UK. In EPC it would 1:50:54 be like 3:00 a.m. 1:50:57 In EMIA it would be like 6:00 p.m. 6:00 1:51:00 a.m. In LAM suppose it would be like 1:51:03 10:00 a.m. 1:51:05 Okay. So if you will just do the uh 1:51:08 means what I told you like via script if 1:51:11 you will just do the opening to closing. 1:51:14 So it will hamper all the things if 1:51:16 suppose some country or entities which 1:51:18 are working on that particular type the 1:51:21 existing flow will get replicated once 1:51:23 you run that scenario. Okay. So that's 1:51:27 why we will have a part different entity 1:51:29 type and different flow type. So we will 1:51:32 not use the entity for that entity 1:51:35 property in the flow type. Okay. See for 1:51:39 flow dimension we will have ID. 1:51:42 Okay. FID we will have a description and 1:51:46 we will have entity. Okay. So this third 1:51:49 entity is not a mandatory field. Okay. 1:51:52 It depends on us whether we want to 1:51:54 input or not. Okay. Let's assume that we 1:51:57 have inputed and we have another 1:51:59 dimension as entity. 1:52:02 and description. 1:52:04 So if we define f01 assigned to these 1:52:07 particular entities four entities then 1:52:11 uh what I told you earlier that we need 1:52:14 to update a process chain right we need 1:52:16 to update a script logic that whether x 1:52:19 dimension type f-01 for this okay and it 1:52:22 should be have a particular timer and 1:52:24 suppose that particular timer for us 1:52:27 will meet a working hour in IMIA. So 1:52:31 what it will happen it will just 1:52:33 replicate [clears throat] the values 1:52:34 existing values and input the new value 1:52:37 means your existing settle value will 1:52:39 get deleted and your new value will come 1:52:42 on that particular system. So that's why 1:52:44 we are not using entity as a property in 1:52:48 flow type while creating report we 1:52:51 that's why we are creating a separate 1:52:52 entity dimension. 1:52:54 So my question was why we are using 1:52:56 entity in flow type. Uh why we are 1:52:59 having entity dimension as a different 1:53:01 one if we have a entity in property for 1:53:03 flow type. The answer would be if we are 1:53:06 using a flow if we are using entity in 1:53:09 this flow type or if we are mapping the 1:53:11 value then there are chances that value 1:53:14 will get replicated if suppose some 1:53:16 particular entity is working on that 1:53:18 particular time. So that's why we are 1:53:20 using entity as different dimension 1:53:22 rather than using in property of flow 1:53:25 type. Okay. So this I will also explain 1:53:28 in the system. I was just explaining 1:53:31 this uh how it is behaving in the here. 1:53:35 Okay. Okay. So let's start models. So we 1:53:40 are having different different models 1:53:42 for creation. Okay. So we are having 1:53:45 different different models. Okay. So uh 1:53:49 basically we are having four models in 1:53:51 the system. First one would be my 1:53:54 consolidation then ownership then our 1:53:57 planning and then rates. Okay. So once 1:54:00 we create all the dimensions we need to 1:54:03 define we need to club those all 1:54:05 dimensions into a particular model for 1:54:07 our proper working. Okay. So for 1:54:10 [snorts] simple consolidation we uh for 1:54:13 consolidation we will have ownership. 1:54:16 Okay. So what are ownership? Anyone have 1:54:19 any idea on ownership? Why we use this 1:54:21 ownership? Ownerships are the values 1:54:25 which are predefined for a particular 1:54:28 company. 1:54:30 Suppose 1:54:32 we have Intel. Intel head office is in 1:54:35 US. Okay. So Intel is basically divided 1:54:39 into all the continents across all the 1:54:41 continents. Okay. So what Intel will do? 1:54:45 Intel will take a ownership means 100% 1:54:48 to its Intel US. Okay. But the business 1:54:52 will come from different different parts 1:54:54 of the uh means across the globe. Okay. 1:54:58 So what Intel will do like my 20% 1:55:00 revenue will come from India, 20% will 1:55:03 come from Japan, 30% will from UK and 1:55:06 remaining 20% would be for XYZ reason. 1:55:10 Okay. So once we define the ownership 1:55:13 values then what it will happen it will 1:55:16 just replicate the same value and while 1:55:20 budget allocation based on the ownership 1:55:23 we can define a predefined budget as 1:55:25 well for a particular cluster or 1:55:28 particular reason. So this is how 1:55:29 ownership will work. See it depends on 1:55:32 the company organization structure how 1:55:35 they want to divide the ownership 1:55:37 values. Okay. If they will divide in if 1:55:40 suppose US is a entity and they will 1:55:43 divide us into like 10 different 1:55:45 different parts like uh Texas for one 1:55:48 Dallas for one California one New York 1:55:51 one so like that uh they can also have a 1:55:54 ownership if they want if not then for 1:55:58 particular cluster wise and there are 1:56:01 some organizations which will take full 1:56:03 100% ownership for its base location 1:56:05 only 1:56:07 because end of the day you will able to 1:56:09 get the P&L and balance sheet report 1:56:11 right for all particular clusters. So 1:56:14 there are some uh mean there are some 1:56:16 clients which are not defining any 1:56:18 ownership. So they are taking 100% as 1:56:21 their ownership only and uh they can 1:56:24 validate the same via P&L report. So for 1:56:27 simple consolidation process with 100% 1:56:30 ownership you can use the finance or 1:56:32 rate models. Under rate we will do the 1:56:35 currency translation scenario. 1:56:37 Consolidation type model can use all the 1:56:40 business rules. So uh see this is 1:56:44 getting more technical. So yeah once 1:56:47 we'll have system. So I will first show 1:56:49 these things then only I will proceed 1:56:51 with other steps. Okay. So right now 1:56:53 just understand that business rules are 1:56:56 basically the rules which are which we 1:56:59 are using for consolidation or carry 1:57:01 forward scenarios. or posting any 1:57:04 journal values. Finance type model can't 1:57:07 use a consolidation monitor but it can 1:57:11 use all the business rule except 1:57:13 elimination and adjustment. So finance 1:57:16 type will not use a consolidation 1:57:18 monitor since it's a part of 1:57:19 consolidation only. You can use 1:57:22 delivered model or create your own. So 1:57:25 uh since SAP have SAP have provided 1:57:29 [snorts] a bunch of model so we can use 1:57:31 that model or we can create our own 1:57:33 model as well. The consolidation engine 1:57:36 can be used for either consolidation 1:57:39 type model or finance type model. Most 1:57:42 model consists of 10 to 15 dimensions. 1:57:45 Every model type 1:57:47 uh category account time entity and some 1:57:50 require more. So category account time 1:57:54 entity is basically for planning and for 1:57:57 other like rate and others rate and 1:57:59 consolidation 1:58:01 uh we need uh rate as a dimension as 1:58:04 well. So this is how we can create 1:58:07 models and this is how your model screen 1:58:09 will looks like. You will go to the uh 1:58:13 navigation page under this three lines. 1:58:16 You will go to uh you need to go to 1:58:18 models and then we will have this 1:58:20 consolidation and this management 1:58:22 consolidation. So I don't think this 1:58:24 management consolidation is there but I 1:58:27 don't know I think it seems to be 1:58:29 earlier one ownership and rates under we 1:58:33 don't have management consolidation we 1:58:35 will have planning in place of 1:58:37 management consolidation. Okay, for 1:58:39 creation of the model, first we need to 1:58:41 input the ID. We need to go to new, then 1:58:45 input the ID and description and then 1:58:48 click on next. Okay. So, it will ask you 1:58:52 whether you want to create a model from 1:58:56 scratch or you need to use the existing 1:58:58 one. Existing means the SAP defined one. 1:59:01 So, if you will click existing defined 1:59:04 one. So under existing defined one we 1:59:06 will have everything like uh standard uh 1:59:10 uh script logic as well. If suppose any 1:59:12 currency translation or anything will 1:59:13 happen. So we will have that thing as 1:59:16 well or we will have business rule. We 1:59:18 will have business process flows, 1:59:20 process templates and everything will be 1:59:22 there. We just need to explore that. 1:59:24 Okay. So we will select a blank one and 1:59:27 under existing we will see all kind of 1:59:29 dimensions and script logic dmps and 1:59:31 others. Okay. So based on our need we 1:59:34 will decide accordingly when we come 1:59:36 into this one. And then for creating new 1:59:39 model the step three would be uh whether 1:59:41 it would be of three parts. Okay. First 1:59:44 one would be my standard. Standard would 1:59:46 be my no other model will be involved. 1:59:49 So under standard it will be used for 1:59:51 planning only. 1:59:54 Second one is finance. Finance is used 1:59:56 for only rate model and consolidation is 2:00:00 my ownership and consolidation model. 2:00:03 Okay. So right now we are just we will 2:00:06 just use finance and 2:00:10 standard. Okay. So under this also we 2:00:13 will have some uh drivers or rates and 2:00:16 we will define that what are the key 2:00:18 figures, what are the ID length, what is 2:00:20 ID, whether it is in string car data 2:00:24 type. Okay. So data entry mode. So this 2:00:28 is for YTD model. Okay. So we can input 2:00:31 data like cash cash equivalents, sales 2:00:34 revenue. This is not needed for 2:00:37 periodic. 2:00:38 Yeah. [snorts] 2:00:39 For data entry mode in standard one. So 2:00:42 we will have basically these four 2:00:44 dimensions. And for col uh for financial 2:00:47 we will have C A T R where R stands for 2:00:50 my currency or rate. And for 2:00:53 consolidation one we will have C Audit 2:00:57 group inter company subtable and 2:00:59 currency. And for creating model we just 2:01:03 need to select the dimensions. So what 2:01:05 dimension you want? You can just click 2:01:07 on that uh tick mark on that dimension 2:01:09 and it will get selected. If you want to 2:01:12 copy a dimens copy a model from any 2:01:15 existing model which is available in the 2:01:17 system then you can uh write you can use 2:01:20 like this as well. copy from source. So 2:01:23 what will be there in that particular 2:01:25 model will get copied from there to this 2:01:28 one what you're creating and afterward 2:01:31 we'll have a review and create. So once 2:01:35 we'll click on review and create a model 2:01:36 will get created. After editing the uh 2:01:40 after uh means creating the model we can 2:01:42 go to edit and we can edit the model as 2:01:44 well via settings. So under this edit 2:01:47 model we'll have this kind of general 2:01:49 settings like large key figure, normal 2:01:51 key figure, work status, enable command, 2:01:54 command length and source data and 2:01:56 feature use within a model like whether 2:01:58 if we are using a work status. So what 2:02:00 work status will do? Work status is 2:02:03 basically the data log state data log. 2:02:06 Okay. So under this data log we have 2:02:08 owner and reviewer. So owner will view 2:02:12 the data and reviewer will need [snorts] 2:02:14 to input the data log. So they two have 2:02:16 the access. Owner is my super user and 2:02:19 reviewer is my basic user. Then data 2:02:22 audit. Okay. So data audit feature will 2:02:26 also enable in the model. We can select 2:02:29 then my data audit will work. So under 2:02:31 this data audit if suppose anyone 2:02:34 anyone will make any changes in the data 2:02:37 you can able to view that via data audit 2:02:39 catalog. 2:02:41 Okay. If master data will get changed or 2:02:44 ID will get changed, you can have a 2:02:46 track of that as well that yeah on that 2:02:48 date that uh means that ID has changed 2:02:51 this data or manipulated this data from 2:02:53 this to this. Okay. Then journal 2:02:55 templates only relevant for reporting 2:02:58 model. So general templates are relevant 2:03:00 for only reporting one. [snorts] 2:03:03 Then enable command. So select this 2:03:05 option to use command. So if suppose in 2:03:08 the input report if you want to input 2:03:11 any value or any uh means command you 2:03:14 can use this one and use as a source of 2:03:17 data means if you it you can use as 2:03:20 source of data for external application 2:03:22 means this process will work when you 2:03:25 are taking data from S uh means SQL or 2:03:30 any XYZ RFC connection. So this is this 2:03:34 we will see once we'll create. So I 2:03:37 don't think we need to create all 2:03:38 different model because we have limited 2:03:41 data only. So let's see what models we 2:03:45 and so I will create means we will 2:03:46 create all models. 2:03:48 Okay. And we'll see in which model we 2:03:51 are we will work. Okay. So uh these are 2:03:54 the basically environment. 2:03:57 So environment is a main uh means 2:03:59 playground area. Under this we will have 2:04:01 dimensions and under the dimensions are 2:04:04 the basic building block and under 2:04:05 dimension we will have rates um we will 2:04:09 have uh models like rate model 2:04:11 consolidation model and ownership model. 2:04:14 Okay. So this is how your model and 2:04:17 dimension will come into existence for 2:04:19 SAP BPC. Just while creating environment 2:04:22 we need to activate and under 2:04:24 environment if everything is created it 2:04:26 is ready for use. Just click on save, 2:04:29 save and process. So this is our first 2:04:31 technical one which we have completed 2:04:34 based on the model uh how to create 2:04:37 model and dimensions. Okay. 2:04:40 So uh this would be uh the third topic 2:04:44 would be my DMPS 2:04:46 like data manager packages. 2:04:49 So this is a very interesting and 2:04:50 important topic in BPC point of view. So 2:04:54 this is like means uh once we create so 2:04:56 we will come to VPC and once VPC will 2:05:00 get mean once VPC will start working and 2:05:02 then we need to just create the DMP 2:05:05 packages. So DMP packages are basically 2:05:08 the lifeline you can consider of a BPC 2:05:12 without DMP BP system will do nothing. 2:05:16 So this is the most important part okay 2:05:19 for data transfers and all. So we are 2:05:22 using DMPS. 2:05:24 So under this you will able to 2:05:26 understand about the configuration and 2:05:28 user use of DMPS. And once we are done 2:05:31 with it then we will close today's 2:05:33 session and we will uh start uh next 2:05:36 session. Okay. Uh in coming days. 2:05:41 Okay. So dmp is a package which will you 2:05:44 which we are using to import, move, 2:05:48 copy, transform, manipulate and clear 2:05:51 the data from EPM addins. Okay. So under 2:05:55 those EPM addins we will have these much 2:05:58 functions to import the data. So how we 2:06:01 will import the data? So first uh we 2:06:04 need to create a transformation and then 2:06:07 conversion and once we will do that and 2:06:09 then we need to create a DMP data 2:06:11 manager package. So under the data 2:06:14 manager package we can take the data 2:06:17 from the system itself. 2:06:20 Okay. We [snorts] can import the data, 2:06:21 we can move the data from one place to 2:06:23 another, we can copy the data, 2:06:26 we can transform or we can manipulate or 2:06:29 clear the data as well. 2:06:31 It provide basic extraction, 2:06:33 transformation and load. So yeah, BPC 2:06:36 worked on ETL principle like extraction, 2:06:40 transformation and loading principle for 2:06:43 advanced business users. 2:06:46 Okay. 2:06:47 It allow to modify package prompt and 2:06:51 script logic files. For example, 2:06:55 DP 2:06:57 are created against delivered BW process 2:07:00 chain. So what is uh process chain for 2:07:03 BW is the same for TMP's data manager 2:07:07 package is for BPC. 2:07:10 Okay. So data manager package are 2:07:12 basically the uh process chains in BPC. 2:07:17 So what is available in BW 2:07:21 package can be bundled into package 2:07:23 links. So each package will have 2:07:25 different different kind of package 2:07:27 links. Okay. And they are different from 2:07:29 each other. Package and package link can 2:07:32 be executed from BW process chain. So 2:07:34 what it will do? So we will input the 2:07:37 package list. Okay. So once we have the 2:07:41 package list, it will show the it will 2:07:44 uh once it we will trigger this. So what 2:07:46 happen in the BW side? it will trigger 2:07:47 the process chain and uh we will get the 2:07:52 data in the BPC. So this is how DMP tab 2:07:56 will looks [clears throat] like. We need 2:07:59 to go to organize. 2:08:01 Under organize we will have three 2:08:03 things. Organize package list. Organize 2:08:06 package link list. Organize delta 2:08:08 initialization. Organize package list 2:08:11 will have all my master data. Organized 2:08:14 package link list will have all my 2:08:16 transaction data process chain. Organize 2:08:19 data initialization. If suppose if you 2:08:21 want to change only some transaction 2:08:23 data then we need to run this one 2:08:26 organized data initialization. 2:08:30 Okay. Below this we have transformation 2:08:33 file. So as I told you we need to go to 2:08:35 new transformation file and create a new 2:08:37 transformation 2:08:39 from scratch. And then uh we need to go 2:08:43 to manage. If you want to make any 2:08:45 changes in our transformation then we 2:08:47 need to go to manage transformation 2:08:48 file. Once we are done with manage and 2:08:52 then we need to save and we need to 2:08:53 validate the transformation. 2:08:55 Once it will get validated and then we 2:08:59 will go to conversion files create 2:09:01 conversion manage validate. 2:09:05 Okay. Right now how I am speaking like 2:09:09 this. So it is not this much that much 2:09:12 simple. So we literally need to 2:09:14 understand how this thing are working in 2:09:16 the system. So once we'll have the 2:09:18 system and some amount of data then we 2:09:20 will directly go and check and do this 2:09:23 one and under this run package. So we 2:09:26 will go to run package. So it will show 2:09:28 different different process chains 2:09:30 different different package link list. 2:09:33 So once we'll click uh we will able to 2:09:35 see the status in view status. 2:09:39 Okay. And in run package also we have 2:09:41 two type of things. Once you will start 2:09:44 run package it will direct directly run. 2:09:46 And the second one is if you will start 2:09:49 run package it will ask you for prompts 2:09:51 that for which prompts you want to run 2:09:52 the package. Okay. So it depends how you 2:09:55 want to uh means create the package link 2:09:59 list. If you want to create it via 2:10:01 prompt then it will ask for prompt. It 2:10:04 will if you will ask if you want to run 2:10:07 it directly then it will run directly as 2:10:09 well. For data manager tab we have two 2:10:13 ribbons. First one is my connection. 2:10:14 Second one is my data manager group. 2:10:18 The connection ribbon is the uh place 2:10:21 where we define the web service 2:10:23 connection where we need to reach the 2:10:26 data manager feature. 2:10:29 And the data manager group is where we 2:10:31 can perform 2:10:33 [snorts] all business planning and 2:10:34 consolidation access data task like run 2:10:37 package or package links, view package 2:10:40 or package link, upload flat file, 2:10:43 download flat file, 2:10:45 preview flat file, 2:10:48 organize package link, package links 2:10:51 package and delta initialization. Create 2:10:54 and manage transformation. create and 2:10:56 manage conversion files 2:11:00 and this is about our security part data 2:11:03 manager and security. 2:11:07 Okay. So we can define tasks 2:11:10 that uh who will do this data manager 2:11:12 task and who will do this task. So if 2:11:14 you if we want uh that owner should uh 2:11:17 run only admin packages then we can 2:11:19 input run admin package and once we will 2:11:22 click so we will get we will assign 2:11:25 owner name over there. If suppose we 2:11:28 want someone we'll need to only edit the 2:11:31 package then we can do like that also. 2:11:34 Okay. Okay. So we can apply locks as 2:11:36 well and we can apply security as well 2:11:39 on 2:11:40 different different task and their task 2:11:43 profiles. 2:11:46 So uh these are the profile descriptions 2:11:50 like run admin package. It will view and 2:11:52 run package which is set in admin 2:11:55 package and user package list. 2:11:58 Second one is run package. It will view 2:12:02 and run packages set to the task type 2:12:04 user package. 2:12:06 [snorts] Third is edit package. So it 2:12:08 will edit create or delete package or 2:12:11 change package type or add 2:12:13 transformation and conversion file. It 2:12:15 cannot change the file name. 2:12:18 Edit transformation 2:12:21 will edit create and delete the 2:12:23 transformation files. 2:12:25 [snorts] 2:12:26 Edit conversion file. So edit conversion 2:12:29 file will edit, 2:12:31 create and delete the conversion files. 2:12:34 Cancel any user package. So it will 2:12:36 cancel other user package only net 2:12:39 provides the capacity means uh uh means 2:12:43 provide the ability to cancel means if 2:12:46 suppose you have a package which you 2:12:49 have outsourced 2:12:50 uh from one system to other so you can 2:12:53 cancel it. 2:12:55 Edit package schedule for any users. 2:13:03 Here you can view logs and change the 2:13:05 schedule for any kind of package 2:13:10 and then edit package links. So you can 2:13:12 edit, create or delete package link, 2:13:18 upload data. So you can upload the data 2:13:20 as well by flat file. You can download 2:13:23 the data as well and you can maintain 2:13:25 the delta initialization 2:13:28 settings as well. If needed, you can run 2:13:31 it as well. [snorts] 2:13:34 So package groups are defined into three 2:13:36 types. First one is my data management, 2:13:39 second one is my finance process and 2:13:41 third one is my system process. [snorts] 2:13:44 So under data management, 2:13:48 we will get all the master data. 2:13:51 Under finance management, we will get 2:13:53 all the GL accounts and other data. 2:13:56 Under system management, we will 2:13:58 maintain the hierarchies and different 2:14:01 different types. 2:14:03 So if you upload suppose if you have a 2:14:06 flat file, right? So this is the package 2:14:08 what we are talking about for upload. So 2:14:11 this upload function uh will work for 2:14:13 transaction data only not for master 2:14:15 data. 2:14:16 So data man DMPS are basically the 2:14:19 process chain. Okay. So so how the 2:14:24 process chain will work is like start 2:14:26 load data and import into model. So this 2:14:29 is how our BPC data manager package is 2:14:33 working 2:14:34 and uh see these are the things which 2:14:37 will come under data manager package 2:14:41 like first one is our organize package 2:14:44 list. So under this we need to uh go to 2:14:49 add package and we need to input uh the 2:14:51 package name whether you want to copy 2:14:53 transaction data. So [snorts] just click 2:14:55 on the copy transaction data and add 2:15:01 that's it. So our copy transaction data 2:15:03 will package will get created. 2:15:08 If you want to run the copy transaction 2:15:10 data. So we will just go to organize or 2:15:13 if you just go to run and we'll just uh 2:15:17 write copy package. So it will run the 2:15:19 copy package transaction data what we 2:15:22 have just created now earlier in the 2:15:24 above slide. Uh so under this uh we will 2:15:28 provide a path for process chain also. 2:15:31 So once we will do once we will add now 2:15:34 so the second option modify package will 2:15:37 trigger. So we'll just click on that and 2:15:39 we will just provide the path for 2:15:41 process chain in BW. 2:15:44 So what data is there in BW? It will get 2:15:46 that data from BW to BPC. If we don't 2:15:50 provide as well it will also uh don't 2:15:53 have we don't have any issue because we 2:15:56 already we are already doing the mapping 2:15:58 in transformation and conversion file. 2:16:01 Okay. So the copy data manager package 2:16:03 will start run. So uh under here if you 2:16:07 will go uh so that is what I have 2:16:10 created. Okay. So under that if you want 2:16:13 to copy a data copy transaction data for 2:16:15 XYZ particular uh entity then we will 2:16:19 have a prompt as well over here. Okay. 2:16:22 Like copy transaction data. If you click 2:16:24 on copy transaction data it will ask for 2:16:26 a prompt that uh means if you want to 2:16:28 input a prompt you can input a prompt or 2:16:30 you can select all. [snorts] 2:16:33 Okay. Okay. So once you select it will 2:16:35 ask you for a transformation file or 2:16:38 means copy the entry. You can input the 2:16:41 entry and then you can just run the 2:16:43 package. So once we'll have system I 2:16:46 will show you step-by-step scenario how 2:16:49 we are creating data manager package and 2:16:51 how we are running this DMP. So you will 2:16:54 get more familiar with this. Okay. Right 2:16:56 now don't panic that uh yeah these 2:16:58 things are there. So once we have system 2:17:02 then we'll do yeah just remember one 2:17:05 thing that 2:17:07 if we have any work status available in 2:17:09 the system or if work status is applied 2:17:12 then it would be very difficult to run 2:17:14 the package because what happen work 2:17:16 status will lock the particular cell. So 2:17:19 if it will lock the cell then your 2:17:21 process gen means uh package will get 2:17:24 failed because it will not allow you to 2:17:27 write any value in the cell. So once it 2:17:29 will not allow then it will force the 2:17:31 package to get fail. Okay. So make sure 2:17:35 that when you are running the DMPS your 2:17:38 work status needs to be open. It should 2:17:42 not be closed. Okay. So these are the 2:17:44 silly things which we need to take care 2:17:47 of. So once we run the package and it is 2:17:49 getting failed continuously then we need 2:17:52 to check the work status as well that 2:17:53 whether my work status logic is open or 2:17:56 closed. 2:17:58 Okay. So after conversion file now we 2:18:01 will have a option of work status. If 2:18:03 you go to data now we will have a tab as 2:18:05 work status. If you'll just click so it 2:18:08 will say that open or close. Just check 2:18:11 it is open. That's it. It is in data. So 2:18:14 we have home in the Excel you we have 2:18:17 home insert page layout. So in the data 2:18:20 we will have work status. So once EPM 2:18:23 will be there. Now if you'll click on 2:18:24 EPM now you will able to see the work 2:18:26 status. That's it. So you can lock it 2:18:29 via model as well and you can lock it 2:18:31 here as well. So it depends if you will 2:18:35 lock it via model means admin rights you 2:18:38 will have you need to must have admin 2:18:40 rights. If you will lock from here you 2:18:42 need to must have user rights. Okay. So 2:18:45 admin can lock it from there also. So if 2:18:48 admin can lock so then you need you will 2:18:50 not able to input anything over here. 2:18:53 then you need to remove that lock and 2:18:55 make sure that both locks are in sync 2:18:57 only. If one is working, if one is lock 2:19:00 and one is open then it will not work. 2:19:03 If both are lock or both are open then 2:19:06 only it should work. So this is how we 2:19:09 can view the status and we can view the 2:19:12 status 2:19:14 of packages that are currently running 2:19:16 and packages that have been completed. 2:19:18 Select view status and under view status 2:19:21 we can see. So here we can see view 2:19:24 status as well. So yeah after run 2:19:27 package are you able to see view status 2:19:30 here you can see view status one after 2:19:33 run package. Uh so once you will run the 2:19:36 package under this one so uh it will you 2:19:40 can able to see the uh status of the 2:19:42 package whether it is successful or 2:19:44 fail. Okay. under this view status one. 2:19:48 So this is what it return uh [snorts] 2:19:50 select view status and then view status 2:19:52 the package stat dialog box a resume of 2:19:55 various packages. If you want to view 2:19:57 the detail log or under this view status 2:20:00 if you want to see a detail log whether 2:20:02 what kind of report I mean what data I 2:20:05 have filtered and what was get loaded in 2:20:09 the system you can able to check that as 2:20:11 well and schedule status uh means 2:20:16 package status displays the result of 2:20:18 package that are executed already. So 2:20:20 under that when you open the view status 2:20:22 now we will have lot of packages uh 2:20:25 successful fail successful fail. So it 2:20:28 will show my existing packages which we 2:20:31 run in the system itself. 2:20:36 Okay. Schedule stata displays the 2:20:38 schedule on which various package are 2:20:40 set to run. See this is how my view 2:20:43 status will look like. 2:20:46 So this is uh the succeed. So once you 2:20:49 click on this succeed one you will able 2:20:51 to see the package logs. Under this 2:20:53 package log how many records are 2:20:55 transferred? How many records are not 2:20:57 transferred? What is the reason for not 2:20:59 transferring of records? You will able 2:21:00 to see everything each and every details 2:21:04 and data update option are also 2:21:06 available. So after importing the 2:21:08 transaction data uh there are normally 2:21:11 subsequent update in the source system 2:21:13 that also need to be imported. when 2:21:15 importing transaction data multiple time 2:21:18 uh there is also a chance of data 2:21:20 duplication. Okay. So always 2:21:24 and always when you are trying to or 2:21:26 when you are going to import the 2:21:28 transaction data make sure you need to 2:21:30 run the clear package first. So once you 2:21:33 run the clear package it will clear all 2:21:36 data and then run the copy transaction 2:21:39 data so that it will copy your data from 2:21:44 fresh otherwise in BPC it will over it 2:21:48 will not override that function it will 2:21:50 just add the function. Okay. So you need 2:21:54 to take care of this 2:21:57 as well. So when you are copy the 2:22:00 transaction data you first need to clear 2:22:03 the existing data and then only you need 2:22:06 to clear the existing data via 2:22:08 clear package list in the master data 2:22:11 and then only you need to apply that 2:22:15 copy transaction data otherwise it will 2:22:18 uh just to double up the values. 2:22:21 Okay or when you will use the delta data 2:22:25 manager package. So what it will do is 2:22:28 it will provide it will definitely you 2:22:31 need to definitely input any prompt 2:22:33 without prompt it will not allow you to 2:22:36 run any data manager package. Okay. So 2:22:40 in data manager package there is a least 2:22:42 chance of having data duplicacy 2:22:44 available in the system. Okay. So 2:22:48 example is after importing the May flat 2:22:50 file on June 1st you received the 2:22:53 adjusted file on June 2nd with all of 2:22:56 the same record with two exception 2:22:58 actual benefit have increased from 1500 2:23:00 to 1,600 or there is a new record 2:23:04 uh for actual direct labor for 160. So 2:23:10 there are two main uh options run a 2:23:12 clear first. So what I told run a clear 2:23:15 first then import the flat file 2:23:16 transaction data and then run that 2:23:19 package. 2:23:21 So it will not allow you to have a 2:23:22 duplicate entry. You can schedule the 2:23:25 package as well like how you are doing 2:23:26 in process chain. So we will just go to 2:23:30 uh means if you want to schedule it 2:23:31 once, twice, daily, weekly, monthly. So 2:23:35 we can do like that also for copying of 2:23:38 uh uh flow type means opening and 2:23:41 closing we are using this approach only 2:23:45 and uh we can able to see the process 2:23:48 chain as well in the BPC that when you 2:23:51 click on this DMP data manager package 2:23:53 which process chain will get triggered 2:23:54 in the BW and for what time it would be 2:23:59 for checking the process chain in the BW 2:24:01 screen we will have a t as RSPC 2:24:05 So just click on that RSBC and you can 2:24:07 able to view your selected uh process 2:24:11 chain and you can view it in data 2:24:15 manager package as well. Data manager as 2:24:18 well. 2:24:20 Okay. So if uh process chain start from 2:24:23 if there is a process which we are using 2:24:25 in BPC so we generally start it from BPC 2:24:28 only like you can see clear transaction 2:24:31 data, copy, export. So these are the 2:24:33 DMPS. So what DMP we will create? It 2:24:36 will create a process 2:24:39 uh there back in the back end as well. 2:24:42 Okay. Yeah. So uh based on these three 2:24:46 we have completed the models, we have 2:24:49 completed the dimensions and we have 2:24:51 completed the data manager packages. 2:24:55 Okay. So this is how uh we will again 2:24:59 once we will have system we'll again go 2:25:01 through this thing like creation of 2:25:02 model, creation of dimensions and the 2:25:05 data manager packages. 2:25:07 Okay. 2:25:08 >> All right. Let's test your knowledge. 2:25:10 Here's a question for you. What is the 2:25:12 primary data source for SAP BPC 10.1? 2:25:16 Option A, flat files. Option B, 2:25:19 relational databases. Option C, SAPBW or 2:25:23 SAP Hannah. Option D, Excel 2:25:26 spreadsheets. Take a moment to think and 2:25:28 when you're ready, choose the correct 2:25:29 option. Remember, each choice holds a 2:25:32 key to unlocking the answer. Good luck. 2:25:34 Type the correct answer in the comment 2:25:36 section. Hey there. Ready to dive into 2:25:39 the world of SAP VPC 10.1. Our course is 2:25:42 your ticket to mastering supply 2:25:44 management, all at your own pace on our 2:25:46 platform. In this course, we'll unravel 2:25:49 the mysteries of SAP VPC 10.1. Think of 2:25:52 it like a Swiss Army knife for planning, 2:25:54 ensuring we've got enough goodies and 2:25:57 getting them where they need to be. 2:25:58 [music] From the basics to expert tips, 2:26:00 we've got you covered. Crafted by 2:26:02 seasoned pros, this course delivers the 2:26:04 goods. Your mentors, top-notch veterans 2:26:07 in the feed, ready to guide you through 2:26:09 and tackle any queries you throw their 2:26:11 way. And hey, [music] don't just take 2:26:12 our word for it. Our students are 2:26:14 singing their praises. Folks just like 2:26:16 you have found this course a game 2:26:18 changer. Best part, it's easy on the 2:26:21 wallet. Learning doesn't have to cost a 2:26:23 fortune. Ready to become a SAP VPC 10.1 2:26:27 [music] maestro? Enroll now. For more 2:26:30 details, visit Zarantex website. 2:26:33 >> So, uh when it comes to BPC, okay, that 2:26:36 is business planning and consolidation. 2:26:39 Okay. And as you are going to work on 2:26:41 10.1 and this is 11.1. Okay. So hardly 2:26:46 there's a few like you know some 2:26:47 difference cosmetic difference right 2:26:49 that also we will cover. Okay. But other 2:26:52 than that functionality logic everything 2:26:55 remains same. Okay. 2:26:58 Now when it comes to BPC business 2:26:59 planning and consolidation SAP has 2:27:02 released this tool. Okay. Having three 2:27:04 components. 2:27:06 One is like this web planning. Okay, 2:27:09 which you can see right now on the 2:27:10 screen here. What one can do whenever 2:27:13 they will login into any BPC server, 2:27:16 this would be the landing page. Okay, 2:27:18 there they can see home library, my 2:27:22 activities. 2:27:23 Okay, second would be EPM which is 2:27:27 enterprise performance and management. 2:27:31 Okay, 2:27:33 you would be once you have EPM installed 2:27:35 on your system, you would be able to see 2:27:37 one additional tabs basically two 2:27:39 additional tabs. One is EPM, second 2:27:42 would be data manager. 2:27:44 Okay, what's the use of this? How we can 2:27:48 work on it? Right, that we will cover 2:27:50 later. But so this is the second area. 2:27:52 Third would be you know your back end 2:27:55 how your data getting stored. So here we 2:27:58 have BW for HANA. Okay. So these are the 2:28:02 three components which covers your PPC 2:28:05 tool completely. The SEP loon pad which 2:28:08 you can see here right once you'll be 2:28:10 log right into this one. This this would 2:28:13 be because it's 11.1 so which runs on 2:28:16 BW4 HANA 10.1 runs on BW 7.5 but what 2:28:22 you have to do what actions you will do 2:28:25 those are most likely same. Okay. So 2:28:27 here as well in the back end it's of BW 2:28:30 plus you would be able to see BPC as 2:28:32 well that we'll show you. Okay. 2:28:35 Basically these three areas which covers 2:28:37 your BPC application. 2:28:40 Okay. Whenever any project comes 2:28:43 whenever any opportunity comes for 2:28:44 planning okay then you know when it 2:28:47 comes to work as a consultant what one 2:28:50 will do they will log on their BPC web 2:28:53 link. Okay. Once you will login on your 2:28:56 BPC web link. Uh so 10.1 screen would be 2:29:00 little different that would be much uh 2:29:02 straighter. Here basically you are in my 2:29:04 activities uh tab. Okay. So in 10.1 you 2:29:09 would be able to see uh right now you 2:29:12 can see go to my activity but there you 2:29:14 would be able to see environment. Okay. 2:29:17 So what is environment? Okay, 2:29:20 environment is basically you know what 2:29:23 what you are going to create your 2:29:25 application whether it's planning 2:29:27 consolidation right that's a shell 2:29:30 environment shell by default it's a SAP 2:29:33 thing which which covers your overall 2:29:36 application so whenever you will be log 2:29:38 into any new system you would be able to 2:29:40 see environment shell okay 2:29:44 so here how to access that go to this 2:29:48 click Click on whatever environment you 2:29:50 can see and this is the environment 2:29:52 shell. By default in any new SAP BPC 2:29:55 system once you log in. This would be 2:29:58 the environment which you will see here. 2:30:01 In a layman term you can understand 2:30:03 environment is nothing. It covers your 2:30:06 overall application. In one environment 2:30:08 you can create many models. 2:30:12 Okay. So this is a practice uh this is a 2:30:14 practice server. Okay. So where you know 2:30:17 different different uh requirements we 2:30:20 are having. So for because of that we 2:30:22 have created it as a embedded but you 2:30:25 would be able to see only standard okay 2:30:28 in your company server as well as to any 2:30:30 BPC 10.1 11.1 classic version or 2:30:34 standard version okay so around the 2:30:36 globe mostly standard one is the most 2:30:39 you know uh most kind of a common and 2:30:42 preferable server which any client goes 2:30:45 for right because that's much uh 2:30:48 straighter and that's good for planning 2:30:50 The difference between embedded is that 2:30:52 embedded is mostly for BW consultants. 2:30:56 So when it comes to embedded so mostly 2:30:58 BPC consultants get rely on BW 2:31:01 consultants because of lot of B BW 2:31:03 dependent functionality that's the 2:31:05 reason standard one uh is the most you 2:31:08 know common one and the popular one. 2:31:10 Okay. So for a time being you can ignore 2:31:12 all the other environments which you can 2:31:14 see but whenever you will be able to 2:31:16 login into a new system you would see 2:31:18 environment shell that is the first 2:31:21 thing you would observe in any VPC 2:31:24 system. Okay. Now the thing is that uh 2:31:28 this is environment shell. Okay. Now 2:31:31 there are two things uh which uh you 2:31:34 know I think I can cover but uh like can 2:31:37 you help me to understand that any of 2:31:39 you is going to play a consultant role 2:31:41 or only a user role you are going to 2:31:44 play in your company because the 2:31:45 activity which I'm going to discuss that 2:31:47 is more about consultants since you have 2:31:50 mentioned that like most of you would be 2:31:53 playing consultant roles so let me show 2:31:55 you this exercise so when you will be 2:31:57 able to see a new system okay so Right? 2:32:01 Now you are in environment shell. Okay. 2:32:04 Now what you need to do you know that 2:32:07 okay you have to create a planning 2:32:09 implementation right you have to work on 2:32:11 implementation for planning let's say 2:32:13 then you need to have your own model so 2:32:16 that you can design the system 2:32:17 accordingly. You can although create 2:32:20 your models and everything in 2:32:22 environment shell but that is not uh 2:32:24 recommended 2:32:26 because environment shell 2:32:28 is the environment uh shell which is 2:32:31 very common having lot of you know 2:32:34 libraries and all which is mostly 2:32:36 technical. So that actually helps you 2:32:39 when you do backup and restore of your 2:32:41 application. So what you can do when you 2:32:44 are working uh so normally when you 2:32:45 start as a consultant you would see 2:32:47 three instances. One is development, 2:32:50 second is quality, third is production. 2:32:53 So when you do in development system you 2:32:56 do the development in quality you do the 2:32:58 testing. Once you are ready with your 2:33:00 application, you move your application 2:33:02 from development to quality. Okay. When 2:33:05 you move then you get many issues right 2:33:08 during that activity. So to avoid all 2:33:11 such things and to not to you know 2:33:14 modify or having a negative impact on 2:33:16 standard environment shell what we 2:33:19 recommend to create your own environment 2:33:21 shell so that you can easily move for 2:33:23 example ROA is having a different server 2:33:27 and you are having a different server 2:33:29 okay so it's better to create a 2:33:32 different different environment uh not 2:33:33 for every model but at least if there's 2:33:36 a you know different server or having 2:33:37 other dependency so that anytime you 2:33:40 feel that you want to move it to 2:33:41 quality, you can move it. You don't need 2:33:43 to depend on other uh team members 2:33:46 whether when their application would get 2:33:48 ready only then you can move it. Okay. 2:33:51 So how to do how to do that? So for that 2:33:54 go to environment. Okay. 2:33:57 Click on environment. 2:33:59 Right. Here you can go manage all 2:34:04 environments. So this screen would be 2:34:05 exactly same to 10.1. 2:34:08 Click on environment shell. Okay. Click 2:34:10 on copy. And there you can give any any 2:34:14 name. Let's say planning. Okay. 2:34:18 Planning. Any any suggestion, any 2:34:20 nomomenclature you would like to 2:34:22 suggest. What you can do? You can uh you 2:34:25 know give a name of your company. Okay. 2:34:27 Or of your division here as well. So 2:34:30 let's say I'll I'll I'll put it as like 2:34:33 uh uh XYZ. Okay. For a time being. And 2:34:38 here you can just give a description or 2:34:41 you can skip this and you hit on copy. 2:34:43 Then what system does it will start 2:34:46 copying the environment. Okay. Normally 2:34:49 in a new system or in a company specific 2:34:52 system because environment number would 2:34:54 be less right system can create 2:34:57 environment very easily but sometimes in 2:34:59 practice systems although this is a 2:35:01 one-time activity you don't need to do 2:35:03 that but I'm showing you so that you it 2:35:06 would be useful for you in future 2:35:07 whenever you have to create it okay so 2:35:10 whatever planning we'll be doing we'll 2:35:11 be doing under this environment okay so 2:35:14 let's try okay I hit copy 2:35:18 sometimes error also comes because it's 2:35:20 a copy it's a you know server it's a 2:35:22 practice server so but don't have you 2:35:25 know think that what's happening because 2:35:27 this is the standard and only way to 2:35:29 create any environment 2:35:33 so you can see when we are creating the 2:35:36 environment our own environment okay 2:35:38 which is nothing but we are copying the 2:35:41 standard environment shell so what is a 2:35:43 standard environment shell uh we'll 2:35:46 discuss but you can see flow entity, 2:35:49 category, account. Okay. Now, what are 2:35:52 these? We will take uh later. So, some 2:35:57 activities going on. 2:36:16 So that's in prog progress and it 2:36:20 depends on the speed of the server as 2:36:22 well. Okay. But it won't take much time. 2:36:26 It will be done soon. Okay. So you can 2:36:28 see we have created a environment our 2:36:31 own environment which is planning_xyz. 2:36:35 So this is the environment which we have 2:36:37 created. Okay. Similarly when you are 2:36:39 going to have a planning implementation 2:36:41 or something this is the first activity 2:36:43 recommended activity to do that. Okay. 2:36:47 Now what environment does right so 2:36:52 whatever activity we will do whatever 2:36:54 application we will build reports 2:36:56 dimensions our data everything would get 2:36:59 reside under this planning_xyz 2:37:02 so how does it plays a role whenever we 2:37:06 you know move anything from development 2:37:08 to quality okay you would see lot of 2:37:11 time that it's recommended to always 2:37:14 applying your environment right now you 2:37:16 can see These environments are online 2:37:18 right you can see online online online 2:37:22 right so that's a prime activity when 2:37:25 you move any data I mean any any object 2:37:27 from your development system to quality 2:37:29 system and so on to production you 2:37:32 always need to at least uh make it 2:37:35 offline while taking the backup and 2:37:38 restore that also we'll see okay so if 2:37:42 uh if I don't cover this then for 2:37:44 consultants sometimes it becomes a 2:37:46 tricky area that okay what exactly needs 2:37:48 to do because they never interacted on 2:37:50 this area. They simply just log in and 2:37:53 start building anything on environment 2:37:55 shell and if environment shell is having 2:37:57 issue your whole application everything 2:38:01 comes under you know that area where you 2:38:03 can't do anything. So it's always 2:38:06 recommended to have a separate 2:38:07 environment in case if anything needs to 2:38:10 be changed or modified at least you have 2:38:13 your safe environment shell. So is it 2:38:16 clear right now? You can see it's 2:38:18 online. What we can do just click on 2:38:20 this one and click on connect. Okay. So 2:38:25 since it's 11.5 it's a little bit faster 2:38:29 as compared to 10.1. So you can see now 2:38:32 we are in our own planning XYZ 2:38:35 environment. Here you can't see but in 2:38:37 10.1 you would see at the right bottom 2:38:40 of the screen. Okay. But if you click on 2:38:44 this one you can see planning_xyz. 2:38:48 So far is it clear to everybody that 2:38:51 what is environment how we can create it 2:38:54 how we login and how we connect into it. 2:38:57 So now 2:38:59 we have our own area okay area I I'll 2:39:02 refer environment shell or you know our 2:39:04 own environment as our area our zone 2:39:07 where we can do our planning. Okay. So 2:39:10 what we have to do here some of the 2:39:12 options are different as compared to 2:39:13 10.1 but they are just uh they are 2:39:16 similar but just a look and feel look 2:39:18 look and feel is little bit different 2:39:21 but the functionality remains the same. 2:39:23 Here you can see administration but if 2:39:25 you if you click on 10.1 when you click 2:39:28 on uh top left corner you would be able 2:39:32 to see models dimensions right security 2:39:35 but here it's a bit different. So here 2:39:37 we have administration. Okay. So for 2:39:40 consultants this is the important area 2:39:43 administration where what they do they 2:39:46 create their own application they build 2:39:48 the logic which works on the dimensions 2:39:51 which works on you know particular model 2:39:54 right they apply roles securities 2:39:56 everything comes under this area. Okay, 2:39:59 this my activities for the users which 2:40:02 we'll discuss later when you define that 2:40:04 what exactly what kind of activities one 2:40:07 needs to perform so that whenever they 2:40:09 login into this landing page they will 2:40:11 see simply my activities or notification 2:40:15 where they'll be approving or rejecting 2:40:17 some request that's it. So that depends 2:40:20 on consultants what right they gives to 2:40:23 other users. Okay. So this is the area 2:40:26 which covers your overall planning and 2:40:29 overall uh BPC application. Okay. Now 2:40:33 here we can see dimensions and models. 2:40:37 If I click on this I can see first 2:40:40 dimensions then models. Okay. The master 2:40:44 data but other than master data what 2:40:47 does dimension covers? Uh so that is 2:40:50 that actually answers that question what 2:40:51 it covers. But what is dimension? So 2:40:54 I'll I'll start on dimensions. So guys 2:40:56 like uh in normally SAP module other 2:41:00 than EPM. So this SAP BPC is related to 2:41:04 enterprise performance management. Okay. 2:41:07 If we keep it aside or you know keep uh 2:41:11 some of the modules which are not the 2:41:13 standard one. So if I talk about 2:41:15 standard one modules of SAP those are 2:41:18 SAP FICO MM SD right they all in in all 2:41:24 of them right what's the common thing is 2:41:27 that when it comes to master data master 2:41:29 data is residing under a particular 2:41:31 table right as you as uh as you 2:41:34 mentioned company code right so that is 2:41:37 getting stored under a particular table 2:41:40 right based on that a web consultant 2:41:43 creates create some program logic or 2:41:47 functional consultant does the 2:41:48 configuration. Okay. And then you'll be 2:41:51 able to see your screen which is good to 2:41:53 capture any transaction which are 2:41:56 happening at company level or at company 2:41:57 code level. Okay. But when it comes to 2:42:00 BPC okay so BPC is not a transactional 2:42:05 system. Okay. This is a reporting 2:42:08 system. This is mainly for the 2:42:10 management for MIS reporting which 2:42:13 fulfills MIS reporting needs. This is 2:42:15 for the CFOs. Okay. Now 2:42:20 if it's not a transactional system then 2:42:22 how does it work right? 2:42:25 So any in any system in the world okay 2:42:28 that is having two type of datas. One is 2:42:32 master data second is transactional 2:42:35 data. Transactional data is nothing just 2:42:37 a figure which lies at the intersection 2:42:40 of the master data. Similarly, if I talk 2:42:44 about dimensions, okay, so in VPC, 2:42:47 there's no standard tables which will 2:42:49 capture a data for your business or for 2:42:52 your client, right? So you have a 2:42:56 dimension concept, right? So dimensions 2:42:59 are like a info objects in terms of BW 2:43:02 if I speak. Okay? if I say sorry. So 2:43:06 that is like a info object right in BW 2:43:10 but I believe if you don't know BW then 2:43:13 again it's a kind of a different term 2:43:14 for you. So I'll I'll explain it in a 2:43:17 very very easy and common uh term. Okay. 2:43:21 So doesn't matter from which place or 2:43:24 which country anyone is. I believe 2:43:26 everybody is aware about the bank 2:43:28 statement. So [clears throat] what does 2:43:30 bank statement covers? Your name, right? 2:43:35 Your bank location, your transaction 2:43:38 detail, 2:43:39 right? Your account number. So what's a 2:43:43 unique information in your bank 2:43:45 statement, your account number, right? 2:43:48 Because 2:43:49 >> a person with the same name, with the 2:43:52 same entity is possible, right? But he 2:43:55 can't have a same account number, right? 2:43:58 He can't have the same multiple account 2:44:00 number. Right? So account number is 2:44:02 unique thing. So when I talk about 2:44:04 account number, customer name, bank 2:44:07 location, transaction amount, currency, 2:44:11 time, right? All these are independent 2:44:15 terms. But this is creating a a meaning 2:44:20 to $100, right? Let's say a guy named 2:44:25 Nick having a $100 who has done 2:44:28 transaction at so and so time from taxes 2:44:32 location. Right? So all these 2:44:34 informations form the bank statement. 2:44:38 Similarly, what are dimensions? 2:44:42 Dimensions are nothing but that covers 2:44:46 you know your business, 2:44:49 right? Your business. uh if I talk about 2:44:51 business areas not like business area of 2:44:54 SAP Eco but you know your I can I I can 2:44:58 say like what is dimension okay see your 2:45:02 profit and loss statement right if you 2:45:04 see that okay what you would observe 2:45:06 that okay my my income my expenses right 2:45:10 what are the drivers for those right 2:45:13 based on that you need to identify your 2:45:15 dimensions and in in the end what should 2:45:19 happen that your business for which 2:45:21 you're going to plan for that everything 2:45:24 should fall within your dimension. It 2:45:26 shouldn't happen that okay something is 2:45:28 required for your business but that is 2:45:31 not getting covered in that in your 2:45:32 dimension if that is the situation you 2:45:35 would not be able to plan your system I 2:45:38 know right now it's hard to understand 2:45:40 like okay what is dimensions because I'm 2:45:43 not talking about any bookish term or 2:45:45 you know any any anything it's totally 2:45:49 related to practical right so I'll show 2:45:52 you 2:45:54 if you go to dimensions 2:45:56 Okay. Now what you can see here account 2:46:00 audit trail category entity flow input 2:46:05 currency right so when you create a 2:46:10 model right some type of dimensions you 2:46:13 need to create okay so before that we'll 2:46:17 see that what does it covers okay 2:46:21 so for example if I go to account 2:46:23 dimension this is standard dimension 2:46:25 Okay. What it has ID? These are the 2:46:30 members. Okay. Which you will be able to 2:46:32 see in your reports. At this level, 2:46:35 you'll be able to do the planning. Okay. 2:46:38 There's a description. Okay. This is 2:46:40 simply like a SAP table. You can see 2:46:42 right GL accounted stores. Now, after 2:46:46 description, whatever column you can 2:46:48 see, this is called or referred as 2:46:51 property of a dimension. 2:46:54 what you can refer it as a property of a 2:46:57 dimension. Okay? Or in BW term you can 2:47:01 say it as a characteristics of a 2:47:03 dimension. 2:47:06 So account is a dimension right which is 2:47:10 very important dimension for any any BPC 2:47:13 or any EPM tool. Okay. So by default 2:47:16 system has generated couple of kind of 2:47:20 properties which you should focus here 2:47:23 which you should focus upon account 2:47:25 type. Now what does account type 2:47:27 suggest? 2:47:28 It tells you about the nature of a 2:47:32 account. Okay for example balance sheet 2:47:34 it's of asset type. Okay. So right now 2:47:38 it's a standard one. So system has 2:47:40 already created it. But when you'll be 2:47:42 creating for any project or for your 2:47:45 company right then you'll be able to 2:47:49 fetch it from SAP system as a master 2:47:52 data okay there if they have maintained 2:47:55 it then you can see that else you need 2:47:58 to maintain it manually or you can 2:48:00 upload the master data from Excel sheet 2:48:03 and then you have to check here that 2:48:06 okay is it mapped against the against 2:48:08 the correct account type or not right 2:48:11 what's the impact it's having that we'll 2:48:13 cover in our reporting area. Second is 2:48:15 like you can see it's having like rate 2:48:18 type by the closing average right 2:48:22 so these are kind of a 2:48:25 standard properties which are associated 2:48:27 with the dimension called as account 2:48:31 okay and this is having a hierarchy. So 2:48:35 there are two kind of a dimensions okay 2:48:39 one is like you know the system 2:48:41 generated one second is like userdefined 2:48:45 okay for userdefined you would be see 2:48:48 able to see this as user defined U1 okay 2:48:52 and for all the standard one you can see 2:48:54 easily type as account audit category 2:48:57 entity and currency so that was about 2:49:01 the base of a dimension now how to 2:49:03 create the dimension what we can do on 2:49:05 dimension that that we'll see in some 2:49:08 time but before that is it clear that 2:49:10 what is dimension how it works I mean 2:49:14 how it works I'll I'll take it further 2:49:16 but uh what is it that's about dimension 2:49:19 but how to create a dimension right 2:49:22 that's a major activity which keeps on 2:49:24 coming at consultant's end okay now why 2:49:29 does it keeps on coming because in any 2:49:31 BPC planning project what happens you 2:49:34 know You start to build your 2:49:36 application, you start to build your 2:49:38 system, right? And during the build you 2:49:42 realize that okay your data is also 2:49:44 coming uh you need a data at so and so 2:49:47 level. So for that that information is 2:49:50 not getting captured in your existing 2:49:51 dimension. So you need to create a new 2:49:54 dimension again. So that's why you 2:49:56 create a new dimension. In other tools 2:49:58 like Hyperion, Oracle system doesn't 2:50:01 allow you in between. in VPC you can do 2:50:03 but some exercise also needs to be 2:50:05 performed as a prerequisite that also 2:50:08 we'll cover later okay so how to create 2:50:12 a dimension okay 2:50:15 click on new and create 2:50:19 any idea uh any ID you can create it 2:50:23 like uh I can create my own dimension by 2:50:28 my own name okay I all I have to do is 2:50:31 like I have to choose Choose what kind 2:50:32 of a type this dimension would have so 2:50:36 that associated properties standard 2:50:38 property I don't properties I don't need 2:50:41 to create they will be created by 2:50:43 default only I need to change it for 2:50:45 example if I create it here as like 2:50:48 planning 2:50:50 let's say planning account okay now 2:50:54 there are these type of dimensions I can 2:50:57 see right type of dimensions category 2:51:00 audit entity through currency subtables 2:51:04 time and user defined. So which type of 2:51:09 account dimension I should select from 2:51:11 this list? It should be account. But in 2:51:14 caseh if I don't want to create it for 2:51:17 like you know as a standard one then I 2:51:20 can go for userdefined. 2:51:22 Okay. So for a time being let's go for 2:51:25 account and I click on create. So this 2:51:29 is the screen where we came now. Okay. 2:51:32 What it has it's having properties as 2:51:35 account type okay rate type scaling 2:51:39 scaling is just how you are showing in a 2:51:41 report right now what it has okay it's 2:51:46 asking from referential integrity for 2:51:49 rate type okay I can select here right 2:51:53 we will we'll discuss here uh we'll 2:51:55 discuss later uh in our model part about 2:51:57 this one but now it's saying it's it's 2:52:01 asking for hierarchies. Okay, if you 2:52:04 want to create any hierarchy, we can 2:52:07 give any any name. Okay, like add and 2:52:12 you can give like parent 2:52:15 one. Okay, and save it. Any name you can 2:52:21 give of this hierarchy. Go to back. 2:52:26 Click on back. Now what you can see need 2:52:28 to be processed. 2:52:30 Okay. Select your dimension again which 2:52:33 you have created and click on process. 2:52:38 Do you want to take environment offline? 2:52:40 I know that. Okay. I'm not moving any 2:52:42 object, nothing. Right? So I can select 2:52:46 no. Now what it will do? It will process 2:52:49 the dimension. 2:52:51 But understand here when you'll be doing 2:52:53 processing it's not uh you know uh that 2:52:57 easy. Many times you would observe few 2:52:59 errors. Okay. So you need to you know uh 2:53:04 clear those errors then only you'll be 2:53:06 able to see this process. But what about 2:53:09 if it never get processed by this one 2:53:12 then there's another way as well which 2:53:14 uh will get covered into models. So this 2:53:18 is how we can create our dimension 2:53:20 called account. Now let's go into a 2:53:21 planning account. Now what it's having 2:53:24 it it's having nothing. It's a blank 2:53:26 dimension which we have created. Right? 2:53:28 We have a option of creating a cop 2:53:31 creating a dimension with members by 2:53:34 copying the dimension as well. Okay. Now 2:53:38 we have created a hierarchy with the 2:53:40 name as parent one. Okay. You can see 2:53:43 here we have we have given it name as 2:53:46 parent one. That's why it's showing 2:53:47 parent one as a hierarchy. Okay. Now how 2:53:50 does it work? Okay. So now what I'll do 2:53:53 I'll I'll create a dummy account. Let's 2:53:56 say it is like GL 0001. 2:54:00 Okay. And I can mention here any any 2:54:04 description you can give it. Okay. Inc 2:54:08 stands for income account. Okay. In 2:54:11 parent I won't do anything. Okay. Now 2:54:14 again I'll create a different account 2:54:16 which is like GL00002. 2:54:20 If I try to create a account with the 2:54:23 same name, 2:54:25 should system allow me? Definitely not. 2:54:28 But sometimes you know when we populate 2:54:30 the data or uh you know we we pull the 2:54:34 data then uh you know we do some mistake 2:54:39 by transformation file and all and then 2:54:40 system won't allow us right? If you see 2:54:43 here it would say like ID is not unique. 2:54:47 Okay. So it should be unique as I made 2:54:51 it unique system has turned red into 2:54:54 green. Okay. 2:54:56 So now we have GL00001 002003 2:55:01 right. It doesn't have any parent all 2:55:05 are children member or all are you know 2:55:08 independent members right? But if I 2:55:12 create another account uh the name like 2:55:15 let's say GL 2:55:18 and I put here suppose this is the this 2:55:23 is normal member right but if I have to 2:55:26 I want that 001 and 003 should fall 2:55:30 under this one what I need to do I'll 2:55:33 I'll mention here gl 2:55:36 parent name Okay. 2:55:43 Now what I need to do I'll click on save 2:55:46 and process. Do you want environment 2:55:48 offline? Say no. So my dimension has 2:55:52 been processed. Okay. 2:55:55 So when you see this data okay 2:55:59 whatever you can see under the dimension 2:56:01 this under the column ID we refer them 2:56:04 as a member. Okay. What is it member? 2:56:07 It's a member of a dimension. Okay. 2:56:11 What are the other columns? Account 2:56:12 type, rate types. These are the 2:56:14 properties, right? Property member inc. 2:56:17 Okay. And 2:56:21 to a dimension overall GL dimension, we 2:56:23 call it as a master data, right? This is 2:56:26 our master data. So you can see we have 2:56:28 created it parent as GL00. Right? Now 2:56:32 what does it do? Right? How we can see 2:56:35 that? So if we go here and click on 2:56:39 hierarchy, 2:56:41 we can see a hierarchy view. If I expand 2:56:45 it further, then I can see GL00001 2:56:47 GL00003. 2:56:50 If I have to change the structure, I can 2:56:52 go back to list. So this is how you can 2:56:56 create a member and this is how you can 2:56:58 create a hierarchy. Okay, which will 2:57:00 play key role in your reporting and in 2:57:04 your requirement. Okay. Now here couple 2:57:07 of things uh I need to share with you. 2:57:10 Okay. So when you create a create a 2:57:13 member ID. Okay. Always try to create a 2:57:18 you [snorts] know a very straight one 2:57:20 and easy to understand kind of a ID 2:57:22 members. Avoid using you know many 2:57:25 underscore in that because system won't 2:57:28 allow you after some time. Plus if you 2:57:31 have included capital letter here, 2:57:33 right? Make sure because VPC is a 2:57:37 case-sensitive tool. Okay? When you will 2:57:41 pull the data from master uh from SAP, 2:57:44 okay, when you will update any master 2:57:45 data, any transactional data to a flat 2:57:48 file, you would have lot of issues 2:57:51 because of this case sensitiveness. So 2:57:53 always make sure you use the correct and 2:57:55 the same name which you have used 2:57:58 already in your members. For example, in 2:58:01 order to create a parent one, right? I 2:58:03 use the same name in the same case 2:58:06 sensitive format, right? It's in 2:58:08 everything is in capital letters GL. 2:58:11 It would have been GL in small then it 2:58:14 would not recognize it. Okay. Let's say 2:58:19 you have GL 2:58:21 003 2:58:23 uh sorry not three 004 2:58:27 okay 2:58:31 let's say you have this much of data 2:58:33 okay what you can do either you can copy 2:58:37 directly simply copy it go here 2:58:42 and click on add and just paste it here 2:58:45 right system would allow you to do copy 2:58:48 Copy paste. Else what you you can 2:58:51 directly copy whole Excel in one go and 2:58:53 just put your cursor here and paste 2:58:55 here. Okay. Or you can upload the Excel 2:59:00 file which you have. Okay. That that is 2:59:03 known as flat file upload in the 2:59:06 dimension that also you can do. Okay. 2:59:15 Since we have like uh copied the cells 2:59:19 so 2:59:20 it's better that at least I 2:59:23 put the properties and we can use it 2:59:26 further as well for our testing. 2:59:45 Okay. So what we have done we have 2:59:48 created few members. Okay. We have added 2:59:51 property description. We are skipping 2:59:53 for a timing. Okay. And then we have 2:59:56 created few parents as well. Okay. We 2:59:59 have tagged few members with the 3:00:00 respective parents. And let's see how 3:00:03 system goes. 3:00:05 If I click on this. Do you want to take 3:00:08 environment offline? Click on no. 3:00:11 So this time IDE system shouldn't allow 3:00:13 me. So you can see it's not allowing me. 3:00:16 Now if I see the details 3:00:19 what what you can see. So guys uh we'll 3:00:22 be also taking all those try to you know 3:00:24 take those issues which you would have 3:00:26 have in your you know uh implementation 3:00:29 days so that you would get some 3:00:32 experience as well and because uh this 3:00:34 training purpose is not just to covering 3:00:36 the sessions right it should also give 3:00:39 you some exposure right okay now what 3:00:43 kind of error we can see first is like 3:00:46 start validating member formula and 3:00:49 validating the member hierarchy. Okay. 3:00:52 The member changes are allowed by BPC 3:00:54 component so and so. So mostly it's 3:00:57 related to and validating member 3:00:59 formulas. Okay. Now can anybody tell me 3:01:03 that? Okay. Because we have already 3:01:05 created these as a members, right? Why 3:01:08 system is throwing in the error? I'll 3:01:10 make it more easy for you. We have 3:01:13 already created GL00001 3:01:16 002 and GL 0, right? 3:01:21 Then why there's error coming here? So 3:01:24 you can see even this this sounds or 3:01:26 when you look at it it looks very small 3:01:28 issue but it can you know take a lot of 3:01:32 time during implementation because you 3:01:35 know there would be a lot of pressure of 3:01:37 you know timelines or creating something 3:01:39 then consultants miss this and they tend 3:01:43 to lose time that okay system is not 3:01:45 allowing you something is happening 3:01:47 right. So always make sure that you use 3:01:51 the correct uh characters. If that's in 3:01:54 capital letters, same should be 3:01:56 maintained in in that way here as well 3:01:58 in the system. Else it would give you 3:02:01 error. Then again I'll come here. I'll 3:02:03 click on save and process. Then system 3:02:06 will again show me the same error. It 3:02:08 won't take much time. So you can also 3:02:11 cross check again here from in the same 3:02:13 way while doing the same thing. Now this 3:02:16 time should system would allow me. See 3:02:19 dimension has have been processed. Okay. 3:02:23 All you can always see the details here. 3:02:26 Okay. Now we have created few more 3:02:29 members. We have seen what role the list 3:02:32 is playing. Now we have created more 3:02:35 parents. Right? Let's see how our data 3:02:37 looks uh looks now right now. Okay. So 3:02:42 what we can see now we have three kind 3:02:44 of hierarchies GL0000 3:02:47 GL00002 3:02:49 and GL005 3:02:51 okay if I expand it further 3:02:54 I can see it's having 8 9 10 3:02:57 if I go here I can see 1 and 3 on 3:03:01 further expansion I can see 6 and 7 3:03:05 falls into one 3:03:08 and GL0 11 falls under tree 3:03:13 and this is what so you can see that you 3:03:17 know how this parent hierarchy you know 3:03:20 creates a impact on your dimensions 3:03:24 design which you creates. Okay. So that 3:03:28 gives uh you know a better 3:03:31 look and feel is as compared to the list 3:03:33 view because in list view right it's 3:03:35 hard to understand until you have 3:03:37 experience right you you can't 3:03:39 understand what's happening what's 3:03:40 parent one right but when you see the 3:03:42 hierarchy right although now you can 3:03:44 understand it because you know the 3:03:46 concept now but if you see here right 3:03:49 you can easily see because of this 3:03:50 pictorial representation that okay 8 9 3:03:53 10 are the members or the children of a 3:03:56 parent 002 Right now you know that okay 3:04:00 how to create this dimension how to 3:04:02 create parent how to create properties 3:04:05 what role they play right now let's 3:04:07 understand what's happening when I 3:04:10 create a create a particular member as a 3:04:13 parent others as a children right whom 3:04:17 I'm referring to as a children those are 3:04:19 falling under a particular 3:04:22 parent node right so the parent node 3:04:25 like GL00002 is a parent. Okay. GL00008 3:04:29 910 are the children of the parent. 3:04:32 Okay. So, BPC is a tool or maybe mostly 3:04:35 EPM tool would use such hierarchy. I 3:04:38 mean uh such terminology which you would 3:04:40 be able to hear like parent and child 3:04:43 relationship or it's like you know or in 3:04:46 terms of SAP roa I can say in terms of 3:04:49 fico it's like you know group GL or 3:04:51 subgl also right but now what's the 3:04:55 difference here is that if you will be 3:04:58 able to or if you try to save anything 3:05:02 okay if you do any posting any trans any 3:05:05 transaction okay at GL00002 level or to 3:05:10 at any parent level system won't allow 3:05:13 you BPC system won't allow you to do 3:05:18 that okay where you can save the data 3:05:21 only at the children level 3:05:25 okay that is 008 9 10 I know that uh you 3:05:30 know you you are thinking that how what 3:05:32 I'm talking about all of a sudden right 3:05:35 because if you're talking about parent 3:05:36 and child relationship then this is just 3:05:39 to know later you will see and realize 3:05:41 that okay how the system is working so 3:05:44 in BPC you can't save the data at parent 3:05:47 level right you can only save the data 3:05:50 at children level so that's why it's 3:05:52 very important whatever 3:05:55 you know uh report you are having or 3:05:59 input form right you will be able to you 3:06:02 are inputting the data at the base level 3:06:05 or at the children level only else 3:06:08 system won't allow you. So far we have 3:06:10 seen that how to create a account 3:06:13 dimension. Okay. Now if I have to create 3:06:16 a customized dimension let's say. Okay. 3:06:20 So for customized dimension I can take 3:06:24 and I can create anything. Let's say 3:06:27 I'll I'll create as a model. Okay. any 3:06:32 any description and here you would 3:06:35 select userdefined 3:06:38 because you know that it's a customize 3:06:40 as per your requirement you are creating 3:06:42 so you need to create a userdefined when 3:06:45 you will create it system would not 3:06:47 create any standard property or 3:06:51 characteristic properties and 3:06:52 characteristics are same characteristic 3:06:55 I'm referring in terms of BW terminology 3:06:58 property I'm referring in terms of BP 3:07:01 PPC tool. Okay. So if I click on create 3:07:05 now here 3:07:07 what I can see scaling is just you know 3:07:10 number of zeros which you can see in 3:07:12 your report or that depends on your you 3:07:14 know look and feel. But other than that 3:07:15 you are not able to see any property 3:07:17 here. There's no property. It's 3:07:20 completely blank. Right? That's the 3:07:23 difference between the standard 3:07:26 dimension and in the userdefined 3:07:28 dimension. For any requirement during 3:07:31 any implementation phase or project 3:07:33 phase, you feel that okay you want to 3:07:35 have the data but you don't know under 3:07:38 what category that data should fall. 3:07:41 Okay. Then you create a userdefined 3:07:45 dimension which is a customized 3:07:47 dimension. Okay. later if you realize 3:07:50 that okay some of the properties which 3:07:52 you need you can create it in your way 3:07:54 or you can copy as well okay so this is 3:07:58 my customized dimension I won't do 3:08:01 anything here if I have to create like 3:08:04 uh any anyone asked me that uh can we 3:08:08 create a multiple hierarchies you can 3:08:10 create multiple hierarchy as well 3:08:16 okay click on Save. 3:08:21 Now this is what we have created model. 3:08:23 Right? Now what it says need to be 3:08:26 processed. So if if there would be any 3:08:30 error okay in the dimension when you 3:08:33 created it even if you process it it and 3:08:36 if it turned into red or in the same 3:08:38 zone then it means there's some issue in 3:08:41 the creation. how you can uh rectify 3:08:44 that that we'll uh see later. Okay. But 3:08:48 let's say if I have to process it what I 3:08:51 need to do I I have to select it and 3:08:55 then hit process. Select no. 3:09:00 Okay. Now it has turned to green. You 3:09:04 can see processed. 3:09:06 If we go there what we can see there's a 3:09:11 blank dimension called as model and 3:09:15 having two parents parent one parent two 3:09:19 and let's say if I create a member okay 3:09:28 you can also practice at your end by 3:09:30 creating many dimensions 3:09:33 Okay. 3:09:43 Okay. I hit on save and process. 3:09:48 So my dimension got processed. And if I 3:09:51 click on hierarchal view. 3:09:54 So what I can see one ABC right now. 3:09:58 This this this I can't see anything 3:10:00 else. So I'll go again. 3:10:03 >> [bell] 3:10:04 >> Now why I'm not able to see it as a 3:10:07 parent 3:10:09 10,000 as a parent. 3:10:12 Now we are clear about the dimensions. 3:10:14 How to create the dimension? Okay. Now 3:10:17 we move towards model. So what is model? 3:10:23 So functionally functionally you have uh 3:10:26 very well uh you know articulated that 3:10:29 uh our structure right. So technically 3:10:33 what my structure is? My structure would 3:10:36 be based on my dimensions. 3:10:39 Okay. A model is you know uh I can say a 3:10:46 view or a overall area which will 3:10:49 encapsulate my 3:10:52 application right in environment shell 3:10:55 it would be my model right. So my model 3:10:58 would be dependent on would be created 3:11:01 based on my dimensions. Okay. So I'll 3:11:07 one thing more because I'll be referring 3:11:10 model many time. I don't want you guys 3:11:12 to get confused because of this one. 3:11:16 Let it be. Okay. Now model. Okay. 3:11:22 So if you have observed here right under 3:11:25 administration the first thing you can 3:11:27 see is a dimension because that's the 3:11:29 first thing which one needs to 3:11:31 understand what role does that play 3:11:34 right what's the use of that and then 3:11:36 only we can see models right so model is 3:11:42 my structure of the application right 3:11:45 which is made up of 3:11:48 my dimensions okay so I can create any 3:11:53 kind of a model. Okay, for example, 3:11:56 planning model, rate model, ownership, 3:11:59 consolidation, you can see here, right? 3:12:02 Now, what's the difference between 3:12:04 these? Okay, 3:12:07 in any EPM tool, right, uh when it comes 3:12:10 to do planning, right, that's the most 3:12:13 uh unknown part, right? And it it goes 3:12:17 uh you know client to client that okay 3:12:21 how one can do planning in what way 3:12:23 right because there are n number of uh 3:12:26 ways to do any planning but when it 3:12:28 comes to consolidation consolidation is 3:12:30 very standard 3:12:32 uh pack which SAP has released right 3:12:35 there are particular ways which you need 3:12:37 to follow right 3:12:39 correct so not like consolidation 3:12:42 planning is very open area right which 3:12:45 you can create it in your own way. Okay. 3:12:48 Now what's the difference? 3:12:50 If I click on planning, this is the 3:12:52 standard model. Okay. 3:12:55 When you create a model which is a 3:12:58 combination of the dimensions, right? 3:13:00 You can see to the right side model 3:13:03 containing exchange rates. Right? Here 3:13:06 you can see rates as a model. Okay. If I 3:13:10 go to consolidation, 3:13:13 what extra thing I can see here? Other 3:13:16 than rates, I can see ownership as well. 3:13:19 Okay. 3:13:21 Now, what is ownership and all that? 3:13:23 We'll discuss during the consolidation 3:13:25 part. But in consolidation, whenever you 3:13:28 do consolidation for any company, right? 3:13:31 Whether the company is having a 3:13:33 subsidiary or holding company, that 3:13:35 relationship needs to be defined. Okay? 3:13:38 For that we have ownership model where 3:13:40 there's a data and then we can use uh 3:13:43 ownership we can create a ownership 3:13:45 structure in our uh consolidation 3:13:48 right so for that we have a consolid 3:13:52 ownership model as well okay similarly 3:13:55 if I go to rates then I have a rate 3:13:58 model as the name suggest rates it 3:14:02 contains exchange rates so what kind of 3:14:06 a dimension you can See category, 3:14:10 currency, account, entity and time. 3:14:14 These the combination of these dimension 3:14:17 forms a structure. That structure 3:14:23 refers that what kind particular kind of 3:14:25 a model it is. So this is relative to a 3:14:28 rate model because it's having a 3:14:30 currency it's having a rate related 3:14:32 accounts rate related entity time as 3:14:35 well as category. Okay. Anyone having 3:14:39 any idea about category? 3:14:41 Okay. So category is a type of a 3:14:45 dimension. Okay. So uh guys as I have 3:14:48 suggested you you can you know login 3:14:50 into your server you can create few 3:14:52 dimensions. There you will be see able 3:14:55 to see that okay other than account 3:14:58 there are other uh dimensions as well 3:15:00 which are standard ones right what 3:15:02 difference that is having that's the 3:15:04 difference of the properties which 3:15:05 you'll be able to see so category what 3:15:08 does category contains it contains what 3:15:11 kind of a data I have whether this data 3:15:14 is actual data budget data or forecast 3:15:16 data so basically nature of the data 3:15:20 this dimension covers so we refer it as 3:15:23 category. Okay. Now if I have to create 3:15:28 my model. Okay. How I can create my 3:15:30 model? There are couple of ways to 3:15:32 create the model. Click on new. 3:15:35 Okay. Any any I any anything you can you 3:15:40 know uh give any name. Let's say 3:15:45 planning is already there right? I can 3:15:48 give like XYZ 3:15:51 planning. This is the name of my model. 3:15:54 Okay. 3:15:56 Planning model for XYZ. 3:16:01 Click on next. 3:16:03 There you can see under source model 3:16:05 there are two options. 3:16:07 One is my blank model which would be 3:16:10 completely blank. Right here I can start 3:16:13 from the scratch. Second is existing 3:16:16 model. If I click on existing model, I 3:16:20 should be able to see these four 3:16:22 options, right? Rate, ownership, 3:16:25 consolidation, planning. Why? Because 3:16:28 these are the existing models. That's 3:16:30 why I can see only these models. If I 3:16:33 select rates and try to create then no 3:16:37 matter what name I have given the type 3:16:39 of model I'll be ended up is of creating 3:16:43 I'll I'll be ended up creating is of 3:16:45 rate rates type of model right which I 3:16:48 don't want. So what I'll do I'll click 3:16:50 on blank. Now go to next. Okay. Now what 3:16:55 I can see here 3:16:58 I can see reporting. There are three 3:17:00 options. One is consolidation. 3:17:03 Second is financial. Third is standard. 3:17:08 I know that I'm doing a planning. So I 3:17:10 don't definitely don't need to do 3:17:12 consolidation. 3:17:14 Now comes two options whether standard 3:17:17 or financial. 3:17:19 What does the difference it makes? If I 3:17:22 click on financial just observe to the 3:17:25 right side. If I click on financial, 3:17:30 did you see the change? It is showing 3:17:34 the option of rates, 3:17:36 right? 3:17:40 >> Yes. 3:17:41 >> Right. It's showing the option of rates. 3:17:45 If I select standard, there would be no 3:17:48 option of rates. Okay. By mistake 3:17:53 consultants 3:17:55 forget to select financial they just 3:17:57 hidden on a standard and select next 3:18:01 when they create it later they identify 3:18:03 that okay they don't don't have standard 3:18:05 rate model why the rate model is not 3:18:07 connected to my planning model because 3:18:11 my model type is standard so always go 3:18:14 with the financial ones when you have to 3:18:17 go with the financial ones whenever you 3:18:20 have the requirement of having a 3:18:23 currency conversion. Whenever you your 3:18:26 company is having operations running in 3:18:29 uh you know many other countries having 3:18:30 different currencies 3:18:32 by doing this 3:18:35 you don't need to again do uh again need 3:18:38 to do any any script logic or 3:18:41 programming to fetch the data from other 3:18:43 models. Automatically your rates is 3:18:46 associated with your planning model. 3:18:49 Okay, is it clear? 3:18:53 Always select financial when you need to 3:18:56 select financial whenever you need 3:18:58 having a need of currency conversion or 3:19:01 you need exchange rates. Right. Never 3:19:03 forget to select financial. Okay. Now 3:19:07 other thing what you can observe here is 3:19:09 a key figure length. Okay. Now there are 3:19:13 two options large and normal. What does 3:19:16 it suggest? If you put here your cursor, 3:19:20 you can see 3:19:22 supports up to 24 digits before a 3:19:25 decimal point and seven digit after a 3:19:28 decimal in transactional data. So 3:19:32 I believe you all are expert financial 3:19:35 expert. So have you ever seen a 3:19:38 transactional data of 24 digits 3:19:42 which is required in any system? I never 3:19:44 seen that. I still remember in you know 3:19:47 back you know it's like seven to eight 3:19:49 years back in one of the project right 3:19:53 uh they selected normal but you know 3:19:56 issues were coming SAP was not able to 3:19:59 support because of the large volume of 3:20:00 the data then we had to select large 3:20:04 right it resolved that issue for some 3:20:06 time but then it it invited unidentified 3:20:10 lot of issues again right So 3:20:15 since then I never use this option. I'll 3:20:18 again suggest you not to go with a large 3:20:20 one because that depends on your 3:20:22 hardware right on your sizing as well as 3:20:26 your memory of the system that is been 3:20:30 decide that is being decided and driven 3:20:32 by your basis consultants correct who 3:20:36 are taking care of the server. Okay. 3:20:39 So go with the normal one, go with the 3:20:42 financial and hit next. Right now for 3:20:46 example, this is a practice server. 3:20:47 There's not a lot of data. Let's say 3:20:49 here maybe it allows me but during the 3:20:53 implementation once it has lot of 3:20:55 entries and all then it will throw me 3:20:57 errors. Okay. But that you need to take 3:21:02 care of it while creating the model 3:21:04 since start always go with the normal. 3:21:07 Okay. If I go to next screen to the 3:21:11 bottom of this pop-up, I can see in red. 3:21:14 Right now it's coming in red because 3:21:15 it's 11.1. Okay. 3:21:18 But you will be implementing on 10.1. 3:21:22 There you won't see it in red. Right now 3:21:25 what does it suggest? You must select 3:21:28 one dimension with the following types. 3:21:30 Account, category, entity, currency and 3:21:35 time. Or I should say 3:21:38 you can't create a model in BPC without 3:21:42 these five dimensions. 3:21:45 These dimensions are must to have to 3:21:48 create the model. This is a SAP 3:21:51 certification question as well. This 3:21:53 comes in the exam. Okay. What are the 3:21:56 mandatory dimensions 3:21:59 or sometimes it may happen or it might 3:22:03 happen again or maybe in future you will 3:22:05 come across many BPC consultants who 3:22:08 claim that okay they are BPC 3:22:10 consultants. Okay. If you have to 3:22:12 examine them simply ask them that okay 3:22:15 what are the mandatory dimensions in the 3:22:18 model. 3:22:20 Those who have actually worked they can 3:22:22 explain you. Those who never worked only 3:22:24 theory concepts they have they can't do 3:22:26 that because they either they they have 3:22:29 learned it but they they won't be able 3:22:31 to remember or recognize that right 3:22:33 because they never created a model. Now 3:22:36 these five dimensions are required. Why 3:22:39 these are required? Because these are 3:22:42 the five dimensions which gives some 3:22:45 meaning to my model as well as to my 3:22:48 data. without them data would not be 3:22:51 completed. For example, I need a GL 3:22:55 account, right? For any transaction, I 3:22:58 need to tell the system what kind of a 3:23:01 category, what kind of a nature of the 3:23:03 data this is, whether it's related to 3:23:05 actual, it's related to budget or 3:23:08 forecast. I need to tell the system this 3:23:11 transaction is related to which location 3:23:15 that's why entity is required. Then of 3:23:17 course currency, right? whether this is 3:23:20 USD, euro, INR right and time under 3:23:25 which month this transaction happens 3:23:27 right so if I select these five 3:23:31 dimensions although these are the 3:23:33 standard ones right but I'll I'll choose 3:23:36 what we have created so what we will 3:23:39 create whatever you will also create 3:23:41 you'll be able to see here right you 3:23:43 just need to drag it down you can see 3:23:45 planning account this is what we created 3:23:47 if you remember Right? See in standard 3:23:51 model also you are telling system that 3:23:54 okay what is your reporting currency 3:23:56 okay so by default you can select it 3:23:59 doesn't matter that you have only one 3:24:01 currency you just keep it there right 3:24:04 how that will make an impact I'll I'll 3:24:06 show you in the reporting part but yes 3:24:08 that is mandatory to create then comes 3:24:13 my category 3:24:16 then entity 3:24:18 and and currency. 3:24:22 Okay. So for currency I can see 3:24:23 reporting currency here as well. And I 3:24:26 believe I saw input currency as well. So 3:24:29 if you don't need I can unselect it. I 3:24:32 can choose this currency as well because 3:24:35 the dimension type is of currency. 3:24:38 So as I selected the five required 3:24:41 dimensions you can see it has turned to 3:24:45 green from red. Right? because we have 3:24:48 fulfilled the requirement and this is 3:24:50 the interview as well as exam as 3:24:53 certification question as well right 3:24:55 what are the important dimensions to 3:24:57 create the model okay 3:25:01 now click on next 3:25:04 copy from source okay before that I 3:25:09 would like to show you again 3:25:11 >> XYZ planning now 3:25:14 we have been you know talking and uh you 3:25:18 know working on BPC front end. In the 3:25:21 beginning I have shared that okay BPC 3:25:23 covers three areas. One is like EPM 3:25:26 which is for reporting. Uh one is second 3:25:29 one is BPC web link. Third one is like 3:25:32 my BW my back end right. So why did I 3:25:35 stopped here to give you a realtime 3:25:38 exposure how it will work? So what we 3:25:41 need to do we have to go to BW for HANA. 3:25:45 So, so guys this is BW for HANA right 3:25:49 you are practicing in the latest server 3:25:52 but in your company it would be 10.1 so 3:25:55 you would be able to see only BW just 3:25:58 double click here okay and then when 3:26:01 you'll be able when you'll be logging 3:26:03 into 10.1 okay where you will need to 3:26:08 look at the changes which you are doing 3:26:10 at BPC right you have to use the 3:26:13 transaction code as RSA1. 3:26:17 Okay. 3:26:18 Once you do RSA1, then you would be able 3:26:21 to see info provider that detail here, 3:26:24 right? But this is BW for HANA. 3:26:27 This we won't use. We'll be using which 3:26:30 one? We'll be using list cube. 3:26:34 What is it? List cube. Easy to remember. 3:26:40 A list of the cubes. Info provider. 3:26:43 Okay. 3:26:46 As I said model 3:26:48 is something which consists of 3:26:51 dimensions. Model is info provider. 3:26:54 Dimensions are info objects. So that is 3:26:57 why it's a very easy transaction code to 3:27:00 remember list Q. Okay. Now in info 3:27:04 provider if you go there right 3:27:09 this is the list which contains my model 3:27:13 my dimensions which are either exist in 3:27:16 BW or in HANA studio or in VPC. Here 3:27:23 simply 3:27:26 one thing more I would like to show 3:27:28 here. See, you can see so many uh you 3:27:32 know descriptions here but these are not 3:27:35 related to BPC. How do I know it's not 3:27:38 related to BPC? 3:27:40 Because there's a technical naming 3:27:41 convention which BPC follows. If 3:27:45 anything related to BPC, right? That has 3:27:49 to start with CPM. CPM is the prefix. 3:27:55 Is it clear to you? CPM. 3:27:58 This is also same in 10.1 as well CPMBB. 3:28:02 The only difference is that in 10.1 you 3:28:05 will be using the transaction code as 3:28:08 RSA1. 3:28:10 Okay. There you will be able to see a 3:28:14 info provider list. Okay. One of them 3:28:17 would have this naming convention to the 3:28:20 right side CPM. If you expand it further 3:28:23 then you can see your environment shell. 3:28:25 Okay. But since this is BW4 HANA 3:28:30 right so here if we have to identify we 3:28:33 can directly search the name right but 3:28:36 before that uh I wanted to give you that 3:28:39 exposure that how my data is getting 3:28:42 saved under what technical name so 3:28:45 always it's easy to identify which 3:28:48 component is related to BPC just look 3:28:51 for CPMBB is it clear to everybody See 3:28:56 there are a lot of standard ones as well 3:28:58 right but we don't have to do anything 3:29:01 with those we have to just go for CPMBB1 3:29:05 the standard ones we can use it when 3:29:08 we'll be deriving uh the data from SAP 3:29:10 system clear so CPMBB would be the 3:29:13 prefix this is the standard nomenclature 3:29:17 right so for example for time right if I 3:29:21 expand it 3:29:24 so this is the technical name for the 3:29:26 time CPMBB B O D J H I K right so from 3:29:31 CPMBB I can understand this is related 3:29:33 to time okay now why we are here right 3:29:39 >> I want all of you to know what we are 3:29:43 doing in BPC front end we don't have to 3:29:46 do the same thing at the back end 3:29:49 we don't need to many consultants many 3:29:53 clients are confused with this concept 3:29:56 they think that okay we have to create 3:29:59 it again in the BW as well no the answer 3:30:03 is no we don't need to create it it will 3:30:05 get created automatically 3:30:08 okay it will be autogenerated by the 3:30:11 system I'll show you how XYZ for a time 3:30:15 being I just select XYZ 3:30:17 and I try to find it 3:30:22 says not found that means 3:30:26 It has not been created in VPC that's 3:30:29 why it's not visible here but the moment 3:30:31 we'll create the planning model there we 3:30:34 will be able to see here okay so now we 3:30:37 are going to see that the does the 3:30:40 changes automatically gets replicated or 3:30:43 not the exercise which we are doing same 3:30:47 is applicable on 10.1 as well okay 3:30:52 now I go here. Okay. I just click on 3:30:55 next, 3:30:57 next, next. Now here what I can see 3:31:01 again on this screen it's revalidating 3:31:04 review and create name XYZ planning. 3:31:08 These are the dimensions and this is the 3:31:10 type as financial. 3:31:13 If for example by mistake if I would 3:31:16 have been selected the standard I I can 3:31:19 go to previous again I can reselect 3:31:22 financial. Okay. So always in BPC always 3:31:26 review before hitting the final button. 3:31:30 In this case create in case of reporting 3:31:33 it would be execute. Okay. 3:31:37 If I click on create system will start 3:31:41 creating the model. So we'll see. So it 3:31:45 says model has been created. 3:31:48 If I go here, I can see these are the mo 3:31:53 like these are the dimensions in my 3:31:55 model. Category, entity, input, 3:31:58 currency, accounts and time. 3:32:02 Okay, 3:32:04 is it clear so far to everyone? 3:32:10 Now 3:32:11 what I'll do? I'll go here. Okay, I'll 3:32:15 select XYZ. 3:32:18 I can see it's not found because that 3:32:20 pop-up window was already open. So I 3:32:22 need to close it. Sometimes you need to 3:32:24 refresh it. But let's say let's try 3:32:27 again. 3:32:29 I'll select 3:32:31 XYZ. 3:32:36 So what I can see now XYZ planning it 3:32:40 was automatically created at the back 3:32:42 end. Right? We didn't do anything. This 3:32:45 is showing whether this is a cube, a 3:32:48 characteristic I mean a info object or 3:32:51 dimension or what is it? This is just a 3:32:54 pictorial representation. Okay. For 3:32:57 example, time our account, right? Model 3:33:00 model we have created as a dimension, 3:33:02 right? 3:33:04 Correct. So whenever you'll be see model 3:33:07 okay not this model the model which you 3:33:11 create you would see this 3:33:14 this symbol right all of the dimensions 3:33:18 which I created they will be created as 3:33:20 a info object so account product these 3:33:22 are the info objects okay and we call 3:33:25 these info objects as a dimensions in 3:33:28 BPC but here uh there's a difference 3:33:31 right this this is just to you know link 3:33:34 think what somebody refers in BW because 3:33:38 your BPC is having a you know database 3:33:41 as a BW. So to make BW consultants 3:33:45 understand the terminology which we use 3:33:47 here so that he can understand that okay 3:33:49 what is dimension but I'll tell you 3:33:51 what's the real difference between the 3:33:52 dimensions of BW as well as B BPC as 3:33:56 this in BPC you can actually create 3:33:59 dimension based on client's requirement 3:34:02 based on understanding and everything 3:34:04 that covers your functional part as well 3:34:06 but when it comes to BW based dimensions 3:34:09 right those are just the info object 3:34:12 which are nothing just a columns having 3:34:14 the data of any legacy system doesn't 3:34:17 matter whe whether that makes a sense or 3:34:18 not they just create it okay so just to 3:34:22 make backend team understand right we 3:34:26 explain them that dimension is my info 3:34:28 object so that for them it's just a 3:34:30 technical name that okay info object is 3:34:32 this this this right but we understand 3:34:35 because since we are the one who are 3:34:37 driving who are creating the or you know 3:34:39 planning or consolidation project how it 3:34:42 should you know correlate correlate with 3:34:44 them. So that's why just for explanation 3:34:46 we explain them in that terminology as 3:34:48 well. So is it clear model you can say 3:34:52 right info cube as you can say info 3:34:55 provider also you can refer right plus 3:34:58 always you know uh avoid using say 3:35:01 characteristic because characteristic is 3:35:04 just a property of our dimension. Okay. 3:35:08 So what we have done we have created XYZ 3:35:11 as this our model. Okay. 3:35:17 So you will come here on this screen you 3:35:19 will select it. You can see that 3:35:21 technical name was autogenerated by the 3:35:23 system. We didn't do anything here. Now 3:35:26 what to do? Execute it here. Field 3:35:31 selection for output. Click on it. 3:35:34 Select all characteristics. All 3:35:36 characteristics means those are the 3:35:39 those which are important field right 3:35:41 they will get selected right you can see 3:35:44 we have dimensions like category entity 3:35:48 currency account time as well as signed 3:35:52 data as well we can see did we create 3:35:55 assigned data yes it's system generated 3:35:59 but why system is generated so remember 3:36:02 whenever we will do any any you you know 3:36:06 uh anything in BPC right any data we 3:36:09 will save that will get saved under this 3:36:14 head heading or header you can 3:36:17 understand because since we this is the 3:36:20 first class as a signed data sign data 3:36:23 is nothing that stores our transaction 3:36:25 amount okay request this is nothing you 3:36:28 can uncheck it 3:36:31 click on click on execute 3:36:34 Okay. 3:36:36 And then again execute it. 3:36:40 So you can see this is my database. 3:36:44 Right? Now it's blank. 3:36:47 This would be same for RSA 1 transaction 3:36:49 as well. Right? The only thing is that 3:36:52 in transaction in RSA 1 when you will be 3:36:55 hitting for example if I show you. 3:37:00 So such kind of a screen you can see in 3:37:02 RSA 1. Similarly, same like this screen. 3:37:05 The only thing is that here you would be 3:37:08 able to see you will you will be able to 3:37:10 see info provider okay by the name CPMV. 3:37:13 So what you need to do you need to 3:37:14 expand it then you can see XYZ and 3:37:19 similarly you can you will double click 3:37:21 on that part right and then this screen 3:37:23 will come 3:37:26 this one where you will be doing the 3:37:28 selection and all. Okay, list uh it's 3:37:32 list cube and in 10.1 it is RSA 1. Okay. 3:37:37 So right now we can see 3:37:41 that okay we are in our cube. This is 3:37:43 the second area. Right now it's blank. 3:37:46 Right. As we do some transactions as we 3:37:50 start working on our dimension members 3:37:53 then only we'll be able to see that okay 3:37:55 how my system is playing the key role 3:37:58 right how my data is looking and all. 3:38:02 Okay, I go back again to my model. So 3:38:06 this is my model. Okay, which is XYZ 3:38:10 planning 3:38:13 how it's looking at the back end? I can 3:38:16 see here right this is the technical 3:38:18 name. Okay, these are the same dimension 3:38:22 name what you have created same you 3:38:24 would observe here as well. So what we 3:38:27 discussed today what is dimension right? 3:38:31 How that works? What type of dimensions 3:38:33 we have? How we can create models, 3:38:37 right? How my model is working based on 3:38:42 my selection as a standard or 3:38:44 financials, right? What type of models I 3:38:46 can create? How I can create whether 3:38:49 blank or with the existing one, right? 3:38:52 How my database is working. 3:38:55 Okay. 3:38:59 So this model and dimension is clear. I 3:39:03 hope it it's clear at BPC weblink level 3:39:06 right I'll refer it as a BPC web link. 3:39:08 So at this uh in this component I 3:39:13 believe this is clear 3:39:15 and in BW I believe it's clear to you as 3:39:19 well right that how my dimensions and 3:39:22 model is looking correct remaining is 3:39:25 this EPM. So how these three are 3:39:28 interlin with each other why these three 3:39:30 fulfills overall VPC application right. 3:39:34 So we have seen that what we are doing 3:39:35 in the front end same changes have been 3:39:37 replicating uh same changes are getting 3:39:40 replicated to the back end as well right 3:39:42 but what about EPM then right so that we 3:39:46 will see now okay 3:39:49 so far uh suppose if if we are in this 3:39:53 hierarchy okay 3:39:56 now here what would happen if I expand 3:39:58 it further right if I understood your 3:40:02 question correctly Right? If I have uh 3:40:05 let's say 100 in this account, 100 in 3:40:08 this account and 100 in this account, 3:40:11 then you are asking me that at GL00002 3:40:15 like how it can have 300 would it be 3:40:18 auto 3:40:19 add auto auto rollup or do we need to 3:40:22 any uh do any aggregation right? So okay 3:40:27 so I'll be sh I'll be I'll be showing 3:40:29 that in in this sheet I mean in the 3:40:32 report but any choice to answer your 3:40:34 question the thing is that since 3:40:36 whatever we if we maintain as a parent 3:40:38 and child whatever child would have 3:40:42 right that is getting autopop populated 3:40:46 or auto rolled up at parent level so we 3:40:49 don't need to do any aggregation for 3:40:51 that in BPC that is automatically ally 3:40:55 happening. 3:40:57 Okay. So the parent would always be 3:41:00 summation of its children. 3:41:03 Similarly, if let's say I want to enter 3:41:07 300 at GL00002. 3:41:10 Okay. And I want that what I entered 3:41:12 here, right? System should allow 3:41:17 100 to each of my children. Right? That 3:41:21 is not possible in VPC directly. 3:41:25 Okay. But if somebody has to do it or 3:41:28 having such kind of requirement right 3:41:31 that we call it as a top-down planning 3:41:35 okay normally we we go with a bottom up 3:41:37 planning but the scenario which I'm 3:41:39 talking about is like a top-down 3:41:41 planning. Okay. So how to achieve that? 3:41:45 So for for that we need a ABAB 3:41:47 consultant. Okay. Who will create a body 3:41:51 program. Okay. That's a body. I believe 3:41:54 all of you are very well aware about the 3:41:55 body, right? The program, the 3:41:58 announcement. 3:41:59 So what he will do, he will create a 3:42:02 write back body which will write back 3:42:04 the data to its children from the top 3:42:08 end. So this is what happens. 3:42:12 Okay. So that's how he will do. So we 3:42:15 don't need to do that. We can explain 3:42:17 our requirement. they will use the 3:42:19 standard enhanced functional modules and 3:42:22 they can do that. Is it clear? 3:42:26 It's only possible through body when it 3:42:28 comes to writing the data at parent 3:42:30 level and allocating to the children 3:42:33 level. 3:42:34 Not just in 10.1 even in 11.1 also it 3:42:38 goes in the same way. Okay, we are on 3:42:42 this screen, right? Which is just a 3:42:44 Excel sheet, right? Excel file. You can 3:42:46 open any Excel file. I'll open it from 3:42:49 the scratch. So, what I need to do, I 3:42:53 have to go to EPM. 3:42:55 Okay. 3:42:57 So, there are two tabs before I log. 3:43:00 Okay. One is EPM, another one is like 3:43:03 data manager. Okay. Now, what does EPM 3:43:06 do? EPM tab helps you to login or to 3:43:11 open any input form or any report which 3:43:15 you have stored in your EP in your BPC. 3:43:18 Okay. Whereas data manager helps you to 3:43:23 run and to execute any calculation. For 3:43:27 example, in SAP standard you do F8, 3:43:32 right? You do F8. Similarly, you can 3:43:36 execute the program or I mean any 3:43:39 calculation through a data manager 3:43:42 package. We will uh take it later as 3:43:44 well. So this is the third component of 3:43:47 BPC which is my EPM which is enterprise 3:43:51 performance management. The look and 3:43:53 feel is same like an Excel sheet. Okay. 3:43:57 You have to login 3:44:00 now before you log. Okay, 3:44:05 you will have a connection thing, right? 3:44:08 You have to go here. How to set up a 3:44:10 connection? If you try to login, let's 3:44:12 say by your credentials, okay, situation 3:44:15 may occur where you will not be able to 3:44:17 see your own created model. How you have 3:44:20 to so what you need to do right because 3:44:22 you created but you are not able to see 3:44:24 here. So in your connection name okay 3:44:28 either create duplicate or go to edit 3:44:32 okay enter your credentials 3:44:40 okay 3:44:42 now here what you can do first check 3:44:46 what environment you are into 3:44:50 so we know our environment is planning 3:44:52 XYZ I hope everybody remembers it right 3:44:58 planning XYZ 3:45:00 so that's the reason we created our 3:45:03 environment because everywhere you will 3:45:04 be seeing environment I could have ended 3:45:07 up that in 30 seconds but then later you 3:45:09 will be able to you know you would be 3:45:11 coming and asking that what is 3:45:13 environment why we didn't cover that's 3:45:15 the reason I I covered that and I 3:45:17 created from the scratch so that you can 3:45:20 relate it so what system is saying now 3:45:23 select environment we select ed our own 3:45:25 environment. Now we'll be able to see 3:45:27 our own model else we can't see that for 3:45:31 example 3:45:33 would have been selected let's say 3:45:35 zarent BPC and I could go for model and 3:45:40 I'll be ended up choosing a wrong model 3:45:43 because I can't see planning model right 3:45:46 so that's the reason select first your 3:45:49 own model on environment under your own 3:45:52 environment you can see your model Okay, 3:45:57 I can create I can click on okay as well 3:45:59 and next time then I'll be logged in. 3:46:01 I'll be def I'll be by default login 3:46:04 into my own model as well. But other 3:46:07 other option what I can create? I can 3:46:09 create generate connection name. 3:46:12 I click on this. So what it's showing me 3:46:15 XYZ planning planning XYZ. I know the 3:46:17 name can be confusing to you, right? But 3:46:20 this is just for an example we we 3:46:22 created, right? 3:46:24 I click on okay. As I clicked on okay, 3:46:26 you can see now the connection name has 3:46:28 been changed. So this is the important 3:46:31 activity. Whenever you'll be logging 3:46:33 into any EPM system, right? How to 3:46:38 create a connection you should be able 3:46:40 to know else you will have you will be 3:46:44 struggling that okay I'm not able to 3:46:45 create my connection. Okay, is it clear? 3:46:49 I'll again show you what you can see 3:46:52 here is server URL bw4hana.st 3:46:56 ST this /BPC this by default system 3:47:00 would show you this BPC/ this and then 3:47:03 HTTPS 3:47:04 this thing you need to take it from your 3:47:08 basis consultant 3:47:11 or you know any IT head of your company 3:47:14 they will share you the link or you can 3:47:17 explore 3:47:18 the same here as well this BPC link also 3:47:22 you can copy here and you can paste 3:47:25 here. 3:47:28 Okay. 3:47:30 Is it clear so far? 3:47:33 So this is how you can create your 3:47:35 connection. 3:47:36 So once you can create your connection, 3:47:39 hit on okay. Uh export uh export is not 3:47:44 possible. I'll tell you why. Because see 3:47:48 uh we we create uh for example it's a 3:47:50 server right? If I have created it, 3:47:54 chances and possibilities that you know 3:47:56 you'll be logging in from your your end 3:47:59 from your ids and you'll be able to see 3:48:01 the same connection. But when it comes 3:48:03 to system, right? Every user first time 3:48:06 they are logging in into the system, 3:48:09 right? So by default that's the first 3:48:12 activity which every user every 3:48:14 consultant needs to create it at their 3:48:16 their end. So far it has not been 3:48:19 replicated but but in case basis 3:48:23 consultant right says that okay they 3:48:26 have single sign on facility then you 3:48:29 might not need to go with it you simply 3:48:32 click on log on and you don't need to 3:48:34 see that but in that case also right 3:48:37 that shouldn't be recommended because 3:48:39 they don't know which model and which 3:48:42 environment you will be logging until 3:48:45 that is the only thing you have in uh 3:48:47 application. 3:48:50 So 3:48:51 now we have created the connection. So 3:48:55 we'll be logging into EPM. 3:48:59 So for that 3:49:06 now this is the EPM. Okay, EPM addin is 3:49:11 the software name, right? If you have to 3:49:13 install it, right? uh right now in 3:49:15 server it's available but in your 3:49:17 company server you can ask it I it guy 3:49:21 or you can ask your uh basis consultant 3:49:24 right that I need to install EPM only 3:49:27 when they will install EPM addin then 3:49:29 only you'll be able to see these two 3:49:31 tabs EPM as well as data manager okay 3:49:35 and many times the question comes what 3:49:37 kind of EPM right what version so for 3:49:40 that you can click on about 3:49:43 EPM 3:49:44 Right here you can see the version 10.0 3:49:48 service pack 34. Right? Depending on the 3:49:51 company on the hardware this keeps on 3:49:55 changing. Okay. So the BPC version is of 3:49:59 11.1 here as you have mentioned in your 3:50:02 company it's 10.1. Okay. So what I'm 3:50:06 doing the examples which I I'm covering 3:50:09 right that covers both 10.1 as well as 3:50:11 11.1. It won't happen that what you are 3:50:15 uh you know uh looking uh at in the 3:50:19 training sessions you will be having a 3:50:21 completely different exposure in real 3:50:24 time server. No, that would be 3:50:26 completely same thing. Only thing is 3:50:28 that look and feel is a bit different 3:50:31 right for example here you can see the 3:50:34 favorite library right dimensions 3:50:38 something like that there you will 3:50:39 directly see dimensions models okay 3:50:42 other than that there's no difference 3:50:44 you know like in iPhone we have like you 3:50:47 know iOS 13 iOS 12 so and so that's the 3:50:52 only kind of difference it's having 3:50:54 otherwise everything remains same plus 3:50:57 the back back end uh the server right 3:50:59 because of the compatibility that is 3:51:01 10.1 is running on BW 7.5 whereas this 3:51:05 11.1 is running on BW4 HANA so this is 3:51:09 the EPM we have successfully logged on 3:51:11 into our model which is XYZ our model 3:51:15 planning XYZ of the environment planning 3:51:18 XYZ right 3:51:20 >> all right let's test your knowledge 3:51:22 here's a question for you which of the 3:51:24 following is not a module in SAP BPC 3:51:29 10.1. Option A, consolidation, option B, 3:51:34 planning, option C, profitability 3:51:36 analysis, option D, supply chain 3:51:39 management. Take a moment to think, and 3:51:41 when you're ready, choose the correct 3:51:44 option. Remember, each choice holds a 3:51:47 key to unlocking the answer. Good luck. 3:51:50 Type the correct answer in the comment 3:51:52 section. Hey there. Ready to dive into 3:51:55 the world of SAP BPC 10.1? Our course is 3:51:59 your ticket to mastering supply 3:52:00 management all at your own pace on our 3:52:03 platform. In this course, we'll unravel 3:52:05 the mysteries of SAP BBC 10.1. Think of 3:52:08 it like a Swiss Army knife for planning, 3:52:10 ensuring we've got enough goodies and 3:52:13 getting them where they need to be. From 3:52:15 the basics to expert tips, we've got you 3:52:17 covered. Crafted by seasoned pros, this 3:52:20 course delivers the goods. Your mentors, 3:52:22 top-notch veterans in the feed, ready to 3:52:24 guide you through and tackle any queries 3:52:26 you throw their way. And hey, don't just 3:52:28 take our [music] word for it. Our 3:52:30 students are singing their praises. 3:52:32 Folks just like you have found this 3:52:33 course a game changer. Best part, it's 3:52:36 easy on a wallet. [music] Learning 3:52:38 doesn't have to cost a fortune. Ready to 3:52:40 become a SAP VPC 10.1 maestro? Enroll 3:52:45 now. For more details, [music] visit 3:52:47 Zarantex website. Okay. So before we 3:52:51 move on to server, okay, in today's 3:52:53 session, we'll try to cover our uh try 3:52:56 to cover about the data manager package. 3:52:59 Okay, these all are standard ones. And 3:53:02 if you want to see that, okay, which one 3:53:04 is your environment, I believe you have 3:53:05 created with the name NG2. Somebody has 3:53:07 created with the name NG2, right? 3:53:10 >> Natrajan did you create from NG2? 3:53:14 Okay, because the reason for asking is 3:53:16 that because at my end when I just 3:53:17 logged in into the system and where the 3:53:19 screen got hanged so the environment is 3:53:21 NG2 so I thought maybe somebody has 3:53:23 created so any which way so here we can 3:53:26 see that environment shell is there okay 3:53:28 that's of a standard one you can 3:53:30 directly hit on it click on copy create 3:53:32 the environment okay and then system 3:53:36 will uh take time depending on the 3:53:38 server okay since it's on uh 7.5 so the 3:53:43 Look and feel and screen layout is the 3:53:45 only difference. Other than that there's 3:53:47 some performance. Performance is like 3:53:49 you know BW for HANA which is uh which 3:53:51 on which 11.1 runs right that's a bit 3:53:54 faster as compared to 10.1. Other than 3:53:57 that everything remains same okay and 3:54:00 also one thing more like in case if you 3:54:02 all are working on the same engagement 3:54:04 okay of any planning project. 3:54:07 >> So make sure you only create one 3:54:10 environment. It shouldn't happen that 3:54:12 everybody is creating different 3:54:13 different environment right your models 3:54:15 can be different like like for example 3:54:18 sales model right your uh you know capex 3:54:22 model finance model those you can create 3:54:25 separately so that you can have 3:54:27 ownership but make sure your environment 3:54:29 remains same okay so today other than 3:54:33 create other than you know knowing about 3:54:35 how data manager works what are the 3:54:36 prerequisites what are the you know 3:54:38 activities how it uh you know function 3:54:40 questions. We'll also see how EPM report 3:54:44 works right what's the role of the data 3:54:46 how that makes the impact on the system 3:54:49 what's the role of my BW system as well 3:54:52 okay so those all scenarios we'll be 3:54:55 trying to cover in today's session 3:54:58 >> thank you for the confirmation sir 3:55:01 >> thank you thanks for your support okay 3:55:05 guys for a timing now we are on 10.1 3:55:07 okay so I'll just connect with any 3:55:12 environment. Okay. So I'll go with 3:55:15 test07 environment 3:55:19 and let's see does it has any models. 3:55:24 So it has a standard planning models. 3:55:28 Okay. So 3:55:31 okay in my last session right when I was 3:55:34 discussing about you know how BPC web 3:55:36 link plays the role right as a 3:55:38 consultant when basis team will share 3:55:40 the BPC web link with you right that 3:55:42 this is the portal where you need to 3:55:44 login with your credentials right so by 3:55:47 default right this is the landing page 3:55:51 of 10.1 okay here you can see 3:55:54 environment is right at the bottom okay 3:55:58 by default fault you will be in 3:56:00 environment shell. So you need to do the 3:56:03 required steps which we covered in last 3:56:05 session by copying your own environment. 3:56:08 Okay. And then you create your 3:56:10 dimensions as well as models. Let's say 3:56:14 uh within your company right uh I 3:56:17 believe you must be in-house team right 3:56:19 who's responsible for doing the you know 3:56:22 planning or implementation. But let's 3:56:25 say you also you know sign up a contract 3:56:27 with some other company. Okay. working 3:56:29 on your planning project. Okay. But you 3:56:32 want everything keep confidential. You 3:56:34 don't want to share with them. So do 3:56:36 when the server is same, right? As you 3:56:38 rightly mentioned, in that case 3:56:41 environment is the best thing because 3:56:43 that allows you to give access based on 3:56:46 ids as well. So what they need to do 3:56:49 they have to create their own 3:56:51 environment and you'll be working in 3:56:52 your own environment and they won't have 3:56:55 access to your environment. So they 3:56:57 can't access your models, dimensions, 3:57:00 whatever design you are having. Same 3:57:02 goes with you as well. If they put 3:57:04 authorization, you also can't do that. 3:57:06 So that's why it's good to have 3:57:08 environment. Okay. And also other thing 3:57:11 is that if for example mostly BPC goes 3:57:15 for planning as well as consolidation, 3:57:18 let's say both are having dependencies, 3:57:20 right? If both planning and 3:57:23 consolidation somebody starts uh doing 3:57:25 in one environment and they have to move 3:57:27 from development to quality. Let's say 3:57:30 consolidation team says that okay we are 3:57:32 done with our design our testing now we 3:57:35 are ready for go live right and they 3:57:37 want to move their whole application uh 3:57:40 there are two ways of moving the objects 3:57:42 one is like through the transports seat 3:57:44 you will go and create the request okay 3:57:47 then you will do the you know sep 3:57:49 traditional way by SC09 or SC 10 by 3:57:53 releasing the transports second is you 3:57:56 will you know take the backup of your 3:57:58 application ation. Now backup of 3:58:01 application can be done on environment 3:58:04 level. So what they would do if they are 3:58:06 having different environment they will 3:58:08 simply backup and then restore in the 3:58:11 quality in that way their work would not 3:58:14 be dependent on you. But in case you 3:58:16 both are in the same environment then 3:58:18 they can't do that because if they do 3:58:20 right then again whatever changes you 3:58:22 are doing because UAT has not happened 3:58:25 then they would always have dependency 3:58:26 on you. So it's better to have different 3:58:28 environment in such scenarios. Other 3:58:31 than that 3:58:33 feel free to have a different model. 3:58:35 Environment covers your model dimension 3:58:38 report logic transaction data master 3:58:41 data everything comes under environment 3:58:43 >> and the beauty of it is that in BPC as 3:58:46 compared to other uh SAP modules in 3:58:49 those you have to collect all the 3:58:50 objects individually. here if you don't 3:58:52 know or maybe let's say you don't want 3:58:55 to do that simply take the backup which 3:58:57 depending on the size of your data that 3:59:00 takes hardly from 10 minutes to 30 3:59:02 minutes you just back up and simply 3:59:05 restore you don't need to worry that 3:59:07 okay like uh did I lose some object or 3:59:10 not okay so that would that would simply 3:59:14 create the same replica in the quality 3:59:17 as well as the as well as in the 3:59:19 production as well okay Okay. 3:59:23 >> But once you are go live and once you 3:59:26 are in production then refrain from 3:59:29 replicating or doing the restore of your 3:59:32 backup because your your system is 3:59:35 running right now. You don't want to 3:59:36 replicate the whole application. So in 3:59:39 that case you have to follow the 3:59:41 traditional way of you know creating the 3:59:43 transport and releasing that so that you 3:59:46 can track that okay who has moved a 3:59:48 particular object what impact it has 3:59:50 made on my production system. So uh now 3:59:54 we are in 10.1 okay and we have already 3:59:59 uh like mostly standard models we have 4:00:01 but we want to create our own model okay 4:00:03 so what we will do in order to show you 4:00:05 how data manager plays the role how EPM 4:00:09 will work so let's have our own model 4:00:11 okay because if we going if we go and 4:00:14 again create dimension all then it will 4:00:16 take time so what I'll do for time being 4:00:19 we'll consider test 07 as the 4:00:20 environment Okay. And I'll simply 4:00:25 copy this ID. We can give 4:00:30 any ID like let's say 4:00:43 now the thing is that why we are copying 4:00:47 the model when we already have a model 4:00:49 right planning 4:00:51 correct 4:00:53 anybody's thinking in that way when we 4:00:55 already have a planning model right Why 4:00:57 do we need to create another planning 4:01:00 model? 4:01:02 uh since we are not aware that who has 4:01:04 created this environment right at what 4:01:05 level they are using these models have 4:01:08 some data in particular this model right 4:01:11 and if I want to remove any particular 4:01:13 dimension from my model then system 4:01:17 would not allow me until I clear that 4:01:20 data okay right first thing 4:01:23 >> so that's why I wanted to create a 4:01:25 different model now the thing is that in 4:01:28 case if the dimension is same right then 4:01:30 we can create our own customized 4:01:32 dimension but since it seems new okay so 4:01:35 that's why and to keep uh you know uh 4:01:38 our model look different as compared to 4:01:41 other models that's why I have created 4:01:43 our own model as planning XYZ 4:01:48 now few dimensions which I don't need I 4:01:51 can remove them okay 4:01:58 so 4:01:59 if you have to remove or add any 4:02:01 dimensions simply click on add remove 4:02:04 and then you'll be able to do that and 4:02:06 then you need to again save your model 4:02:10 and I tell you planning and 4:02:11 consolidation are the business concepts 4:02:14 what matters is all these technical 4:02:16 workarounds right because that becomes 4:02:19 showstopper during the project if you 4:02:22 are you know not aware or never touched 4:02:25 such part of the system 4:02:27 so that all we will try to cover during 4:02:30 our session ions. 4:02:32 So now our planning model is ready and 4:02:34 we have seen that it has couple of 4:02:36 different dimensions. So let's see what 4:02:38 product has. So it's a userdefined 4:02:41 dimension. 4:02:44 So it has product A, B, C. Okay, this 4:02:46 can work for us. Not an issue. 4:02:49 So now our model is ready. Okay. And we 4:02:52 know how to create dimension. Now comes 4:02:55 our EPM part, right? that what I'm going 4:02:58 to do with this structure how it will 4:03:01 work. So for that we have to login into 4:03:05 our 4:03:06 EPM. 4:03:12 So what we need to do either we can 4:03:14 create duplicate. So we'll create 4:03:16 duplicate if somebody has created it. 4:03:18 Then we'll select and click on edit 4:03:21 because we want that whenever we login 4:03:23 as this is one time activity on any 4:03:25 project you have to do we want that 4:03:27 whenever we login into the system by 4:03:29 default we login into our own system. 4:03:32 Now here two things one is like you are 4:03:35 entering the credentials okay but in 4:03:38 case if your basis consultant and your 4:03:40 company decides let's give all the user 4:03:43 single sign on option then you don't 4:03:45 need to give ID and password every time. 4:03:48 Okay. 4:03:53 Now here we will select our environment 4:03:56 which is test 07. Correct? Then our 4:04:00 model right 4:04:03 which we can't see here. 4:04:07 Wait a minute. 4:04:09 Okay. So what's happening first? We have 4:04:12 to uh this this part you know uh like we 4:04:15 can cover later as well. But let me just 4:04:17 go here. So actually we have to assign 4:04:21 the authority as well, right? That okay 4:04:23 which user can access. 4:04:26 So this is the ID which I'm using. Okay. 4:04:30 Can see data access profile. 4:04:40 So don't worry about this section. We'll 4:04:44 cover in detail as well. But for a time 4:04:46 being when you are not able to see your 4:04:49 own model when you have selected your 4:04:52 environment that means your ID needs to 4:04:55 have that access. So the question which 4:04:58 Mino asked that okay what's the use of 4:05:00 having different environment and all so 4:05:02 you can see menu even we are not able to 4:05:05 you know login into our own system but 4:05:07 now we have since we have admin access 4:05:09 that's why we can allow it by going to 4:05:12 data access profile. Okay, here we can 4:05:15 select all members. 4:05:28 So the these are the security areas 4:05:33 we'll cover in detail. Okay. 4:05:42 So earlier it was not coming. Why did it 4:05:44 uh now why why we can see this? Because 4:05:46 you have allowed the access okay in our 4:05:49 security part. So that we'll cover in 4:05:51 detail as well. 4:05:53 So I have created the connection name by 4:05:56 hitting generate connection name. System 4:05:59 will generate the connection name with 4:06:00 the with your model name. By your model 4:06:02 name you can have your connection name 4:06:04 and simply click okay. So this is where 4:06:08 we have to loged in. 4:06:15 Now we are into EPM. Okay. So EPM stands 4:06:19 for enterprise performance management. 4:06:22 Okay. So when basis consultant install 4:06:26 EPM addin on your machine on your laptop 4:06:29 then you'll be able to see two extra 4:06:31 tabs in your Excel. Okay. One is EPM 4:06:35 second one is data manager. Okay. So 4:06:38 these two areas we'll start to cover in 4:06:41 today's session. Okay. In EPM what you 4:06:44 have you can create your report. Okay. 4:06:48 You can edit your report. There are many 4:06:51 ways to you know make changes in your 4:06:55 report that all functionality will get 4:06:57 covered in EPM tab. Whereas in data 4:07:00 manager this tab is used to execute the 4:07:03 calculation to run the logic. Okay. 4:07:06 That's why we use for that we use data 4:07:09 manager. Okay. 4:07:11 Now in EPM there are two areas you can 4:07:16 see one is EPM context. So EPM context 4:07:20 is having what? It's having account 4:07:23 category entity measures product 4:07:28 reporting currency and time. 4:07:31 So what are these? These are the same 4:07:34 dimensions which we have in our model. 4:07:39 Okay, which is planning XY Z. You can 4:07:44 always see the data connection as XYZ. 4:07:47 Okay. Now if we go there and if I click 4:07:51 on models, how many dimensions 4:07:54 can you see here in in this model? 4:07:59 There are six dimensions in this model. 4:08:01 But when I go here right in my EPM which 4:08:05 is connected to my same model planning 4:08:08 XYZ. Okay. How many tabs I can see in 4:08:12 Excel in EPM context? 4:08:16 Is it six or seven? So the measures is 4:08:19 the extra one. Right? The seven 4:08:23 >> even in exam or in interview this 4:08:26 question keeps on coming right. Do we 4:08:29 create measures as a dimension in BPC? 4:08:33 Those who don't focus or don't don't 4:08:36 know or having no exposure they say that 4:08:37 yes we create but no this is not 4:08:40 required to create system generates it. 4:08:43 System creates it by default. What it 4:08:46 covers? It covers like a look and feel 4:08:48 of the data whether it's periodic YTD 4:08:52 right but we don't need to get into that 4:08:53 because our this is our planning model. 4:08:56 So you can skip this one. Okay. So never 4:08:59 get confused that okay I didn't create 4:09:02 measures what's the role of measures. 4:09:04 Similarly in other you know uh counter 4:09:08 tools of planning right as compared to 4:09:11 BPC in that measures is something which 4:09:15 you need to create but here in BPC it 4:09:18 creates automatically you do don't need 4:09:20 to do that in consolidation you can see 4:09:22 that whether it's in YTD MTD so this is 4:09:26 just to view the data okay so for in 4:09:29 that regard we can use that same data 4:09:33 stores what value we are passing in the 4:09:36 system what input we are giving so that 4:09:38 stores my transaction amount okay that's 4:09:40 a different one okay that also we don't 4:09:44 need to show in the system I mean in BPC 4:09:48 but but when somebody will write the 4:09:51 body in a web program right they will 4:09:53 mention sign data right so ne so never 4:09:58 get confused that okay I don't have any 4:10:00 field as signed data sign data is by 4:10:02 default created which store which stores 4:10:05 your transaction data. Okay. Similarly, 4:10:09 what measures does you can view the data 4:10:12 in different context whether periodic 4:10:14 YTD that's the only purpose of it. Okay. 4:10:18 So most of the time you even don't need 4:10:20 to use it because mostly all the 4:10:22 functionalities you'll be able to 4:10:23 achieve by your report or by your client 4:10:26 requirement what they have. Okay. Now 4:10:29 how this EPM context plays the part that 4:10:33 we will see but before that what we'll 4:10:36 do we'll create a simple report 4:10:40 okay or an input form. So there are many 4:10:44 ways to create the report or input form 4:10:47 okay first we'll take very straight and 4:10:51 easier one. Okay to the right hand side 4:10:54 you can see report layout right 4:10:59 correct these are having all my 4:11:01 dimensions here 4:11:04 plus we have page access row axis and 4:11:07 column axis so any report is having 4:11:11 three sections first is let's say my 4:11:15 page axis 4:11:17 which stores 4:11:20 commonly 4:11:22 applicable 4:11:23 detail on 4:11:27 the report. Okay. 4:11:31 Or 4:11:32 from where 4:11:34 you can drive or select 4:11:39 or 4:11:41 make any selection 4:11:44 based on which 4:11:47 report will be driven. Okay. So page 4:11:53 access would be you know at the always 4:11:55 at the top of your row and column. Okay. 4:12:00 Then comes your row axis where you have 4:12:04 any any dimension in your row and then 4:12:07 you have your column axis. 4:12:11 Okay, 4:12:14 is it clear? 4:12:16 I'll explain you further. Okay, when I 4:12:19 create the report, but this is how you 4:12:22 know the format of the report goes. 4:12:25 Always whatever you can see at the top 4:12:27 that means that's a page access. That's 4:12:30 whatever you will do there that would be 4:12:32 applicable for whole report and the 4:12:34 report is a combination of rows and 4:12:36 columns like in Excel normal report we 4:12:39 have 4:12:40 now what we going to do 4:12:43 we'll simply create a basic report okay 4:12:49 so there are many ways first we'll go 4:12:51 with a very straight and easy one 4:12:55 I just drag account 4:12:59 Okay. 4:13:01 Similarly, I can drag 4:13:07 time. Okay. Now, what are these? I just 4:13:12 dragged account in the row and time in 4:13:16 the column. 4:13:24 Other than that, there's another way. 4:13:27 You can just drag put it under under row 4:13:31 axis 4:13:32 and then time under column axis. 4:13:39 So what we did we put account under row 4:13:42 access time under column access. 4:13:44 Technically when I did this system 4:13:47 should create you know a report in this 4:13:50 manner. Okay. But it's not working 4:13:52 because since I can see the data is 4:13:54 older one. So we'll replicate with the 4:13:56 correct data. 4:13:58 So we'll remove it. 4:14:03 Okay. Now I have this. This is my 4:14:07 report. For a time being I close this. 4:14:10 Now I want to understand what is it. 4:14:13 Okay. 4:14:15 So there's option called edit report. Go 4:14:19 to edit report. Here you can see that 4:14:24 you know in which column you want to 4:14:26 place your report. So you can 4:14:30 change the position as well. Okay. Click 4:14:33 okay. 4:14:35 Now I can see my report is here. Okay. 4:14:40 Now this Q1, Q2, Q3, Q4 this is nothing 4:14:45 simple 4:14:46 you know representation of the members 4:14:50 of time dimension okay here what it's 4:14:53 doing it's showing 2006 as a year okay 4:14:57 fiscal year and having four quarters now 4:15:01 if you double click on it because you 4:15:02 know that this is quarter right here you 4:15:04 can't save any data if you just double 4:15:06 click on it it will get expand January 4:15:09 February, March. Similarly for quarter 2 4:15:12 as well, 4:15:14 April, May, June. 4:15:18 This is for quarter 3 4:15:23 and this is for quarter 4. 4:15:27 Now this is for total assets, total 4:15:30 liabilities and equity and balance 4:15:32 sheet. So these are the these could be 4:15:35 or must be a parent account, right? So 4:15:38 let's do the same thing here as well. If 4:15:40 I just double click on it, I can see 4:15:42 total equity, total liability. 4:15:46 On further 4:15:48 doing double click, I can see share 4:15:50 equity retained earning. If I click on 4:15:52 double total ent total liabilities, I 4:15:55 can see account payable long-term depth. 4:15:58 Okay, see whatever you can see here 4:16:01 total entity at the bottom at the top of 4:16:05 it. These are the children of total 4:16:07 equity. Similarly, long-term debt 4:16:11 account payable are the children of 4:16:12 total liabilities. 4:16:15 Okay? Because you can see there's a 4:16:17 change in the position. They are, you 4:16:19 know, indenting towards right side. 4:16:22 Similarly, total liabilities and equity 4:16:24 is the parent of total equity as well as 4:16:27 total liabilities. If I double click on 4:16:29 it, then it will 4:16:32 roll down roll up again, right? to total 4:16:35 liabilities and equity. Now you must be 4:16:38 wondering that okay this is a bit 4:16:40 confusing or it's not that straight and 4:16:43 all. It's nothing like that. It's very 4:16:44 easy. There are other ways as well 4:16:46 right. But uh I want to you know give 4:16:49 you all the you know exposure and 4:16:51 experience right which you can have 4:16:54 while implementing. For a time being 4:16:57 let's go with this example. 4:17:03 So you can see when you double click on 4:17:05 it right it expands 4:17:08 to 4:17:10 n number of levels like depends on how 4:17:14 many children it's having. Okay. 4:17:17 Now what I'm going to do let's say 4:17:22 I enter 100. 4:17:24 Okay. 4:17:30 So 100 + 200 + 300 + 400 it comes around 4:17:38 1,000 right. So ideally when I enter 4:17:43 when I input these numbers right and in 4:17:46 my previous session I I I explained and 4:17:49 I shared that whatever data you will 4:17:51 input to the children it will roll up to 4:17:53 its parent right so ideally in total 4:17:56 equity it should show me 1,000 okay so 4:18:01 before doing that what I need to do I 4:18:03 just input the number right it's looking 4:18:05 same like an excel right but where does 4:18:08 it makes the difference that no It's not 4:18:10 an excel. It's directly talking with the 4:18:12 database. 4:18:14 It happens when you save the data in the 4:18:16 system. Okay. Now, how we can save the 4:18:19 data. For saving the data, we have this 4:18:23 saved data, right? Which is disabled 4:18:26 right now. Okay. 4:18:28 Why it's disabled? So, this is a report, 4:18:31 right? Not a input form. Okay? So, how 4:18:35 to convert a report in input form? Okay. 4:18:38 Those who know 4:18:40 good for them I know they might be 4:18:43 getting bored in this session that okay 4:18:45 like how it's working but those who 4:18:46 don't know for them okay you can go here 4:18:51 in options sheet options and here okay 4:18:57 you have to select use as input form 4:18:59 okay 4:19:01 all of you please pay attention always 4:19:04 select use as input form and hit okay 4:19:07 then only 4:19:09 your report will be converted into input 4:19:12 form you can see the save data button is 4:19:14 enabled now okay 4:19:17 if I refresh right whatever data I have 4:19:20 entered here what would happen it would 4:19:23 go why because I didn't save that in the 4:19:27 database so before doing the required 4:19:31 action right what I'm going to do I'll 4:19:34 show you 4:19:37 TWW. 4:19:39 Okay. 4:19:41 So this is for 10.1 4:19:45 why I'm showing you why I'm going to 4:19:47 show you because uh you know uh we have 4:19:50 created the model we have created the 4:19:52 dimension right ideally my 4:19:55 back end right my database table that 4:19:57 must be blank right so that I want to 4:19:59 show you and what would happen if I save 4:20:02 the data how it would behave how the 4:20:04 data get restored into the database that 4:20:07 all we need to know right so that's 4:20:12 So here earlier it was RSA1 was in the 4:20:16 use or RSPC but now you know the patch 4:20:20 has been upgraded even in 10.1 as well. 4:20:23 So you can use list Q 4:20:26 here you would option you would have 4:20:27 option to choose info provider. Okay we 4:20:32 can search by the name. So this is 4:20:35 planning XYZ. Okay we know what's the 4:20:38 name of our model. Simply 4:20:40 search your model name. 4:20:43 Execute it. 4:20:45 Go to field selection for output. Select 4:20:48 all characteristics. 4:20:53 So we can see it's completely blank, 4:20:56 right? There's nothing here. So I go 4:20:59 back to my EPM. Okay. So as I said, BPC 4:21:04 covers three components or three areas. 4:21:06 One is like BPC web link. Second is EPM. 4:21:09 Third is my database. So for all the 4:21:13 those three areas as a consultant we 4:21:17 don't need to do any any connection. It 4:21:19 will be automatically done right. System 4:21:22 will take care of that. We don't need to 4:21:24 do any manual exercise for that. So 4:21:28 we'll go with our example 100 200 300 4:21:32 400. Okay. 4:21:37 I'll click on save. Now it says four 4:21:40 data records will be sent. Do you want 4:21:43 to continue? As you hit on yes, what it 4:21:47 will do? It will place it will save 4:21:50 these numbers into the BW database. 4:21:54 Okay. 4:22:01 So what we can see if it would have been 4:22:04 successful it could have shown it would 4:22:07 have been uh you know showing accepted 4:22:09 count as four but now it's showing zero 4:22:12 rejected count four. So this is how you 4:22:15 will read the error messages as well. 4:22:17 The more errors you will get during the 4:22:18 build or during practice that's good for 4:22:20 your learning. Okay. So what's the error 4:22:23 message? Total product of dimension 4:22:26 product is not a base member. 4:22:29 Okay. 4:22:33 So this is related to total product. 4:22:35 Okay. 4:22:37 Now 4:22:40 I have selected 4:22:42 accounts and time. I didn't select any 4:22:46 product. Why it's giving me error for 4:22:47 the product? 4:22:49 See what we have in our report is like 4:22:52 account. Okay. 4:22:55 Here I mention account or I what I can 4:22:59 do whatever dimension you select there's 4:23:02 are options whole report gets driven by 4:23:05 these four types only I go to sheet 4:23:07 option okay 4:23:10 and here 4:23:12 in formatting 4:23:14 okay 4:23:16 I can select repeat row header sorry 4:23:22 display dimension names Okay, 4:23:26 now I again refresh it. So what I can 4:23:29 see how many dimensions I have in my 4:23:32 report? Two account as well as time. 4:23:37 If I go here 100, 200, 300, 400 and hit 4:23:43 on save. What it does? It throws me an 4:23:46 error about the product. 4:23:48 Now the question is when I selected only 4:23:51 account and time why it's showing me for 4:23:53 the product. So it doesn't matter how 4:23:56 many dimensions guys you will include in 4:23:59 your report. By default whatever data 4:24:02 you will input in the report it will 4:24:05 always be across the intersection 4:24:09 of the members of the dimensions. 4:24:13 Now here 4:24:15 we have EPM context. I can see my 4:24:19 account is having balance sheet. Okay. 4:24:23 Category actual entity consolidation 4:24:26 entity measures I can ignore product 4:24:29 total product. So this is the only 4:24:32 dimension where the member is selected 4:24:34 by default as a parent member that's why 4:24:38 system is not allowing me. So the reason 4:24:41 for showing you this example by 4:24:44 knowingly or unknowingly when you have 4:24:46 to create you know many reports and all 4:24:48 sometimes we forget to pay attention on 4:24:52 our EPM context. Now how it can happen? 4:24:54 It can happen because we normally just 4:24:58 to save the area right to make it 4:25:01 broader. We just remove it and then we 4:25:04 think that okay everything is working 4:25:05 fine but it's not accepting that is 4:25:08 because of EPM context. So always click 4:25:10 on this one. 4:25:13 Okay here you are. So what I'll do I'll 4:25:16 select other member any any random 4:25:19 member I can select which should not be 4:25:20 a parent. I'll select product A. Now 4:25:23 what should happen if I enter 100 200 4:25:28 300 400 would it allow me to store or 4:25:31 not? Yes, it will. So we can see 4:25:35 accepted four saved four rejected count 4:25:39 zero that means whatever we have entered 4:25:42 it got saved successfully in the system. 4:25:45 I'll click okay. And now if I refresh it 4:25:49 right my data would remain stay in the 4:25:54 report because it got saved. So what I 4:25:56 can see I entered 100 200 300 400 4:26:00 automatically system is rolling up total 4:26:03 entity as 1,000. Okay but what about 4:26:07 this one total liabilities and equity 4:26:10 and balance sheet I didn't do anything 4:26:12 here. Why it's coming? 4:26:15 because my total asset as well as total 4:26:19 equity are getting rolled up to I mean 4:26:21 total total assets and total liabilities 4:26:24 are getting rolled up to total 4:26:26 liabilities and equity that's why it's 4:26:27 showing 1,000 4:26:30 okay whereas if I expand balance sheet 4:26:39 so total liabilities and equity gets 4:26:42 rolled up to balance sheet why it's 4:26:44 showing me negative negative sign 4:26:45 because of my account type property. 4:26:48 Okay. Now 4:26:52 let's check in the database. So this is 4:26:54 blank right now. Okay. Just go back 4:26:58 it. So you can see that now there are 4:27:03 four entries in the system. What are 4:27:06 those? 100 200 300 400. 4:27:10 In BW backend system, you would not ever 4:27:15 see any parent member data. Okay, that 4:27:19 will happen only in EPM. Okay, 4:27:21 automatically. So for BPC system never 4:27:26 saves any rollup data 4:27:29 understood always remember this from a 4:27:32 conceptual point of view. Okay? Because 4:27:35 it always saves the data at base level. 4:27:38 That's why it will always save the data 4:27:41 in the back end at base level only. It 4:27:45 would not shoot any parent level data. 4:27:48 So we can see there are unwanted columns 4:27:51 as well which you can hide it or what 4:27:53 you can do you can go there right you 4:27:56 can choose field select for select all 4:27:59 characteristics 4:28:03 other than dimensions whatever it is you 4:28:05 can remove it right make sure you always 4:28:08 select sign data which stores your 4:28:10 transaction data which we just entered 4:28:12 in the system okay and 4:28:17 other than that if I remove these these 4:28:20 are the properties these also you can 4:28:22 remove it. Okay. So we can see this 4:28:27 or to show you in a very 4:28:31 short manner what I can do I can remove 4:28:33 this 4:28:38 because properties are not required to 4:28:41 be shown. So earlier uh so guys earlier 4:28:44 you know uh if I talk about two to three 4:28:47 years back like you know uh these 4:28:50 options were not coming earlier like 4:28:52 properties and all based on latest 4:28:54 patch. Now the system is allowing 4:28:57 earlier it was only showing you what you 4:28:59 are going to save in your report. But 4:29:02 now you can see whatever required 4:29:04 properties our dimensions are having 4:29:06 they all are getting visible in the back 4:29:08 end as well. Because for back end it's 4:29:11 simply a 4:29:13 characteristic nothing else. 4:29:21 Okay. So this is what we stored 4:29:23 actually. Okay. 4:29:26 These are the ids for my equity. Okay. 4:29:31 This is my entity type of data. What 4:29:34 kind of data? I just told this is actual 4:29:37 kind of data. 4:29:39 Although in real time scenario actual is 4:29:41 something which will flow from other SCP 4:29:44 system or you know any any other legacy 4:29:46 system to your BPC it should get stored 4:29:50 in budget category but just for showing 4:29:52 you this is the first time that's why uh 4:29:55 we have used actual okay this is for 4:29:58 product A and N is this is by default 4:30:01 the property you can ignore this [bell] 4:30:03 one and this is the currency okay and 4:30:07 this is my sign data. Now here is my 4:30:11 balance sheet 4:30:13 a parent child I mean a parent node or a 4:30:17 child node. So if I select let's say my 4:30:22 product as total product system would 4:30:24 not allow me right. So I had to select a 4:30:28 child member. But here in account I have 4:30:31 a parent node. Then why system is 4:30:34 allowing me to save the data. Right? It 4:30:36 should also be selected at a children 4:30:40 node. Right? 4:30:52 Okay. So 4:30:54 before I do refresh okay so the thing is 4:30:58 that if you select any dimension in your 4:31:00 report okay account time whatever only 4:31:05 those would be the active dimension 4:31:09 drivers I mean not drivers but you know 4:31:12 you can say that my dimension would be 4:31:14 driven by my report only not by my 4:31:18 context. 4:31:19 Clear? 4:31:21 For example, 4:31:23 if I I select I addit report. 4:31:34 Okay. 4:31:36 Now what I did I selected product A. 4:31:40 Okay. In my report 4:31:43 which is the 4:31:46 base level already. Okay. 4:31:51 Now what I'm going to do 4:31:53 I'll save the data. Okay, this time 4:32:04 so did you see system allowed me to save 4:32:07 the data even the total product have 4:32:09 been selected in my EPM context as well. 4:32:18 That means whatever would be in my 4:32:21 report 4:32:23 they would get the preference not the 4:32:26 EPM context but those dimensions which 4:32:29 are not covered in my EPM report that 4:32:32 will be running through EPM context. So 4:32:36 this is how EPM context plays 4:32:40 or it stops your work basically it it 4:32:44 adds up the struggle right that why it's 4:32:47 not working why this report is having 4:32:48 issue so all such scenarios would help 4:32:51 you and will make your you know 4:32:54 experience much smoother when you'll try 4:32:56 report at your end so what we learned 4:33:00 that through EPM context we can select 4:33:03 the members but those dimensions if they 4:33:07 are already in the report on that EPM 4:33:10 context won't work. EPM context would be 4:33:13 applicable only for those dimensions 4:33:15 which are not present in the report or 4:33:17 not visible in the report. And we'll 4:33:20 take a look on our cube. 4:33:25 So we can see budgeting entries as well, 4:33:29 right? 4:33:31 See, so this is the data we have 4:33:33 created. Okay. So, so far like uh before 4:33:38 uh we move ahead for data manager or for 4:33:41 other aspects okay of the report right 4:33:45 so let's see this if I show you here 4:33:48 okay it shows 200 right now okay BS 211 4:33:54 okay 4:33:56 let's see how it works I was coming on 4:33:58 that part actually there are many other 4:34:00 scenarios okay let's say we take 700 4:34:04 Now ideally 200 should get replaced with 4:34:07 the 700 4:34:09 only one record which is going to save 4:34:15 what we actually saved we saved 700 4:34:18 right so what it did system checks that 4:34:21 okay 700 means 200 already there then 4:34:23 500 more right so it makes it 700 why 4:34:27 because BPC is a software okay which 4:34:30 basically works on you know 4:34:34 accounting mode right debit and credit 4:34:37 okay that's why it does the adjustment 4:34:40 now for example if I have to remove this 4:34:44 okay if I just remove it and save the 4:34:48 data now what should happen it's zero 4:34:53 right now what should system show me 4:34:56 zero 4:34:58 so what it will do it will do the entry 4:35:01 in debit credit pay Okay. 4:35:05 So you can see 700 right got knocked off 4:35:10 with these values having negative sign 4:35:13 500 700 minus 700 so that comes zero it 4:35:19 will never save zero it will always 4:35:22 replicate with a reverse number 4:35:24 okay because it's working in accounting 4:35:27 mode debit credit so in BPC there's a 4:35:31 way to add comments okay but it has some 4:35:34 restriction 4:35:35 Okay, up to that level, you will be able 4:35:38 to give comments. 4:35:40 So yes, it has that feature as well. So 4:35:43 that will be covering as we go by for 4:35:45 reporting. 4:35:47 >> How about the supporting document? For 4:35:48 example, I have a document that I want 4:35:50 to attach. So will you be able to 4:35:52 attach? 4:35:54 >> Document is something which you can't 4:35:56 attach but you can definitely share a 4:35:58 link of that. Okay. In that command 4:36:00 because it 4:36:01 >> comment section, right? 4:36:02 >> Yes, it has a restriction. But as the 4:36:05 other other new tools in the market 4:36:07 right which are available in that 4:36:09 there's no limit you can save any number 4:36:11 of pages as a comment as well. And the 4:36:13 good thing is that here the commands 4:36:16 would be you know uh more like attached 4:36:19 to a particular report but there the 4:36:21 comments will get overridden by the 4:36:23 selection of data. 4:36:25 So that's a good thing and that uh that 4:36:29 is something you know which uh you can't 4:36:30 expect because mostly we we expect that 4:36:33 okay in our database numbers or 4:36:35 combination of the data will get stored 4:36:38 but you know that is using some 4:36:40 different table to store that without 4:36:42 having uh the same thing in our 4:36:44 database. So like you know right now 4:36:47 it's BPC similarly there's SEC for 4:36:50 planning right SAP analytics cloud yeah 4:36:53 yeah multiple lines multiple pages I 4:36:55 would say there is no limit that one 4:36:58 okay so we have seen that okay how to 4:37:01 create a basic report how my child and 4:37:05 parent node making an impact on the 4:37:07 report when it comes to saving the data 4:37:10 okay how EPM context play its role okay 4:37:14 in terms of driving the overall report. 4:37:17 Okay. Now, other than that, if I have to 4:37:20 create a fresh report. Okay. What's the 4:37:24 other way? Right. So, for that what you 4:37:26 can do, you have a edit report option as 4:37:29 well. Okay. Here also you can see three 4:37:32 sections. Page access, row access and 4:37:36 column access. 4:37:38 Okay. So, what we can do? I'll 4:37:42 I can select here, move it or I can drag 4:37:45 and drop. Okay, I put that under page 4:37:48 access. Okay, I can go there. 4:37:52 I can select individual 4:37:58 member. Okay. And then I click on okay. 4:38:03 I can I can remove anything. Okay. 4:38:12 in my time dimension. I'll select all 4:38:17 and I just delete them. 4:38:22 So now what I'm going to show you those 4:38:26 are the real time problems and how to 4:38:28 deal with that. Okay. So what we can see 4:38:31 there the last updated year is 2017. 4:38:35 Okay. And we are in 2024. 4:38:37 So these members are not in the time 4:38:41 dimension. Correct? So what we will do? 4:38:45 We'll go here. 4:38:47 We'll go to our dimension. This is time 4:38:50 dimension. Right. This is where I'm 4:38:52 supposed to make the changes. Agreed. 4:38:54 >> Yeah. 4:38:55 >> I'll go here and I can see that. Okay. 4:38:58 They have a lot of data. Okay. As per 4:39:02 the some requirement or scenario. What 4:39:05 I'll do? I'll just scroll it down. 4:39:09 Now I have to create 2024. 4:39:16 Click on add. 4:39:21 Okay. 4:39:23 I'll create 4:39:25 this simpler hierarchy. 4:39:44 Sometimes it does because you know 10.1 4:39:47 is the you know uh older version which 4:39:50 is going to have a sunset by let's say 4:39:54 2027 4:39:55 and it depending on the server right so 4:39:59 whatever weird things you can expect you 4:40:01 can expect up to you know uh this 10.1 4:40:05 in the system even in the realtime 4:40:08 systems as 4:40:33 So what it saying that error exist in 4:40:36 the member list. So we need to solve 4:40:38 those errors. 4:40:55 I think that was that got created that's 4:40:58 why it's showing that ID is not unique. 4:41:03 Okay. So in here 4:41:16 Okay. So, our dimension got processed. 4:41:19 Okay. 4:41:24 Now, we'll filter. 4:41:30 So, you can see that it's not showing 4:41:32 2024.06, 4:41:35 right? 4:41:36 >> There's nothing. There's no member. 4:41:38 system sometimes does such kind of a 4:41:41 weird thing then you can come back 4:41:45 let's go again okay 4:41:48 yes so BPC demands lot of patience with 4:41:53 consultants as well okay 4:41:57 the system has allowed us now what we'll 4:42:01 do we'll come here okay 4:42:05 we saw that still it's not showing What 4:42:07 we'll do, we'll cancel it. Okay, we'll 4:42:11 go back here. 4:42:14 And again, it's not showing us, 4:42:17 right? Although we have created in our 4:42:20 BPC web link, but that is not visible 4:42:23 here in my EPM report. And on the other 4:42:28 hand, we are saying that everything is 4:42:30 connected. We don't need to do anything 4:42:31 manually. Okay. So maybe let's click on 4:42:35 cancel. 4:42:37 Even I log off. I'm going to login 4:42:40 again. Okay. 4:42:53 Okay. We are in the report. We have 4:42:57 logged in again. Okay. I believe 4:42:59 whatever changes had to be visible that 4:43:01 should be visible by now. Okay. So 4:43:04 although I have to do the same exercise 4:43:06 I'll move it to page access so that I 4:43:10 can centrally drive it. 4:43:13 I'll select product C this time. 4:43:16 I'll remove this unwanted 4:43:19 parent node. I'll go to time dimension. 4:43:23 So you can see that right now 4:43:28 there's another way as well. Okay. Let's 4:43:31 say you can't do you know log off login 4:43:33 again and again. Okay. So for that 4:43:36 ideally this is something which you 4:43:38 should try when nothing is working for 4:43:40 you. Okay. 4:43:42 I'll create 2025 4:43:46 01. 4:43:53 So we have 2025 as well. Okay. Now in my 4:43:58 report if I go here I don't see 2025. I 4:44:02 just simply cancel it. Okay. If I go 4:44:06 again and hit on time 4:44:11 I can't see 2025. Okay. So rather than 4:44:15 going logging and log log off again. 4:44:18 Okay. What you can do click on more. 4:44:21 Okay. And here you can click on refresh 4:44:26 meta data. Okay. 4:44:29 So that also does the job. Okay. So that 4:44:32 you don't need to login and log off 4:44:34 again. Okay. Go to time. 4:44:39 See 4:44:41 we are able to see 2025 right without 4:44:44 doing log log on and log off right. 4:44:53 Correct. So that's a easier way but uh 4:44:56 like uh mostly people are not aware 4:44:59 because they never tried that. Okay. So 4:45:01 this is the way and these are the issues 4:45:04 which you will always have or you can 4:45:07 have while having implementation because 4:45:10 whenever you create a new member any ID 4:45:13 you would be not able to see the report 4:45:15 then what you need to do and this action 4:45:17 you you need to perform either mostly go 4:45:20 for refresh metadata that doesn't work 4:45:23 log off log on again plus as we have 4:45:26 just observed there was no unique ID but 4:45:29 system was throwing the error simply 4:45:31 Filter the option, right? Filter it out. 4:45:33 If that is available, good. Not 4:45:36 available, just go back and back again, 4:45:39 right? Within the dimension and create 4:45:42 system would allow you. So, this is a 4:45:44 technical, you know, uh flaw of BPC 10.1 4:45:48 version that happens not just in server 4:45:52 ones but also in real time systems as 4:45:55 well. Okay. So you don't need to lose 4:45:57 your cool just have patience and try 4:46:00 again. So it would allow you. So what we 4:46:03 going to do? 4:46:05 So this is the second way of creating 4:46:07 the report. Okay. 4:46:10 See if technically 4:46:13 you are clear right then you can 4:46:15 implement any scenario. It's just the 4:46:18 terminology whether be it planning, 4:46:20 forecasting, consolidation, anything. 4:46:22 It's just a scenario. If you know that 4:46:24 okay how you'll make the system work 4:46:26 right 4:46:28 what I'll do I'll just simply select I 4:46:30 can select manually as well I can select 4:46:33 parent node as well okay you can select 4:46:35 the required members 4:46:41 click on add members okay now here you 4:46:44 have option how you want to display in 4:46:46 the report whether in this way or simply 4:46:49 in ID way so I just selected ID so that 4:46:52 you know that would take less space in 4:46:55 my column section. Similarly, I go to 4:46:58 accounts. I'll just remove them. I'll go 4:47:03 to income, 4:47:05 operating income, expenses or let's see 4:47:09 gross margin and total sales. We have 4:47:12 third party sales, inter company, I'll 4:47:15 remove it. Cost of goods sales, material 4:47:18 cost, labor cost. 4:47:20 Okay. And then we have a portal cost. 4:47:25 So here also I have options. So I'll 4:47:27 choose description. I need only 4:47:29 description not ids. So such kind of 4:47:32 requirement keeps on coming that okay 4:47:34 sometimes you want to view only ID. 4:47:36 Sometimes ID and description sometimes 4:47:38 only description. So you can select 4:47:41 through this option. Okay. Click okay. 4:47:45 And you can choose the position 4:47:49 where you want to show and just hit 4:47:51 okay. 4:47:53 So now we can see that this is our 4:47:55 report. Okay. 4:47:58 So that looks much straight and easier 4:48:01 as compared to the last format for 2006 4:48:04 which we saw. Right? So here also you 4:48:08 have option 4:48:10 go to sheet options for any report 4:48:12 always sheet option is the key. It has 4:48:15 everything. Okay. Now there are four 4:48:18 tabs formatting, refresh and protection 4:48:21 that we will take uh as we go by. So 4:48:24 here you can see that it has options 4:48:28 like you know display dimension names 4:48:31 repeat headers and columns. If I select 4:48:34 this one okay and if I select this one 4:48:39 okay then what would happen? Indent 4:48:41 parent indent children. Indent is there 4:48:44 like ch children are getting indented to 4:48:46 right side right because personal cost 4:48:49 is my parent labor cost material and 4:48:51 third party sales are the children okay 4:48:54 or I can choose no indent indentation as 4:48:57 well now if I refresh it this is what I 4:49:01 have plus other than that I have other 4:49:03 options okay to change the look and feel 4:49:08 okay that how I'm expanding anything 4:49:10 whether member and children children, 4:49:13 descendants. Okay, I can choose 4:49:16 descendants and I refresh it because 4:49:19 it's already expanded. Okay, I can 4:49:22 choose children as well. In a large 4:49:24 report, you can do in this way. Okay, so 4:49:26 what I'll do? 4:49:30 So this data will get stored for product 4:49:33 C. Okay, since it's a parent but nothing 4:49:36 came because these are not the direct 4:49:40 children of this personal cost. So we 4:49:42 can even remove this one. Okay. 4:49:48 So 100 200 300 we have. So these are the 4:49:51 three columns 100 200 300 we just saved 4:49:55 for product C. 4:49:57 So I hope everybody in this call is very 4:49:59 much clear that how our you know uh 4:50:02 whatever we input in our EPM report how 4:50:05 that makes impact in my database how it 4:50:08 will look like in my database right. So 4:50:11 this signed data. So this signed data is 4:50:14 something which we entered as a figure 4:50:16 in our EPM report right that gets saved 4:50:20 under the column sign data. It is at the 4:50:23 intersection of the other dimensions 4:50:26 members right like budget product C USD 4:50:30 US these are the accounts labor cost and 4:50:34 all right for these time time periods 4:50:38 right these for these periods now we 4:50:40 know that okay how to create a basic 4:50:42 report how to just enter the data right 4:50:45 how to play with dimension with member 4:50:47 with model right then how 4:50:52 I can do things with the calculation. 4:50:55 Okay. How my calculation will play the 4:50:57 part. 4:50:59 >> See property is you know in edit report 4:51:02 you can go. Okay. There also you can go 4:51:06 you can choose or make selection based 4:51:10 on properties as well. Here this is the 4:51:12 option filter by properties or there are 4:51:15 EPM functions as well. Okay. So on which 4:51:18 we'll discuss. Okay. when we'll be you 4:51:21 know only working on proper on only 4:51:24 working on reporting part but here you 4:51:27 know like as for today's agenda it's 4:51:29 more about data manager package right 4:51:31 and before data manager package I wanted 4:51:34 you guys to be on the same page with me 4:51:36 that okay how that works and where that 4:51:38 works so for that basic reporting 4:51:40 knowledge was required so that we have 4:51:43 covered here now this is what we have 4:51:46 done on EPM and this is what you will do 4:51:48 on EPM tab So this is all about creating 4:51:50 the report input form. Okay. Then what 4:51:54 about data manager? Okay. As I said data 4:51:57 manager is the tab which is used to 4:52:00 execute the calculation which is used to 4:52:02 make the system work based on some 4:52:06 conditions or based on some process 4:52:08 chains of okay which are standard ones. 4:52:13 So that actually def process chains are 4:52:16 nothing predefined 4:52:18 functionality or calculation. Okay. 4:52:21 So data manager is used to execute the 4:52:25 calculation. How to create the data 4:52:27 manager. Okay. 4:52:30 So before creating the data manager you 4:52:33 always need to create a data manager 4:52:36 group. Okay. That defines 4:52:39 what is the data manager? What's the use 4:52:41 of that? Okay, how to do that? So for 4:52:45 that we have organize, 4:52:48 package list, package link list, right? 4:52:53 There are different use of these. But 4:52:55 before that let me show you how my data 4:52:58 manager looks like. When I click on run 4:53:01 package, now what does this run package 4:53:03 means? Package will execute a particular 4:53:06 calculation. Okay, if you click on this, 4:53:10 what you can see here, 4:53:13 there are two process chains, right? In 4:53:17 package chain, in package group, this is 4:53:20 for model consolidation. 4:53:22 Okay? Having different different process 4:53:25 chains, these are standard ones. 4:53:28 Okay. So before that what we'll do, we 4:53:32 have to create. 4:53:33 >> Yeah. Yeah. So here you can see 4:53:36 connected to planning this one. Okay. 4:53:38 But when we go there that shows ng2 that 4:53:41 is the reason it's not showing us our 4:53:45 own model. Okay. So for that what you 4:53:48 can do you can simply come here click on 4:53:52 this one minute VPC connection. 4:53:58 Okay. 4:54:00 Choose your connection again. 4:54:04 Now if we go to data manager run package 4:54:08 we can see planning XYZ okay 4:54:12 and there's another thing many times 4:54:15 when you will select this thing right 4:54:18 even after then system would not allow 4:54:20 you right so in that case what you can 4:54:23 do go to EPM okay and then you can click 4:54:28 on report actions 4:54:31 manage connections 4:54:33 And here again you need to select 4:54:36 particular 4:54:38 model and click okay. Okay that that you 4:54:42 need to do when you try everything but 4:54:44 still system is not allowing you. Now if 4:54:49 you click on run package okay what we 4:54:51 can see data management. So all the 4:54:54 basic operations related to data for 4:54:57 that there are predefined 4:55:00 or 4:55:02 you know readyto use process chains are 4:55:07 available which will do particular 4:55:10 work. How it will work that we'll see. 4:55:14 For example copy it says copy 4:55:16 transaction data. it will copy the 4:55:19 transaction data from one intersection 4:55:22 to other intersection. Okay. 4:55:27 So if I select this simply click on run 4:55:32 then it says handling of records how you 4:55:34 want to carry forward. There are many 4:55:37 ways of doing that but since uh this is 4:55:39 our first session on data manager 4:55:41 package. Okay. So copy records with 4:55:44 match key or copy by replacing data in 4:55:47 same data region of this this this right 4:55:51 we can select this one. 4:55:54 Go to next. Do you want to run default 4:55:58 logic? Now what is default logic? That 4:56:00 also we'll discuss. Click on no. Do you 4:56:04 want to check work status? I know there 4:56:06 are many new terms are coming for you 4:56:08 right? So that will cover. So for a 4:56:11 timing click on no. 4:56:14 Now here we are. Okay. Now what it shows 4:56:18 based on our model right it's showing 4:56:20 the exact dimensions which we are having 4:56:22 in our model right 4:56:25 now we have to define okay we have to 4:56:28 select how as the name suggest copy what 4:56:32 it will do it will copy my data set from 4:56:35 one intersection of the data of same 4:56:37 dimension to other intersection of the 4:56:40 dimension members. So for example what I 4:56:42 want to copy I want to copy all these 4:56:44 numbers right 4:56:47 to 4:56:48 where to a particular any member which 4:56:51 I'm going to select okay so for example 4:56:54 if uh I believe we have done the entries 4:56:57 in January right I'll select click on 4:57:01 head. 4:57:16 So in the meanwhile screen appeared. So 4:57:17 what we going to do? We will see that 4:57:20 how this data manager does the work, 4:57:23 right? How it can do particular 4:57:25 calculation. So copy is the standard 4:57:28 function offered by BPC. Okay. So what 4:57:32 we'll do, we'll copy the data from 4:57:34 January 24 to June 24. Okay. Without 4:57:41 doing the same exercise again because 4:57:43 right now it's just three entries. Okay. 4:57:45 But in real time scenario, you know, the 4:57:48 volume of data is huge. Let's say more 4:57:49 than 5,000 10,000, right? So it's not 4:57:52 possible for you to copy and paste 4:57:54 everything. So you will simply run the 4:57:57 package that will do the job for you. 4:58:00 Okay. 4:58:39 Okay. 4:58:42 And that was for product C, right? We 4:58:45 won't do anything over there. 4:58:48 It was for budget. 4:58:51 Okay. So, what we are doing all the 4:58:53 system is not allowing us to select uh 4:58:56 it but ideally it does. So we just 4:58:59 entered in our source 2024.01 4:59:02 January data into June month. Okay, 4:59:05 let's see whether it works or not. But 4:59:07 this is how you will use the copy data 4:59:10 manager package. If you hit on copy, so 4:59:13 it again shows you that okay, this is 4:59:16 what your selection, right? Everything 4:59:19 remains same. You're copying the data 4:59:21 from January data into June data. Okay, 4:59:27 there are three ways in data manager 4:59:29 package. One is like run. If I hit on 4:59:31 finish, system will start executing the 4:59:34 calculation, executing the process 4:59:36 chain, right? Which will copy the data 4:59:39 from January 2024 to June 2024. 4:59:44 Another way is like schedule. Okay, 4:59:46 schedule is like you know you can run 4:59:49 you can decide that okay after 1 hour it 4:59:52 has to be running or on particular day 4:59:54 that also you can do run and schedule 4:59:56 you want to run as well as you want to 4:59:58 schedule that also you can do so we'll 5:00:00 use run click on finish 5:00:05 some black screen is coming I can't see 5:00:07 what message it's giving but let's close 5:00:11 it now whether it's running or not we 5:00:14 can see the status and view status 5:00:17 We can see it has succeeded. 5:00:21 Now many times when you run the package 5:00:23 right and if calculation is not much it 5:00:26 will directly show you the result 5:00:27 whether succeeded failed or anything. 5:00:29 But how do you know whether it has done 5:00:31 something or not but if not technically 5:00:33 at least you can just double click on it 5:00:36 and at least try to see that okay how 5:00:38 many records it has written. So we can 5:00:41 see that okay except count three submit 5:00:44 count three. So at least three records 5:00:47 that means something happened right 5:00:50 ideally three records is what system 5:00:53 need to copied and if it has done that 5:00:56 then that means it's successful what 5:00:58 I'll do I'll come on EPM if my copy 5:01:03 package has worked properly right I 5:01:05 should be able to see the data in June 5:01:08 month but here we don't have June month 5:01:10 so we have to select again so I'll just 5:01:13 refresh it Right? We can't see the data 5:01:16 because we didn't select that member. So 5:01:18 now I'm going to have that member again 5:01:21 in my time dimension. 5:01:37 Maybe we need to 5:01:39 close. I don't want to actually we 5:01:41 didn't save it. 5:01:50 Let's say this is 2024 June month. Okay, 5:01:54 I hit enter. 5:01:58 Okay, I refresh. Now if if it's June, 5:02:00 right? As I refresh, system would show 5:02:03 me the same data what we have in 5:02:05 January. 5:02:06 So this is how data manager helps you 5:02:10 right to perform calculation without 5:02:13 doing the you know uh same work by in 5:02:16 traditional way where you will copy the 5:02:19 data and then paste it and then save it 5:02:21 right so it saves lot of time plus we 5:02:25 will do calculations okay how that works 5:02:28 based on data manager package that also 5:02:30 we'll see so is it clear that why it's 5:02:33 working and how it worked to everyone 5:02:35 one. So you can ideally you can go to 5:02:38 data manager. Okay. You can go to view 5:02:41 status. 5:02:43 You can see the status. Double click on 5:02:46 this. 5:02:47 Okay. You can expand it and you can see 5:02:51 this everything would get covered here 5:02:53 that from here to this is the 5:02:55 combination. 5:02:57 Okay. These are the accept counts and 5:02:59 submit count is zero. If there would be 5:03:01 any error submit count would have been 5:03:03 zero. But here you can see it's three 5:03:06 that means it has uh you know it 5:03:09 performed the required calculation. So 5:03:11 this is the log file. Okay, you can see 5:03:14 for others as well, right? Because right 5:03:16 now only in this environment I'm 5:03:18 running, right? If you would be 5:03:20 accessing the same model you would be 5:03:22 running here also I can see that okay so 5:03:24 and so user is here you can see that 5:03:26 okay user right 5:03:28 >> okay 5:03:29 >> so based on this you can see that okay 5:03:31 which user is working on where what they 5:03:34 have executed right so data manager 5:03:37 package as we have seen we can you know 5:03:40 run it we can schedule right we can 5:03:43 execute so there are many process many 5:03:46 activities which don't need human 5:03:49 intervention right and that can be 5:03:51 executed during the night times right 5:03:53 where we don't want anybody to wake up 5:03:55 and you know run the uh particular job 5:03:58 or particular process chain right so we 5:04:02 can automate them so that in the morning 5:04:04 when they will log into the system 5:04:05 automatically system will execute that 5:04:08 if there is any issue any log right they 5:04:11 have to hardly see the status in the 5:04:12 morning if the jobs have been executed I 5:04:16 mean the data management packages have 5:04:18 been executed perfectly fine then you 5:04:21 can see it succeeded. If there's some 5:04:23 error you can see failed. Okay. Then 5:04:26 what happen again? Those needs to be run 5:04:28 manually during the daytime. If there's 5:04:32 some, you know, particular calculation 5:04:33 activities dependent on that. 5:04:36 >> All right. Let's test your knowledge. 5:04:38 Here's a question for you. What is the 5:04:40 advantage of using SAP BPC 10.1 over 5:04:46 traditional spreadsheetbased planning? 5:04:48 Option A, better data security. Option 5:04:51 B, improved collaboration. Option C, 5:04:54 faster processing times. Option D, all 5:04:57 of the above. Take a moment to think and 5:05:00 when you're ready, choose the correct 5:05:01 option. Remember, each choice holds a 5:05:03 key to unlocking the answer. Good luck. 5:05:06 Type the correct answer in the comment 5:05:08 section. 5:05:09 Hey there. Ready to dive into the world 5:05:11 of SAP BPC 10.1? Our course is your 5:05:15 ticket to mastering supply management 5:05:17 all at your own pace on our platform. 5:05:19 [music] In this course, we'll unravel 5:05:21 the mysteries of SAP VPC 10.1. Think of 5:05:24 it like a Swiss Army knife for planning, 5:05:26 [music] ensuring we've got enough 5:05:28 goodies and getting them where they need 5:05:30 to be. From the basics to expert tips, 5:05:32 we've got you covered. Crafted by 5:05:34 seasoned pros, this course delivers the 5:05:36 goods. Your mentors, top-notch veterans 5:05:39 in the feed, ready to guide you through 5:05:41 and tackle any queries you throw their 5:05:43 way. And hey, don't just take our word 5:05:45 for it. Our students are singing their 5:05:47 praises. Folks just like you have found 5:05:49 this course a game changer. Best part, 5:05:52 it's easy on the wand. Learning doesn't 5:05:54 have to cost a fortune. Ready to become 5:05:57 a SAP VPC 10.1 maestro? [music] 5:06:00 Enroll now. For more details, visit 5:06:03 Xarentex website.