Though the initial details as to how to make the SFAPI call etc. have been covered in the earlier course titled "SAP Successfactors Odata and SFAPI API-How to work with them". I have still went ahead and added this lecture here for the benefit of students. However, if any additional details over SFAPI basics and other operations including OData , students are highly encouraged to refer the exclusive course "SAP Successfactors Odata and SFAPI API-How to work with them". This has been placed here for the benefit of the students, however if they want to get into more details and basics of operations of SFAPI other than Compound Employee , the earlier course is recommended. 

In this lecture, we will understand how to download and install the SOAP UI tool, which will be used to execute various web service calls to SAP Successfactors.

Though the initial details as to how to make the SFAPI call etc. have been covered in the earlier course titled "SAP Successfactors Odata and SFAPI API-How to work with them". I have still went ahead and added this lecture here for the benefit of students. However, if any additional details over SFAPI basics and other operations including OData , students are highly encouraged to refer the exclusive course "SAP Successfactors Odata and SFAPI API-How to work with them".

Here in we will see how to enable the calling from SOAP UI to Successfactors in view of the disablement of the TLS (Transport Layer Security) v1.0; else you might experience SSL handshake exception when communicating with Successfactors from SOAP UI.

Also please note if the link as provided as resource to this lecture is not getting open by clicking here; please search for note 2461964 over the net , it would be available there as it is a public SAP note so is available free to be accessed.

Though the initial details as to how to make the SFAPI call etc. have been covered in the earlier course titled "SAP Successfactors Odata and SFAPI API-How to work with them". I have still went ahead and added this lecture here from my previous course for the benefit of students as to get know how on how to execute SFAPI calls to Successfactors. Still if additional details related to SFAPI operations other than Compound Employee are needed please refer the earlier course which covers information about SFAPI and OData in more exquisite details.

This session is just to provide the input that the structure of the response of the CE API may change as per the processing parameters passed to it. This session is mainly for the people who are from the coding background and want to integrate CE API via the traditional stub / skeleton approach to know that here the output might not be a fixed structure.

The structure of the response of the Compound Employee API might change as per the input processing parameters those are passed to the CE API. This is a practical demonstration of the above argument.

Here, we will do the practical session as to how to gather the Compound Employee Metadata , what are all the steps to gather the metadata. This is completely hands-on session with some conceptual points also discussed. Please do not miss this session.

We will have a look at the login , list, describe and describeEx operation calls to the Successfactors instance and also understand the output returned.

Here, we will explore the request structure of the Compound Employee API and will understand its various sub-components Select, From, Where, Processing Parameters. And will also see how it does relate to the CE API metadata that we gathered in the previous section.

Here, we will understand how the select clause of the Compound Employee can be constructed. We will also get a taste of how the various segments show up in the compound employee API response.

This session has the downloadable excel sheet that we discussed upon in the previous session.

Here, based on the understanding built so far over the Select Clause we will execute some of the queries over Compound Employee.

Here we will discuss over how to iterate over the results obtained via Compound Employee API to get all the results.

Here, we will discuss over how the where clause for Compound Employee API is constructed and what all parameters can be specified here.

Here, we will take a short detour to discuss the order by clause. What all parameters are supported to be placed in the order by clause.

Here, we discuss about the isContingentworker parameter , its objective and will also seek over various executions its significance.

Here, we will have a look over couple of these fields person_id and per_person_uuid and how it affects the CE API response.

Here, we will look at the select parameters company and company_territory_code and along with its behavior as a select parameter we will also see how the valid values to be placed for these parameters can be gathered in Successfactors.

Here, we will look at the select parameters employee_class and department and along with its behavior as a select parameter we will also see how the valid values to be placed for these parameters can be gathered in Successfactors.

Here, we will look at the select parameters division and compensation_pay_group and along with its behavior as a select parameter we will also see how the valid values to be placed for these parameters can be gathered in Successfactors.

Here, we will look at the select parameters business_unit and location and along with its behavior as a select parameter we will also see how the valid values to be placed for these parameters can be gathered in Successfactors.

Here, we will look at the select parameter job_code and along with its behavior as a select parameter we will also see how the valid values to be placed for this parameter can be gathered in Successfactors.

Here, we will discuss over the selectFrom and selectTo select parameters ,will understand the format they can be applied in and how they affect the CE output.

Here, we will get into more conceptual level to understand the selectFromDate and selectToDate  where clause parameters more closely.

Herein, we will discuss over the select parameter snapshot_date , its significance and other logistics over like what are the supported operators, format of the value in which can be provided to snapshot_date parameter and the processing parameter needed to run this CE query.

Here, we will strive to gather more clarity on the snapshot_date and will look for the various queries executed from snapshot_date.

Here, we will look for another select parameter 'Effective_End_Date' which indeed works as a filter rather than a select condition, and we will see how its behavior levy an impact on the response of CE.

Here, we will look at the various dimensions of the last_modified_on parameter : format, supported operators and concept.

Please note here we are discussing over the last_modified_on without placing any processing parameters. Last_modified_on behavior during the delta transmission mode is discussed in further details later down in the course.

Here, we will look further to some more concepts related to the last_modified_on parameter.

Please note here we are discussing over the last_modified_on without placing any processing parameters. Last_modified_on behavior during the delta transmission mode is discussed in further details later down in the course.

Here, we will look at the various dimensions of the start_date parameter : format, supported operators and concept.

We will also discuss whether it is supported for query modes other than full transmission.

Here, we will discuss further on some of the additional concepts of the start_date parameter.

Here, we will try to appreciate the start_date even more and will compare it with the last_modified_on for one of the use case.

Here we will do a comparative study of 3 dates : Start_Date , Effective_End_Date and Last_modified_on and will try to revise and also enhance our understanding of execution of these select parameters

Here we will do a comparative study of 3 dates : Start_Date , Effective_End_Date and Last_modified_on and will try to revise and also enhance our understanding of execution of these select parameters

Attached xls file here compares the various select parameters those can be placed in the CE query where clause. It enlists the following parameters: SelectFromDate, SNAPSHOT_DATE, EFFECTIVE_END_DATE, Last_modified_on, START_DATE, fromDate..toDate

Herein, we will have an overview over what all URN parameters we are going to discuss in the upcoming sessions.

Herein, we will discuss as to how maxRows alter the behavior of the response returned from the CE Query.

Here, we will have a look over the startingRow parameter and its impact on CE query output.

Here, we will have a look over the externalKeyMapping parameter and its impact on CE query output.

Here, we will see how URN parameter resultOptions levy an impact on the output. What all values are supported for the resultOptions, i.e. we will have an overview over the objective and supported values by this URN parameter.

We will also discuss in this session one of the value supported by resultOptions and that is allJobChangesPerDay.

We will discuss in this session two of the values supported by the resultOptions URN parameter allCompensationChangesPerDay and configuredFieldsOnly

Here, we will see how and when to provide more than one value for the same urn parameter resultOptions.

Here, we will introduce the segmentsForEnhancedEffectiveEndDateFilter and also understand one of the values it can have.

Here, we will have a look at another value of the segmentsForEnhancedEffectiveEndDateFilter and its significance.

Here, we will look at yet another urn parameter and that is segmentsForCompleteness and try to understand its significance.

Here, we will understand the ways that are available from Successfactors to meter various API calls / records out from the cloud and also to see the audit logs of the calls been made to Successfactors.