1
00:00:00,690 --> 00:00:04,940
Hi fence welcome to yet another session on success factors here.

2
00:00:04,950 --> 00:00:11,260
We will continue our discussion on the effective due to entities behavior with dollar expand.

3
00:00:11,680 --> 00:00:14,280
So have been looking at the scenarios.

4
00:00:14,280 --> 00:00:23,930
Those are locate the rules that define the dollar expand behavior when navigated from the base to the

5
00:00:24,080 --> 00:00:31,750
chase or the navigation entity here Bill looking an additional scenario for let's proceed to the scenario.

6
00:00:32,720 --> 00:00:40,910
So hearing we have ENP employment object and from that is the that is acting as the base entity and

7
00:00:40,910 --> 00:00:47,970
will be navigate thing to the composition entity which is acting as the navigation entity.

8
00:00:48,080 --> 00:00:55,710
So the query that we have is that GDP as API system affords us success at best outcome for and 4 4 3.

9
00:00:55,820 --> 00:00:58,060
Slash order to slash v 2.

10
00:00:58,190 --> 00:01:03,320
And we have the object and be employment format is Jason.

11
00:01:03,320 --> 00:01:09,350
That is what we wanted the response to be awkward in digital format and we are using the printer based

12
00:01:09,350 --> 00:01:15,160
on user ready which you go through and through a treatable conceit and personally extreme equals on

13
00:01:15,190 --> 00:01:19,840
the Tea Party and will expand decomp in full.

14
00:01:19,880 --> 00:01:31,130
And if so we know that decomp in four and a V is the navigation property of BNP employment object and

15
00:01:31,130 --> 00:01:38,750
that never gets us to the MP compensation object if we're going to the properties for the MP employment

16
00:01:39,170 --> 00:01:45,890
object in the service material document and the if we go into the relationship of this navigation entity

17
00:01:45,890 --> 00:01:53,030
call info and a V will be able to find out the association and if you go into the institution by the

18
00:01:53,030 --> 00:01:59,050
name which is presented by the relationship then you will see the total response to the object in the

19
00:01:59,240 --> 00:02:07,670
compensation as we did in the previous session hearing before going forward let's seek out what type

20
00:02:07,670 --> 00:02:08,600
of objects these are.

21
00:02:09,980 --> 00:02:16,100
So this example demonstrates the behaviour of dollar expended when navigated from the base which is

22
00:02:16,100 --> 00:02:23,990
the ENP employment object which is a type ofa non effective data object to the navigation entity which

23
00:02:23,990 --> 00:02:28,160
is MP compensation which is an effective digital object.

24
00:02:28,880 --> 00:02:34,980
So what we are doing is navigating from a non effective data object to the effectively dead entity.

25
00:02:35,340 --> 00:02:37,420
And this is a query that we are making use of.

26
00:02:37,940 --> 00:02:45,380
We are expanding the company for any company for the Navy is the navigation property of the employment

27
00:02:46,280 --> 00:02:50,440
which navigates us to the entity in big compensation.

28
00:02:51,260 --> 00:02:58,250
If we want to see more and it is how ENP employment and employee composition are related.

29
00:02:58,250 --> 00:03:01,640
So we can go into the success factors Integration Centre.

30
00:03:01,720 --> 00:03:07,660
So let's proceed and let's go into the integration centre severe in the success factors Integration

31
00:03:07,660 --> 00:03:08,100
Centre.

32
00:03:08,320 --> 00:03:15,550
So if you type into four factors Integration Centre tool box in the search box here to the integration

33
00:03:15,550 --> 00:03:20,980
centre would come up and if you click on it it will come down this screen here and we go into the data

34
00:03:20,980 --> 00:03:28,520
model navigator and in the data model Navigator as a name suggest we can navigate through the data model

35
00:03:28,820 --> 00:03:32,420
which is exposed as auditor APAC.

36
00:03:32,630 --> 00:03:43,750
So herein we will select ENP employment that is the one object that we want and from MP employment and

37
00:03:43,750 --> 00:03:52,400
we want the relationship between ENP employment and employee compensation so we have to be competition

38
00:03:52,910 --> 00:03:55,420
to the selective picking process.

39
00:03:55,990 --> 00:04:04,180
And here we have the relationship defined by the two objects as we can see on the up and zooming in

40
00:04:04,180 --> 00:04:04,570
a bit

41
00:04:07,900 --> 00:04:17,210
yeah so you can see on the left hand side we have the ENP employment and on the right hand side have

42
00:04:17,350 --> 00:04:19,680
the MP compensation.

43
00:04:19,740 --> 00:04:26,590
This is the start and price control and click on the second one and then click on this entity MP and

44
00:04:26,590 --> 00:04:29,350
plummet and to find navigation.

45
00:04:29,350 --> 00:04:32,550
So what it does is come up in full and if it's shown up.

46
00:04:33,370 --> 00:04:40,190
So in order to move from the MP employment to the MP compensation you need to go into the combat for

47
00:04:40,190 --> 00:04:41,420
Navy navigation.

48
00:04:41,590 --> 00:04:46,170
That is all you can think of how we can move from one entity to the other.

49
00:04:46,220 --> 00:04:48,530
And how are they related.

50
00:04:48,550 --> 00:04:48,970
All right.

51
00:04:49,240 --> 00:04:56,800
So these highlighted in the blue part is the campaign for the Navy on the MP employment object right.

52
00:04:56,800 --> 00:05:04,850
So now if you can see that look at this little to one that is an employment object can be either 0 or

53
00:05:04,850 --> 00:05:10,190
1 like there could be an employment as the separate but the two that are not but associated with an

54
00:05:10,190 --> 00:05:18,110
employment there could be many compensation information right there could be many MP compensation object.

55
00:05:18,290 --> 00:05:26,500
So the ENP employment is related with the MP competition no one too many manner and the navigation that

56
00:05:26,500 --> 00:05:30,000
can be used just campaign for anything.

57
00:05:30,040 --> 00:05:31,830
So now let's go back to the query.

58
00:05:31,840 --> 00:05:37,690
So number three Luis will try to execute this particular query in the post when I do and to seek out

