SAP SuccessFactors Employee Central Complete Course Day 9 | Objects

0:01 This conference will now be recorded. Yeah, thank you for bringing up. Okay. Now you can have the association between the objects either one to one or one to many. Okay. So different scenarios can have you know different associations. In standard corporate data model we have associations defined only for three objects and that doesn't limit us to no create association at other object level. Now we can create we can create associations at other objects as well. If you have a requirement of adding the association first let's see how to know or where are these associations configured. How many associations are

0:47 there? Okay. If you look at location object, pay range object and pay component group object. So these three objects have associations. Now let me go to pay range. You expand pay range associations. There are three associations. ID of the association is always ID. You have three associations here. ID is ID. And then you have multiplicity one to one or one to many. Destination entity whether this association is required or not. Destination means which object you want to link. Now here if you see pay range is a element which contains grid. Pay

1:35 grid is a object. You see pay grid is also object. Geozone is also object. Look legal entity is also object and you have one to one one to one here and one to many here. Now if I go and open the same in front end manage organization pay and job structure. Go to manage pay manage organization pay and job structure and look at the existing pay range. So if I want to create a pay range, it is mandatory to have your grade selected. So where are these grades coming from? The grades. All of these grades 10

2:20 Cadbury, 11 Cadbury, 12 Cadbury. So all of these grades are here. Now if I go search for the grades here, it shows up the grades. These are pay grades. If I go select a grade, this is grade. This is grade element. Similarly, if I go create a pay range, I can choose one pay grade to one pay range. If the association is defined between two objects with multiplicity one to one, it is always within the fields. Now, these are fields. Along with these fields, we have this field as well. But this is not a field. Technically, this is not a field. This is an association as one to one. This is also association 1 one but we have added it

3:07 as an association as 1 one. So you can go and choose the value from here. These are the existing users and wherever we have associated the object with multiplicity one to many. So you will see it as a separate section. This is your certification question. Whenever you associate one object with the other object with multiplicity one to one it will be along with the other fields and if it is one to many will always be a different no a section it's kind of different section now you see legal entity I can add many number of any number of legal entities to this range so one legal entity go add another legal entity legal entity is nothing but a

3:53 company okay so I go add here another. So I can keep on adding any number of companies here. Many companies can be added to one pair because the association defined is one to many. And this is it says this is mandatory. These two are optional and this is mandatory. Why? Because here it is set to have true required and false here. Similarly, if I go and look at the association defined between pay component group and pay component, it is only one one association. So, it is showing vertically. ID is ID, multiplicity is one to many, destination object is pay component and required is equal to true. Here you have

4:41 association two associations one to one and one to many. Geozone is 1:1 and legal entity is one to many. So if I go and look at the object location you will see one geo zone and many legal entities. Somebody has added today they have added business units. Okay this is added clear on association. Now how do we define this associations in the code this is in the table structure that's fine but if I want to look at the code you go to source and if you see here association is starting here and ending here it is

5:29 starting here and ending here these are the two associations okay before the field before or before the hrs element closes we have the associations S okay we go here table view and if I want to add a new association you cannot do that in table structure you'll have to go to you'll have to go to code now how do I do that if I go here source I want to add association just copy the existing one just copy existing one paste it here and you can change the destination entity. Let's say this is my association. I've added three here.

6:17 Now if I go to table view, so I see here three geo zone legal entity and another one is also legal entity. But I want to have let's say dynamic role. So you go add here dynamic role. Okay. Now you will see this added to your location. Okay. Again same thing if I want if I don't want to use you'll have to go delete that delete that line item in the source view.

7:04 clear on association. Yes. Okay. Yeah. Let me refresh this. And then next after association element label fields associations and after association we have the last option of such criteria. The fields here what you see this fields this fields this fields these fields all of them are same only in table structure they are duplicated in code they are not duplicated. So if I place my cursor here and go to source it takes you to the same place. If I place my cursor here it takes you to the same place it if I

