Welcome to the SAPHANA Academy. My name's Bob and in this video series from the SAP HANA Academy
and Digital Partner Engineering we'll be looking at SAP Fieldglass integration /
In this video we're going to be looking at editing one of our connectors to look at
the various options available to us . In the previous few videos we've been looking at
enabling integration connectors. Now in the next few videos what we're going to be doing is
creating a job posting using one of these connectors.
Documentation s widely available within help.sap.com. If i go back to SAP Fieldglass integration,
what we'll see is we've got a document called the SAP Fieldglass Connector .
If i open that link, the see documentation on all the default connectors which exist within SAP Fieldglass.
I'm going to show you a variant of one of the connectors which i've already created
based on job posting uploads, so i'll do a search for that because the API or connector is very
much the same as what I've created. Again if i expand the search menu on the left hand side
we'll be able to see all the possible connectors that are available to us. Within this document
there's lots of information available.
But on the right hand side, if i click on the search glass and then select "job posting upload"
will have detailed documentation on that specific connector. The first thing you'll notice
is that the data format that SAP Fieldglass accepts is in csv formats for this job posting upload.
But in our example we're going to submit in json format so for a partner to send data in json
format what they'll need to do is ask their SAP Fieldglass support contact to set preprocessors for json format for that specific API.
This can only be done by SAP Fieldglass administration at this time.
Adding these preprocessors will convert the json data into csv format or whatever SAPFieldglass accepts.
The documentation is split into separate sections.
Firstly you have an overview of the connector which details the format prerequisites, second you've got a section called
configuration considerations, you've also got some assumptions and tips on using this connector
which will help you when using the various parameters within the connector . Lastly you've
got a section called file formatting which details every component within the connector. It will also
indicate if that field is required or is optional. So you can see here you've got the component
column, the required column, you've also got notes that will also help you configure those columns
as well as documentation concerning the headers. You've also got documentation concerning the
detail objects as well. So here you can see we've got the same things: you've got the data type,
you've got an indicator if the column is required, the column name, so on and so forth. Again each of these
connectors has this type of documentation . for both the header and detail columns.
It's quite comprehensive and it's all contained within this single connector library document.
Now that we've looked at that API documentation, what we'll do is look at one of those APIs.
If i go to the enable integration connection wizard, we'll look at setting up that connector.
For the next few videos, we're going to be looking at job postings So if i scroll down, we'll select "job posting" and if i select
"select" -- what you'll notice is that in this example, we don't have a series of stepwise questions.
Some of the connectors don't have those questions . What you'll see is a list of all the possible connectors.
Now I've already set up this connector so if i scroll down we seet a variant, or what you could call
a copy of an existing connector. i've called it jobposting_upload .i've already enabled it and i'm just going to show you some
of the key features within this connector. Of course you've got the details of the connector on the left hand side,
additionally you've got some setup options on the right hand side to do with things like
delimiters, and if i scroll to the bottom you can see within client internal integration that the
transfer method will be SOAP and we've also got some connection header settings as well.
You can see things like we've got the number formats where we have numbers or dates, and we also
have specific options such as transaction -- which helps you determine how record errors are handled.
Quite simply "true "means if there are any record errors, then the entire upload fails
and as you can imagine "false" means that only records that are in the error fail , while remaining records are
committed successfully. You've also got other options such as approval required -- which as you
can imagine determines if objects are required to go through an approval process. You've also
got comments where you can include a comment field containing text notes about the upload file.
In the second tab we have our upload column transform options, so in this simple example we've got
two columns. We've got a business unit code where we've transformed the name of the column
and we've also got an address column where we've combined some address details in one single column.
The next tab has to do with connectivity -- so as we know we looked at this in the previous video --
this details our various users and the various licenses. Again, in the next
video within postman we're going to be using this API user and license.
There's a couple more interesting tabs: the integration audit trail
displays the status and activity details of connect to upload and download processing.
Here, you can see when the API or connector was hit and the timer was hit and if there's any major issues.
As you can imagine the modification log details when the the connector was actually modified,
and by which user. Of course the other option is to edit this connector.
Just to show you those options, this is one that's already been created so we're modifying. Of course
you can do things like change the name, you can also change the version, the integration system,
we can also change our delimiting options (i didn't set any here)
and also if we've set any encoding options (but i've got nothing to change)
We've got our header values in terms of our numbers and dates nothing to change here.
Here we've got security we looked at this in the last video nothing to change
Here we come to the columns that we might want to transform so again we've got those two columns the
business unit code and the address which has been combined into one column. Nothing really to change
here, although we could of course delete it. Lastly we've got the connectivity which again is that SAP
Fieldglass SOAP web service. And that's it. We're lastly presented with that license key and
the user that we're going to be using in postman . When i go to the next step, we've actually
finished. There's nothing here to change . We've completed the nine out of the nine required items.
The only thing i want to mention here is we can enable or disable these connectors. This one at the moment
is enabled and in terms of actions what we can do if we want is to create variants or copies
of our connectors to connect to different systems, or if we want to have different versions
of our connectors. Now that we've looked at setting up our connectors within our integration
tools, we've got our connector ready to be used . What we're going to be doing in the next video
is actually deal with authentication and accessing our connectors via postman. We'll firstly
need to deal with authentication and so we can send a post to SAP Fieldglass. And then when we've
authenticated correctly, we'll be able to create a job posting using that connector from postman.