59
00:05:37,770 --> 00:05:43,770
what is the data being written that it's go into the notepad purposeless because I've copied that regional

60
00:05:43,780 --> 00:05:55,850
query over here so they can be copied so I'll copy this and we're going to Bozeman to take a new tab

61
00:05:56,300 --> 00:06:03,070
when filling the query that we have copied and we'll fill in these basic authorizations that we have.

62
00:06:03,500 --> 00:06:05,290
Let's try to run it.

63
00:06:05,840 --> 00:06:07,740
All right to record the data.

64
00:06:07,870 --> 00:06:16,310
Now we know those set being written which is genetic and the error has one element which is being written.

65
00:06:17,180 --> 00:06:19,550
So the parent had a card Heidi.

66
00:06:19,550 --> 00:06:25,400
So we know that this is all the details out of the parent object that is the ENP in play on the field

67
00:06:25,400 --> 00:06:32,060
are being treated for the ENP and climbed up took over here and the fees that are being returned corresponds

68
00:06:32,420 --> 00:06:43,370
to a specific entry or to a specific instance of GMP employment which is uniquely defined or which can

69
00:06:43,370 --> 00:06:50,860
be uniquely identified by this particular card right.

70
00:06:50,980 --> 00:06:57,030
And how we can uniquely identify that particular record because it has a key information personality

71
00:06:57,320 --> 00:07:02,970
the external is equal to 1 0 3 2 3.

72
00:07:03,330 --> 00:07:10,660
So personality externally is equal to 1 0 3 2 3 and 3 double duty and the Israelis equal to one guaranteed

73
00:07:10,680 --> 00:07:11,370
double digit.

74
00:07:11,460 --> 00:07:14,850
So that is the key information for and employment object.

75
00:07:15,750 --> 00:07:23,180
So this is the entry which just being the one that a card in Japan from the parent entity.

76
00:07:23,280 --> 00:07:26,990
So let's copy this and take out a card of it.

77
00:07:27,220 --> 00:07:36,600
So parent which is the E and B employment we get the card Heidi as this now this is a non effective

78
00:07:36,600 --> 00:07:43,450
dated entity as is evident because they're just not static in the key.

79
00:07:43,900 --> 00:07:47,270
We have the authority external and youth rating.

80
00:07:47,520 --> 00:07:53,110
Now let's take a look at these they didn't application entity recorded.

81
00:07:53,130 --> 00:07:55,270
These are the child entry records.

82
00:07:55,340 --> 00:07:56,730
Those have been displayed.

83
00:07:57,290 --> 00:08:02,530
So if you go here and we go into the company for Navy which we have already expanded.

84
00:08:02,710 --> 00:08:05,190
So we have got the in fine Navy.

85
00:08:05,190 --> 00:08:12,720
Now since we saw that the EMC employment and ENP compensation are related to each other in one is to

86
00:08:12,720 --> 00:08:17,600
manage relationship comp in for a Navy result would be an edit.

87
00:08:18,270 --> 00:08:26,540
And as we anticipated this is a very sensitive and close by Discworld basis and this collapse the result

88
00:08:27,120 --> 00:08:33,900
and we see that within the area there is going to be only one record of compensation that is being returned.

89
00:08:35,100 --> 00:08:41,430
If we expand this then we see all these ideas are the fields and the values.

90
00:08:41,470 --> 00:08:48,560
Now all these fields and values correspond to in the specific instance of employee compensation.

91
00:08:48,750 --> 00:08:55,480
That is our unique record entity and which is uniquely identified by the keys.

92
00:08:55,580 --> 00:09:00,900
So now which is that the cooperating or which is that instance it is this particular part.

93
00:09:01,020 --> 00:09:04,750
So let's copy this and let's take a note of it.

94
00:09:04,810 --> 00:09:08,170
Richard Aedy We can mention it as a child.

95
00:09:08,220 --> 00:09:16,520
Just ENP compensation and will they stick you are all over here.

96
00:09:16,540 --> 00:09:24,290
Here we can see since it isn't an effective dated entity we have got started in the key right and we

97
00:09:24,290 --> 00:09:26,590
have been working there.

98
00:09:26,960 --> 00:09:30,620
So this has got the composite key constituting two fields.

99
00:09:30,620 --> 00:09:35,360
One is this started and the other received the Ready 1 0 2 double to 3.

100
00:09:35,360 --> 00:09:42,060
So now we have got this information from the original creating.

101
00:09:42,060 --> 00:09:51,620
Now let's say we were given a commission that we would have to find out what would be the record or

102
00:09:51,640 --> 00:09:59,850
the specific instance of PMP compensation which should be returned when we are executing this original

103
00:09:59,850 --> 00:10:07,200
query and we would not have let's say liberty of executing that and finding in reality what it could

104
00:10:07,200 --> 00:10:07,530
be.

105
00:10:07,860 --> 00:10:16,400
So how we would have proceeded is now we know comping for a Navy is the navigation property of the MP

106
00:10:16,410 --> 00:10:20,970
employment which navigate us to the ENP compensation object.

107
00:10:21,330 --> 00:10:25,100
So what we will be doing is like we'll move would have defined and you're right.

108
00:10:25,470 --> 00:10:29,410
MP compensation of check right.

109
00:10:29,820 --> 00:10:36,430
And now what we would have done is we would have said in the let's say if we wanted it to be or put

110
00:10:36,430 --> 00:10:42,900
it in the form of Jason and we wanted this.

111
00:10:43,330 --> 00:10:51,930
And since we were on the record corresponding to those which have shown up in the MP employment part

112
00:10:51,950 --> 00:10:57,200
in three days which is facing the MP environment so the MP employment outlook personally and externally

113
00:10:57,200 --> 00:11:02,880
that is equal to this and we want to filter it and the MP compensation we know the keys are in that

114
00:11:02,880 --> 00:11:03,980
idea and this thing.

115
00:11:04,040 --> 00:11:06,640
So we'll fill in you there Heidi.

116
00:11:06,770 --> 00:11:16,910
He calls 1 0 2 2 2 3 and now here in the commission that we have is since we are navigating from a non