7:51 place my cursor here go source it takes you to the same place. So all of them are same. Now after associations you have trigger rules. Okay. So we generally don't use any rules here in corporate data model. This is a sample rule which is added but we don't use any rules. Rules we'll be talking in the coming sessions almost like after 50%age we'll be starting off with the trigger rules. We'll see or we'll talk more about the business rules. Okay sessions. And the last one that we have is the search criteria. After fields you have search criteria. What does search criteria mean? Now whenever you search for any

8:38 object if I go choose geo zone. Okay these are existing geo zones. So you see the name and this is the code RTV_1. Let's say if I say RTV_1, I'm searching with these two fields. Which fields? Either with code or name. So when I search with name AP or name, you see this is AP. So with what fields you want to search now search criteria for this object is these two fields code and name. Maybe the front end the the field label is showing as code but back end

9:24 the id of the field is external code. So the search criteria is added as external code of this field and name of this field. I go here search criteria expand. By default for every object the search criteria is two fields external code and name. Which external code? You go expand the fields here. Expand the fields here. External code. What is the external code label? Go and check the label of external code. This is code. That means you can search with code of an element. Code of a field. Okay. external code of a field or

10:12 name of a field because the search criteria is defined as two. And here if I go and look at location, okay, search criteria is defined as four fields. Search criteria is defined as four fields. Corporate address, city, corporate address count, country, external code and name. Now if I go here search for location I search for location you see I can have I can search with name of the location ID of the location corporate address city corporate address country. So with any of these fields I can search and I can also search with IND which is country.

11:00 So it shows up all of those locations which are in country India. because we are using country corporate address country as one of the search criterias for our object. Now if I go to any of the location where is corporate address? Now this is your corporate address. You have city and country. With these two fields you can also judge. Now here the town or city is blank. So that's why when you search for a B1 A B HIO1 you see city is null because it is not maintained country is India AB_1 and

11:47 AB now this is AB_1 so either you can search with the external code or name field if I go to search criteria of the location corporated or city entry, external code and name. Clear on association and search criteria. By default for all of the objects the search criteria set as external code and name field. You know in the HRS field in the HRS field the third HRS field the okay

12:35 the the count is different compared to one and two. For example in the one you have 76. Yeah that is 76 and next is also 76 but the third one is coming as a different. Can you just go on the right side? Yeah the third one. The last one. Yeah. Yeah. Okay. So here they have it given only the standard uh fields what are now if I go here source view. So how many fields we have. Okay you see here field. This is a field and let me minimize. Oh okay. So this is the label of the element. 1 2 3 4 5 6 7 8 9

13:24 10 11 12 13 14. So we have all of these fields. Okay. So let's go and see in the table structure why they are showing up. Uh HIS field expand external code. Okay. So these are fields which are enabled by default. And then you have custom strings. Okay. only 20 up to 20 are showing up here. If I place my cursor here. Okay. And see here, I still have this field showing up here. This is not available. Okay. Maybe the table

14:09 limitation. They have table limitation. They're showing up only 29 here. But we have the actual file in the low source file. You have all of those. Or here you have all of those. Okay. Okay. Any other doubts? That's it. That's your corporate data model. So, what did we see in corporate data model? It is the ids of the elements, labels of each of those elements, fields where we have max length, label of the field, visibility of the field, required whether it is

14:54 true or false. Okay, max length visibility required association relationships and then trigger rule. We don't generally use any rule. Okay. And then you have search criteria. Simple. Okay. You know what does this uh HR element mean? Like dynamic role. His element dynamic role is one of the foundation objects which is used in workflows. Okay. Now dynamic role is a role where you define the approvers

15:42 dynamically. If you want uh approver to be triggered dynamically, we use dynamic roles. Okay, give you an example. Now if I want to trigger an approval based on a location let's say we have different locations Bangalore, Mumbai, Chennai let's say we have this locations we are operating from these locations now Bangalore some X is the approver Mumbai Y Chennai C and Hyderabad H. So these are approvers. These are the approvers I configure in dynamic role. Okay. Let's

