VID16-- Creation of MDF based foundation objects & its Associations

Brief Summary

This video explains how to create relationships between parent and child objects in SAP SuccessFactors Learning using associations. It covers the different types of associations (generic object to generic object, generic object to foundation object, and XML-based to generic object), and when to use composite or valid when association types. The video also explains when to create associations at the parent or child object level, based on whether the objects are independent or dependent.

  • Explains the concept of parent and child objects in SAP SuccessFactors Learning.
  • Describes how to create associations between objects using configure object definition.
  • Covers the different types of associations and when to use them.
  • Explains when to create associations at the parent or child object level.

Parent and Child Objects

The video introduces the concept of parent and child objects using the example of head offices and branch offices. A head office (e.g., Mumbai, Hyderabad) can have multiple branch offices reporting to it. These branch offices are considered child objects because they report to the parent head office. The key difference is that while a head office and a branch office can exist independently, a child branch must report to a specific head office. This structure is used to maintain job location details for employees, ensuring that when a head office is selected, only the relevant branch offices are displayed.

Foundation Objects and Organisation Structure

Foundation objects are used to define the structure of a company, including its organisation, pay, and job structures. The video explains how to create relationships between parent and child objects to define the organisation structure. For example, a head office is a parent object, and branch offices are child objects. Similarly, a branch office can be a parent object, with departments as child objects. The selection of the parent object determines the available child objects. These objects can exist independently with their own start and end dates, meaning they are not dependent on any other object.

Types of Associations

To create a relationship between parent and child objects, associations are used. The video outlines different types of associations: generic object (MDF-based) to generic object, generic object to foundation object (XML-based), and foundation object (XML-based) to generic object. The type of association depends on whether you are linking two MDF objects, an MDF object to an XML-based object, or vice versa. The video highlights that associations are configured in the configure object definition, where you can specify the association name and multiplicity (one-to-one or one-to-many).

Multiplicity and Object Types

When creating associations, you must choose between one-to-one and one-to-many multiplicity. One-to-many is used when one parent object is linked to multiple child objects (e.g., one head office to many branches). One-to-one is used when one parent object is linked to only one child object. The video also distinguishes between dependent and independent objects. Independent objects have effective dating as basic or none, meaning they can exist on their own. Dependent objects derive their details from the parent object and exist only if the parent object exists.

Independent Objects: Business Unit and Division

The video uses the example of business units and divisions to explain associations between two independent objects. Both business units and divisions are MDF-based foundation objects that can exist independently. For independent objects, the association is configured at the child object level. In this case, the association is created within the division object definition to link it to the parent business unit. The type of association used is "valid when" because both objects have effective dating set to basic or none.

Dependent Objects: Legal Entity and Legal Entity USA

The video explains how to create associations for dependent objects using the example of legal entity and legal entity USA. Legal entity is an independent object with effective dating set to basic, while legal entity USA is a dependent object with effective dating from parent. For dependent objects, the association is created at the parent object level. In this case, the association is configured within the legal entity object definition to link it to the child legal entity USA object. The multiplicity is one-to-one, and the type of association used is composite.

Field Criteria and Filtering

The video briefly touches on how these associations are used for filtering data. The configuration sets up the relationships between parent and child objects, but the actual filtering based on these relationships is achieved through field criteria. Field criteria is the next step after creating associations, and it determines how the system filters data based on the selected parent object. The video concludes by emphasising the importance of understanding the different types of associations and when to create them at the parent or child object level.

Summarize any YouTube video in seconds

Get summaries like this one for any video, in your language, with the free Summ app.

Download on the App Store
Get it on Google Play

Transcript

YouTube Transcript Generator

0:01 foreign object okay once you select parent object as Mumbai then you will have a you will have some child objects why are we calling this child objects because these come under this parent object it means their report to this parent object Okay so this Branch can exist on its own okay and even this errant also can exist on its own okay but yeah only difference is this

0:48 Branch cannot exist on its own or I'm sorry okay it has to report to some branch okay so a child branches yes so let's say I have another setup I have another office head office in Hyderabad also okay and then yeah baby branches it um okay let's see if you're happy branches one pack next we have um

1:47 okay let's say these are the branches related to Hyderabad head office branch yes okay it means every head office has its own child branches or branches which report to it similarly even for Hyderabad head office also there are some specific branches which report only to Hyderabad they cannot report to Mumbai okay so let's say I have a position or for an employee I am maintaining the this job location details um okay employee

2:32 job info here company code let's say I give some ABC company um head office maintenance which is in Mumbai okay um right so let's say I'm mentioning Andheri okay so head office so I'll have two different options one is Mumbai and the other one is Hyderabad okay so let's say I have selected because you have two different database both of them being generic objects you

