3001960 - Recruiter field from JobRequisition query in SuccessFactors not available in SAP Analytics Cloud (SAC)

• Build the query with relevant fields like "recruiter" are not available from "JobRequisition" query in SAC.

• SAP Analytics Cloud (Enterprise)
• SAP SuccessFactors

1. Login to SAC.
2. Go to Modeler.
3. Create a model from Data Source.
4. Select import connection type: SAP SuccessFactors
5. Select RCM- Job Requisition > JobRequisition.
6. Try to build the query with relevant fields e.g. "recruiter" and observe not all fields are available.
7. However, if you select the JobRequisitionOperator, the "recruiter" field is available.

• Product limitation.
• Detailed explanation:

It turns out that JobRequisition -> Recruiter is a one-to-many relationship and is defined as such in the metadata. The entry for the recruiter nav property is

<NavigationProperty Name="recruiter" sap:required="false" sap:creatable="true" sap:updatable="true" sap:upsertable="true" sap:visible="true" sap:sortable="true" sap:filterable="true" Relationship="SFOData.RcmJobReq_Operator_recruiter" FromRole="JobRequisition" ToRole="JobRequisitionOperator" sap:field-control="jobReqPermissionsNav/recruiter" sap:label="Recruiter"></NavigationProperty>

This tells us where to look for details about the relationship between JobRequisition and JobRequisitionOperator (which is actually describing the relationship to recruiter) in the bolded bit.
Looking at that relationship in the metadata:

      <Association Name="RcmJobReq_Operator_recruiter">
        <End Type="SFOData.JobRequisition" Multiplicity="1" Role="JobRequisition"></End>
        <End Type="SFOData.JobRequisitionOperator" Multiplicity="*" Role="JobRequisitionOperator"></End>
      </Association>

What this means is that for each Job Req, we run the risk of returning more than one recruiter value (even if in practice there's just the one). This leads to ambiguity in the wrangling/modeling area and is not supported per help guide "Import Data Connection to OData Service"

While OData exposes one-to-many navigation, SAP Analytics Cloud cannot follow these relationships because doing so would distort the measures at the parent level.

The workaround suggested is that we access it the other way around. That is, from JobRequisitionOperator, we expand to JobRequisition and we're able to get recruiter values that way. This is the general workaround for 1-* relationships; access data from the many side instead of the one. From memory, that was not providing the exact values you were after, though, so this may be a disappointing conclusion.

• An enhancement request is already opened for the topic: Fields defined as picklist are not being pulled in SAC
• Please, review and vote for it, that you wish to support and plan to take advantage of in your organization. Note: You will be notified on updates regarding ideas you have voted for.
• For more details please, see KBA 2424376 - How to create an enhancement request for SAP Analytics Cloud?

This document and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.

This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

• 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
• Have a question? Ask it here and let our amazing SAP community help! Or reply and share your knowledge!
• 2487011 - What information do I need to provide when opening an incident for SAP Analytics Cloud?
• 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
• Search for SAP Analytics Cloud content using Google or Bing:
• https://www.google.ca/search?q=site%3Ahttps%3A%2F%2Fapps.support.sap.com+SAP+Analytics+Cloud
• https://www.bing.com/search?q=site%3Ahttps%3A%2F%2Fapps.support.sap.com+SAP+Analytics+Cloud
• Note: Add relevant text or warning/error messages to the text search field to filter results.
• SAP Analytics Cloud > Learning > Data Connections
• SAP Analytics Cloud > Learning > Guided Playlists
• SAP Analytics Cloud > Learning > Guided Playlists > Getting Support
• Need More Help? Contact Support or visit the solution finder today!

Your feedback is important to help us improve our knowledge base.

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud, https://hcs.cloud.sap, https://hanacloudservices.cloud.sap, https://cloudanalytics.accounts.ondemand.com, https://hanacloudservices-us.accounts.ondemand.com, https://www.sap.com, https://help.sap.com, predictive analytics (analysis), data analysis (analytics) tools, analytics tools, sap analytics cloud, data literacy, advanced analytics, data democratization, analytics software, real time analytics, self service analytics, advanced data analytics, analytics as a service, analytics cloud / cloud analytics, saas analytics, cloud bi, enterprise planning, cloud data analytics, cloud based analytics, analytics cloud platform, modern analytics, real time analysis, cloud analytics solution(s), what is sap analytics cloud, cloud analytics tools, analytics in the cloud, cloud analytics software epm, business intelligence , KBA , LOD-ANA-DES , Story Design & Visualizations , LOD-ANA-AQU-ODATA , Acquiring Data into SAC using an ODATA connection , LOD-ANA-GTW , Gateway for SAP Analytics Cloud API , Problem