16:28 say and this is used in one of the workflow a transfer workflow. If I'm transferring an employee who's in hydrobed, it goes to H. If I'm transferring an employee who's in Bangalore, it goes to X. Similarly, Mumbai, it goes to Y. Chennai, it goes to C. System will dynamically choose who is the approver. It doesn't go to all of them. It only goes to one of these people based on the location of the user to whom we are initiating the request. This is dynamic role. Now this is one of the element in within dynamic role. So it can be based on company, business unit, division, department, location, grade, event, reason. So any

17:13 of these things can be used as dynamic role assignments or combination of one or two. Company one Bangalore location. Company one Mumbai location. Company two Bangalore location. Company two. Company two Mumbai location. We can also have different approaches with combination of both company and location or company department and location. So you can have any combinations. So you configure it system will trigger the approver dynamically. Okay. We'll talk more about this dynamic roles in workflow session. Okay. So, but there are two HS elements. One is dynamic role and one is dynamic role assignment. Dynamic within dynamic role. Similarly,

18:00 how we have the corporate address in location within dynamic role you have dynamic role assignments. Go to dynamic role here. So, you see dynamic role assignments. So that's why it is showing up. Okay. Okay. So we only have 11 elements association al together but because some of the objects have sections. Okay. Like dynamic role assignment is part of dynamic role. Corporate address is part of location object. workflow config step, step approver and workflow contributor, workflow config CC. All of

18:45 these are part of workflow section. So if I go to element workflow, you will see all of them in one object called workflow. This is workflow config. This is workflow step approvers. This is workflow contributors. And this is workflow CC role. 1 2 3 four. Four sections in player. 1 2 3 and four in workflow config. Yeah. Okay. Now it's clear what we know. Yeah. Yes. Somebody have a question in the chat. Let me take that as well. To create an association, do we use ID or label? Always whenever wherever you want to use, you always use

19:31 the ID of the object, not the label of the object. Label can be anything. Today we have it as X. Tomorrow you change it to Y. Label can be changed at any time. Now today we are calling it as location group. But tomorrow if customer says we can change it to state. But if you are referring this object somewhere else, you should go and change there as well. So that's why we don't use the names, we use the ids. IDs are always unique. Huh? Yeah, IDs are always unique. Somebody else also had a question. Was that any other questions?

20:17 Can we move on? Okay. So that's your corporate data model. Defining the corporate data model. So you design what fields you want to have in each of the objects and wherever you have to change you can go and make those changes in data model you go employee central implementation configuring the system sorry here 1.3 right 1.3 this part is done defining the super admin. Now the sorry defining the corporate data model

21:04 is done. Now fourth step is to define the country specific corporate data model. Fourth step is defining country specific corporate data model. What is country specific corporate data model? Country specific corporate data model defines the corporate address of each country. Right? Again, this can also be downloaded or uploaded from instance. I will duplicate this screen and on the search bar global search bar I search for corporate data

21:51 model. You go to import export country region specific XML for corporate data model. Okay. So you have here import and export. If I go export, go to your file, right click and open with XML pad. Okay. Go to table view country specific fields. We only

22:38 have one element here called corporate address defined for 52 different countries. For these 52 countries, we have the element corporate address defined. So all of these are corporate addresses for different countries. Again, this is a country ID. For each country ID, we have the address format defined. If I go to India, I this is India. Okay. Corporate address. Expand the corporate address. There are eight fields. What are those fields? Expand those eight fields. Address 1 2 3 city county state

23:23 zip code and country. Let me open corporate address location. Here you have country. Go choose India. You go choose India. So these are the fields. Now why is it saying address line one? Here it is. Address one. Right? The label is defined as address line one. Okay. It is defined as one. Now somebody must have removed all of those labels. Okay. So that's fine. Address line one. And you don't have county in India. We don't have county here. But this county field is