3:20 will see both of them in the drop down okay then lecture have selected Mumbai but branch office the child objects okay I should not see both of them or I should not see Hyderabad related Branch offices I should specifically see only Branch offices which are reporting to Mumbai head office yes so when I go to Branch here in the drop down I should see so to filter this based on the head office that I have selected I will select

4:05 anderia as my branch office okay let's say Andheri may be our location set or let's say departments beginner another structure Department and uh HR Finance marketing and advertising

4:52 okay and let's say we have purchasing the furniture purchasing what are the operations now these are departments so again when I select Andheri I should be able to see only these two departments I should not see HR purchasing or operations okay so next if I select borivali I should be seeing either marketing as my department or advertising in the dropdown I should be able to select only these two I should be seeing only any of these three or I can I should say only these three

5:39 and I should be able to select only one from any of these three not these uh these two are these two okay so let's say I have selected Mumbai as my head office is you tell me because I have selections and there you selected so it should be finance and sales correct exactly let's say I am selecting Finance foreign

6:35 okay so in this way there is a company organization structure okay looking at this you will be able to understand what is the structure of the organization so this is one of the reason why we have Foundation objects okay so using the foundation objects will Define the structure of the company so I've told you that we can Define organization structure pay structure and job information job structures okay these structures whatever that we are trying to Define here are related to the organization structure okay so I am trying to create relationship between a parent object and

7:22 a child object head office is the parent object and Branch offices are the child objects um then again if I take this one as the parent object then the Departments are becoming the child child object okay so every time there is a different department under I'm sorry different parent object under different child object different child objects yeah based on which parent object you are selecting the child object will differ will differ okay similarly in case if you're talking about finance and sales departments your child objects okay if you're talking about the Department Child objects then your parent object will be different you cannot say that head office is the

8:07 parent object it has to be branches okay uh clear with this point he is the parent that is the child correct that's right okay okay we have head office okay this is an object we have branches this is another object and then we have the Departments with these are different objects so these objects can exist on its own it means it will have its own start date and end date okay so when I say it has its own started and indeed it means they can exist independently they are not

8:54 dependent on any other object okay so earlier when we were discussing about uh metadata framework I was telling you that based on the effective data we can decide whether it is a dependent object or a child object okay dependent object or a independent object sorry okay so in case if you select basic or even none it means it can exist on its own independent object yeah but if you select from parent it means this dependent derive its details or it will exist only if the parent object exists dependent objective dependent object okay so now what we'll do is let's say legal entities is an existing object

9:40 okay or yeah normally this is the hierarchy which 90 percentage of the companies follow okay legal entity business unit division Department cost center so this is the hierarchy so on the top it will be always legal entity next it will be business unit then Division and gun Department okay but some of the clients do interchange these based on their requirement okay now let's say I select I have company code and based on that I want to filter the business units

10:27 okay so similar the way we have now defined head office let's say this is the head office and these are the branches foreign first thing I need to create a relationship between these two objects I have to do something in the system some configuration so that the system will know that okay this is going to be the parent object and this is going to be the child object so to create this relationship we create something called as associations okay so if this is the object now we

11:12 have come in to configure object definition and we opened legal entity foreign okay this is the place where we create the association between the parent and the child object okay now we'll see what are the different types of associations then we'll try to create the association between a parent and the child object Okay so uh I want you to again I'm telling you I want you to go through this header files and the fields okay yes then let's get into the associations part so first thing Association name you can give any name here you just want to

11:57 give it a name so that you will identify it that's it okay let's say if you want to create an association between a legal entity and a business unit you can just give two business unit simple okay the only thing that you have to do is you have to blindly remember what I am telling you that's it even if I uh if you do it 10 times and if I come back to you after three months and ask you how do you create Association you will definitely forget there are higher chances for you to forget because this is not something which we create on a daily basis it will exist throughout the success factor usage I mean in case you're using

12:44 for last 10 years or for next 10 years also it is not going to change because okay so let's uh not get into the configuration let's first try to understand what are all the different fields available and then we'll do the actual configuration okay first we have given some name next we have two different options this is called multiplicity of an association okay multiplicity do you want to create one-to-one

13:31 Association or one to many okay so in our example I have explained one to many it means when I select a particular head office I have multiple child objects okay multiple branches so it means one object is linked to many branches right then in that case you will be selecting one to many one too many so in case you think you must have a certain appearance there is only one head office and only one branch you get the one to one yeah correct simple X is exactly that's it simple next what you have to do is you have to select the parent object

14:24 when both the objects are independent objects it means both the objects have effective dating as either basic or none if it has parent then it's a different setup okay so we give the parent object okay okay I'm really sorry first thing I have to tell you about the associations different kinds of associations so associations are different types hmm jio to jio which means this is generic