117
00:11:16,910 --> 00:11:21,840
effective data entity to an effective dated entity.

118
00:11:21,860 --> 00:11:23,830
So what should be the order.

119
00:11:23,840 --> 00:11:27,790
Should there be any date button which because that we need to provide.

120
00:11:28,730 --> 00:11:30,450
The answer lies in the rules.

121
00:11:30,470 --> 00:11:36,080
So if you go to the site which be sorted who's here.

122
00:11:36,500 --> 00:11:42,170
So we see that there is a second rule which applies to this case if the base entity is not effective

123
00:11:42,170 --> 00:11:48,410
dated today it is used as adopted for an expanding navigation entity.

124
00:11:48,440 --> 00:11:49,950
So in that respect.

125
00:11:50,660 --> 00:11:58,620
So what we need to do is since even before employment has been a non effective dated entity now what

126
00:11:58,640 --> 00:12:07,790
we need to provide hearing is the cause of debt which is the current debt we have to mine the case in

127
00:12:07,790 --> 00:12:13,980
which we have to fill in the update and there needs to be no dollar value because it is a custom created

128
00:12:14,000 --> 00:12:22,880
pattern beta and UTC could do and we have to provide to this date in d d d by V and then via a baby

129
00:12:23,190 --> 00:12:25,890
M and MIDI format.

130
00:12:26,570 --> 00:12:31,260
So not a fit to deaths and if few tried to execute doomed

131
00:12:36,580 --> 00:12:42,160
both back just go back to people's mental and let's say to execute this clause

132
00:12:44,990 --> 00:12:50,050
fill in the authorizations that we have.

133
00:12:50,540 --> 00:12:51,450
Make a call

134
00:12:55,130 --> 00:12:55,990
and head in.

135
00:12:56,040 --> 00:13:04,100
But forget is state is this particular object which is being returned to all of these fields are responding

136
00:13:04,100 --> 00:13:13,400
to the record a specific regard idea of V.A. compensation uniquely identified by these key values.

137
00:13:13,400 --> 00:13:16,730
So the entire object is this debit card.

138
00:13:16,910 --> 00:13:22,040
Copy this and for will do is we'll compare it with these.

139
00:13:22,190 --> 00:13:23,310
You are right.

140
00:13:23,380 --> 00:13:31,520
That being a guard when we had made the original query bearing feet and navigated from deep base far

141
00:13:31,520 --> 00:13:40,240
from the parent to the child entity so we go hear and we had this particular query from the audition.

142
00:13:40,280 --> 00:13:42,430
Right.

143
00:13:42,430 --> 00:13:45,290
And now let's see where do we get.

144
00:13:45,290 --> 00:13:50,260
So this is derived information that we based on the rules that we did right.

145
00:13:50,730 --> 00:13:53,930
And let's confess whether these are the same.

146
00:13:54,350 --> 00:13:56,130
Ah there is a difference.

147
00:13:56,810 --> 00:13:57,750
So we see that.

148
00:13:57,760 --> 00:13:58,350
Okay.

149
00:13:58,400 --> 00:14:04,850
Started time was the same Post of January 2017 and the user data is also same.

150
00:14:04,850 --> 00:14:07,900
So that is the same day card which is being outputting.

151
00:14:08,180 --> 00:14:10,070
So where does that end date.

152
00:14:10,070 --> 00:14:19,390
That that a full understanding of us over the last part is correct and it is indeed following the rules.

153
00:14:19,430 --> 00:14:25,180
And the doubling of footage from the audition query is in accordance with their food right.

154
00:14:25,270 --> 00:14:26,200
So that is fair.

155
00:14:26,290 --> 00:14:28,970
Saw you go to the slide point.

156
00:14:29,210 --> 00:14:30,660
We saw that okay.

157
00:14:30,830 --> 00:14:36,310
Number two the rule that was applied was number two if the base entity is not effective dated today

158
00:14:36,310 --> 00:14:41,450
it is used as as of date when expanding the navigation entity.

159
00:14:41,600 --> 00:14:42,240
Right.

160
00:14:42,350 --> 00:14:43,810
And that is where we saw that.

161
00:14:43,810 --> 00:14:44,280
Okay.

162
00:14:44,330 --> 00:14:51,950
The original query that we executed so that the resolved to what we are int value and that resolved

163
00:14:52,040 --> 00:14:57,630
for the there was only one parent apart which was being put in now find that their entry card what is

164
00:14:57,630 --> 00:15:01,170
the child being uploaded by the same.

165
00:15:01,170 --> 00:15:07,200
So that is where everybody 2017 0 1 0 1 I knew that I d wanted a 2 2 2 3.

166
00:15:07,310 --> 00:15:11,960
But despite the protective code in both the cases all right.

167
00:15:12,030 --> 00:15:13,730
So coming to the next slide.

168
00:15:15,460 --> 00:15:25,480
Here we would look at this scenario building we will try to understand the behavior or expand exhibits

169
00:15:25,660 --> 00:15:27,970
when moving between the entities.

170
00:15:27,970 --> 00:15:31,720
So here we have the two components are two entities kept showing up.

171
00:15:31,720 --> 00:15:39,250
One is the employee compensation and the other one is to become a recurring so obvious entity being

172
00:15:39,250 --> 00:15:47,590
the employee compensation and that navigation entities become a cutting the thing here is before proceeding

173
00:15:47,620 --> 00:15:49,850
let's see what type of objects are these.

174
00:15:49,990 --> 00:15:54,270
Now the base object MP compensation is an effective dated entity.

175
00:15:54,820 --> 00:15:58,180
So here in this case the base object is the effectively to the entity.

176
00:15:58,510 --> 00:16:04,710
So we know first and foremost the rule number one should be adhering to and if we navigate from the

177
00:16:04,710 --> 00:16:15,290
base entered due to the navigation entity and if OK so desperately need both these objects to give effective

178
00:16:15,320 --> 00:16:20,650
dated nature to first of all let's see where the ENP pick on budget cutting is also effective due to

179
00:16:20,650 --> 00:16:23,930
nature and if you see that to be contracting.