24:09 labeled as district. For India, this field is labeled as district. The ID of the object is county. But the id of the field is county. But the name or the label what we are using is district. Okay. And state is a pick list. It is a drop-down where you see all of the states of India. So if I go and check the pick list here. Now this field state field is referring to a pick list. Go expand the pick list and see here state_indd. That means all of these values what we have in the state or union territory field. These fields are these values are coming from a pick list

24:57 called state_indd. Similarly if I go and select a US corporate address there are nine fields again here you have state pick list it is mapped to state USA. So if I choose state sorry country as United States then system will show me the states of this country. So these are the states of this country. Okay so all of these fields nearest landmark there's a field called nearest landmark. What is this nearest landmark for us? See address three is

25:43 labeled as nearest landmark. This is set as true. required is set to true. Expand this is nearest landmark. Clear? Yes. Yes sir. Yes sir. Corporate country specific corporate data model is simple. We only have one element called corporators where we define the country specific fields for each country. You want me to make any change and show or is it

26:29 fine? Usually we will not make any changes in country specific corporate data model because what fields you want to have that's customer will not go to the screen to maintain location. It is we who would be operating it. Okay. So let me remove this business unit here. Upload the corporate data model.

27:18 Okay. Clear on corporate data model and country specific corporate data model. Yes sir. Fourth step. Next is the fifth step. Step five which is setting up of MDF objects. From here onwards we do a lot of configuration in instance. Okay. Till here this is part of either provisioning or instance but we generally don't do any of these changes in system. Okay. But from here it is always the is setting starts from setting up of MDF foundation object. configurations we start from setting up

28:04 of MDF foundation objects. Okay, let's see before going and setting up the objects let's see the type of objects. So far we have discussed about foundation objects right? So types of objects object definition object maintenance and bulk object maintenance and we'll also see examples of each of

28:49 those objects. Foundation object. Now we know foundation object. We know where do we define them? Corporate data model. Where do you maintain them? Manage organization pay and job structure. Don't get confused between maintenance and definition. Definition is designing the screen what fields you want to have and maintenance is in those fields you go add the

29:35 data that's maintenance. Examples have location, pay grade, pay range etc. Pay component frequency workflow etc. All of these are examples. If you have bulk objects to be maintained. Now if your customer says I operate I operate from 100 different locations. So we need to create all of those 100 locations. But maintaining the 100 locations manually through manage organization pays difficult task. It is possible but it is a difficult task. It might not take 2 or 3 days to create those 100 locations. Instead we can have all of those details in one Excel file and upload. So this

30:20 upload can be done through import foundation data. There's a screen called import foundation data where we can go and upload the data. Okay. Next here the fifth step is setting up of MDF foundation objects. So we'll discuss what are MDF foundation objects. There were many foundation objects initially or some time back we used to have many foundation objects but now we only see those 11 foundation objects. Location group, geo zone, location, pay

31:06 frequency, pay component, pay component group, workflow, dynamic role, event reason. So these are only 11 foundation objects that we have. Along with this foundation object there were many which are migrated to instance which are removed from corporate data model and these objects are called MDF foundation objects. Metadata framework foundation objects. Okay. So where do we define them? They are removed from corporate data model and place them in instance. There's a place called configure object definition. Configure object definition and maintenance part we do it in manage

31:52 data. If you have to create those objects you'll we'll be doing it in manage data. And what are the examples of these objects? We have legal entity which was a foundation object earlier but now it is MDF foundation object. business unit, division, department, cost center, job classification, etc. So all of these are the examples of MDF foundation objects which were part of corporate data model earlier but now they are migrated and we define them in configure object definition maintain them in manage data because they we have migrated them we maintain them in manage data and we can

32:39 also upload or download using import and export data. Foundation objects can only be imported uploaded from import foundation data. We cannot download we need to use reports. But for MDF foundation objects we have option of importing and exporting it through import and export data. The third type of objects are generic objects. All of those objects which exist even before the MDFs are migrated, they are all called the