15:09 object to generic object okay okay it means the associations are between two different MDF objects um okay so it means you are going to Define these associations using configure object definition okay so you come into configure of the definition and at the bottom of the object you will be able to see the association's configuration part and there you will be creating the associations okay then we can even create association between jio and then F4 sorry so when I say F4 Foundation it means a MDF based Foundation objective

15:57 and this is XML based okay so yeah let's say I'll give you an example here I'll give an example between legal entity and business unit okay example let's say I want to create an association between department and location okay then we have F4 XML based to jio which means MDF based okay let's say I want to

16:44 create an association between um a component and division just for an example okay XML based objects MDF based object layer okay um Foundation objects you mentioned you know XML based huh hello are you human

17:29 okay sorry internet I'm not able to hear your voice properly your watch is very much yeah yeah see what I'm asking is you mentioned Department correct so what does it mean like objective department is an object is XML based object minute department is a MDF based object

18:15 so um because location maybe I understand the department is not a foundation object that is MDF for best okay got it now what exactly are you trying to ask me no now I got it I was confused with Department why did you mention Department in Foundation object that's what I was thinking okay all right okay so these are all the different types of associations now first thing let's cover this generic object to generic object which means it is between two MDF objects

19:00 okay so in a nice say two different MDF objects again there is a difference there are different types of associations let me get into an Excel sheet better okay first one I'm saying jio means um generic object it means MDF is object to here MDF base objects okay next I have jio MD of objects to F4 XML based next I have F4 XML to jio MDF so why are we interchanging this

19:47 because one can become child and the other one can become parent one can become a parent and another one can become child I say interchange is another different type of Association okay now in MDF also we have MDF to mdfk beach maybe we have two different type of associations between two dependent objects and independent objects okay so MDF and ndfk Beach may

20:33 be we have two different associations one is dependent object and the other one is independent objects um okay so when I say dependent objects it means the effective data will be infected as parents parent okay when I say independent objects it means the effective basic or none basic or none okay so um now the example that we will take is between two independent objects okay so the example that we are taking

21:20 is now let's say we are associating between business unit and division okay so business units unit and division both are Foundation objects which are MDF based okay and both can exist independently because their effective dating will go back to the system now effective dating is not from parent simple okay this is basically let me go into division okay effective rating basically so it

22:05 means both these objects can exist independently both these have different date settings it will exist from a different date okay so now I was explaining this Association part so first we'll give the name of the association let me delete this or no okay I'm giving the name of the association to business unit Association I want to link this particular object with many uh objects okay parent objects

22:53 so I am going to select one to many okay destination object I am going to select business unit okay so why are we selecting business unit what is the procedure here now let's get back to the Excel sheet so now we are discussing this topic independent objects right so when we are talking about independent objects the association the association should be built or configured a big child object level

23:42 okay remember this now when I say dependent objects the associations will be created at the parent object level now remember this okay so what I meant by this I'll try to explain now independent object child object level dependent object parent object level yeah now we'll try to explain this part okay I am saying in for independent objects the association have to be configured at the child object level so now we are taking the example of business unit and this is division okay so business unit is my

24:30 parent object it means this is the top one okay um okay it means division will be reporting to the business unit yes okay so if I want to create Association for independent objects we know that both business unit and division are independent objects why because the effective dating is basic basic okay then now we know that division is going to be the child object so if we know that there is a child object involved and uh there is a parent object with and both are MDF based objects then we have to go into this particular object

25:16 definition child objects object definition so that's what I meant by creating an association at the child object level Okay so now I want to create a relationship between this business unit under Division and I want to tell the system that my parent is business unit my division styled objects parent is business unit so to Define this now I'll go to configure object definition and open division okay so I'm going into configure object definition and I open the object division okay because this is the child object and this is an independent object

26:01 or when Nature around then we will be able to see the associations part here I have given the name of the parent object as the association okay business unit if you don't want to give business unit and if you just want to give business you can still give it business okay it's just a name for you to identify that there is an association between this object and this order then I want to give create this association with one too many yeah I want to have multiple multiple associations relationship then we have the destination object child object and I'm telling the system or random

26:49 configuring the association with a parent object so yeah business unit because this is my parent object this is my parent object now so we went into the child object configure object definition and we are trying to associate it with the parent object business unit so I'll select business unit as the parent object then this is a little important type we have three different types we 99 point nine percentages we use only composite and valid value

27:34 okay joined by column we hardly use it I'll uh tell you about this later on we we hardly use it 99.9 percent we only use these two okay so let's focus on these two now we have two different types here okay one is composite and the other one is valid when okay why do we use composite and when should we use valid one Whenever there is a parent and child type of effective dating

