WEBVTT
1
00:00:04.248 --> 00:00:06.120
Okay, my name is Andrew Zeff.
2
00:00:06.120 --> 00:00:07.380
I am with FRB.
3
00:00:07.380 --> 00:00:09.570
I'll be providing these office hours today
4
00:00:09.570 --> 00:00:12.030
on behalf of the Treasury Department.
5
00:00:12.030 --> 00:00:15.690
Today's meeting will be on G-Invoicing
6
00:00:15.690 --> 00:00:19.230
In Flight Orders and order uploads.
7
00:00:19.230 --> 00:00:23.040
We are having a large group of people joining today.
8
00:00:23.040 --> 00:00:26.850
Just so you know, we ask that you stay on mute
9
00:00:26.850 --> 00:00:28.620
unless you have a question.
10
00:00:28.620 --> 00:00:31.140
You can come off mute to ask questions.
11
00:00:31.140 --> 00:00:35.880
We have instructions in the chat of hitting star-six
12
00:00:35.880 --> 00:00:37.140
and perhaps hitting your mic
13
00:00:37.140 --> 00:00:39.270
at the top of the menu, perhaps.
14
00:00:39.270 --> 00:00:42.870
We will be providing some demonstration here today.
15
00:00:42.870 --> 00:00:45.400
So if you just dialed in, you may want to join
16
00:00:45.400 --> 00:00:48.153
to see the video as well as the audio.
17
00:00:51.540 --> 00:00:53.670
I will be muting everybody
18
00:00:53.670 --> 00:00:55.770
and I just want to mention one more time,
19
00:00:55.770 --> 00:00:59.470
this meeting will be recorded for future edification
20
00:01:00.420 --> 00:01:01.253
and welcome.
21
00:01:03.030 --> 00:01:04.740
Just checking the time here.
22
00:01:04.740 --> 00:01:06.510
We have a good number of people already joined,
23
00:01:06.510 --> 00:01:07.860
so I'm gonna go ahead and get started.
24
00:01:07.860 --> 00:01:10.410
We do have a large number of folks
25
00:01:10.410 --> 00:01:12.510
on the call and continue to join.
26
00:01:12.510 --> 00:01:14.403
So again, we welcome you.
27
00:01:15.540 --> 00:01:18.630
First note we want to take is that if you have questions
28
00:01:18.630 --> 00:01:22.800
about policy-related concerns
29
00:01:22.800 --> 00:01:25.650
other than the functionality of what we're about to present,
30
00:01:25.650 --> 00:01:29.970
please put them into chat or you can forward your questions
31
00:01:29.970 --> 00:01:33.060
via email to the treasury department.
32
00:01:33.060 --> 00:01:37.713
Again, I have that email address at the top of the chat.
33
00:01:38.550 --> 00:01:40.770
That would be just scrolling up there
34
00:01:40.770 --> 00:01:43.497
so you can make sure you know it's there.
35
00:01:43.497 --> 00:01:48.330
Treasuryigt@fiscal.treasury.gov.
36
00:01:48.330 --> 00:01:50.010
You can also email myself.
37
00:01:50.010 --> 00:01:52.170
My email address is there as well.
38
00:01:52.170 --> 00:01:55.710
Andrew.zeff@stls.frb.org.
39
00:01:55.710 --> 00:01:59.940
I have a number of people on the call from my team,
40
00:01:59.940 --> 00:02:02.250
the AIT team.
41
00:02:02.250 --> 00:02:05.370
Also, we have folks from the development team
42
00:02:05.370 --> 00:02:08.130
in production support in case you have any questions
43
00:02:08.130 --> 00:02:10.110
that maybe I can't answer them,
44
00:02:10.110 --> 00:02:12.060
we'll make sure to get you the answers.
45
00:02:12.900 --> 00:02:13.890
All right?
46
00:02:13.890 --> 00:02:17.737
That said, I'm going to go ahead and jump into this.
47
00:02:17.737 --> 00:02:19.920
First, we're gonna go through here
48
00:02:19.920 --> 00:02:24.510
the requirements for In Flight Orders and order uploads.
49
00:02:24.510 --> 00:02:28.500
We'll touch on feature management system requirements,
50
00:02:28.500 --> 00:02:30.600
user requirements, that kind of thing,
51
00:02:30.600 --> 00:02:32.490
to make sure folks know what the roles are
52
00:02:32.490 --> 00:02:36.099
for being able to perform what we're gonna show today,
53
00:02:36.099 --> 00:02:41.070
and then we'll go through and talk about In Flight orders
54
00:02:41.070 --> 00:02:43.890
as a standard user interface within G-Invoicing
55
00:02:43.890 --> 00:02:46.470
and creating an order and performance.
56
00:02:46.470 --> 00:02:48.960
And then we'll go step by step through
57
00:02:48.960 --> 00:02:53.040
creating and updating the template that's required
58
00:02:53.040 --> 00:02:55.503
for performing bulk uploads.
59
00:02:57.630 --> 00:02:59.760
And I'm just gonna do a quick audio check here.
60
00:02:59.760 --> 00:03:01.350
Maybe someone from my team can validate
61
00:03:01.350 --> 00:03:04.133
that we're doing good here and you can hear me just fine.
62
00:03:07.200 --> 00:03:09.960
You're loud and clear, Andrew.
63
00:03:09.960 --> 00:03:12.209
Ah, appreciate that. All right.
64
00:03:12.209 --> 00:03:16.140
So let's start with what we're the subject matter is today
65
00:03:16.140 --> 00:03:19.290
Order Upload/IFO Bulk Uploads.
66
00:03:19.290 --> 00:03:22.260
It is a progression of G-Invoicing
67
00:03:22.260 --> 00:03:24.300
to meet the In flight Order mandate
68
00:03:24.300 --> 00:03:26.250
that begins October 1st, 2023
69
00:03:26.250 --> 00:03:27.800
set by the Treasury Department.
70
00:03:28.980 --> 00:03:33.330
The bulk-order capability does allow for order upload
71
00:03:33.330 --> 00:03:36.120
via IFO bulk upload,
72
00:03:36.120 --> 00:03:39.240
or we could use this for In Flight orders,
73
00:03:39.240 --> 00:03:40.803
which was the original intent.
74
00:03:44.250 --> 00:03:45.810
Just noting at the bottom there,
75
00:03:45.810 --> 00:03:47.790
order-upload template that is used
76
00:03:47.790 --> 00:03:48.630
and we'll be showing this
77
00:03:48.630 --> 00:03:51.135
towards the end of the conversation,
78
00:03:51.135 --> 00:03:54.750
actually meets the same validation requirements
79
00:03:54.750 --> 00:03:58.770
as if you were populating a order and performance
80
00:03:58.770 --> 00:04:01.113
within G-Invoicing using the UI.
81
00:04:01.950 --> 00:04:05.580
And I'll bring that back up again to you coming up.
82
00:04:06.900 --> 00:04:10.650
These are the roles required for performing order uploads
83
00:04:10.650 --> 00:04:13.080
and IFO bulk uploads,
84
00:04:13.080 --> 00:04:15.540
mainly for bulk uploads by the way,
85
00:04:15.540 --> 00:04:18.420
for example, the performance supervising manager role
86
00:04:18.420 --> 00:04:21.870
is required for PPQs and we'll talk about what that is.
87
00:04:21.870 --> 00:04:25.443
Prepaid quantities as a performance transaction type.
88
00:04:26.490 --> 00:04:29.640
The supervisor approval role is required.
89
00:04:29.640 --> 00:04:32.880
You're actually able via the bulk uploads
90
00:04:32.880 --> 00:04:37.880
to create an approved order of both partners
91
00:04:39.180 --> 00:04:42.180
providing their approvals in the files that are uploaded.
92
00:04:42.180 --> 00:04:44.553
And the result is an open order.
93
00:04:47.730 --> 00:04:52.110
Just taking note that the roles are required separately
94
00:04:52.110 --> 00:04:54.243
for requesting and for servicing.
95
00:04:57.660 --> 00:04:59.580
Additional requirements.
96
00:04:59.580 --> 00:05:01.650
Feature management must be enabled
97
00:05:01.650 --> 00:05:03.663
requesting and/or servicing.
98
00:05:05.160 --> 00:05:07.230
Also, and I'll point this out
99
00:05:07.230 --> 00:05:09.660
when we're going into the demonstration,
100
00:05:09.660 --> 00:05:12.300
when you're creating a GT&C,
101
00:05:12.300 --> 00:05:16.350
the agencies both agree and approve the GT&C
102
00:05:16.350 --> 00:05:18.030
and part of that is to identify
103
00:05:18.030 --> 00:05:21.120
who the order-originating partner is.
104
00:05:21.120 --> 00:05:22.950
And that is to partner, in this case,
105
00:05:22.950 --> 00:05:27.603
that must begin the bulk upload process.
106
00:05:31.260 --> 00:05:32.880
This slide is just to point out
107
00:05:32.880 --> 00:05:35.910
that the notifications being used
108
00:05:35.910 --> 00:05:40.140
for order uploads, bulk uploads are the same
109
00:05:40.140 --> 00:05:44.610
as for what you're seeing now with orders.
110
00:05:44.610 --> 00:05:45.930
And we're just summarizing
111
00:05:45.930 --> 00:05:49.023
each of the notification capabilities there for you.
112
00:05:52.354 --> 00:05:54.840
Okay, so feature management.
113
00:05:54.840 --> 00:05:57.960
Feature management is coming along.
114
00:05:57.960 --> 00:06:00.020
It will become available with 5.0.
115
00:06:00.930 --> 00:06:03.030
You need a master administrator
116
00:06:03.030 --> 00:06:05.490
to enable or disable any of the features.
117
00:06:05.490 --> 00:06:09.030
There are a few features that are essentially managed
118
00:06:09.030 --> 00:06:11.013
by production support,
119
00:06:11.970 --> 00:06:14.853
but for bulk upload capability needs,
120
00:06:16.260 --> 00:06:20.970
a master administrator would need to enable an order
121
00:06:20.970 --> 00:06:24.400
to allow for this capability to appear in the menuing.
122
00:06:25.780 --> 00:06:30.780
We're just showing an example here of the requesting.
123
00:06:30.840 --> 00:06:32.850
I'd have to make sure to save the feature
124
00:06:32.850 --> 00:06:34.980
after you click yes to it.
125
00:06:34.980 --> 00:06:37.330
And again, I'll download this in just a minute.
126
00:06:40.380 --> 00:06:43.350
So if you wanted to see what the process was for doing this
127
00:06:43.350 --> 00:06:45.450
before I do the demonstration,
128
00:06:45.450 --> 00:06:47.640
you would select the Administration tab,
129
00:06:47.640 --> 00:06:51.750
go down to Manage Features Flag, and you have to do this
130
00:06:51.750 --> 00:06:54.960
for both requesting and servicing separately.
131
00:06:54.960 --> 00:06:57.840
Here we're showing the bulk order uploads,
132
00:06:57.840 --> 00:07:00.210
which is what our topic is, right?
133
00:07:00.210 --> 00:07:05.210
IFO bulk uploads, and then we select yes to it.
134
00:07:09.270 --> 00:07:10.170
Hi Angela, yep.
135
00:07:10.170 --> 00:07:11.347
I see your question there.
136
00:07:11.347 --> 00:07:12.267
"Is master administrator the only one
137
00:07:12.267 --> 00:07:14.220
who can perform this operation
138
00:07:14.220 --> 00:07:16.050
of enabling/disabling feature management.
139
00:07:16.050 --> 00:07:16.950
The answer is yes.
140
00:07:20.370 --> 00:07:21.240
Okay.
141
00:07:21.240 --> 00:07:22.620
Hi there, Andrew.
142
00:07:22.620 --> 00:07:27.620
So not enabling and disabling, but actually doing the loads.
143
00:07:28.740 --> 00:07:29.850
Well, right,
144
00:07:29.850 --> 00:07:32.827
so I'll just go back for you a little bit, Angela.
145
00:07:32.827 --> 00:07:34.950
These are roles that are required
146
00:07:34.950 --> 00:07:36.600
for being able to do bulk upload.
147
00:07:38.340 --> 00:07:43.340
Okay, so the person performing the load can...
148
00:07:44.790 --> 00:07:46.280
So I understand...
149
00:07:47.160 --> 00:07:50.700
So if I have the order supervising manager role,
150
00:07:50.700 --> 00:07:54.300
I can actually load the role
151
00:07:54.300 --> 00:07:57.332
or load the file into the system
152
00:07:57.332 --> 00:08:02.100
after the master administrator turns on the feature?
153
00:08:02.100 --> 00:08:03.170
Or...
154
00:08:05.700 --> 00:08:07.131
That's where I'm confused.
155
00:08:07.131 --> 00:08:09.030
Okay, so let me summarize it
156
00:08:09.030 --> 00:08:09.930
a little better for you.
157
00:08:09.930 --> 00:08:10.830
It's a great question.
158
00:08:10.830 --> 00:08:15.382
So the master administrator first has to enable the feature
159
00:08:15.382 --> 00:08:17.670
and there's like five, you know...
160
00:08:17.670 --> 00:08:20.250
76% are easy, another example of that
161
00:08:20.250 --> 00:08:23.550
that the feature management will allow you to enable.
162
00:08:23.550 --> 00:08:28.410
In order for somebody to be able to bulk-upload a file,
163
00:08:28.410 --> 00:08:29.670
then they would have to have
164
00:08:29.670 --> 00:08:32.133
the order supervisor manager role.
165
00:08:33.900 --> 00:08:38.280
If in that file is approver information
166
00:08:38.280 --> 00:08:41.370
and you're expecting the approvals to be provided
167
00:08:41.370 --> 00:08:45.990
within the upload, then the order-supervisor-approver role
168
00:08:45.990 --> 00:08:47.190
would be needed.
169
00:08:47.190 --> 00:08:51.090
If you then also want to provide information
170
00:08:51.090 --> 00:08:53.760
on advanced PPQs within the same file,
171
00:08:53.760 --> 00:08:56.970
then the performance supervisor manager role
172
00:08:56.970 --> 00:08:58.050
would be required.
173
00:08:58.050 --> 00:08:59.730
All of these for the same person, right,
174
00:08:59.730 --> 00:09:03.130
that is uploading the file into the system
175
00:09:04.080 --> 00:09:06.330
either on the requesting or servicing side.
176
00:09:06.330 --> 00:09:07.800
Oh, Andrew, thank you so much
177
00:09:07.800 --> 00:09:09.602
for clarifying that difference.
178
00:09:09.602 --> 00:09:11.610
(chuckles) Happiness.
179
00:09:11.610 --> 00:09:13.200
Now I'm sure if you're asking it,
180
00:09:13.200 --> 00:09:14.490
there must be tons of people asking
181
00:09:14.490 --> 00:09:17.730
and wondering the same thing, Angela, so always good.
182
00:09:17.730 --> 00:09:19.290
All right?
183
00:09:19.290 --> 00:09:20.123
So yeah.
184
00:09:20.123 --> 00:09:23.250
So this is where we were, you know,
185
00:09:23.250 --> 00:09:25.660
these are the steps to enable feature management
186
00:09:27.330 --> 00:09:28.890
and let's see what's next.
187
00:09:28.890 --> 00:09:29.723
Oh, okay.
188
00:09:29.723 --> 00:09:33.540
So for feature management, we now have a reporting mechanism
189
00:09:33.540 --> 00:09:38.310
that all users will be able to download and see.
190
00:09:38.310 --> 00:09:42.011
It pivots on either the agency or on the feature
191
00:09:42.011 --> 00:09:44.370
so that you can see if your trading partners
192
00:09:44.370 --> 00:09:46.383
have that capability enabled.
193
00:09:47.430 --> 00:09:48.980
And I'll show you that as well.
194
00:09:50.670 --> 00:09:52.803
Looks like I'm gonna show it to you now.
195
00:09:53.768 --> 00:09:55.080
So I'm gonna go ahead and log in.
196
00:09:55.080 --> 00:09:56.920
You know, by the way, 5.0,
197
00:09:56.920 --> 00:09:58.440
while I'm waiting for this to load,
198
00:09:58.440 --> 00:09:59.730
I'll mention this to you,
199
00:09:59.730 --> 00:10:04.680
5.0 is coming out for production in February 16th,
200
00:10:04.680 --> 00:10:07.773
and then for QAC February 24th.
201
00:10:08.850 --> 00:10:10.397
I am actually in what we call a QAF
202
00:10:10.397 --> 00:10:15.003
or the future state if you will, of G-Invoicing.
203
00:10:17.400 --> 00:10:18.330
And let's see.
204
00:10:18.330 --> 00:10:20.340
So I'm gonna go with Administration,
205
00:10:20.340 --> 00:10:23.130
here's the Feature Flag Management,
206
00:10:23.130 --> 00:10:24.453
I'll go to Requesting.
207
00:10:27.960 --> 00:10:29.610
Notice I have 'em all enabled.
208
00:10:29.610 --> 00:10:34.023
If I wanted to disable, I would say No here and then Save.
209
00:10:36.270 --> 00:10:38.670
And that's not needed for my demonstration.
210
00:10:38.670 --> 00:10:43.020
I could actually close down the batch-order uploads.
211
00:10:43.020 --> 00:10:45.150
Very happy that it's already enabled.
212
00:10:45.150 --> 00:10:48.450
And note that the centrally-managed options
213
00:10:48.450 --> 00:10:51.300
are managed remotely by production support,
214
00:10:51.300 --> 00:10:52.450
like I mentioned there.
215
00:10:55.950 --> 00:10:57.847
I'm just looking at the questions here.
216
00:10:57.847 --> 00:11:02.553
"Why can't a preparer upload and view and submit,
217
00:11:04.890 --> 00:11:06.090
Deborah, maybe you wanna come off mute
218
00:11:06.090 --> 00:11:08.243
so I can make sure I can understand the question there.
219
00:11:09.464 --> 00:11:11.100
Sure.
Sure, go ahead.
220
00:11:11.100 --> 00:11:13.200
Yeah, I was just wondering, so I'm a preparer,
221
00:11:13.200 --> 00:11:16.740
why couldn't I upload the template
222
00:11:16.740 --> 00:11:18.630
and then have the supervising approver
223
00:11:18.630 --> 00:11:21.630
go in and view and submit, so that way it is approved
224
00:11:21.630 --> 00:11:25.683
instead of having the supervisor approver upload?
225
00:11:27.480 --> 00:11:31.530
So the thing about how the bulk uploads works,
226
00:11:31.530 --> 00:11:33.630
it's kind of an all or nothing,
227
00:11:33.630 --> 00:11:36.540
it's not a step by step like you would see in the UI,
228
00:11:36.540 --> 00:11:37.977
otherwise I would definitely agree with you.
229
00:11:37.977 --> 00:11:39.630
You could separate out the roles,
230
00:11:39.630 --> 00:11:43.500
but with bulk order upload, again, it's all or nothing,
231
00:11:43.500 --> 00:11:47.250
it's all one line per entry, if you will.
232
00:11:47.250 --> 00:11:51.030
And that one line includes everything from the ALC
233
00:11:51.030 --> 00:11:56.030
to the TAS information to also the approver information.
234
00:11:57.330 --> 00:12:02.100
So if you didn't supply it all, it would error out on you.
235
00:12:02.100 --> 00:12:03.000
That's my understanding.
236
00:12:03.000 --> 00:12:05.150
And from my testing, that's what I've seen.
237
00:12:06.300 --> 00:12:07.860
Okay, thanks.
238
00:12:07.860 --> 00:12:08.693
Sure.
239
00:12:09.540 --> 00:12:11.040
So I set this to No.
240
00:12:11.040 --> 00:12:12.360
I'm gonna go ahead and put it back to Yes,
241
00:12:12.360 --> 00:12:14.560
just so you can see me do that one more time
242
00:12:15.690 --> 00:12:18.030
and notice this is gonna affect lots more
243
00:12:18.030 --> 00:12:21.377
than just the capability for order upload.
244
00:12:23.402 --> 00:12:24.235
Okay.
245
00:12:25.288 --> 00:12:26.121
All right.
246
00:12:27.450 --> 00:12:30.870
So once feature management's enabled,
247
00:12:30.870 --> 00:12:35.010
then we could start talking about, in the user interface,
248
00:12:35.010 --> 00:12:39.060
there's order upload for In Flight Orders.
249
00:12:39.060 --> 00:12:41.610
I'm sorry, In Flight Orders is available
250
00:12:41.610 --> 00:12:45.180
as well as the advanced PPQ.
251
00:12:45.180 --> 00:12:47.823
So here we see we create a new order,
252
00:12:49.470 --> 00:12:53.280
we now have this indicator with a dropdown selection
253
00:12:53.280 --> 00:12:55.410
of Yes or No for In Flight Orders.
254
00:12:55.410 --> 00:12:59.220
What this does is enable the next screen,
255
00:12:59.220 --> 00:13:03.750
which is Advanced PPQ or Prepaid Performance Quantity.
256
00:13:03.750 --> 00:13:06.370
This is a new performance transaction
257
00:13:07.410 --> 00:13:11.700
and with the In Flight Order indicator set to Yes,
258
00:13:11.700 --> 00:13:13.440
you can now, as servicing,
259
00:13:13.440 --> 00:13:16.950
create an advanced performance transaction,
260
00:13:16.950 --> 00:13:21.150
select this Do Not Settle, and this allows for agencies
261
00:13:21.150 --> 00:13:26.150
to begin to denote what fiscal responsibility
262
00:13:27.000 --> 00:13:28.620
has already been met
263
00:13:28.620 --> 00:13:31.830
with an order that was outside of G-Invoicing
264
00:13:31.830 --> 00:13:34.200
prior to (indistinct).
265
00:13:34.200 --> 00:13:35.793
That is its sole purpose.
266
00:13:37.110 --> 00:13:39.140
And you check this box...
267
00:13:40.590 --> 00:13:44.343
Action will not result in any transfer of funds.
268
00:13:46.680 --> 00:13:47.970
So I'll just pause there
269
00:13:47.970 --> 00:13:50.280
in case there's any questions about that.
270
00:13:50.280 --> 00:13:51.630
All right?
271
00:13:51.630 --> 00:13:53.798
And then very quickly-
I have a question.
272
00:13:53.798 --> 00:13:56.070
I'm sorry.
Sure, go ahead.
273
00:13:56.070 --> 00:13:58.680
So that advanced indicator,
274
00:13:58.680 --> 00:14:03.000
is that just for agreements that are set up for advances
275
00:14:03.000 --> 00:14:06.660
or is that basically the indicator
276
00:14:06.660 --> 00:14:08.010
that we would have to use
277
00:14:08.010 --> 00:14:12.540
so G-Invoicing does not settle that amount.
278
00:14:12.540 --> 00:14:13.920
So I can definitely say
279
00:14:13.920 --> 00:14:16.350
the second part is absolutely true.
280
00:14:16.350 --> 00:14:20.370
If you had, again, a fiscal amount
281
00:14:20.370 --> 00:14:22.800
that was already settled with IPAC,
282
00:14:22.800 --> 00:14:25.110
outside of G-Invoicing with the order previously
283
00:14:25.110 --> 00:14:28.010
before you created a new order inside G-Invoicing.
284
00:14:28.010 --> 00:14:29.073
So prior to.
285
00:14:31.560 --> 00:14:33.420
We have a an agreement already.
286
00:14:33.420 --> 00:14:36.390
Like for example, let me just bring up an order.
287
00:14:36.390 --> 00:14:38.310
Op. That didn't work,
288
00:14:38.310 --> 00:14:40.193
I have to type this out right.
289
00:14:44.550 --> 00:14:49.533
So this order was based on this GT&C that was created.
290
00:14:50.370 --> 00:14:55.370
The two agencies understood when they created this GT&C,
291
00:14:55.620 --> 00:14:58.050
and you know folks, there's gotta be a lot of communication
292
00:14:58.050 --> 00:15:01.710
between agencies, but when this GT&C was created,
293
00:15:01.710 --> 00:15:04.350
the agencies knew that they were going to be
294
00:15:04.350 --> 00:15:07.200
trying to get coverage for an order
295
00:15:07.200 --> 00:15:08.940
that was already in process.
296
00:15:08.940 --> 00:15:11.220
You've already had some performance transactions
297
00:15:11.220 --> 00:15:12.990
into IPAC already.
298
00:15:12.990 --> 00:15:16.890
And so this order, for example,
299
00:15:16.890 --> 00:15:19.920
I've already pre-created this so I can show you this.
300
00:15:19.920 --> 00:15:22.080
The order, we set the In Flight,
301
00:15:22.080 --> 00:15:23.400
and I can do this for you in a moment,
302
00:15:23.400 --> 00:15:26.310
but we made the indicator set to yes
303
00:15:26.310 --> 00:15:29.340
and then here's Schedule 1 for example.
304
00:15:29.340 --> 00:15:31.440
It does have to be an advanced order
305
00:15:31.440 --> 00:15:36.440
just to allow for in flight and in advance
306
00:15:36.900 --> 00:15:40.145
to allow for the performance transaction to be created.
307
00:15:40.145 --> 00:15:44.193
And so if I show performance here, I am acting as servicing.
308
00:15:45.480 --> 00:15:48.120
I can go to Schedule 1 here where we did this.
309
00:15:48.120 --> 00:15:50.703
It was an advanced performance transaction.
310
00:15:52.260 --> 00:15:54.360
I can go to the performance transaction here
311
00:15:54.360 --> 00:15:56.490
to take a look at this.
312
00:15:56.490 --> 00:15:59.130
And notice it says Previously Settled.
313
00:15:59.130 --> 00:16:01.290
So they had checked the box
314
00:16:01.290 --> 00:16:04.110
when they created that performance transaction
315
00:16:04.110 --> 00:16:06.257
and because it's previously settled,
316
00:16:06.257 --> 00:16:10.650
the amount is shown as pre-allocated,
317
00:16:10.650 --> 00:16:14.703
withdrawn from the agreement amount, total amount,
318
00:16:15.998 --> 00:16:19.747
and it will not be affected by IPAC.
319
00:16:19.747 --> 00:16:22.320
And reaching here, I'm trying to make sure
320
00:16:22.320 --> 00:16:24.540
I'm answering your question, so if I didn't,
321
00:16:24.540 --> 00:16:27.450
maybe you could help me out there a little bit.
322
00:16:27.450 --> 00:16:28.870
Sure, no, I appreciate it.
323
00:16:28.870 --> 00:16:30.930
So essentially then, like for this one,
324
00:16:30.930 --> 00:16:32.130
I just wanna kind of put it into
325
00:16:32.130 --> 00:16:33.510
kind of a real-life scenario.
326
00:16:33.510 --> 00:16:35.430
So let's say it's an In Flight Order
327
00:16:35.430 --> 00:16:37.020
and based on what you have here,
328
00:16:37.020 --> 00:16:41.370
we've currently already settled $40,000 against this order.
329
00:16:41.370 --> 00:16:45.240
So we would need to establish Schedule 1
330
00:16:45.240 --> 00:16:48.000
as the total amount that we've already settled
331
00:16:48.000 --> 00:16:50.670
in order to be able to set this as an advance?
332
00:16:50.670 --> 00:16:52.590
Correct, so like here. Here's Schedule 2,
333
00:16:52.590 --> 00:16:54.000
I haven't done it against Schedule 2,
334
00:16:54.000 --> 00:16:55.760
just so I can show you, okay?
Okay.
335
00:16:55.760 --> 00:16:57.810
Everything you said, I would agree with,
336
00:16:57.810 --> 00:16:59.070
by the way.
337
00:16:59.070 --> 00:17:01.020
I'm gonna select advance, right?
338
00:17:01.020 --> 00:17:03.813
It's against an In Flight Order, okay?
339
00:17:04.800 --> 00:17:08.100
Of course we have to stay within the right dates,
340
00:17:08.100 --> 00:17:11.400
performance dates and of course the counting period.
341
00:17:11.400 --> 00:17:12.780
Now see this one is set to zero.
342
00:17:12.780 --> 00:17:14.700
That's the one that we just looked at
343
00:17:14.700 --> 00:17:17.010
that we already did the advanced performance
344
00:17:17.010 --> 00:17:18.930
PPQ transaction against.
345
00:17:18.930 --> 00:17:23.930
This one we have not, so I'm gonna say 1,000,
346
00:17:25.020 --> 00:17:26.223
select create.
347
00:17:27.420 --> 00:17:29.596
Did not...
348
00:17:29.596 --> 00:17:32.190
I don't think I did that right.
349
00:17:32.190 --> 00:17:34.920
This went into just being a regular. Let's see what it did.
350
00:17:34.920 --> 00:17:38.010
Yeah, so this one actually is going through,
351
00:17:38.010 --> 00:17:40.890
so it looks like I didn't do that one correctly, honestly.
352
00:17:40.890 --> 00:17:41.883
I'm being straight with you.
353
00:17:41.883 --> 00:17:46.290
This one is going straight in and it will.
354
00:17:46.290 --> 00:17:48.780
Because I did not check that box,
355
00:17:48.780 --> 00:17:52.143
it will do an IPAC settlement.
356
00:17:53.550 --> 00:17:54.759
Okay.
357
00:17:54.759 --> 00:17:56.370
I was hoping that I could have shown you that.
358
00:17:56.370 --> 00:17:57.770
Where did I go wrong?
359
00:17:57.770 --> 00:17:59.460
So I have to test that out
360
00:17:59.460 --> 00:18:00.870
and find out why I didn't do it right
361
00:18:00.870 --> 00:18:04.109
but we could go back-
Okay.
362
00:18:04.109 --> 00:18:05.776
Go ahead.
363
00:18:07.227 --> 00:18:08.877
Was somebody gonna say something?
364
00:18:10.500 --> 00:18:12.060
Yeah, I think you missed the box
365
00:18:12.060 --> 00:18:13.110
at the top right.
366
00:18:13.110 --> 00:18:16.200
There was an empty box that you didn't do the drop down on.
367
00:18:16.200 --> 00:18:18.063
There you go, yeah.
Top right.
368
00:18:18.063 --> 00:18:19.126
Yep. I knew it.
369
00:18:19.126 --> 00:18:23.370
Me and all my fog here, Glory, I missed that.
370
00:18:23.370 --> 00:18:25.740
So what I could do, I think I have the time.
371
00:18:25.740 --> 00:18:29.420
Yeah, I can go ahead and very quickly...
372
00:18:32.300 --> 00:18:34.683
...copy this order and get it processed again.
373
00:18:36.030 --> 00:18:37.350
If y'all don't mind, I'm gonna go ahead.
374
00:18:37.350 --> 00:18:41.400
Notice this is either yes or no.
375
00:18:41.400 --> 00:18:42.233
Say yes.
376
00:18:42.233 --> 00:18:43.830
All the dating, everything you would normally do
377
00:18:43.830 --> 00:18:45.300
is the same.
378
00:18:45.300 --> 00:18:47.583
Of course it is based on this agreement.
379
00:18:49.350 --> 00:18:51.120
You're gonna have to watch me for just a second,
380
00:18:51.120 --> 00:18:52.413
do an approval here.
381
00:18:59.400 --> 00:19:03.573
So we have to wait for requesting to approve now.
382
00:19:11.100 --> 00:19:12.540
Yes.
383
00:19:12.540 --> 00:19:14.190
Okay, so I'm gonna approve for...
384
00:19:16.110 --> 00:19:17.673
Go. Requesting.
385
00:19:18.660 --> 00:19:21.840
And then I'm gonna have to go back into servicing.
386
00:19:21.840 --> 00:19:25.170
So I'm gonna approve, and then we have an open order here
387
00:19:25.170 --> 00:19:27.900
as soon as it's done, right? There we go, it's open.
388
00:19:27.900 --> 00:19:29.220
I'm gonna go back to servicing
389
00:19:29.220 --> 00:19:30.470
to do the performance transaction for you
390
00:19:30.470 --> 00:19:32.720
to make sure you see it done properly, folks.
391
00:19:35.460 --> 00:19:37.050
Okay, so I'm in servicing, right?
392
00:19:37.050 --> 00:19:39.153
Servicing always starts the performance.
393
00:19:42.660 --> 00:19:45.610
Did I like not grab the right one?
394
00:19:45.610 --> 00:19:48.933
Let's see. Oh, sorry.
395
00:19:52.560 --> 00:19:53.393
There we go.
396
00:19:54.750 --> 00:19:57.060
Okay, show performance.
397
00:19:57.060 --> 00:19:59.400
So yeah. So let's see.
398
00:19:59.400 --> 00:20:02.160
It is an In Flight Order.
399
00:20:02.160 --> 00:20:05.430
Here's Schedule 1 and now y'all catch me up here.
400
00:20:05.430 --> 00:20:08.340
I do advance, select the date,
401
00:20:08.340 --> 00:20:11.910
there's the do not settle that I did not select last time,
402
00:20:11.910 --> 00:20:14.040
which is my fault, okay?
403
00:20:14.040 --> 00:20:17.276
I'm gonna do 'em both since y'all have been patient with me.
404
00:20:17.276 --> 00:20:18.600
I'm gonna let you see 'em both done at once.
405
00:20:18.600 --> 00:20:20.130
So I'm gonna do 'em both here.
406
00:20:20.130 --> 00:20:25.130
Neither of these will create an IPAC order transaction
407
00:20:25.140 --> 00:20:26.140
and so there you go.
408
00:20:28.620 --> 00:20:30.840
And you can do adjustments against those.
409
00:20:30.840 --> 00:20:33.510
We sometimes get that kind of question.
410
00:20:33.510 --> 00:20:36.330
And we can go into each of these performance
411
00:20:36.330 --> 00:20:38.940
and see what's previously settled.
412
00:20:38.940 --> 00:20:40.263
That's our indicator.
413
00:20:42.047 --> 00:20:45.510
Did that help you?
It does.
414
00:20:45.510 --> 00:20:47.760
It definitely helps. Thank you very much.
415
00:20:47.760 --> 00:20:49.620
My last question, and then I'll be quiet, I promise.
416
00:20:49.620 --> 00:20:52.083
No I don't mind.
(chuckles) The GT&C,
417
00:20:52.083 --> 00:20:55.751
does that have to be set to allow advances
418
00:20:55.751 --> 00:20:59.490
in order for the In Flight Orders
419
00:20:59.490 --> 00:21:02.040
to have that advanced feature on the schedule?
420
00:21:02.040 --> 00:21:03.990
You're absolutely correct.
421
00:21:03.990 --> 00:21:07.050
If you go and take a look at the, you know...
422
00:21:07.050 --> 00:21:08.887
Partner information, I believe it's under,
423
00:21:08.887 --> 00:21:12.000
we have to say yes to advance.
424
00:21:12.000 --> 00:21:13.850
Let's see if I can find a way. Sorry.
425
00:21:14.730 --> 00:21:17.103
This is the advance information, delivery.
426
00:21:21.480 --> 00:21:23.142
If you mean detect a GT&C-
Yeah.
427
00:21:23.142 --> 00:21:26.590
Yeah, y'all are right.
(Attendee chuckling)
428
00:21:26.590 --> 00:21:27.780
Thank you. I can just do that there.
429
00:21:27.780 --> 00:21:30.480
And I'm sorry, I must have drank too much coffee here.
430
00:21:30.480 --> 00:21:33.180
The advanced indicator must be set to yes
431
00:21:33.180 --> 00:21:34.140
or you're not gonna be able
432
00:21:34.140 --> 00:21:36.660
to create an order with advanced period, right?
433
00:21:36.660 --> 00:21:38.768
So the answer's definitely yes.
434
00:21:38.768 --> 00:21:40.669
Okay, thank you very much.
435
00:21:40.669 --> 00:21:42.679
Sure. (chuckles)
436
00:21:42.679 --> 00:21:44.340
Appreciate y'all's patience by the way.
437
00:21:44.340 --> 00:21:47.910
So, so far we've talked about system requirements, right?
438
00:21:47.910 --> 00:21:51.120
What user information, user roles need to be added,
439
00:21:51.120 --> 00:21:53.880
master administrator for creating feature management,
440
00:21:53.880 --> 00:21:55.800
enabling feature management
441
00:21:55.800 --> 00:21:58.800
and then we get into the bulk upload
442
00:21:58.800 --> 00:22:00.393
and utilizing the template.
443
00:22:02.250 --> 00:22:04.080
You know, we wanna make sure you realize
444
00:22:04.080 --> 00:22:07.200
that you can use the user interface,
445
00:22:07.200 --> 00:22:09.450
but I have to say that if you start
446
00:22:09.450 --> 00:22:13.200
going down a bulk-upload trail,
447
00:22:13.200 --> 00:22:16.890
you can still look at the orders that are created,
448
00:22:16.890 --> 00:22:19.476
but if you start updating them,
449
00:22:19.476 --> 00:22:21.960
then there's gonna be problems if only one
450
00:22:21.960 --> 00:22:25.590
of your partners have performed the upload to date
451
00:22:25.590 --> 00:22:27.960
and I'll come back and make sure you know that
452
00:22:27.960 --> 00:22:29.220
towards the end.
453
00:22:29.220 --> 00:22:30.870
But I wanted to point that out.
454
00:22:30.870 --> 00:22:34.260
But you can create, as we've just shown, right,
455
00:22:34.260 --> 00:22:38.400
an advanced PPQ performance transaction
456
00:22:38.400 --> 00:22:41.220
with an In Flight Order using the UI,
457
00:22:41.220 --> 00:22:42.520
which is what we just did.
458
00:22:44.520 --> 00:22:46.140
Again, you know, so we're gonna move forward
459
00:22:46.140 --> 00:22:47.730
and start using the bulk upload,
460
00:22:47.730 --> 00:22:50.880
which is an alternate approach that allows you
461
00:22:50.880 --> 00:22:54.660
to do a large number of orders at once
462
00:22:54.660 --> 00:22:58.860
into G-Invoicing at one time,
463
00:22:58.860 --> 00:23:01.080
also working with your trading partner.
464
00:23:01.080 --> 00:23:05.880
These orders can be approved and set to open
465
00:23:05.880 --> 00:23:09.120
as soon as both agencies perform their side
466
00:23:09.120 --> 00:23:11.820
of the bulk upload process.
467
00:23:11.820 --> 00:23:15.720
That said, we have already noted
468
00:23:15.720 --> 00:23:19.697
that OP, the order originating partner indicator,
469
00:23:19.697 --> 00:23:23.310
has to be recognized.
470
00:23:23.310 --> 00:23:25.170
Who will start the process?
471
00:23:25.170 --> 00:23:29.130
Who will be partner one in performing the upload?
472
00:23:29.130 --> 00:23:29.963
That is determined
473
00:23:29.963 --> 00:23:34.050
by this order originating partner indicator
474
00:23:34.050 --> 00:23:35.850
set in the GT&C.
475
00:23:35.850 --> 00:23:39.000
And just as the question was just asked, yes,
476
00:23:39.000 --> 00:23:41.910
the GT&C must allow for advances
477
00:23:41.910 --> 00:23:45.060
in order to allow for advanced PPQ as well.
478
00:23:45.060 --> 00:23:46.310
These are all-
So, one note though.
479
00:23:46.310 --> 00:23:47.640
In this bulk upload,
480
00:23:47.640 --> 00:23:50.220
users still have to manually, themselves,
481
00:23:50.220 --> 00:23:53.069
create the GT&C, correct?
482
00:23:53.069 --> 00:23:56.220
So that part is still completely manually done
483
00:23:56.220 --> 00:23:57.720
by both agencies first,
484
00:23:57.720 --> 00:24:00.690
otherwise I guess the bulk upload would reject?
485
00:24:00.690 --> 00:24:03.750
I guess two... (audio cuts out)
486
00:24:03.750 --> 00:24:06.300
Manually create it no matter what.
487
00:24:06.300 --> 00:24:08.130
Yes, the answer is yes,
488
00:24:08.130 --> 00:24:12.030
you have to go into the user interface to create a GT&C,
489
00:24:12.030 --> 00:24:15.240
get it approved by both agencies before you can begin
490
00:24:15.240 --> 00:24:17.730
to create an order against any GT&C.
491
00:24:17.730 --> 00:24:19.590
That's absolute fact.
492
00:24:19.590 --> 00:24:20.850
And I have another question.
493
00:24:20.850 --> 00:24:24.090
So the bulk upload, let's say agency A and agency B
494
00:24:24.090 --> 00:24:26.460
have a bulk upload, they work together,
495
00:24:26.460 --> 00:24:28.590
and let's say there's 20 orders
496
00:24:28.590 --> 00:24:32.430
that the agency wants to bulk upload.
497
00:24:32.430 --> 00:24:35.160
What would happen if that there's two GT&Cs
498
00:24:35.160 --> 00:24:38.520
that are just wrong, the reference GT&C hasn't been entered?
499
00:24:38.520 --> 00:24:40.830
Would the bulk completely fail
500
00:24:40.830 --> 00:24:43.447
or would there be an error indicator identifying,
501
00:24:43.447 --> 00:24:45.900
"Okay, you tried to upload 20,
502
00:24:45.900 --> 00:24:48.390
two rejected, 18 are fully uploaded?"
503
00:24:48.390 --> 00:24:49.440
I know this is technical,
504
00:24:49.440 --> 00:24:52.410
but I just wanna go through some system concerns
505
00:24:52.410 --> 00:24:55.350
or ramifications as we work on our analysis.
506
00:24:55.350 --> 00:24:56.610
Mmm-hm. Yep.
507
00:24:56.610 --> 00:24:59.430
I believe it's in a later slide, but the answer is yes,
508
00:24:59.430 --> 00:25:01.249
it's either all or nothing.
509
00:25:01.249 --> 00:25:04.290
You know, you said, "Well if only two to 20 fail,"
510
00:25:04.290 --> 00:25:06.300
you can have 300 rows, right,
511
00:25:06.300 --> 00:25:08.793
representing possibly 300 orders.
512
00:25:11.100 --> 00:25:13.830
We really recommend that you get the formatting right
513
00:25:13.830 --> 00:25:16.737
with doing one or two rows, get familiar with it,
514
00:25:16.737 --> 00:25:20.370
and then adding on to those with that file
515
00:25:20.370 --> 00:25:23.235
with a larger amount of order data
516
00:25:23.235 --> 00:25:26.010
so that you don't run into that
517
00:25:26.010 --> 00:25:27.810
and you don't run into frustrations.
518
00:25:28.770 --> 00:25:33.210
To me, you know, having 300 of problems,
519
00:25:33.210 --> 00:25:35.100
300 rows of possible problems,
520
00:25:35.100 --> 00:25:38.040
is far more difficult than one or two
521
00:25:38.040 --> 00:25:39.510
just to get the formatting right
522
00:25:39.510 --> 00:25:42.863
and then flow the formatting down within the Excel document
523
00:25:42.863 --> 00:25:45.150
is probably the better suggestion.
524
00:25:45.150 --> 00:25:48.840
The other thing is, you asked something I want to touch on,
525
00:25:48.840 --> 00:25:53.130
which is that you can have multiple GT&Cs in there
526
00:25:53.130 --> 00:25:56.760
denoted against multiple different order creations
527
00:25:56.760 --> 00:25:58.980
at the same time in the single file.
528
00:25:58.980 --> 00:26:02.760
It probably is best if you isolate your files
529
00:26:02.760 --> 00:26:05.490
to partner by partner and not mixing them
530
00:26:05.490 --> 00:26:06.990
so that if you're running into problems
531
00:26:06.990 --> 00:26:09.570
or different partners have different concerns
532
00:26:09.570 --> 00:26:12.501
and you have to work with them on updating the file,
533
00:26:12.501 --> 00:26:15.510
then it just would be mind numbing
534
00:26:15.510 --> 00:26:19.170
if you had multiple partners in the same files in my mind.
535
00:26:19.170 --> 00:26:22.590
That's just a suggestion.
If one rejects
536
00:26:22.590 --> 00:26:24.323
the whole file rejects?
Yeah.
537
00:26:24.323 --> 00:26:25.530
Okay, I think that's really important
538
00:26:25.530 --> 00:26:26.760
for the agencies to know.
539
00:26:26.760 --> 00:26:30.723
That's not frankly optimal, but thank you for the feedback.
540
00:26:31.650 --> 00:26:33.000
Understood.
541
00:26:33.000 --> 00:26:34.110
Yep. And we do touch on it,
542
00:26:34.110 --> 00:26:35.730
we do wanna make sure you're familiar with that.
543
00:26:35.730 --> 00:26:37.263
So all good here.
544
00:26:39.060 --> 00:26:39.893
What else?
545
00:26:39.893 --> 00:26:43.210
The order upload file must adhere to defined format
546
00:26:45.060 --> 00:26:48.060
so that the information
547
00:26:48.060 --> 00:26:52.683
has to be exactly what is in the GT&C
548
00:26:52.683 --> 00:26:55.110
with your partner information, your ALC information,
549
00:26:55.110 --> 00:26:56.060
that kind of thing.
550
00:26:57.240 --> 00:27:00.240
The format, and we're gonna go into the formatting,
551
00:27:00.240 --> 00:27:05.160
has to be acceptable by G-Invoicing
552
00:27:05.160 --> 00:27:07.800
and those validation requirements
553
00:27:07.800 --> 00:27:10.170
are actually the same as in the UI,
554
00:27:10.170 --> 00:27:11.910
but here you're manually doing it.
555
00:27:11.910 --> 00:27:15.723
So you know, you have to be definitely aware of that.
556
00:27:18.930 --> 00:27:23.880
This note here in the process that we're about to go over,
557
00:27:23.880 --> 00:27:28.530
servicing or requesting whoever is the OOPI,
558
00:27:28.530 --> 00:27:31.740
after they successfully upload their part
559
00:27:31.740 --> 00:27:36.654
of the order upload, must send an output file
560
00:27:36.654 --> 00:27:38.553
to their trading partner.
561
00:27:40.680 --> 00:27:45.540
Treasury is highly concerned that these files
562
00:27:45.540 --> 00:27:49.655
only be sent via secure channels and you know,
563
00:27:49.655 --> 00:27:54.655
we could advise how treasury or FRB
564
00:27:54.690 --> 00:27:58.170
encrypts their files, but each agency seems to have
565
00:27:58.170 --> 00:28:02.640
their own capability and preference.
566
00:28:02.640 --> 00:28:05.100
So within your agency, you should work
567
00:28:05.100 --> 00:28:09.450
with your G-Invoicing point of contact to identify
568
00:28:09.450 --> 00:28:11.910
how best to transfer files
569
00:28:11.910 --> 00:28:16.263
if you're gonna be using this via secure channels.
570
00:28:22.260 --> 00:28:23.520
Deborah, you're exactly right.
571
00:28:23.520 --> 00:28:25.440
You have to create a GT&C,
572
00:28:25.440 --> 00:28:29.277
both agencies must have approved the the GT&C,
573
00:28:29.277 --> 00:28:32.100
and then we could go into creating
574
00:28:32.100 --> 00:28:37.100
the user-interface-based or FLI-ed order or bulk uploads.
575
00:28:40.320 --> 00:28:42.690
In fact, you know, I created this slide
576
00:28:42.690 --> 00:28:45.813
because I wanted to be able to talk about the process
577
00:28:45.813 --> 00:28:47.523
at a very high level.
578
00:28:49.500 --> 00:28:52.650
Both agencies identify independently
579
00:28:52.650 --> 00:28:54.620
with your trading partner.
580
00:28:54.620 --> 00:28:58.173
What In Flight Orders need to be addressed?
581
00:28:59.520 --> 00:29:02.310
We are recommending, have been recommending
582
00:29:02.310 --> 00:29:06.460
for over a year to my understanding
583
00:29:07.920 --> 00:29:10.980
that agencies should be looking to minimize
584
00:29:10.980 --> 00:29:14.400
as much as possible to In Flight Orders if it's possible.
585
00:29:14.400 --> 00:29:15.570
But whatever's remaining,
586
00:29:15.570 --> 00:29:18.390
both agencies really need to have a communication.
587
00:29:18.390 --> 00:29:21.540
I made this box really big so that everyone can see
588
00:29:21.540 --> 00:29:24.270
that yes, I have to talk to my trading partner
589
00:29:24.270 --> 00:29:27.210
about what we're going to do.
590
00:29:27.210 --> 00:29:29.760
So the initiating partner,
591
00:29:29.760 --> 00:29:32.223
the trading partner that has the OOPI,
592
00:29:33.180 --> 00:29:37.020
then begins to create an Excel file,
593
00:29:37.020 --> 00:29:39.480
has to be saved as a csv file,
594
00:29:39.480 --> 00:29:42.600
and we're gonna talk about this, I'll show examples of this.
595
00:29:42.600 --> 00:29:46.570
The originating partner then uploads the csv file
596
00:29:48.390 --> 00:29:50.313
using the interface,
597
00:29:51.480 --> 00:29:54.240
and then after they get a success,
598
00:29:54.240 --> 00:29:57.030
and the order's initially created
599
00:29:57.030 --> 00:29:59.700
on the originating partner side,
600
00:29:59.700 --> 00:30:02.910
they then have a button that they select
601
00:30:02.910 --> 00:30:06.363
that provides an output file for partner two.
602
00:30:07.680 --> 00:30:10.770
Some things on this file can be changed, some can't.
603
00:30:10.770 --> 00:30:15.770
For example, this file contains the actual new order number
604
00:30:15.990 --> 00:30:18.490
and that should not be messed with by partner two.
605
00:30:19.710 --> 00:30:22.020
So then, via secure channel,
606
00:30:22.020 --> 00:30:24.663
partner two receives this output file.
607
00:30:25.650 --> 00:30:29.310
They then validate, look at it,
608
00:30:29.310 --> 00:30:32.430
make updates where it needs to be updated,
609
00:30:32.430 --> 00:30:35.610
should be communicating with your trading partner.
610
00:30:35.610 --> 00:30:39.300
We have a button that if partner two
611
00:30:39.300 --> 00:30:41.490
absolutely hates the entire file
612
00:30:41.490 --> 00:30:43.590
and wants to start over completely,
613
00:30:43.590 --> 00:30:45.033
partner one can do that.
614
00:30:45.870 --> 00:30:47.640
We have a button to delete the order
615
00:30:47.640 --> 00:30:49.263
that was created by partner one.
616
00:30:51.750 --> 00:30:53.013
If partner two is happy,
617
00:30:54.510 --> 00:30:56.910
they may like the corrections they've made,
618
00:30:56.910 --> 00:30:59.193
they then save the file as a csv,
619
00:31:00.330 --> 00:31:05.253
upload the csv file into the bulk-order interface,
620
00:31:06.270 --> 00:31:09.840
and then the partners review where they're at,
621
00:31:09.840 --> 00:31:11.040
what the order looks like,
622
00:31:11.040 --> 00:31:12.720
anything else that needs to be done.
623
00:31:12.720 --> 00:31:14.580
And in servicing, whichever there,
624
00:31:14.580 --> 00:31:15.720
partner one or partner two,
625
00:31:15.720 --> 00:31:19.770
servicing can then do performance transactions
626
00:31:19.770 --> 00:31:21.843
such as advanced PPQ if needed.
627
00:31:25.290 --> 00:31:26.123
Alright.
628
00:31:30.990 --> 00:31:35.990
So moving it forward, we have to talk about the template,
629
00:31:36.210 --> 00:31:37.830
and like I've already said,
630
00:31:37.830 --> 00:31:40.260
I say it multiple times on purpose, right?
631
00:31:40.260 --> 00:31:44.370
I wanna make sure you know that the information in the GT&C
632
00:31:44.370 --> 00:31:47.430
needs to be adhered to or you're just gonna get errors
633
00:31:47.430 --> 00:31:49.053
every single time.
634
00:31:49.953 --> 00:31:53.310
The ALC information, the organizational group information
635
00:31:53.310 --> 00:31:55.653
for both servicing and requesting are denoted.
636
00:31:58.766 --> 00:32:00.630
The start and end dates must be adhered to.
637
00:32:00.630 --> 00:32:03.450
As the question was, the advanced indicator
638
00:32:03.450 --> 00:32:07.383
must be set to affirmative or yes to allow for advanced PPQ.
639
00:32:08.700 --> 00:32:11.700
And of course both agencies have to recognize
640
00:32:11.700 --> 00:32:14.070
who the originating partner is
641
00:32:14.070 --> 00:32:17.913
that is allowed in the GT&C to create the order.
642
00:32:21.990 --> 00:32:26.100
The person that just last asked her question, you know,
643
00:32:26.100 --> 00:32:29.651
we agree, this is something you have to know
644
00:32:29.651 --> 00:32:32.940
that everything in the order must be valid
645
00:32:32.940 --> 00:32:36.390
and it will be validated or you'll get errors.
646
00:32:36.390 --> 00:32:39.420
We do have error logging there.
647
00:32:39.420 --> 00:32:43.980
We can see per upload attempt what the errors were.
648
00:32:43.980 --> 00:32:46.920
You can download that file, an output file,
649
00:32:46.920 --> 00:32:49.293
to see that offline if you need to.
650
00:32:51.210 --> 00:32:55.500
We know that currently, the max size is 25 meg,
651
00:32:55.500 --> 00:32:57.300
it is flat text file.
652
00:32:57.300 --> 00:33:02.300
So we're not really setting a large-capacity sizing
653
00:33:03.060 --> 00:33:07.443
of how many orders could be in the Excel csv file to date.
654
00:33:08.370 --> 00:33:09.453
We may get to that.
655
00:33:12.223 --> 00:33:16.500
This warning is, if partner one does the upload,
656
00:33:16.500 --> 00:33:18.849
partner two can see the order
657
00:33:18.849 --> 00:33:20.970
even though they have not performed their upload.
658
00:33:20.970 --> 00:33:25.970
Again, if partner one starts messing in the UI
659
00:33:25.980 --> 00:33:28.746
with the order, each of those orders,
660
00:33:28.746 --> 00:33:32.820
they will not be able to use upload file successfully
661
00:33:32.820 --> 00:33:33.840
for that order.
662
00:33:33.840 --> 00:33:35.940
What happens if trading partner one
663
00:33:35.940 --> 00:33:38.490
wants to use the order upload
664
00:33:38.490 --> 00:33:42.247
but trading partner two will not?
665
00:33:43.775 --> 00:33:44.608
Right?
666
00:33:44.608 --> 00:33:48.570
So partner one creates the order,
667
00:33:48.570 --> 00:33:53.217
they could use the output file to notify partner two
668
00:33:53.217 --> 00:33:57.420
of the order numbers and they could still forward
669
00:33:57.420 --> 00:33:59.220
that output file that they receive
670
00:33:59.220 --> 00:34:02.577
after successfully creating the order to partner two
671
00:34:02.577 --> 00:34:06.120
and partner two can then use those order numbers
672
00:34:06.120 --> 00:34:08.970
that are in the file to go into the UI
673
00:34:08.970 --> 00:34:12.990
and look at each of the orders and approve or make changes,
674
00:34:12.990 --> 00:34:15.360
that kind of thing, as needed.
675
00:34:15.360 --> 00:34:18.093
As always, I should say. with any other order.
676
00:34:21.240 --> 00:34:23.610
Thanks.
Okay, cool.
677
00:34:23.610 --> 00:34:24.860
Good question by the way.
678
00:34:26.355 --> 00:34:29.790
Angela again. I have a quick question.
679
00:34:29.790 --> 00:34:32.880
Do we know who will be using this
680
00:34:32.880 --> 00:34:36.270
as a way to look at our files
681
00:34:36.270 --> 00:34:39.000
and somewhat plan or prepare?
682
00:34:39.000 --> 00:34:43.873
Maybe there could be in March's implementation plans,
683
00:34:45.990 --> 00:34:50.019
a question or maybe a survey that could be shared
684
00:34:50.019 --> 00:34:54.990
like GSA, yes, GSA is going to use it for ABC,
685
00:34:54.990 --> 00:34:58.380
or OPM's going to use it for credit monitoring,
686
00:34:58.380 --> 00:35:00.930
or FBI's gonna use it for fingerprinting.
687
00:35:00.930 --> 00:35:02.730
Like certain agencies
688
00:35:02.730 --> 00:35:06.390
because they have regular, consistent-type billings
689
00:35:06.390 --> 00:35:07.800
or things like that
690
00:35:07.800 --> 00:35:12.750
that they're gonna look to utilize this functionality for
691
00:35:12.750 --> 00:35:17.750
so that when we're doing our individual agency analysis,
692
00:35:17.790 --> 00:35:22.260
we kind of have an idea of which way to go, right?
693
00:35:22.260 --> 00:35:27.260
Because again, NRC, we're small fish in big pond, right?
694
00:35:27.780 --> 00:35:29.490
So we're thinking,
695
00:35:29.490 --> 00:35:33.360
possibly it's easier just to do the one-offs,
696
00:35:33.360 --> 00:35:37.290
but if we find the majority of the larger agencies
697
00:35:37.290 --> 00:35:40.590
are using the In Flight Order uploads,
698
00:35:40.590 --> 00:35:43.230
we might wanna tailor our approach.
699
00:35:43.230 --> 00:35:44.063
Don't know.
700
00:35:47.250 --> 00:35:50.640
It's a fair question and you know,
701
00:35:50.640 --> 00:35:52.170
we're gonna take note of that.
702
00:35:52.170 --> 00:35:54.360
I believe we could pursue that.
703
00:35:54.360 --> 00:35:55.860
I think it's a great question.
704
00:35:56.910 --> 00:36:01.910
I will say that the In Flight
705
00:36:02.670 --> 00:36:04.140
probably will affect everybody.
706
00:36:04.140 --> 00:36:05.070
We've had folks,
707
00:36:05.070 --> 00:36:06.810
and I can't tell you which agencies
708
00:36:06.810 --> 00:36:08.400
that I've heard in the past,
709
00:36:08.400 --> 00:36:10.830
have denoted that they would prefer to be able
710
00:36:10.830 --> 00:36:14.880
to bulk upload high numbers of orders at once
711
00:36:14.880 --> 00:36:17.530
instead of doing the manual approach.
712
00:36:17.530 --> 00:36:22.410
On the other hand, both agencies have that option, right?
713
00:36:22.410 --> 00:36:23.703
You could still go into the UI
714
00:36:23.703 --> 00:36:27.120
even if your trading partner is or is not.
715
00:36:27.120 --> 00:36:29.310
It could be a one-off thing, you know,
716
00:36:29.310 --> 00:36:30.930
one sided if you will,
717
00:36:30.930 --> 00:36:33.240
still allowing the other trading partner to,
718
00:36:33.240 --> 00:36:35.403
and so we are taking note.
719
00:36:36.240 --> 00:36:37.290
Do appreciate it by the way.
720
00:36:37.290 --> 00:36:38.700
That's a good-to-know.
721
00:36:38.700 --> 00:36:42.480
Thank you for sharing that option with us
722
00:36:42.480 --> 00:36:44.490
that we could go into the UI
723
00:36:44.490 --> 00:36:49.490
even if our partner one chooses IFL upload. Thank you.
724
00:36:51.000 --> 00:36:53.280
Sure, exactly. Yep.
725
00:36:53.280 --> 00:36:54.806
Okay. So-
I have a question.
726
00:36:54.806 --> 00:36:56.139
Okay.
727
00:36:56.980 --> 00:36:58.530
Just a clarification.
728
00:36:58.530 --> 00:37:02.463
So as far as like what is in the approval field,
729
00:37:03.810 --> 00:37:05.460
so when you upload the file,
730
00:37:05.460 --> 00:37:07.440
the approval fields are filled in
731
00:37:07.440 --> 00:37:12.180
with the original approvers and dates,
732
00:37:12.180 --> 00:37:16.320
and then if Partner two uploads the file,
733
00:37:16.320 --> 00:37:21.320
assuming they have the same approval dates and approvers,
734
00:37:21.480 --> 00:37:25.710
then that would stay as is, but if they approve in the UI,
735
00:37:25.710 --> 00:37:29.310
does it then change to whoever's approving
736
00:37:29.310 --> 00:37:30.753
and then the current date?
737
00:37:32.490 --> 00:37:34.080
Does that make sense?
Right.
738
00:37:34.080 --> 00:37:35.100
Yeah, yep.
739
00:37:35.100 --> 00:37:39.780
I think your question is if somebody put information
740
00:37:39.780 --> 00:37:43.830
into the file, in this case approvers,
741
00:37:43.830 --> 00:37:46.043
and then that was on partner one's side,
742
00:37:46.043 --> 00:37:47.543
and then partner two comes in,
743
00:37:48.720 --> 00:37:51.480
the order has not been approved yet,
744
00:37:51.480 --> 00:37:54.120
anyone that has approval role to can see the order
745
00:37:54.120 --> 00:37:56.223
could do the approval in the UI.
746
00:37:58.649 --> 00:38:02.100
And then that will overwrite the approvals
747
00:38:02.100 --> 00:38:06.430
that were uploaded through the file process-
748
00:38:06.430 --> 00:38:07.530
Okay. Okay.
749
00:38:07.530 --> 00:38:09.003
So wait. No.
750
00:38:09.880 --> 00:38:13.980
If both agencies provided approvals in the file,
751
00:38:13.980 --> 00:38:18.300
the order would appear and become status of open
752
00:38:18.300 --> 00:38:20.850
with the approvals already provided.
753
00:38:20.850 --> 00:38:22.020
You'd have to do a modify
754
00:38:22.020 --> 00:38:23.760
if you wanted to change the approvers
755
00:38:23.760 --> 00:38:25.310
and dates after that.
Right.
756
00:38:26.490 --> 00:38:27.646
No. Okay.
757
00:38:27.646 --> 00:38:30.180
That was half of what I was asking.
758
00:38:30.180 --> 00:38:33.120
So if both agencies use the order upload
759
00:38:33.120 --> 00:38:37.680
with the same approval information, then it stays as that,
760
00:38:37.680 --> 00:38:40.230
but if trading partner one uploads
761
00:38:40.230 --> 00:38:44.923
with approval information, but trading partner two
762
00:38:46.080 --> 00:38:49.010
goes into the UI to do it, then it gets...
763
00:38:50.610 --> 00:38:53.820
Then the approval is whatever is done at that time
764
00:38:53.820 --> 00:38:55.890
versus what was in the file.
765
00:38:55.890 --> 00:38:58.025
I would agree with that.
Okay.
766
00:38:58.025 --> 00:38:59.249
Just yeah.
767
00:38:59.249 --> 00:39:00.270
And you know, you can stipulate
768
00:39:00.270 --> 00:39:01.440
in working with your trading partner
769
00:39:01.440 --> 00:39:04.170
not to ever put information in on your behalf,
770
00:39:04.170 --> 00:39:06.900
your partner two's behalf for example, you know,
771
00:39:06.900 --> 00:39:08.070
that kind of thing.
772
00:39:08.070 --> 00:39:09.930
Communication between the partners.
773
00:39:09.930 --> 00:39:12.030
I would even go as far as saying the trading partners
774
00:39:12.030 --> 00:39:14.520
should work together to create the initial file
775
00:39:14.520 --> 00:39:17.880
just to make things simpler and quicker for you to work,
776
00:39:17.880 --> 00:39:18.713
that kind of thing.
777
00:39:18.713 --> 00:39:21.240
So that would be best.
778
00:39:21.240 --> 00:39:23.010
We always fall back to, you know,
779
00:39:23.010 --> 00:39:24.510
communicating with each other and make sure
780
00:39:24.510 --> 00:39:26.021
that this works for you well.
781
00:39:26.021 --> 00:39:26.876
So then based...
782
00:39:26.876 --> 00:39:28.620
Okay, so as far as like the...
783
00:39:28.620 --> 00:39:30.400
So then as far as what the status is,
784
00:39:30.400 --> 00:39:33.990
when you do the order upload, it would just be based
785
00:39:33.990 --> 00:39:36.840
on whatever approvals were provided?
786
00:39:36.840 --> 00:39:39.540
Well, yeah, if you did not provide approvals,
787
00:39:39.540 --> 00:39:44.540
it would still be shared with requesting for example,
788
00:39:44.610 --> 00:39:46.620
and you know, development,
789
00:39:46.620 --> 00:39:49.283
if there's anything you want to add to that, feel free.
790
00:39:50.957 --> 00:39:53.590
Okay, thank you.
791
00:39:53.590 --> 00:39:55.500
All right? All right?
792
00:39:55.500 --> 00:39:58.260
Let me just back up here a second and make sure. Yep.
793
00:39:58.260 --> 00:39:59.700
So this is what, you know...
794
00:39:59.700 --> 00:40:02.910
We try to identify because there's so much here
795
00:40:02.910 --> 00:40:04.410
to be considerate of.
796
00:40:04.410 --> 00:40:06.575
Here's partner one's considerations.
797
00:40:06.575 --> 00:40:08.647
Somewhere in big letters it should be,
798
00:40:08.647 --> 00:40:11.678
"Communicate with your partner everywhere," right?
799
00:40:11.678 --> 00:40:14.729
Partner two, they receive the file.
800
00:40:14.729 --> 00:40:18.330
Again, if they disagree with the data,
801
00:40:18.330 --> 00:40:22.440
they could ask partner one to reject, you know,
802
00:40:22.440 --> 00:40:24.180
to reverse the order,
803
00:40:24.180 --> 00:40:27.510
to remove the order basically in a rejection.
804
00:40:27.510 --> 00:40:30.456
They could, in the UI, reject the order as well,
805
00:40:30.456 --> 00:40:33.510
if they haven't already approved, right?
806
00:40:33.510 --> 00:40:34.950
If they have already approved,
807
00:40:34.950 --> 00:40:37.260
then they have to work together to do a modify
808
00:40:37.260 --> 00:40:38.520
is what it comes down to.
809
00:40:38.520 --> 00:40:40.140
So over and over, I come back to,
810
00:40:40.140 --> 00:40:42.090
you gotta be able to, each step,
811
00:40:42.090 --> 00:40:46.413
communicate with your partner to make this work.
812
00:40:47.730 --> 00:40:50.550
And again, every order in the upload must be valid,
813
00:40:50.550 --> 00:40:54.093
pass the validations or you'll just have failures.
814
00:40:55.620 --> 00:40:56.700
Hi, this is Jurgen Brenner
815
00:40:56.700 --> 00:40:58.530
from NIST Department of Commerce.
816
00:40:58.530 --> 00:41:00.130
I have a quick question on that.
817
00:41:02.220 --> 00:41:06.780
Let's say you do an order upload for your in flight
818
00:41:06.780 --> 00:41:11.560
and maybe an IPAC comes in and so the dollar amount changes
819
00:41:12.720 --> 00:41:16.410
by the time your original file was created
820
00:41:16.410 --> 00:41:19.323
and by the time you do an upload,
821
00:41:20.366 --> 00:41:22.830
and let's say you have 20 transactions
822
00:41:22.830 --> 00:41:25.650
or 30 transactions on the file.
823
00:41:25.650 --> 00:41:28.260
Would you recommend, or is it possible,
824
00:41:28.260 --> 00:41:32.850
to just reverse the entire file, correct the amount
825
00:41:32.850 --> 00:41:33.930
and then re-upload it?
826
00:41:33.930 --> 00:41:37.410
Or is it possible to update the amount
827
00:41:37.410 --> 00:41:39.910
if they're posted as unapproved
828
00:41:41.010 --> 00:41:43.050
on the order in G-Invoicing?
829
00:41:43.050 --> 00:41:44.300
What's your take on that?
830
00:41:47.340 --> 00:41:49.343
So it sounds as though,
831
00:41:49.343 --> 00:41:51.532
and you can correct me there,
832
00:41:51.532 --> 00:41:54.690
partner one did an upload,
833
00:41:54.690 --> 00:41:59.570
partner two's looking at the order itself in the UI
834
00:42:00.660 --> 00:42:03.750
and would they be able to change
835
00:42:03.750 --> 00:42:05.790
the schedule information, for example?
836
00:42:05.790 --> 00:42:07.710
Is that kind of your question?
837
00:42:07.710 --> 00:42:08.543
Yeah, yep.
838
00:42:08.543 --> 00:42:09.987
Let's say like an IPAC came in
839
00:42:09.987 --> 00:42:12.840
and it lowered the unliquidated balance
840
00:42:12.840 --> 00:42:15.510
and you aren't posting history or anything like that,
841
00:42:15.510 --> 00:42:17.915
you're just posting the unliquidated balance
842
00:42:17.915 --> 00:42:19.443
on the in flight.
843
00:42:20.310 --> 00:42:21.960
I'm trying to think how best to answer that
844
00:42:21.960 --> 00:42:24.570
because there's so many, so much info.
845
00:42:24.570 --> 00:42:25.590
I have questions, right?
846
00:42:25.590 --> 00:42:29.400
You know, did partner two also do the upload,
847
00:42:29.400 --> 00:42:31.110
bulk upload as well?
848
00:42:31.110 --> 00:42:34.410
If the status is in open, then we can do a modify.
849
00:42:34.410 --> 00:42:35.850
I think what you're trying to get at,
850
00:42:35.850 --> 00:42:39.240
is that, and this is a good point I think you're making,
851
00:42:39.240 --> 00:42:42.807
which is you're in the process of doing bulk upload
852
00:42:42.807 --> 00:42:46.710
in In Flight Orders and while you're doing that negotiation
853
00:42:46.710 --> 00:42:48.150
and trying to create the orders,
854
00:42:48.150 --> 00:42:50.850
somebody in the background outside of G-Invoicing
855
00:42:50.850 --> 00:42:52.710
did an IPAC settlement.
856
00:42:52.710 --> 00:42:54.512
Is that right?
Exactly. Exactly right.
857
00:42:54.512 --> 00:42:57.870
And you know, the first part is,
858
00:42:57.870 --> 00:43:01.020
that is, I think, treasury and everyone's big worry
859
00:43:01.020 --> 00:43:04.680
with In Flight Orders that it's possible
860
00:43:04.680 --> 00:43:06.300
that that can happen.
861
00:43:06.300 --> 00:43:08.790
I try to tell my agencies, "You gotta be very careful.
862
00:43:08.790 --> 00:43:12.780
You gotta talk to your people that may be involved
863
00:43:12.780 --> 00:43:14.340
or may be in that big net
864
00:43:14.340 --> 00:43:18.480
that this file is going to address."
865
00:43:18.480 --> 00:43:21.240
And what could you do about it?
866
00:43:21.240 --> 00:43:24.360
It's possible to do a modify-create
867
00:43:24.360 --> 00:43:27.990
as long as you're allowed advance to do a another schedule
868
00:43:27.990 --> 00:43:31.050
and then do an advanced PPQ for that amount
869
00:43:31.050 --> 00:43:33.480
that you noted the IPAC settled against.
870
00:43:33.480 --> 00:43:35.130
And I really wanna pause here
871
00:43:35.130 --> 00:43:38.730
in case anyone on my team or Treasury
872
00:43:38.730 --> 00:43:40.980
has another response to that.
873
00:43:40.980 --> 00:43:42.720
Okay. Alright.
874
00:43:42.720 --> 00:43:47.040
I think my team gives me a silent thumbs up on that.
875
00:43:47.040 --> 00:43:49.223
Do you have any follow up questions on that?
876
00:43:50.220 --> 00:43:52.020
No, I think you've addressed them.
877
00:43:52.020 --> 00:43:55.410
It's just basically we've gotta be careful with timing,
878
00:43:55.410 --> 00:43:58.380
the timing of this whole process, so.
879
00:43:58.380 --> 00:43:59.213
Right.
880
00:43:59.213 --> 00:44:01.140
At this point currently, you know,
881
00:44:01.140 --> 00:44:03.573
you can still do IGT via IPAC.
882
00:44:04.590 --> 00:44:08.580
You know, again, you gotta work within your agency
883
00:44:08.580 --> 00:44:09.720
and with your trading partners
884
00:44:09.720 --> 00:44:10.970
in good communication while you're doing this.
885
00:44:10.970 --> 00:44:13.770
Well, and I think also, Jurgen,
886
00:44:13.770 --> 00:44:15.480
you bring up a good point,
887
00:44:15.480 --> 00:44:18.750
is internally make sure everything's cleared out
888
00:44:18.750 --> 00:44:21.453
of any suspense account you might be holding.
889
00:44:25.230 --> 00:44:26.130
Yep. Yeah.
890
00:44:26.130 --> 00:44:28.860
We definitely have to have the reconciliation complete
891
00:44:28.860 --> 00:44:32.640
before the the upload is approved.
892
00:44:32.640 --> 00:44:33.603
Yep.
Yep.
893
00:44:34.530 --> 00:44:36.300
So thank you for bringing that up
894
00:44:36.300 --> 00:44:39.090
because I hadn't even taken that into consideration,
895
00:44:39.090 --> 00:44:41.850
so thanks.
Yep. Thanks.
896
00:44:41.850 --> 00:44:43.590
Yep. Appreciate that.
897
00:44:43.590 --> 00:44:46.743
All right, I'm gonna go ahead and move forward though.
898
00:44:48.240 --> 00:44:50.700
This is what the interface looks like.
899
00:44:50.700 --> 00:44:55.080
We wanted to make sure we outline it very clearly.
900
00:44:55.080 --> 00:44:57.480
You browse through the file to upload,
901
00:44:57.480 --> 00:45:00.090
you can give it a nickname if you want.
902
00:45:00.090 --> 00:45:02.130
You can actually select normal orders.
903
00:45:02.130 --> 00:45:04.620
So this isn't just for In Flight orders going forward
904
00:45:04.620 --> 00:45:07.890
as people get used to using it, that's their preference.
905
00:45:07.890 --> 00:45:10.530
We're going to select In Flight orders, right?
906
00:45:10.530 --> 00:45:12.333
And then this will pop up.
907
00:45:13.410 --> 00:45:16.140
And it is not something to be ignored.
908
00:45:16.140 --> 00:45:18.060
Are you the order originating partner?
909
00:45:18.060 --> 00:45:20.010
So partner one will always say yes
910
00:45:20.010 --> 00:45:22.410
and partner two will always say no.
911
00:45:22.410 --> 00:45:25.290
If partner two says yes, they're going to get errors
912
00:45:25.290 --> 00:45:28.601
and then they may not realize
913
00:45:28.601 --> 00:45:31.650
that they caused the error just by saying yes instead of no
914
00:45:31.650 --> 00:45:34.740
that they are not the order-originating partner.
915
00:45:34.740 --> 00:45:37.833
Once we select that, we then select upload.
916
00:45:39.150 --> 00:45:40.530
We wait, right?
917
00:45:40.530 --> 00:45:44.580
The system will parse the file, and again,
918
00:45:44.580 --> 00:45:49.580
it has to be successful with no errors for the most part.
919
00:45:51.240 --> 00:45:53.576
So maybe system erroneous errors
920
00:45:53.576 --> 00:45:57.120
are coming up on my side right now in QAF
921
00:45:57.120 --> 00:45:58.200
and we're working on that,
922
00:45:58.200 --> 00:46:01.770
but that's not what you normally would see.
923
00:46:01.770 --> 00:46:05.970
And then after it parses, this button does not appear
924
00:46:05.970 --> 00:46:09.450
until the parsing comes up without errors.
925
00:46:09.450 --> 00:46:12.360
We then select Create Shared Order
926
00:46:12.360 --> 00:46:14.970
and that's when the actual orders are created
927
00:46:14.970 --> 00:46:16.810
based on the file that we uploaded
928
00:46:17.880 --> 00:46:20.280
for your trading partner to be able to see.
929
00:46:20.280 --> 00:46:22.950
And we outline it here as well.
930
00:46:22.950 --> 00:46:24.183
Make sure you see that.
931
00:46:25.310 --> 00:46:28.200
Partner two is very similar.
932
00:46:28.200 --> 00:46:31.980
The only difference again is that trading partner two
933
00:46:31.980 --> 00:46:34.680
must say no, they are not the order-originating partner
934
00:46:34.680 --> 00:46:37.833
to allow this to come through.
935
00:46:39.330 --> 00:46:41.180
Get any errors in that kind of thing.
936
00:46:44.700 --> 00:46:47.737
So Rachel, your question is valid.
937
00:46:47.737 --> 00:46:51.724
"Would it be clearer to ask who's the buyer and the seller?"
938
00:46:51.724 --> 00:46:55.260
No, because either the buyer or the seller
939
00:46:55.260 --> 00:46:57.630
could be the order-originating partner
940
00:46:57.630 --> 00:47:01.530
depending upon how the GT&C was created.
941
00:47:01.530 --> 00:47:02.843
It's a good question though.
942
00:47:06.780 --> 00:47:09.180
I don't know if you noticed, but right here,
943
00:47:09.180 --> 00:47:11.970
if you go to the file upload area,
944
00:47:11.970 --> 00:47:14.280
you can download a template.
945
00:47:14.280 --> 00:47:17.790
We have another spot for you to download it as well.
946
00:47:17.790 --> 00:47:20.070
You do have to use the template
947
00:47:20.070 --> 00:47:24.683
in order to be able to upload these files.
948
00:47:26.850 --> 00:47:28.383
These are the two locations.
949
00:47:29.280 --> 00:47:33.267
Again, one is in the product itself, in the UI,
950
00:47:33.267 --> 00:47:36.660
the other is in our FIDS location.
951
00:47:36.660 --> 00:47:40.260
And we are uploading, you know,
952
00:47:40.260 --> 00:47:43.530
making updates as needed to the template itself.
953
00:47:43.530 --> 00:47:46.080
This is kind of a semblance of what the file looks like.
954
00:47:46.080 --> 00:47:48.450
There's actually a lot of information
955
00:47:48.450 --> 00:47:50.790
and instruction per column,
956
00:47:50.790 --> 00:47:54.510
but I'm gonna go through with you the most important things
957
00:47:54.510 --> 00:47:55.833
that we need to address.
958
00:47:59.460 --> 00:48:00.870
This slide is being provided
959
00:48:00.870 --> 00:48:03.840
as an at-a-glance review of the cells
960
00:48:03.840 --> 00:48:05.010
in a required formatting
961
00:48:05.010 --> 00:48:07.635
for a successful parsing and uploading
962
00:48:07.635 --> 00:48:11.403
into G-Invoicing uploads UI.
963
00:48:13.500 --> 00:48:15.450
At the bottom of the slide
964
00:48:15.450 --> 00:48:18.210
is the source of the TAS information requirements
965
00:48:18.210 --> 00:48:19.803
for your future review.
966
00:48:22.920 --> 00:48:27.473
The following slides will discuss how to actually format
967
00:48:28.684 --> 00:48:30.543
as per what we're showing here.
968
00:48:34.230 --> 00:48:35.063
This slide...
969
00:48:37.410 --> 00:48:39.270
The next cell is the A cell.
970
00:48:41.043 --> 00:48:46.043
This cell requires capitalized X, F, or A
971
00:48:46.290 --> 00:48:50.190
as appropriate for the specific TAS-A column.
972
00:48:50.190 --> 00:48:54.870
We're showing here an example in Excel for that cell
973
00:48:54.870 --> 00:48:56.223
as a capital X.
974
00:48:57.960 --> 00:49:00.750
Here, you're not seeing
975
00:49:00.750 --> 00:49:02.130
what's in the cell, right?
976
00:49:02.130 --> 00:49:07.130
So somebody put an ALC information in there
977
00:49:07.680 --> 00:49:11.490
and you right click on it and say Format Cell,
978
00:49:11.490 --> 00:49:14.040
select Custom, highlight the General
979
00:49:14.040 --> 00:49:16.500
and then put eight zeros there, okay?
980
00:49:16.500 --> 00:49:19.657
Now you could tell me that,
981
00:49:19.657 --> 00:49:23.130
"Well I have eight characters in the ALC
982
00:49:23.130 --> 00:49:25.980
already identified in the cell,"
983
00:49:25.980 --> 00:49:27.360
and actually it would be okay,
984
00:49:27.360 --> 00:49:29.823
but I need to make sure you know how to do it.
985
00:49:32.077 --> 00:49:36.900
These are the TAS cells that are most affected by TAS.
986
00:49:36.900 --> 00:49:40.590
And we're gonna go through these here separately.
987
00:49:40.590 --> 00:49:44.310
So like the AID, it may say 14,
988
00:49:44.310 --> 00:49:46.710
but I need to have a zero in front of it.
989
00:49:46.710 --> 00:49:49.410
So I'm gonna right click on a cell, select Custom,
990
00:49:49.410 --> 00:49:51.810
and again, put three zeros there and hit Okay.
991
00:49:54.447 --> 00:49:58.650
For the main numerics,
992
00:49:58.650 --> 00:50:00.930
sometimes there are only three characters
993
00:50:00.930 --> 00:50:03.270
and so you need to have...
994
00:50:03.270 --> 00:50:05.640
Oh, it's okay right there.
995
00:50:05.640 --> 00:50:08.250
So, you need to have four characters,
996
00:50:08.250 --> 00:50:11.820
or placeholders as I heard Spencer say, which is right.
997
00:50:11.820 --> 00:50:16.820
So, if there is 146 instead of 1046,
998
00:50:17.130 --> 00:50:18.960
then we'd get a zero in the front.
999
00:50:18.960 --> 00:50:20.710
That's what that's gonna do for us.
1000
00:50:22.140 --> 00:50:23.340
Same thing with SUB.
1001
00:50:23.340 --> 00:50:26.400
I see a lot of just one numeric there
1002
00:50:26.400 --> 00:50:29.103
and you want to have three.
1003
00:50:31.470 --> 00:50:33.570
What else? Object class.
1004
00:50:33.570 --> 00:50:36.180
So object class is very specific.
1005
00:50:36.180 --> 00:50:39.810
You need to look for this to go find the object class cells.
1006
00:50:39.810 --> 00:50:42.093
It may be blank.
1007
00:50:43.200 --> 00:50:45.270
And development, correct me if I'm wrong,
1008
00:50:45.270 --> 00:50:46.920
we will not accept blank,
1009
00:50:46.920 --> 00:50:50.504
you have to put some kind of identified numeric there
1010
00:50:50.504 --> 00:50:52.713
for your object class.
1011
00:50:57.540 --> 00:51:01.953
This file, to be accepted, must be in a .csv format.
1012
00:51:02.910 --> 00:51:06.060
When you're working with the file in Excel
1013
00:51:06.060 --> 00:51:09.672
or if you open a csv after you save it,
1014
00:51:09.672 --> 00:51:13.530
you need to re-save as a .csv
1015
00:51:13.530 --> 00:51:15.930
after you're finished formatting.
1016
00:51:15.930 --> 00:51:18.420
We have heard from members of DOD,
1017
00:51:18.420 --> 00:51:21.510
their recommendation is to separately save the file
1018
00:51:21.510 --> 00:51:25.350
as an Excel, xlsx for example.
1019
00:51:25.350 --> 00:51:27.960
And then, as needed, as you're making updates
1020
00:51:27.960 --> 00:51:31.140
to save the file out as a .csv,
1021
00:51:31.140 --> 00:51:34.833
to save the headache of having to reformat over again.
1022
00:51:39.150 --> 00:51:42.630
I did note that you can open this in Notepad.
1023
00:51:42.630 --> 00:51:45.630
Notepad does not add additional character sets
1024
00:51:45.630 --> 00:51:47.220
or remove formatting.
1025
00:51:47.220 --> 00:51:49.989
A lot of people will find that arduous
1026
00:51:49.989 --> 00:51:53.250
because it's ugly.
1027
00:51:53.250 --> 00:51:54.147
It is.
1028
00:51:54.147 --> 00:51:55.920
You really have to know what you're doing.
1029
00:51:55.920 --> 00:52:00.920
And if you have 300 orders or 300 orders with 200 schedules,
1030
00:52:01.725 --> 00:52:03.410
it's gonna be a lot of...
1031
00:52:04.980 --> 00:52:06.600
Almost need a microscope to understand
1032
00:52:06.600 --> 00:52:08.610
what you're seeing sometimes, so.
1033
00:52:08.610 --> 00:52:09.610
But it is an option.
1034
00:52:16.020 --> 00:52:20.070
Julianne, "Is the object class required only for the buyer?"
1035
00:52:20.070 --> 00:52:23.280
My understanding is yes. It's a good point.
1036
00:52:23.280 --> 00:52:26.130
But when partner one does the upload,
1037
00:52:26.130 --> 00:52:27.830
they can include that information.
1038
00:52:32.460 --> 00:52:36.360
Okay, well this has been a lot of fun.
1039
00:52:36.360 --> 00:52:38.070
We are gonna do a demonstration of the upload
1040
00:52:38.070 --> 00:52:39.420
here in a minute.
1041
00:52:39.420 --> 00:52:43.800
We just left this slide up because we want folks
1042
00:52:43.800 --> 00:52:47.763
to, one last time, talk to each other,
1043
00:52:48.600 --> 00:52:52.440
make sure that you're doing best practices, if you will,
1044
00:52:52.440 --> 00:52:54.810
of negotiating, talking about it.
1045
00:52:54.810 --> 00:52:59.810
The point about IFOs and potentially hitting IPAC
1046
00:52:59.940 --> 00:53:02.643
on the outside is possible at this time.
1047
00:53:03.690 --> 00:53:07.860
So negotiating and good communication is important.
1048
00:53:07.860 --> 00:53:10.613
As I said, start with a minimum number in the csv
1049
00:53:10.613 --> 00:53:12.543
and the minimum number of rows.
1050
00:53:15.390 --> 00:53:17.300
You know, you gotta...
1051
00:53:18.616 --> 00:53:19.770
If you go with large number
1052
00:53:19.770 --> 00:53:22.186
or if you're not familiar with the formatting,
1053
00:53:22.186 --> 00:53:25.803
you may have to do this a few times to get it right.
1054
00:53:26.730 --> 00:53:29.550
Contacting the AIT to get that formatted down
1055
00:53:29.550 --> 00:53:30.840
if you're having problems and concerns.
1056
00:53:30.840 --> 00:53:32.520
We don't want you floundering
1057
00:53:32.520 --> 00:53:35.550
as you're getting used to using this product.
1058
00:53:35.550 --> 00:53:39.930
There is another way of doing this that I will show you
1059
00:53:39.930 --> 00:53:41.013
towards the end here.
1060
00:53:43.110 --> 00:53:45.420
It works and I'll show you that too.
1061
00:53:45.420 --> 00:53:46.253
What else?
1062
00:53:46.253 --> 00:53:50.610
Keeping track of your files by partner is recommended.
1063
00:53:50.610 --> 00:53:52.260
The last thing we want
1064
00:53:52.260 --> 00:53:55.770
is the same orders being created twice.
1065
00:53:55.770 --> 00:53:57.450
Again, that could be a problem, right?
1066
00:53:57.450 --> 00:54:00.240
There's no throttle on this,
1067
00:54:00.240 --> 00:54:03.480
there's no governor throttle to stop that from happening.
1068
00:54:03.480 --> 00:54:07.110
So we're asking partners to be mindful
1069
00:54:07.110 --> 00:54:10.500
of what files have been already used
1070
00:54:10.500 --> 00:54:12.600
and what orders have already been created.
1071
00:54:16.770 --> 00:54:17.603
Okay?
1072
00:54:19.020 --> 00:54:19.853
I'm just reading through just
1073
00:54:19.853 --> 00:54:21.443
to make sure we're covering everything.
1074
00:54:21.443 --> 00:54:26.127
Users should not change orders in G-Invoicing and their ERP
1075
00:54:26.127 --> 00:54:28.740
including IFO generated orders
1076
00:54:28.740 --> 00:54:33.330
until both partners have finished, is the recommendation.
1077
00:54:33.330 --> 00:54:36.360
More than one time about the OOPI, who is first.
1078
00:54:36.360 --> 00:54:38.710
File must contain the proper number of columns.
1079
00:54:39.900 --> 00:54:43.683
The last row must have a hash in it and you'll see this.
1080
00:54:45.900 --> 00:54:46.733
Okay.
1081
00:54:50.610 --> 00:54:52.920
Each partner must appropriately select yes or no,
1082
00:54:52.920 --> 00:54:53.910
and I've told you, you know,
1083
00:54:53.910 --> 00:54:55.787
who is the order originating partners
1084
00:54:55.787 --> 00:54:57.187
is what this is referencing.
1085
00:54:58.650 --> 00:54:59.483
Okay.
1086
00:55:01.110 --> 00:55:03.780
I probably am gonna have to log back in.
1087
00:55:03.780 --> 00:55:05.313
Let's see if that's true.
1088
00:55:07.050 --> 00:55:09.300
No, I'm still there. Okay.
1089
00:55:09.300 --> 00:55:13.290
So if I go down here,
1090
00:55:13.290 --> 00:55:18.003
this is where the order uploads option is.
1091
00:55:21.330 --> 00:55:22.163
Okay.
1092
00:55:23.010 --> 00:55:25.413
This is where you would browse for the file.
1093
00:55:26.340 --> 00:55:27.690
I can go ahead and do that.
1094
00:55:29.850 --> 00:55:30.683
There you go.
1095
00:55:32.193 --> 00:55:33.483
Give it a nickname.
1096
00:55:39.510 --> 00:55:42.003
Selecting whether it's normal or In Flight.
1097
00:55:43.290 --> 00:55:46.083
Notice I am partner one, we'll say yes,
1098
00:55:47.460 --> 00:55:49.010
and then I would select upload.
1099
00:55:53.190 --> 00:55:55.800
Okay, so while we're waiting,
1100
00:55:55.800 --> 00:55:58.440
it will take, I believe it's every 30 seconds,
1101
00:55:58.440 --> 00:56:01.380
the job process and background will capture
1102
00:56:01.380 --> 00:56:03.333
and I can hit refresh here in a moment.
1103
00:56:04.218 --> 00:56:06.270
This is what the button looks like
1104
00:56:06.270 --> 00:56:10.590
to actually create a successfully-uploaded file.
1105
00:56:10.590 --> 00:56:13.773
You can click into each of these areas.
1106
00:56:14.760 --> 00:56:17.640
See, we have errors here, for example.
1107
00:56:17.640 --> 00:56:19.890
We can actually view the errors.
1108
00:56:19.890 --> 00:56:21.003
This is the errors.
1109
00:56:22.020 --> 00:56:23.677
If we go back up here, we could say,
1110
00:56:23.677 --> 00:56:27.600
"You know what? Partner two gave me an earful."
1111
00:56:27.600 --> 00:56:29.100
Let's just delete it and start over.
1112
00:56:29.100 --> 00:56:31.980
Let's remove the orders that I actually created.
1113
00:56:31.980 --> 00:56:36.540
This button is the export of the file that would be sent
1114
00:56:36.540 --> 00:56:40.426
to your trading partner via secure channels.
1115
00:56:40.426 --> 00:56:41.460
Okay?
1116
00:56:41.460 --> 00:56:43.230
And so it's saying In Progress,
1117
00:56:43.230 --> 00:56:45.750
let's click refresh and see what I got here.
1118
00:56:45.750 --> 00:56:48.930
Okay, so we have success here.
1119
00:56:48.930 --> 00:56:51.690
I'm noting the batch number.
1120
00:56:51.690 --> 00:56:54.840
You know, when we create an output file,
1121
00:56:54.840 --> 00:56:57.150
it creates an output file for us.
1122
00:56:57.150 --> 00:57:00.543
We will see that.
1123
00:57:01.470 --> 00:57:03.030
So we're gonna let it do that
1124
00:57:03.030 --> 00:57:04.530
and actually create the orders.
1125
00:57:04.530 --> 00:57:06.330
That's what it's doing.
1126
00:57:06.330 --> 00:57:09.333
I'm gonna go ahead and bring up the file that I used.
1127
00:57:11.700 --> 00:57:13.710
I designated, when partner one begins,
1128
00:57:13.710 --> 00:57:15.720
we don't know what the order number is.
1129
00:57:15.720 --> 00:57:18.210
You can put pretty much anything in here.
1130
00:57:18.210 --> 00:57:21.873
These two rows are referencing the same order.
1131
00:57:22.770 --> 00:57:24.630
These two rows are referencing the same order.
1132
00:57:24.630 --> 00:57:26.910
So I created a Schedule 1 and a Schedule 2
1133
00:57:26.910 --> 00:57:28.650
for each of these.
1134
00:57:28.650 --> 00:57:31.227
You'll see that hash has to be there,
1135
00:57:31.227 --> 00:57:32.610
and you know, there's other information
1136
00:57:32.610 --> 00:57:37.610
like, the first row must be on line four for example.
1137
00:57:39.060 --> 00:57:40.560
And I'm just gonna go across,
1138
00:57:40.560 --> 00:57:43.593
this has to be a valid GT&C that we're referencing.
1139
00:57:45.810 --> 00:57:47.400
We can tell you what each of these mean.
1140
00:57:47.400 --> 00:57:51.330
Like, this would be S for servicing or R for requesting.
1141
00:57:51.330 --> 00:57:54.540
Here's a date cell, right?
1142
00:57:54.540 --> 00:57:58.113
So I'm gonna right click on it and say Format Cells.
1143
00:57:59.910 --> 00:58:01.380
Bring this up so you can see it better.
1144
00:58:01.380 --> 00:58:03.120
This just says Custom.
1145
00:58:03.120 --> 00:58:05.400
Yeah, I mean I'd already formatted it, right?
1146
00:58:05.400 --> 00:58:09.930
But if it wasn't, then it would say General here
1147
00:58:09.930 --> 00:58:13.170
and then I would start typing double Ms, double Ds
1148
00:58:13.170 --> 00:58:15.273
and four Ys there.
1149
00:58:16.140 --> 00:58:18.513
Good news is, it does remember it per file.
1150
00:58:19.740 --> 00:58:22.170
I could even use the format painter
1151
00:58:22.170 --> 00:58:24.273
to do all of these at once.
1152
00:58:25.680 --> 00:58:27.660
I'm gonna just go across, okay?
1153
00:58:27.660 --> 00:58:28.650
There's a lot of columns
1154
00:58:28.650 --> 00:58:30.930
so I hope you have some patience for me and I apologize
1155
00:58:30.930 --> 00:58:32.550
but I want you to see this.
1156
00:58:32.550 --> 00:58:34.770
Here's my requesting ALC,
1157
00:58:34.770 --> 00:58:37.203
this requesting group has to be accurate.
1158
00:58:40.860 --> 00:58:42.960
And then we're just walking through
1159
00:58:42.960 --> 00:58:45.450
everything you probably are familiar with already
1160
00:58:45.450 --> 00:58:49.110
from creating an order.
1161
00:58:49.110 --> 00:58:53.280
Each of these fields, you're already being provided for
1162
00:58:53.280 --> 00:58:54.113
in the UI.
1163
00:58:55.065 --> 00:58:56.880
There's servicings ALC.
1164
00:58:56.880 --> 00:58:59.460
I'm using the same agency obviously, you know,
1165
00:58:59.460 --> 00:59:00.693
for my demonstration.
1166
00:59:04.500 --> 00:59:08.070
Advanced information cuz we are doing advance
1167
00:59:08.070 --> 00:59:08.973
in the schedule.
1168
00:59:12.053 --> 00:59:13.803
I want contact information,
1169
00:59:15.870 --> 00:59:17.973
funding information for requesting.
1170
00:59:20.790 --> 00:59:22.560
Again, dates.
1171
00:59:22.560 --> 00:59:24.750
Someone asked about date signing.
1172
00:59:24.750 --> 00:59:27.183
Approver dates has to be accurate.
1173
00:59:29.490 --> 00:59:31.560
Again, anytime I see dates,
1174
00:59:31.560 --> 00:59:33.653
I wanna make sure they're formatted right.
1175
00:59:36.030 --> 00:59:38.080
I'm trying to do this as fast as possible
1176
00:59:39.194 --> 00:59:40.860
so I don't make you fall asleep. I apologize.
1177
00:59:43.650 --> 00:59:44.823
Line numbers.
1178
00:59:46.890 --> 00:59:49.110
So here we have Schedule 1 and Schedule 2
1179
00:59:49.110 --> 00:59:51.210
for each of the lines.
1180
00:59:51.210 --> 00:59:52.830
If I wanted to have a second line,
1181
00:59:52.830 --> 00:59:54.030
we could do that there, right?
1182
00:59:54.030 --> 00:59:55.680
We can just change that to a two.
1183
00:59:58.800 --> 01:00:01.310
So like, cost...
1184
01:00:02.310 --> 01:00:05.040
And I don't know, when we go in to see the examples,
1185
01:00:05.040 --> 01:00:08.940
I purposely did a climbing scale so we can denote that.
1186
01:00:08.940 --> 01:00:10.590
Here's the AID.
1187
01:00:10.590 --> 01:00:11.760
Again, I would right click,
1188
01:00:11.760 --> 01:00:14.673
say Format Cells, select Custom.
1189
01:00:15.660 --> 01:00:17.970
Yep, I already have three zeros but if I didn't,
1190
01:00:17.970 --> 01:00:19.530
I would just type it in there.
1191
01:00:19.530 --> 01:00:21.393
It would say General perhaps.
1192
01:00:23.010 --> 01:00:24.330
Let's see if I can just show you an example
1193
01:00:24.330 --> 01:00:25.478
of what it would look like.
1194
01:00:25.478 --> 01:00:27.051
So if it was custom, see, it says General
1195
01:00:27.051 --> 01:00:29.490
and then I would just put in my zeros
1196
01:00:29.490 --> 01:00:31.233
or my placeholders and say Okay.
1197
01:00:34.470 --> 01:00:36.813
This is the infamous capitalized X.
1198
01:00:38.310 --> 01:00:40.920
The main, it is four characters.
1199
01:00:40.920 --> 01:00:42.990
Let's see if I actually formatted it.
1200
01:00:42.990 --> 01:00:45.630
Again, it's not required cuz I was successful.
1201
01:00:45.630 --> 01:00:47.223
Yep, we did do that.
1202
01:00:48.390 --> 01:00:51.483
SUB. Again, three characters for the SUB.
1203
01:00:52.740 --> 01:00:54.480
And here's your object class code.
1204
01:00:54.480 --> 01:00:59.400
I'll go ahead and select Format Cells, Custom
1205
01:00:59.400 --> 01:01:01.980
and what we would wanna put here
1206
01:01:01.980 --> 01:01:03.873
is like that.
1207
01:01:06.000 --> 01:01:08.213
Just to make sure we have the proper placeholders.
1208
01:01:10.290 --> 01:01:13.350
Bona Fide Need is provided for requesting, and yeah,
1209
01:01:13.350 --> 01:01:16.500
requesting could have provided that on their own
1210
01:01:16.500 --> 01:01:18.630
when they do their upload.
1211
01:01:18.630 --> 01:01:20.040
Okay.
1212
01:01:20.040 --> 01:01:21.450
All right.
1213
01:01:21.450 --> 01:01:23.103
And then I would do file.
1214
01:01:24.420 --> 01:01:27.540
Sorry, File, Save As,
1215
01:01:27.540 --> 01:01:29.640
I wanna make sure it's a csv file
1216
01:01:29.640 --> 01:01:32.793
or the system won't accept it.
1217
01:01:34.230 --> 01:01:35.643
So let's see how we did.
1218
01:01:37.500 --> 01:01:39.780
So I click in here, right?
1219
01:01:39.780 --> 01:01:40.860
I want you to see that.
1220
01:01:40.860 --> 01:01:44.280
So watch how things, on this side, change
1221
01:01:44.280 --> 01:01:47.373
as I click into the selection of the file.
1222
01:01:50.250 --> 01:01:53.580
Again, I can delete this or I can send this file
1223
01:01:53.580 --> 01:01:54.680
to my trading partner.
1224
01:01:55.950 --> 01:01:58.983
My trading partner, requesting in this case,
1225
01:01:59.850 --> 01:02:02.163
will need to format this.
1226
01:02:04.080 --> 01:02:08.660
And these are the actual orders that the system created for,
1227
01:02:08.660 --> 01:02:11.283
so we don't want partner two changing these.
1228
01:02:12.750 --> 01:02:15.870
I am gonna have to format this so I hope you have patience.
1229
01:02:15.870 --> 01:02:17.760
It won't take me a minute,
1230
01:02:17.760 --> 01:02:20.400
but you get to see me to do it firsthand.
1231
01:02:20.400 --> 01:02:21.303
See here's the Ms.
1232
01:02:23.520 --> 01:02:24.363
Ds.
1233
01:02:25.568 --> 01:02:26.401
Say Okay.
1234
01:02:28.290 --> 01:02:30.360
And I'm gonna go really quickly.
1235
01:02:30.360 --> 01:02:35.360
This is information that would enable requesting
1236
01:02:35.730 --> 01:02:38.280
to find the order if they didn't look
1237
01:02:38.280 --> 01:02:40.380
for the order numbers to the left.
1238
01:02:40.380 --> 01:02:42.153
This is put in for the tracking number.
1239
01:02:42.153 --> 01:02:45.850
This is the batch number that servicing used
1240
01:02:46.782 --> 01:02:48.270
that was created.
1241
01:02:48.270 --> 01:02:50.610
Let's see if we can show you that.
1242
01:02:50.610 --> 01:02:52.413
Yep, Batch 298.
1243
01:02:59.614 --> 01:03:02.486
Okay, I got a little more work to do here.
1244
01:03:02.486 --> 01:03:04.260
I have to update the TAS information
1245
01:03:04.260 --> 01:03:07.053
and so I'm just gonna go across here.
1246
01:03:15.180 --> 01:03:16.764
Because I've done it before in this file,
1247
01:03:16.764 --> 01:03:20.163
I know it's at the bottom so I'm just saving myself a step.
1248
01:03:31.110 --> 01:03:32.550
And I would underscore for you, Andrew,
1249
01:03:32.550 --> 01:03:37.320
that yes, once you've exported this file, the SB2 orders,
1250
01:03:37.320 --> 01:03:40.170
you don't want to mess with that order number.
1251
01:03:40.170 --> 01:03:42.390
That's the new SB2 order number that was created,
1252
01:03:42.390 --> 01:03:44.040
that is the number that we'll use
1253
01:03:44.040 --> 01:03:46.800
to connect the partner two file with the partner one file.
1254
01:03:46.800 --> 01:03:48.600
So yes, leave those, those are good.
1255
01:03:48.600 --> 01:03:50.220
That's supposed to assist partner two
1256
01:03:50.220 --> 01:03:51.717
making it easier for them to upload.
1257
01:03:51.717 --> 01:03:55.230
And then also, that batch number that you mentioned, Andrew,
1258
01:03:55.230 --> 01:03:58.560
it's good for both partner one and partner two to use
1259
01:03:58.560 --> 01:04:00.690
to find those files in their order list,
1260
01:04:00.690 --> 01:04:02.400
to find those SB2s because by then,
1261
01:04:02.400 --> 01:04:05.010
partner two will have access to see those files
1262
01:04:05.010 --> 01:04:06.270
in their order list as well.
1263
01:04:06.270 --> 01:04:08.580
So that batch number was pretty helpful.
1264
01:04:08.580 --> 01:04:09.630
Thank you.
1265
01:04:10.680 --> 01:04:12.580
Okay, so I'm doing your requesting AID
1266
01:04:13.740 --> 01:04:15.360
and now I'm gonna just make sure
1267
01:04:15.360 --> 01:04:17.640
it's got three placeholders there.
1268
01:04:17.640 --> 01:04:19.710
Capital X, I'm happy with.
1269
01:04:19.710 --> 01:04:21.210
Don't have to really do the main
1270
01:04:21.210 --> 01:04:22.740
because it is four characters.
1271
01:04:22.740 --> 01:04:23.610
I knew that already,
1272
01:04:23.610 --> 01:04:27.873
but let's just make the demos solid for you,
1273
01:04:31.374 --> 01:04:34.020
Okay? And I'm gonna have to make a placeholder here
1274
01:04:34.020 --> 01:04:36.813
for three characters for the SUB.
1275
01:04:42.090 --> 01:04:45.630
This is already provided for me, but you know, again,
1276
01:04:45.630 --> 01:04:48.663
I'm just trying to make sure you get the full demo here.
1277
01:04:50.100 --> 01:04:50.933
Yeah.
1278
01:04:52.950 --> 01:04:55.320
Okay, I believe we're done.
1279
01:04:55.320 --> 01:04:59.613
I'm not gonna enter the PPQ here today.
1280
01:05:00.630 --> 01:05:03.240
I'm gonna do that manually.
1281
01:05:03.240 --> 01:05:05.373
So then I File, Save As.
1282
01:05:07.794 --> 01:05:08.673
Ugh, yep.
1283
01:05:09.810 --> 01:05:12.063
Pardon me while I do a little homework here.
1284
01:05:12.990 --> 01:05:14.760
Save this file.
1285
01:05:14.760 --> 01:05:17.700
Okay, so I saved the file, it's a csv.
1286
01:05:17.700 --> 01:05:19.500
Now I'm gonna go over to Requesting,
1287
01:05:20.910 --> 01:05:21.843
Order Upload.
1288
01:05:24.870 --> 01:05:26.733
Again, I'll browse for the file.
1289
01:05:30.109 --> 01:05:30.942
I'll move it out here
1290
01:05:30.942 --> 01:05:32.810
to make sure I can find it for you very quickly.
1291
01:05:34.140 --> 01:05:39.093
Nickname and you could put the batch in there, right?
1292
01:05:40.740 --> 01:05:41.580
But I just wanna mention,
1293
01:05:41.580 --> 01:05:46.580
some folks actually like to use as an alternative...
1294
01:05:46.800 --> 01:05:48.100
Lemme just go to tracking.
1295
01:05:54.210 --> 01:05:55.710
We've had discussions internally
1296
01:05:55.710 --> 01:05:59.640
about how some agencies want to utilize this
1297
01:05:59.640 --> 01:06:01.500
for other purposes.
1298
01:06:01.500 --> 01:06:04.500
Perhaps their ERP notations or something like that.
1299
01:06:04.500 --> 01:06:05.583
You can do that.
1300
01:06:07.935 --> 01:06:08.910
For my demonstration, at a minimum,
1301
01:06:08.910 --> 01:06:11.970
wanna make sure that I can find the file.
1302
01:06:11.970 --> 01:06:13.770
We can go and look at the order number
1303
01:06:13.770 --> 01:06:17.610
that the file gives to us from partnering one.
1304
01:06:17.610 --> 01:06:20.040
And I think...
1305
01:06:20.040 --> 01:06:21.630
Yep, I did.
1306
01:06:21.630 --> 01:06:24.570
It's very easy to hit yes here
1307
01:06:24.570 --> 01:06:27.570
for requesting for the partner two.
1308
01:06:27.570 --> 01:06:29.040
You gotta make sure to say no
1309
01:06:29.040 --> 01:06:30.240
or you're gonna get an error.
1310
01:06:30.240 --> 01:06:33.027
And that's why I went back and redid it. Okay?
1311
01:06:33.027 --> 01:06:36.963
I'm gonna do In Flight, no on partner two.
1312
01:06:38.190 --> 01:06:39.303
Hit Upload.
1313
01:06:41.280 --> 01:06:43.730
Okay? And now we're gonna wait here for a moment.
1314
01:06:45.270 --> 01:06:46.683
For 30 seconds.
1315
01:06:49.080 --> 01:06:51.210
While you wait, can I ask you a quick question?
1316
01:06:51.210 --> 01:06:52.830
Feel free.
1317
01:06:52.830 --> 01:06:54.750
Back to the file
1318
01:06:54.750 --> 01:06:57.420
where the system generated the order numbers.
1319
01:06:57.420 --> 01:07:01.316
What again was it that told the system that,
1320
01:07:01.316 --> 01:07:03.780
"Hey, these two lines are supposed to be
1321
01:07:03.780 --> 01:07:05.970
the same order number?"
1322
01:07:05.970 --> 01:07:09.650
When I created the original file...
1323
01:07:10.500 --> 01:07:12.983
Lemme see if I can bring up the original file for you.
1324
01:07:15.339 --> 01:07:16.470
When I created the original file,
1325
01:07:16.470 --> 01:07:21.470
I actually indicate unique information per row.
1326
01:07:22.710 --> 01:07:24.180
See I did it that way.
1327
01:07:24.180 --> 01:07:28.320
You could do it As and Bs, my understanding,
1328
01:07:28.320 --> 01:07:30.510
but this makes the most sense for me.
1329
01:07:30.510 --> 01:07:32.580
Right?
Okay. Okay.
1330
01:07:32.580 --> 01:07:35.293
So it's not the line or the schedule
1331
01:07:35.293 --> 01:07:37.560
and it's not anything like that.
1332
01:07:37.560 --> 01:07:40.653
It's what you're entering in column A.
1333
01:07:41.610 --> 01:07:43.023
Correct. Agreed.
Okay.
1334
01:07:45.000 --> 01:07:46.680
Thank you.
Yeah. Now...
1335
01:07:46.680 --> 01:07:48.630
And what Denise mentioned
1336
01:07:48.630 --> 01:07:51.450
is partner two should never mess with this
1337
01:07:51.450 --> 01:07:53.370
or you're gonna have a mess, right?
1338
01:07:53.370 --> 01:07:55.223
You'll get errors and it just won't work.
1339
01:07:56.381 --> 01:07:57.883
What would be the effect
1340
01:07:57.883 --> 01:07:59.220
if we locked those cells?
1341
01:07:59.220 --> 01:08:03.270
I don't even know if you can do that in csv files actually.
1342
01:08:03.270 --> 01:08:04.520
Can you lock those cells?
1343
01:08:05.954 --> 01:08:07.254
Probably not.
Not sure.
1344
01:08:08.220 --> 01:08:11.190
I'm not sure your thought process would be honestly.
1345
01:08:11.190 --> 01:08:12.540
You're saying, oh, it's just so partner two
1346
01:08:12.540 --> 01:08:13.810
never can mess with the
1347
01:08:13.810 --> 01:08:16.024
order numbers themselves.
Yeah.
1348
01:08:16.024 --> 01:08:18.600
I've never tried it for csv files.
1349
01:08:18.600 --> 01:08:21.360
It's a good point. Something worth trying.
1350
01:08:21.360 --> 01:08:24.558
No guarantees that'll work though, right? (laughing)
1351
01:08:24.558 --> 01:08:26.310
Let's just say that. I will say that.
1352
01:08:26.310 --> 01:08:28.890
So I am requesting, I am partner two.
1353
01:08:28.890 --> 01:08:33.120
I went through and received the file via secure channel.
1354
01:08:33.120 --> 01:08:35.310
I did the upload and now
1355
01:08:35.310 --> 01:08:37.740
it looks like it completed successfully
1356
01:08:37.740 --> 01:08:41.610
and now it's actually updating the information
1357
01:08:41.610 --> 01:08:43.083
from the partner two side.
1358
01:08:53.820 --> 01:08:55.143
Please stand by.
1359
01:08:57.330 --> 01:08:58.730
Shouldn't take but a minute.
1360
01:09:00.480 --> 01:09:03.000
And of course if you have larger orders, you know,
1361
01:09:03.000 --> 01:09:05.430
large number of orders, it's gonna take longer.
1362
01:09:05.430 --> 01:09:08.230
Two orders with two Schedule 2s is pretty quick usually.
1363
01:09:12.960 --> 01:09:16.350
Okay. Yeah, I'm getting a couple...
1364
01:09:16.350 --> 01:09:19.140
These are errors you probably will never see.
1365
01:09:19.140 --> 01:09:20.310
We haven't even received them.
1366
01:09:20.310 --> 01:09:22.410
These are internal to the system errors.
1367
01:09:22.410 --> 01:09:25.530
It did say the order completed successfully,
1368
01:09:25.530 --> 01:09:27.570
which I am not surprised about.
1369
01:09:27.570 --> 01:09:29.430
We've been very successful.
1370
01:09:29.430 --> 01:09:33.630
Batch 289 is the nickname I added just for my edification
1371
01:09:33.630 --> 01:09:35.422
so I can go find that file.
1372
01:09:35.422 --> 01:09:36.990
Let me show you something here.
1373
01:09:36.990 --> 01:09:38.790
I could find it by the order number.
1374
01:09:38.790 --> 01:09:41.160
I'm sure you're thinking that and I would agree.
1375
01:09:41.160 --> 01:09:44.250
But you can also, if you left that information there,
1376
01:09:44.250 --> 01:09:47.430
you can also go to order-requesting tracking information
1377
01:09:47.430 --> 01:09:52.430
and there's 298, 2 different orders.
1378
01:09:52.530 --> 01:09:54.680
I'm gonna look at each one of them for you.
1379
01:09:56.389 --> 01:10:00.603
There's two schedules as I had pointed out, right?
1380
01:10:02.940 --> 01:10:05.700
This is 30 and the next one is 20.
1381
01:10:05.700 --> 01:10:08.760
So when I open the other one, it'll be 40 and 50 there.
1382
01:10:08.760 --> 01:10:11.580
We did allow for advanced pay,
1383
01:10:11.580 --> 01:10:13.800
so I will be able to do a advanced PPQ
1384
01:10:13.800 --> 01:10:16.050
on one of these here in a moment.
1385
01:10:16.050 --> 01:10:20.793
I'm gonna go back to the order, go find the other one.
1386
01:10:22.722 --> 01:10:23.986
Lemme see. Did I do that wrong?
1387
01:10:23.986 --> 01:10:24.819
Let's see. Oh, yep.
1388
01:10:24.819 --> 01:10:27.030
This is 40 and I'm looking at the quantities.
1389
01:10:27.030 --> 01:10:31.323
That's 50 and that's 40. I did 50, 40, 30, 20.
1390
01:10:32.670 --> 01:10:35.820
And the order is open
1391
01:10:35.820 --> 01:10:40.290
so both agencies approved in the file successfully.
1392
01:10:40.290 --> 01:10:41.490
You can actually look at...
1393
01:10:41.490 --> 01:10:43.950
Yeah, that doesn't really help you much cuz it's all me,
1394
01:10:43.950 --> 01:10:46.950
but still, you can see it's there.
1395
01:10:46.950 --> 01:10:50.095
I'm gonna now go over to servicing,
1396
01:10:50.095 --> 01:10:51.480
I'm gonna grab this order number.
1397
01:10:51.480 --> 01:10:54.022
Just gonna finish it off for you.
1398
01:10:54.022 --> 01:10:55.563
Go find the order.
1399
01:10:59.130 --> 01:11:01.143
Show performance as servicing.
1400
01:11:02.190 --> 01:11:04.940
There's the two schedules that were created via a file.
1401
01:11:06.540 --> 01:11:07.593
It is in flight.
1402
01:11:10.860 --> 01:11:12.510
Again, I know I did this for you once,
1403
01:11:12.510 --> 01:11:14.700
but let's just do it for this file.
1404
01:11:14.700 --> 01:11:18.810
And let's not forget, right, training helps.
1405
01:11:18.810 --> 01:11:20.490
Gonna have to train your folks, right?
1406
01:11:20.490 --> 01:11:23.463
It's not gonna be blaring at your users to check the box.
1407
01:11:25.020 --> 01:11:28.920
And if it was only a partial, we could just do 2,000.
1408
01:11:28.920 --> 01:11:30.470
Don't know if you noticed that.
1409
01:11:31.530 --> 01:11:32.780
And then I'll say create.
1410
01:11:35.220 --> 01:11:37.020
So the key to me is looking there
1411
01:11:37.020 --> 01:11:40.020
and seeing previously settled as the status.
1412
01:11:40.020 --> 01:11:44.100
I know successfully doing a removal
1413
01:11:44.100 --> 01:11:47.793
of fiscal available for this order and not creating an IPAC.
1414
01:11:52.650 --> 01:11:57.510
Okay, I'll just ask if there's any questions
1415
01:11:57.510 --> 01:11:59.197
or anything at all that we can provide to you here.
1416
01:11:59.197 --> 01:12:03.837
You know, we went through the requirements,
1417
01:12:03.837 --> 01:12:07.440
the feature management, using the UI for In Flight Order,
1418
01:12:07.440 --> 01:12:10.200
dropdown and creating an advanced PPQ,
1419
01:12:10.200 --> 01:12:12.656
and then using the bulk uploads.
1420
01:12:12.656 --> 01:12:17.100
We wanna make sure you know that 5.0 webinars
1421
01:12:17.100 --> 01:12:21.690
are now available for your users to register for
1422
01:12:21.690 --> 01:12:23.133
beginning in February.
1423
01:12:25.410 --> 01:12:26.460
Yep.
1424
01:12:26.460 --> 01:12:29.521
Want to thank Treasury for being on the call today
1425
01:12:29.521 --> 01:12:32.760
and of course, you can always ask questions directly
1426
01:12:32.760 --> 01:12:34.110
of the Treasury Department.
1427
01:12:35.190 --> 01:12:38.880
This is the program team from the Treasury for G-Invoicing
1428
01:12:38.880 --> 01:12:40.260
and my team.
1429
01:12:40.260 --> 01:12:43.920
My name is Andrew Zeff. I work for Robert Mattison.
1430
01:12:43.920 --> 01:12:47.250
We're part of the Agency Onboarding and Implementation team,
1431
01:12:47.250 --> 01:12:48.517
AIT from FRB.