33:25 generic objects. We do it same as MDF foundation objects. We define them in configure object definition. This is configure object definition and we manage them through manage data. Examples we have time type, f holidays, f position etc. So all of these are your generic objects. They are defined in configure object definition and maintained in manage data and bulk objects can also be maintained in import and export data. So what is the difference? Why do we have two different names? MDF and

34:14 generic MDF objects which are migrated from corporate data model are called MDF objects. Technically speaking both of them are same. You can call them MDF or generic. Anything is fine. Can also call them as these MDF objects. You can call you can also call them as generic objects because they are configured or defined in configure object definition. Okay. And the last type of objects are employee objects. Where do we define them? succession data model or you do it in MBC screen manage

35:00 business configuration we know now we don't do it in h I have a question okay MDF objects or the global objects yes and generic it it depends okay it depends we have country specific objects also there Okay, object maintenance we use add new employee for the first time if you are hiring you add them through add new employee and later we use employee files to maintain the data examples you have job information you

35:46 have personal information you have comp information you have address information, national ID information. So all of them are examples. So here succession data model or country specific succession data model both of them are maintained in both of them are defined in MB MBC screen also manage business configuration. Okay. So you here you can have the country specific ones as well and bulk objects can be maintained using import employee data. import employee data. So this table is very very important. You will

36:33 get some questions in your interviews, some questions in your certification as well. So if you are to if you are asked if your customer says no they want to have 100 cost centers maintained in the system. So where do you maintain them? You have two answers to select. So you can maintain using manage data and also maintain using import and export data. Okay. Similarly, if you are asked to create a location, where do you create? Or if you are asked to define location, where do you define? Configure object definition, corporate data model, manage organization pay, manage data. They'll give four options. You'll have to choose

37:20 one. Okay. So, if you know this table, 50%age of your configuration is ready. 50%age of the configuration. What we do? We do it from this table. Very very important. You just have to understand where are these objects configured and maintained. So what is that object? Where do we define and where do you maintain? So the fifth step of setting up MDF objects. Let's go and look at what does SAP says here. Here as part of phased migration of foundation objects to MDF which is metadata framework. The following

38:07 foundation objects are now MDF foundation objects also referred as JOS generic objects. Any AG information configured using these foundation objects will now be configured using corresponding MDF foundation objects. What are those objects? Cost center. This got migrated in Q4 2014 release. Earlier the release was happening quarterly. Q1, Q2, Q3, Q4. We are calling them Q1, Q2, Q3, Q4. Now because success factors have changed the release schedule to offly it is now called 1 H and 2 H. First half and second half of the year and this is quarterly cost center migrated in Q4 2014. Department migrated in 2015, Q2 2015 all of this and then these you these got migrated in

38:53 Q4. So all of these are MDF foundation object. Cost center, department, division, business unit, legal entity, job function, pay group, K, pay calendar, job code, job family, job classification, local. So all of these elements only these elements as part of phased as part of migration. The object definition for these foundation objects have also been migrated from corporate data model to MDF. And as a result, the migrated foundation objects will no longer be configured in corporate data model. Instead, the configure object definition page is used to configure MDF foundation objects and manage data page will be used to manage MDF foundation

39:41 objects. Okay. So any doubts here? Now you know what are the types of objects? So what is the difference between MDF and generic objects? Where do you maintain? Where do you define them? Yes. No doubts. Yeah, we had to mug up. Sorry, we had to go through that one. What will you go through? Just just a simple table with four rows, five columns. That's it. Can somebody tell me what are the foundation objects that we have seen in corporate data

40:27 model is or pay? No, I want the names of the foundation objects that you have seen in corporate data model. Location location dynamic release pay grade workflow dynamic dynamic release roles workflow workflow yeah all of those workflows comes under workflows only okay next event reason event reason Okay. Have five more, right? Uh,

41:15 pay component. Pay component. Okay. Dynamic role assignment. Dynamic role assignment is part of dynamic ro object. Configuration. What configuration? So we have pay component group, we have frequency, we have location group here. Okay. FP range. Okay. How many of them are there? Total of 11. So here within workflow you have workflow config.