180
00:16:24,200 --> 00:16:30,790
OK so there is also an effective digital object but it is an advanced object so it has got MCP enabled

181
00:16:31,180 --> 00:16:37,620
as well so multiple changes per day so that is enabled for this particular object as well.

182
00:16:37,630 --> 00:16:40,310
So it's a fast effective dated object.

183
00:16:40,540 --> 00:16:43,680
In any case it is a category of an effective digital object.

184
00:16:43,730 --> 00:16:46,360
So rule number two still holds true.

185
00:16:46,480 --> 00:16:48,160
What does that state is.

186
00:16:48,340 --> 00:16:56,030
If the base entry navigation entity Both are effective dated it would then be affected and navigation

187
00:16:56,030 --> 00:17:03,800
into the other effective dated then then expanding the navigation entity the effective start date of

188
00:17:03,840 --> 00:17:12,420
the base entity is used as deep as update of the navigation entity.

189
00:17:12,900 --> 00:17:16,000
Alright so where do we start to date.

190
00:17:16,000 --> 00:17:24,820
Effective start date of the base entity that would be propagated and that could be used as a barometer

191
00:17:25,210 --> 00:17:33,820
to supply the value for as update query when executing these output for anti child entity.

192
00:17:34,000 --> 00:17:34,760
All right.

193
00:17:34,940 --> 00:17:39,200
Lestrade to understand on ground there's two in hands on here.

194
00:17:40,930 --> 00:17:41,950
So have happy.

195
00:17:41,980 --> 00:17:49,910
You are a good executing as GDP as it is to move forward such as our component 4 4 3 or the DSP to design

196
00:17:49,930 --> 00:17:50,530
that audit.

197
00:17:50,560 --> 00:17:51,230
You are right.

198
00:17:51,610 --> 00:17:54,120
And then the EMT compensation object.

199
00:17:54,280 --> 00:18:00,760
We wanted to put images and format from but I mean that we have applied all that he had us bust up January

200
00:18:00,760 --> 00:18:06,860
2017 and the filter is applied on youth variety cosponsored by it.

201
00:18:06,960 --> 00:18:14,050
So we are taking into account details that I want to repeat about it and we've expanded the navigation

202
00:18:14,140 --> 00:18:18,760
EMV become recurring and every now since.

203
00:18:18,760 --> 00:18:25,150
It is interesting so let's go back again into the order to murder navigator and try to seek out how

204
00:18:25,150 --> 00:18:31,160
the EMT comp. And the EMT paid comfort occurring are associated.

205
00:18:32,050 --> 00:18:38,680
So if you see first of all we went in from the champion climbing to the M B comp. And now what we are

206
00:18:38,680 --> 00:18:43,370
doing is we are going from MP compensation to the MPP comp ticketing.

207
00:18:43,370 --> 00:18:48,370
That is we are moving further object A to B and then from B to C.

208
00:18:48,960 --> 00:18:56,830
So if we go into the order the modern navigator sets affect us Application Integration Centre and hearing

209
00:18:56,830 --> 00:19:02,720
what people do is first of all let's try to the same.

210
00:19:03,400 --> 00:19:08,490
The by navigation is not we will select the entity though but here.

211
00:19:08,510 --> 00:19:12,980
So let's choose the entities topology and remove these entities here.

212
00:19:13,010 --> 00:19:15,620
So earlier we had selected PMP

213
00:19:17,780 --> 00:19:22,130
implement filters to remove test panels so D.

214
00:19:22,320 --> 00:19:25,690
OK so ENP composition any help required of that.

215
00:19:25,910 --> 00:19:29,030
So we will keep it so we keep it here.

216
00:19:30,030 --> 00:19:33,850
Here in compensation is here and now.

217
00:19:34,380 --> 00:19:41,550
And b be calm recurring in concrete cutting so facilitate that as well.

218
00:19:42,060 --> 00:19:43,970
So what you will see is.

219
00:19:43,980 --> 00:19:49,310
So we have the navigation from data from the base entity to the child entity.

220
00:19:49,680 --> 00:19:55,630
So ENP competition is a parent you have to be a company getting kissed the child and B can see that

221
00:19:55,640 --> 00:19:55,980
okay.

222
00:19:56,220 --> 00:20:03,650
And b competition is serious due to one and where the composition can f many right.

223
00:20:03,700 --> 00:20:10,770
So sure nobody had indeed to be just joining the entities on us we can selected this.

224
00:20:10,860 --> 00:20:18,090
First of all let's let there be competition and then keeping press control keeping s.t. arrows pressed

225
00:20:18,310 --> 00:20:22,300
select in composition and go back to the parent entity.

226
00:20:22,340 --> 00:20:30,740
I click this particular dialog box would output appear these lists of choices and Bentley confined navigation.

227
00:20:30,780 --> 00:20:38,070
So if we do that we see that even to be complicating and if is the navigation property of the parent

228
00:20:38,150 --> 00:20:45,240
which is the end to confrontation which would navigate us to the ENP become particularly object.

229
00:20:45,340 --> 00:20:45,660
All right.

230
00:20:46,050 --> 00:20:49,100
So then that is where it is shown up over here.

231
00:20:49,130 --> 00:20:54,860
And if you see the board line which is showing relating the both of the two entities towards the MP

232
00:20:54,870 --> 00:21:03,540
compensation underlying DC 0 1 and 2 were still line on display in itself joining the game and the compensation

233
00:21:03,570 --> 00:21:06,980
we see and so that is an instrumental relationship.

234
00:21:07,080 --> 00:21:17,310
So now so that is really understood and we can see the keys for the keys for the ENP composition our

235
00:21:17,310 --> 00:21:23,510
start date and the user I.D. and the keys for the MP compensation.

236
00:21:23,630 --> 00:21:29,320
There are four keys a component sequence number start to date and user rating.

237
00:21:29,530 --> 00:21:30,100
Right.

238
00:21:30,210 --> 00:21:37,850
So the start date and use that idea that it did are the two keys for the MP compensation and therefore

239
00:21:37,890 --> 00:21:40,480
keys for the pay complicating.