28:24 then we will use composite type okay this is a little confusing is that's it there's no other way I cannot give you a logic to for you to remember this part okay valid when we will use only when both the objects have effective dating as basic or not okay um which we have to keep in mind yeah exactly correct

29:11 so yeah this one is one thing this one is another thing yes so we have different types of associations here types of Association okay all right

29:56 generic object MDF Foundation object XML MDF XML m d f I okay so I'll just uh repeat this once again types of associations we have the OT 0 to F1 fo to go okay where do we configure the association when we have independent objects it means the uh

30:41 the effective dating is either basic or none we will create the association in the child object if there are dependent objects then we will create the association in the parent object okay when do we select composite these two are interlinked when you are using independent objects then you will use valid one

31:27 this one you will use compost okay is this clear now okay independent objects Association dependent object selector we will create the association at the parent level object and the type of Association will be composite so now the objects are two different independent objects because we are creating the association between and a foundation object Division and the foundation object business unit so the association type will be valid when

32:13 okay clear with this why you're there I cannot hear you hello uh Avinash I'm not able to hear you okay so this is how the association is created between two different independent objects now we have seen this part okay so we have configured association between a business unit

33:01 and a filed object division okay so if you want to check these associations you just come to configure optic definition come to division object and you will be able to see the associations at the bottom chicken now let's talk about this one dependent objects we will create this Association only when there is an association between a parent object which is a different independent object under child object which is dependent on the uh parent object okay okay

33:46 let's take the example of legal entity for legal entity base object is actually a independent object how do you know that it's an independent object because the effective data is basic simple basically okay now I am saying that now I want to create an association between a parent object and a child object and here the child object is a dependent object both

34:32 parent and child objects are independent but yes when I say dependent objects parent only is a independent but child object is a dependent dependent okay so now we have to pick up two different objects where the parent is a independent object and the child is a dependent object

35:17 okay now we picked up the parent object because the effective rating is basic now we have to pick up a child object there is a child object which is country specific legal entity let's say USA so when you select legal entity USA is it means this cannot exist on its own simple okay so when I say this a this uh effective dating is from parent now the system should know what is the parent you're just saying that okay this object cannot exist on its own and it has a

36:02 parent object but what is that parent object how do you know so you will have to link or relate this object this child object with a parent object okay so now we have a child object which says the effective trading is from parent the parent object will be legal entity okay because the effective rating is basic okay so here in my Excel sheet I mentioned that to create an association when there are dependent objects it means the parent is a independent object and when the child is a dependent object then we will create the association in the parent object level foreign

36:54 entity USA So based on this okay based on Association must be configured in the current level of parent object level so parent objects okay so earlier when we were looking at independent objects division or the business unit okay but because division is a child object Association Division okay I I know it is very confusing but I want you to watch this video multiple times and write down notes because

37:46 this is this is the only part where is which is very tricky and it's called logic this is how the sap system is built and you have to blindly remember it that's it okay dependent objects so the parent object will be legal entity and the child object will be legal entity USA so I have to go into this parent object to create the association with the child object okay the associations are already existing I'll show you how it is built so legal entity configure object definition or just like any other object the association will be at the bottom of the

38:32 object okay so yeah okay just some Association name saying to Legal entity USA then the multiplicity always have to be one to one okay you cannot have one to many because there is only one child object and you can have only one child object Association this cannot be one too many so you have to create one to one here and then select the destination object so yaha pay destination object will be your child object this one okay you have to select the child object will clear create some on our own for

39:18 now I am showing you the existing one because it is already built okay legal entity USA will be my child dependent objects and type of Association as I've told you here Whenever there is a there are dependent objects the association okay that's it we have to save this so this is how the associations are created okay so how do we use this filtering where do we use this filtering see for now you have only see the configuration back end may go relationships

40:05 okay we have not created any data see when I'm selecting Mumbai as my head office I want to see these three branch offices and if I select any of these Branch offices based on that the department should get filtered so we have not come to this example part or data part this is all data part we have only created the relationship between the parent and the child object right now tomorrow what we'll do is we have something called as field criteria which is the continuation of Association okay so in the yesterday's class when I was uh teaching you about

40:52 this feels different yeah and I said we are going to discuss about this part later on okay we have only talked about condition so this field criteria is the next step of Association based on this the filtering will happen yeah okay so this uh for now I don't want to con confuse you anymore so for now I'll I've just created the association part between the parent and the child and also the parent and the child wherein we have created the association between two generic objects okay and two genetic objects independent objects

41:37 or dependent objects Association Okay so if you can just take a screenshot of this one anyway you'll be able to watch this video and uh even from the video also you can take the screenshot but remember this part okay this is most important part so let's continue tomorrow

Share

YouTube Video Summaries