42:02 Okay. Workflow contributor, webflow CC, approvers, all of these four are part of workflow. Dynamic role you have dynamic role assignment. There's one more. Now it shows as another object but it is not another object. It's part of your dynamic role only. Dynamic role assignments. And then you have corporate address in location. Okay. Now the foundation objects what we are talking about. Okay. I I'm going back to your kickoff

42:56 template employee central foundation object. So we have 10 more minutes. So I'll discuss this as well. Employee central foundation objects. Foundation objects are the building blocks of easy system. And there are four categories in it. First one is orc structure, location structure. Location structure also comes under ar structure. We don't have separate structure called location structure. It is also part of a structure. Job structure and pay structure. So these are the elements. Okay. Now some of them are migrated we are calling them MDF and some of them are still in corporate data model so we are calling them foundation objects. Okay. Now within O structure we see legal entity, business unit, division, department and cost center. So

43:43 these five elements are migrated. All of the O structure elements are migrated and we maintain them in manage data. We define them in configure object definition. Second, location structure. Both of them are in corporate data model. So we define them in corporate data model. Maintain them in manage organization pay. Third, we have job structure, job classification and job function. Both of them are migrated and we maintain them in manage data. So we last structure which is pay structure. Now some of these objects are migrated and some are still in corporate data model. Pay group is migrated. Pay range is still in corporate data model. Frequency is still in corporate data

44:29 model. Pay component, geosone, pay component group. So all of these 1 2 3 4 5 are still in corporate data model. Pay group and pay calendar are migrated to instance and we maintain them in manage data. So let's see what are each of those objects. What does a structure do? O structure tells us where in the organization the employee and position belongs. Now if somebody asks you where are you working what you will say a company name right so I'm working for deote oh okay deote of what department are you working in okay I'm working in maybe SAP okay or maybe a division or a business unit is SAP within SAP what

45:15 module are you working in I'm working on SAP MM or SAP HR so are you a technical consultant or a functional consultant I'm working as functional consultant. So now if you look at the structure the highest level is your company within company you are segregating all of those under your company. Okay maybe as a business unit or a division or a department or a subd department. Okay I'm working in HR department. Do you have any sub departments of HR? Maybe payroll, maybe admin, maybe learning, maybe performance, maybe appraisals, maybe compensation. So these are the several subd departments of HR. Now some customers may say that we want to have all of these as a all of

46:02 them as sub departments or some may say that we have only one department called HR. We don't want to segregate further into sub department. So we want to use only department. So we can have the department. So all of it comes under the O structure. Next is the job structure tells us what they do in the organization. So if you have engineers, if you have production managers, production executives, what do know what is their job in the organization? So some do the production, some do the electrical work, some do the civil work, some do the mechanical works. Depending on their role they are in, they would be doing different jobs, right? So job structure

46:48 tells us what a person does in the organization. Pay structure tells us what should be paid to the employees. You have different pay grades. Okay. Now trainees would be paid stipened. Manager should be paid some amount maybe 10 lakhs to 20 lakhs. Residents or directors should be paid between 50 to 1 cr. Okay. Now the pay structure is different. They have basic, they have H, special, medical, convenience. Now this is this structure is different for different employees. So all of this is defined in P structure. Now location structure can be a separate or part of the O structure states where employee physically sits in the organization. They say where do you know

47:35 where are you located? If I'm located in my location is Bangalore but I'm working from Chennai. Okay. So that is your physical location where you work. My base location is Bangalore. Okay. Now these are the foundation objects. So what can we do with these foundation objects is we can rename them. So we have seen that locations group I have renamed it to state. Right? Similarly pay range can be renamed to salary range. Pay grade can be renamed to band. So whatever name that you want to give to those foundation objects you can go and rename them. So depending on the type of the object that you want to rename either

