What am I trying to achieve?
Call SuccessFactors Compound Employee API (CEAPI) with ABAP and store certain data of an employee to fulfil a business need. It has to be CE API and not ODATA.
How am I doing this?
I'm using CL_HTTP_ CLIENT to make...
Introduction
When SAP HCM customers move to SuccessFactors Employee Central (EC) for global HR purposes, they break their core HR process of Hire to Pay into two systems. The process now becomes "Hire in EC" and "Pay in SAP HCM". An employee hired in...
Introduction:
Customers choose SuccessFactors Employee Central, EC from hereon, for a myriad of reasons. The most common amongst those is the creation of a Global HR system. Global HR system creates the necessary boundary between HR functions and non...
ada62dbc143d47dcaa7496633e62ca2c You're right in your observation - this offers nothing new vis-a-vis what's already covered in the standard documentation. What it is, is a commentary on the design aspects, its incremental refinement over years and t...
Ok, now that makes sense. Now this is a network issue. If the URL is not a public URL, then your ABAP system (the client) must somehow "see" this URL. You got to do this either by exposing the URL via a proxy that's accessible to you e.g. SAP Cloud C...
SOAMANAGER is your transaction to get your WSDL, endpoint url and the likes. If you’re looking for the RFC around which the web service is built, the endpoint already provides some hints - e.g. the name of the web service. Use that and head to SE37. ...
Figured this out finally.Instead of setting the cookie as a header, set the cookie as a cookie.Beats me because cookie is also a HTTP header.Anyway, this is how it works in ABAP.* Cookie in header
* gv_sessionid = 'JSESSIONID=2232312321321123123.oioj...