240
00:21:40,530 --> 00:21:42,210
Now let's go back to the.

241
00:21:42,210 --> 00:21:50,980
You are right that without having to go to the site so now what we do is we will try to execute this

242
00:21:50,980 --> 00:21:51,580
query.

243
00:21:51,580 --> 00:21:58,540
Now the thing is we are trying to seek out how dollar expense would behave when it is going from an

244
00:21:58,550 --> 00:22:02,690
effective rated entity to an advanced effective rated entity.

245
00:22:02,690 --> 00:22:10,480
So let's say you created this go into these not bad press plus we have video already posted over here.

246
00:22:10,480 --> 00:22:17,670
So we have to first credit the additional query so let's go and try to place that into the postman tool

247
00:22:18,250 --> 00:22:25,670
and try to query this so we will open a new tab and put in the committee will provide the necessary

248
00:22:25,670 --> 00:22:34,270
automated libations to query that and let's try to hit send and get the output again.

249
00:22:34,280 --> 00:22:36,200
As anticipated the dancers and the red.

250
00:22:36,950 --> 00:22:37,610
All right.

251
00:22:37,820 --> 00:22:41,520
So now let's see how many.

252
00:22:42,100 --> 00:22:43,040
Okay here.

253
00:22:43,050 --> 00:22:46,230
This time there are parent record ideas which have been our project.

254
00:22:46,610 --> 00:22:47,940
So let's copy.

255
00:22:48,000 --> 00:22:54,230
So this is one first record eighty which is being output for the period.

256
00:22:54,270 --> 00:23:07,260
Let's go do not bad press does take a record of it to feed it given to first record right here and then

257
00:23:07,270 --> 00:23:15,630
it ship parent second record and we'll call and seek out the second record.

258
00:23:15,710 --> 00:23:24,720
What is the second record because you know it and this is the second record which is being hard all

259
00:23:24,770 --> 00:23:25,040
right.

260
00:23:25,310 --> 00:23:33,380
So hearing what you do is so now we would take one by one these theoretical ideas which are output.

261
00:23:34,040 --> 00:23:41,450
So hearing what you would do so for this particular record for the period on the car.

262
00:23:41,840 --> 00:23:46,940
Let's see what is the child entity which is being which is being our project.

263
00:23:46,970 --> 00:23:51,880
So it could be a company caring so that it's expanded and we're able to see this part.

264
00:23:51,890 --> 00:23:57,360
So again there is an edit to let collapsed and see how many words are there.

265
00:23:57,680 --> 00:24:05,510
So there are two little sensible for the child responding to the first parent and therein we have these

266
00:24:07,960 --> 00:24:08,620
landing sites.

267
00:24:08,640 --> 00:24:13,010
There is no child.

268
00:24:13,250 --> 00:24:17,560
We have a record has this

269
00:24:21,310 --> 00:24:27,490
right here and we have the keys for the accompaniment.

270
00:24:27,640 --> 00:24:36,550
We can see the big is here for the base salary sequence number is 1 start date time is 0 1 1 2 0 then

271
00:24:36,760 --> 00:24:37,210
18

272
00:24:41,210 --> 00:24:41,670
okay.

273
00:24:41,770 --> 00:24:47,440
Two sets goes into the second record I am sorry I know this has corresponding to the second record.

274
00:24:47,740 --> 00:24:50,020
So let me start over there.

275
00:24:54,570 --> 00:24:56,380
Yeah under this second rate card.

276
00:24:59,120 --> 00:25:00,120
Right.

277
00:25:00,140 --> 00:25:09,340
And then similarly for the other record that we have in the child so we get to second the other record

278
00:25:09,340 --> 00:25:16,380
from the child that this particular part which is far this.

279
00:25:17,230 --> 00:25:20,370
So here it just for the Beacon print union.

280
00:25:24,640 --> 00:25:25,000
OK.

281
00:25:25,570 --> 00:25:32,720
So here in the union A.P. phone and be a cell and we get the sequence number as one I started time 2

282
00:25:32,760 --> 00:25:37,530
3 8 0 1 0 1 and we have these radios on duty double to 8.

283
00:25:37,540 --> 00:25:39,320
So these are the two track records.

284
00:25:39,400 --> 00:25:47,460
And similarly for one the spawning child records that see so far the fear in number one parent 81.

285
00:25:47,490 --> 00:25:50,900
We have the results have been our product.

286
00:25:50,930 --> 00:25:58,200
So these are the two results which have been out put it and here and we can see either the two records

287
00:25:58,260 --> 00:26:04,850
which have been reported that is the base salary US

288
00:26:07,780 --> 00:26:13,480
and here we can see the sequence number is three Ls and secret number the floater rotates therefore

289
00:26:13,470 --> 00:26:27,750
the L is so fixed up to that value and we seek out the beach I regard to let expanded child China can't

290
00:26:27,750 --> 00:26:31,050
be and here and we have to beat China the card

291
00:26:34,210 --> 00:26:36,990
they just wanted a competent union.

292
00:26:36,990 --> 00:26:37,780
Right.

293
00:26:37,930 --> 00:26:39,980
So they had two different competent.

294
00:26:40,090 --> 00:26:43,310
And there are these four wonder card which has been.

295
00:26:43,470 --> 00:26:49,350
But we're confident and in the first part we see that sequence number three.

296
00:26:49,360 --> 00:26:49,710
All right.

297
00:26:50,020 --> 00:26:52,660
So now what we will do is now we need to verify this.

298
00:26:52,660 --> 00:26:58,990
So what we want to do is we have been given the original query and we have no way to seek out what would

299
00:26:59,000 --> 00:27:01,180
be the output for the parent to make.

300
00:27:01,280 --> 00:27:03,000
We cannot security and thing.

301
00:27:03,300 --> 00:27:09,840
So now how are we going to derive what would be the output for the child.

302
00:27:09,940 --> 00:27:17,020
What would be the query that we execute so that we got we get these child objects out particular spawning

303
00:27:17,390 --> 00:27:18,670
or additional query.

304
00:27:18,790 --> 00:27:26,170
So now what we will do is we know since it is and if we become a victory object so possible we'll try.