48:20 you go to corporate data model and do that change or you go to configure object definition if you want to do it for MDF for generic objects. You can associate them meaning build the relationship between objects. One object can be associated with another object. Now you will see the business unit, the company associating with business unit, business unit associating with division, division associating with department, department associating with cost center. Okay. Similarly, pay grade associated with pay range. Pay components associated with pay component group. So you can build the relationship by associating the objects. You can decide

49:06 what data is held against them. Now if I have changed my label of one of the object from location group to state all of those values that I maintain in that object are states now okay so you decide what you are going to now I create a custom object I've named it as sub department so what whatever that you create now those are the sub departments which are belonging to a particular department so you associate both of them and use them wherever required. Right? You can default data to employee record from them. Now you maintain some data. Yesterday we discussed two scenarios where now the job code when you whenever you update a job code system was

49:51 updating all of the other fields. So that is propagating the data transferring the data or defaulting the data. Similarly, after creating a position, if you assign this position to employee, system defaults all of the data from position to employee that is defaulting data and all of these objects are effective dated. Effective dated meaning every object that you create in the system. Okay. Now, some of them mostly 99%age of the times the objects are effective. So, every record that you create it would be with one effective date. Let's say you are implementing for one of the customer called Starbucks. Starbucks started in 2000. Company established in 2000. So the company

50:37 effective date when you are creating that company in the system. So the effective date the start date is let's say 110 2020 2000. Let's say 11200. That means your company exists from 2000 because you have to hire or add employees starting from 112,000. Maybe there are employees who are there in the organization from 112,000. So you'll have to hire them or add them into the system. Right? So the effective date should be from 112,000. So every object is effective dated. Maybe I'm planning to expand my business. I want to create one more business, one more company starting from 11 1225. I might be hiring or I may be hiring some employees or moving some employees from one company to other

51:22 company starting from 11205. So you create a company with 112025 and move those employees. Earlier when you look at the history of the employees employees started their journey with the organization from 11200 okay in this company X later we have created one more company we moved this employee to this company from this data. So you will see the historical records of the data and you have the effective dated. Okay. So all all of the objects are effective dated. Any doubts here? So we will stop it here for today and we'll continue tomorrow. I don't see

52:09 implementation guide in the drive. You don't see implementation guide. There is there implementation guide is there. Yeah, it would be starting with like this SF_EC_Master_MPL. Okay, you may check and if it is not there, I'll upload. Okay. But but I think it is not latest. Which version do we have? I'll ask them to upload the latest one. I'll share the new one. This is one H 2024. You should be having the one H 2024. We have two H2. Okay. I'll I'll share the latest one

52:55 then. Okay. And from tomorrow you will have lot of work to do. So every day we'll be doing the configuration. of till today whatever that we have done it's almost like no theoretical part only few things like corporate data model country specific that we have done but from tomorrow onwards everything we'll be doing in the system only okay so tomorrow we'll set up the MDF foundation objects we'll have that homework for Saturday and Sunday okay uh Wenu I've got a the server which I'm logging to you know the credentials shared by you

53:41 am I only person using that or multiple persons using the same portal we we never know portal yes there are many users who are using that maybe hundreds we never know no uh because we are taking the server out yeah the account yeah we never know how many users are using that uh account or that company or demo instance Okay. How does that matter? I am making some changes and those are being reverted. So that's how I yeah maybe because you're know you're making some changes and

54:28 others are trying to do that and then see now yesterday when I have downloaded the data model I saw the association only legal entity but today when I you know when I have downloaded it or when I have opened the system it was showing one more object called business unit in location generally we don't use business unit In location we only use legal entity but somebody has changed it. So what I have done I have re-uploaded that data model. Now you see here business unit usually business unit is not associated with location. The legal entity is associated with location. Okay. People practice a lot of things and we cannot know control

55:14 users. See now legal entity. Okay. All right. Thank you. Yeah. Thank you. Okay. Thank you all. Have a great day. We'll catch up tomorrow. Thank you [Music] so much.