305
00:27:26,170 --> 00:27:26,680
Do you.

306
00:27:26,740 --> 00:27:28,880
I hear so derived.

307
00:27:29,430 --> 00:27:39,160
So query for derivation a query for derivations without actually knowing it but the output will just

308
00:27:39,160 --> 00:27:40,180
follow these rules.

309
00:27:40,390 --> 00:27:47,680
So we'll provide in the let's say we wanted in the output in the format of Tucson and what we want to

310
00:27:47,680 --> 00:27:53,170
do here is first of all we have to apply the free turn.

311
00:27:54,110 --> 00:27:54,630
Right.

312
00:27:54,700 --> 00:28:01,430
We need to apply the filter wherein we need to say we component are.

313
00:28:01,480 --> 00:28:11,410
We can also apply only for user i t equals 1 0 3 double to 8.

314
00:28:12,260 --> 00:28:25,440
And now here in in the additional query that we executed the data we had placed the from date.

315
00:28:25,500 --> 00:28:25,860
Right.

316
00:28:25,860 --> 00:28:32,700
We have players from data from 1st of January 2017 that is to then 17 0 1 0 1.

317
00:28:32,700 --> 00:28:33,000
Right.

318
00:28:33,270 --> 00:28:36,510
So as for the rule.

319
00:28:36,510 --> 00:28:39,570
The thing is that to do that to effective dated entities.

320
00:28:39,570 --> 00:28:40,280
Right.

321
00:28:40,290 --> 00:28:47,130
And then we navigate from the base to the navigation and Jackie's daughter expand but take the effective

322
00:28:47,130 --> 00:28:53,930
starting date from the base but just in case effective started from the base effective start date is

323
00:28:53,930 --> 00:28:57,950
this because we are finding our particular spawning entry affiliate.

324
00:28:58,050 --> 00:29:01,800
So effective started with just 1 7 2 0 1 0 1.

325
00:29:01,800 --> 00:29:10,360
So that would be taken up as the as of date for the navigation of the for the navigation entity.

326
00:29:10,490 --> 00:29:17,630
So hidden will put as off date equals 17 0 1 0 1.

327
00:29:17,620 --> 00:29:21,780
And here we will try to execute this particular query.

328
00:29:21,790 --> 00:29:28,390
Now let's go back to your statement and let's try to execute it and we'll compare whether they are.

329
00:29:28,400 --> 00:29:35,800
Could that be kept as a result of this query conforms or is equal to the output that we got from the

330
00:29:36,640 --> 00:29:39,090
original query for the child object.

331
00:29:39,100 --> 00:29:46,510
So if we try to execute this particular query hearing what we see Okay we get it set it and we have

332
00:29:46,870 --> 00:29:49,750
the two outputs which have been returned.

333
00:29:50,320 --> 00:29:57,910
And if you seek out the unique record ideas so be first to follow at this particular record eighty from

334
00:29:57,910 --> 00:29:59,060
the desired section.

335
00:29:59,080 --> 00:30:02,860
So we will say a record eighty is this

336
00:30:06,140 --> 00:30:06,960
right.

337
00:30:07,280 --> 00:30:15,710
And Visa card I.D. is as trade together even as then so be card ideas this

338
00:30:19,000 --> 00:30:25,050
right so hearing we are getting relaxed compare.

339
00:30:25,100 --> 00:30:28,700
So we have the query for the revision and this the child.

340
00:30:28,700 --> 00:30:32,360
So earlier from the agent query we go to the court I.D. for the child.

341
00:30:32,660 --> 00:30:34,550
So it was this sell us.

342
00:30:34,550 --> 00:30:41,490
So this has been said to us it is 3 l l it is started to those 17 0 1 0 1.

343
00:30:41,510 --> 00:30:44,860
So it is date 2017 0 1 0 1.

344
00:30:44,890 --> 00:30:45,510
Yes.

345
00:30:45,590 --> 00:30:49,890
And is right is my duty to get a to April the same.

346
00:30:50,030 --> 00:30:55,900
So the one a child one it is same as a one off.

347
00:30:55,910 --> 00:30:57,180
This particular part.

348
00:30:57,300 --> 00:30:57,530
Right.

349
00:30:57,590 --> 00:31:05,690
And similarly there is a component of union to the same three l l the same and subject in 17 little

350
00:31:05,690 --> 00:31:09,260
longer the 16 same and to do the ability to double it.

351
00:31:09,260 --> 00:31:12,550
So both of these child records are also same.

352
00:31:12,650 --> 00:31:18,620
Now if in case there is a curiosity as to why the sequence number three and is showing up so let's go

353
00:31:18,620 --> 00:31:26,000
back into these success factors application to know if you navigate to that utilizing whether or treatable

354
00:31:26,280 --> 00:31:36,690
it that is my way of telling Jews and if you try to seek out the child to court which is can be taken

355
00:31:36,780 --> 00:31:43,670
recurring so far that we need to go into compensation tab here and we will do it.

356
00:31:43,770 --> 00:31:46,190
And there's a deeply complicating fight.

357
00:31:46,260 --> 00:31:49,470
So what we'll do is likely be going into deep history

358
00:31:56,450 --> 00:31:56,890
Alec.

359
00:31:57,430 --> 00:32:09,620
So here we can see that on January 2000 10 to 1 2017 that is on January's 1 0 January 0 1 2017.

360
00:32:09,640 --> 00:32:16,850
There have been three modifications to the MP compensation on the same day.

361
00:32:17,110 --> 00:32:20,230
The first modification was on January 1 2017.

362
00:32:20,230 --> 00:32:28,060
That is John Dalziel one of three second modification was also on January 1 2017 which is from the second

363
00:32:28,060 --> 00:32:35,240
of three within the group first changed the base salary was changed and the union view changed.

364
00:32:35,350 --> 00:32:41,740
And third modification also happened on the same day where the big change happened.

365
00:32:42,740 --> 00:32:48,580
Well the base salary change from the frequency of baby of monthly to by Vicki.

366
00:32:49,030 --> 00:32:53,250
So there you see that teaching is happened on the same day.

367
00:32:53,530 --> 00:33:00,720
And we know that he NPP complicating is the advanced effective dated entity that is it is startlingly

368
00:33:00,750 --> 00:33:04,090
effective dated but it is MCP reasonable.

369
00:33:04,180 --> 00:33:13,340
So it basically allows multiple changes all day and that are also being tracked so we can seek out to

370
00:33:13,340 --> 00:33:17,130
look at what other changes have happened on that particular date.

371
00:33:17,140 --> 00:33:23,020
So we see their teaching changes that has happened and these teeth response to the sequence number that

372
00:33:23,020 --> 00:33:24,030
we have.

373
00:33:24,030 --> 00:33:24,280
Right.

374
00:33:24,280 --> 00:33:29,500
So we have this sequence number which has been shown up as t l currently.

375
00:33:29,500 --> 00:33:31,870
So that the response to this particular fire.

376
00:33:32,380 --> 00:33:38,140
So now this is brings us to the other part of it that when we apply.

377
00:33:38,320 --> 00:33:40,950
So what happened is people good or bad restless.

378
00:33:41,470 --> 00:33:48,120
So then we apply the good to the old system derived query that indeed was this.

379
00:33:48,750 --> 00:33:58,830
So if you apply as paid now and if you apply as of date barometer on a particular entity which is effectively

380
00:33:58,860 --> 00:34:06,040
rated R advanced if activated entity then what it happens is it brings out obviously it applies the

381
00:34:06,060 --> 00:34:15,070
adopted freedom plus it brings out the latest the latest sequence number which is applicable on that

382
00:34:15,070 --> 00:34:15,850
particular day.

383
00:34:16,090 --> 00:34:23,320
So on the back sequence numbers are put in and that is where when we executed this query only the sequence

384
00:34:23,320 --> 00:34:30,880
number three l was out footed corresponding to both the p components and we do not see the sequence

385
00:34:30,880 --> 00:34:38,150
number of 1 and 2 being output did for each of these competence.

386
00:34:38,330 --> 00:34:38,750
All right.

387
00:34:39,330 --> 00:34:46,290
So that is the difference over here that brings that if this difference is broken by the as of date

388
00:34:46,770 --> 00:34:57,250
parameter for now if you would have executed instead of as of date if you would have a combination of

389
00:34:57,250 --> 00:35:03,010
the from the to date are either a combination of from the two that are either of those then who would

390
00:35:03,010 --> 00:35:08,380
have seen that OK it would have output in each and every sequence number as well.

391
00:35:08,660 --> 00:35:15,370
So if you try to execute this query the same query and instead of as update to providing these from

392
00:35:15,370 --> 00:35:15,880
date

393
00:35:18,530 --> 00:35:25,910
and also lets say we want to limited to see all the changes that has happened in 2017.

394
00:35:26,390 --> 00:35:30,440
So we will limited as to that particular year.

395
00:35:30,890 --> 00:35:32,500
So from Foster generally.

396
00:35:32,500 --> 00:35:36,550
So between 1st of January and 34 from December 2017.

397
00:35:36,660 --> 00:35:42,140
And if we tried to execute this particular query so we will be able to see on those changes that has

398
00:35:42,140 --> 00:35:47,570
happened on MPP complicating object in the year 2017.

399
00:35:47,570 --> 00:35:51,800
And we get the results today and let's see how many results we have.

400
00:35:52,060 --> 00:35:55,270
So we have got six results.

401
00:35:55,280 --> 00:35:57,410
So now if you see closely.

402
00:35:57,770 --> 00:36:03,170
So this is for a competent reason and the sequence number is 1.

403
00:36:04,040 --> 00:36:04,420
All right.

404
00:36:04,880 --> 00:36:11,940
So 1 record for that they sell so can record for percent then somebody else too.

405
00:36:12,200 --> 00:36:17,870
And then the third record also for sale and sequence number three.

406
00:36:17,870 --> 00:36:22,360
So all the three sequences number of sequence numbers for the base salary have been uprooted.

407
00:36:22,670 --> 00:36:30,130
And similarly the sequence numbers 1 L for union 1 and for union B Company.

408
00:36:30,130 --> 00:36:33,440
And similarly for unions and number two.

409
00:36:33,520 --> 00:36:38,780
And accordingly the you for union pay conference sequence number three.

410
00:36:38,830 --> 00:36:43,520
So here we can see there has been this six years which have been uprooted.

411
00:36:44,020 --> 00:36:47,440
Three of those corresponds to the peak competent self.

412
00:36:47,540 --> 00:36:52,360
So it has particular number two by two for basal and ticket number 120 for union.

413
00:36:52,420 --> 00:36:55,330
So that is where we saw in these way as well.

414
00:36:55,360 --> 00:37:05,740
So one two and Ted right there have been three changes so now three changes for each of the union and

415
00:37:05,910 --> 00:37:09,300
company to legislatures up to six things.

416
00:37:09,320 --> 00:37:09,550
Right.

417
00:37:10,820 --> 00:37:18,370
So now the thing that has happened is so we understood the adopted part.

418
00:37:18,380 --> 00:37:25,880
And we were able to determine the concept and conceptually we were able to understand again what every

419
00:37:25,960 --> 00:37:27,200
the child would show.

420
00:37:27,200 --> 00:37:32,110
And we were able to predict the behavior of dollar expense without actually.

421
00:37:32,140 --> 00:37:39,200
SIEGEL Well Mr. Quinn so similarly you would have done for this act in regard for the period taken out

422
00:37:39,200 --> 00:37:44,650
so colloquially for the revision would have been or what would have been over here this likely would

423
00:37:44,650 --> 00:37:52,030
have taken the effective start date and we would have placed the updated equal to 2018 0 1 0 1 and if

424
00:37:52,030 --> 00:37:57,390
you would have executed this query all over the child that would go into the placement tool and tried

425
00:37:57,390 --> 00:38:01,550
to execute this query except that you can replace the query.

426
00:38:01,580 --> 00:38:08,480
But he has provided the necessary authorization for the output and if you seek out here the citizens

427
00:38:08,490 --> 00:38:16,660
city which you love and we have got to put one has decreased the the unique record that we have from

428
00:38:16,660 --> 00:38:26,110
the entity complicating is a is is so varied we have to be confident basal and the sequence number of

429
00:38:26,110 --> 00:38:41,410
fun and fob b we have now for the B V have the art shown up on the sheet.

430
00:38:42,190 --> 00:38:46,360
So here and we have these for the union conference in December 1 and 1.

431
00:38:46,780 --> 00:38:53,710
And does it compare to the previous output when we ran the original query so does so it has gone to

432
00:38:53,710 --> 00:39:00,470
this number one each for each of the P competence and the date time has been 2018 to 1 2.

433
00:39:00,630 --> 00:39:02,770
So 2018 has been shown over here.

434
00:39:02,800 --> 00:39:04,440
So yes it does.

435
00:39:04,450 --> 00:39:08,350
So let's go back to the presentation we have.

436
00:39:08,350 --> 00:39:08,710
All right.

437
00:39:08,920 --> 00:39:16,960
So here in this saw there to give and be executed did this original query then it out put it to parent

438
00:39:16,960 --> 00:39:23,600
records 1 and 2 the two parent records the unique parent records of the and compensation effective dated

439
00:39:23,610 --> 00:39:24,250
entity.

440
00:39:24,460 --> 00:39:31,840
Now for one for the first parent here we've got these two child records and which workers according

441
00:39:31,840 --> 00:39:37,820
to the CPS number three the list sequence done for both of deeply the components because the mother

442
00:39:37,830 --> 00:39:45,790
took it as a data event that the effective dated entities that it brings out the unique record which

443
00:39:45,880 --> 00:39:48,620
is effective at that point in time.

444
00:39:48,640 --> 00:39:55,720
So at that point in time first of all they were given the card which would be output put it and here

445
00:39:55,810 --> 00:40:01,700
we have the latest sequence from birth records which was at that point in time the earlier CPS number

446
00:40:01,730 --> 00:40:04,350
records 1 and 2 were not active at that point today.

447
00:40:04,480 --> 00:40:11,230
Those police that I met those were the records which are basically being kept in the application track

448
00:40:11,280 --> 00:40:15,100
of changes has happened in due course on the same date.

449
00:40:15,640 --> 00:40:22,990
So daring variable to a defined and we were able to derive the exact value of the child object based

450
00:40:22,990 --> 00:40:25,220
on the rules right now.

451
00:40:25,330 --> 00:40:30,790
Similarly for second record 90 minutes regarding we were able to get out the two child objects which

452
00:40:30,790 --> 00:40:38,290
is for each of the big components we had to sequence one and they started 180 plus two generally right.

453
00:40:38,560 --> 00:40:44,650
So here in the rules to apply applied is if the birth both the base entity and navigation and the effective

454
00:40:44,650 --> 00:40:50,020
data and then when expanding the navigation entity the effective target of the base entity is you set

455
00:40:50,020 --> 00:40:56,050
the date of the navigation entity so that that rule number one that was applied and rule number and

456
00:40:56,050 --> 00:41:01,810
the rule that was applied but rule number five if one is specified from it I included as query options

457
00:41:02,140 --> 00:41:08,980
then only a top level entity is preferred by different grid included all lower entity levels are added

458
00:41:09,010 --> 00:41:11,870
to this follow rules 1 2 and entry as illustrated above.

459
00:41:12,400 --> 00:41:17,260
So when we did see that again does one two and three.

460
00:41:17,270 --> 00:41:26,480
So these are being followed by the non dog entity so here in the top level entity was ENP compensation

461
00:41:26,840 --> 00:41:31,090
and from the MP compensation we navigated the MPP on.

462
00:41:31,250 --> 00:41:36,060
And in this original query we did apply from that.

463
00:41:36,680 --> 00:41:43,210
So we did apply this from right here which was 2017 that could take up defenses here.

464
00:41:43,300 --> 00:41:43,760
Yes.

465
00:41:43,790 --> 00:41:47,120
Which was the 2017 0 1 0 1.

466
00:41:47,120 --> 00:41:51,310
So now that to say that okay from that included is applied.

467
00:41:51,320 --> 00:41:54,740
So just applied on the NDA top level component.

468
00:41:54,860 --> 00:42:00,510
The rest components which is ENP pay from recurring which is the change component here.

469
00:42:00,530 --> 00:42:04,880
That would follow who's 1 2 and 3.

470
00:42:04,880 --> 00:42:08,410
So here it is 120 in both of these entities are effective.

471
00:42:08,410 --> 00:42:14,390
So this particular rule would be followed here which said that okay the as of date would be the value

472
00:42:14,850 --> 00:42:19,770
as object would be applied on the child entity equal to the effective standard of the base entity.

473
00:42:20,390 --> 00:42:24,970
So that the second rule which was applied right.

474
00:42:24,980 --> 00:42:32,660
So this was set and then there was an effective dated and 2D rule that was applied that which is if

475
00:42:32,660 --> 00:42:40,250
navigation and 2D and TPV enable then as of data returns the record having highest sequence number of

476
00:42:40,260 --> 00:42:46,490
defective Richard accords for that given as a date so far as I've paid for faster data than it's ever

477
00:42:46,490 --> 00:42:47,710
been there were two records.

478
00:42:47,860 --> 00:42:50,700
So for the sequence number.

479
00:42:50,990 --> 00:42:58,110
And then when we executed the query only the latest one we trust super very close to three that we 40

480
00:42:58,580 --> 00:43:00,350
child records.

481
00:43:00,350 --> 00:43:00,730
All right.

482
00:43:01,040 --> 00:43:09,770
So here in this particular stage we understood the behaviour of the expand when the base and the navigation

483
00:43:09,770 --> 00:43:14,490
entities are not effective dated and effective data respectively.

484
00:43:14,930 --> 00:43:22,280
And if they are the effective dated and experiences advance effective date it respectively hope the

485
00:43:22,280 --> 00:43:27,410
concept was cleared to thanks for listening.

486
00:43:27,460 --> 00:43:29,050
Stay tuned and happy Monday.