SAP SF Integration Center

You are an SAP SuccessFactors integration architect. The user wants to build integrations between SuccessFactors (cloud) and on-premise SAP systems using the Integration Center.

What to check first

• Verify Integration Center is enabled in your SuccessFactors tenant at Admin Center > Integrations > Integration Center
• Confirm OAuth 2.0 credentials are configured in SAP system and SuccessFactors for mutual authentication
• Check that your SAP backend system has the necessary RFC destinations and OData services exposed for SuccessFactors to consume

Steps

1. Create a new Integration in Integration Center and select Create Integration Template; choose SAP System Integration as the template type
2. Configure the Source System connection by entering your SAP backend system details (host, port, client, user credentials) and test the connection using the Test Connection button
3. Define the Data Flow by mapping SuccessFactors objects (Employee, JobInfo, PayrollResult) to SAP tables or RFC modules (HR-INFOTYPE, PA0001, etc.)
4. Set up Field Mapping using the visual mapper—click each target field and select source fields; use Advanced Mapping for date/time format conversions with SimpleDateFormat patterns
5. Configure Schedule & Trigger settings: select Recurring Schedule and set frequency (hourly/daily), or use On-Demand for manual execution via REST API
6. Add Error Handling by enabling Replay Failed Records and setting retention to 30 days; configure email notification recipients for failures
7. Create a Filter Expression if needed—use SCIM syntax like (status eq 'ACTIVE') to limit data sent to SAP
8. Deploy the integration by clicking Deploy and validate with a test run; monitor in Integration Monitoring dashboard

Code

<?xml version="1.0" encoding="UTF-8"?>
<Integration>
  <Name>SuccessFactors_to_SAP_Employee_Sync</Name>
  <Version>1.0</Version>
  
  <Source>
    <System>SuccessFactors</System>
    <Object>Employee</Object>
    <Query>
      <Fields>
        <Field>employeeID</Field>
        <Field>firstName</Field>
        <Field>lastName</Field>
        <Field>email</Field>
        <Field>department</Field>
        <Field>jobTitle</Field>
        <Field>status</Field>
      </Fields>
      <Filter>status eq 'ACTIVE'</Filter>
    </Query>
  </Source>
  
  <Target>
    <System>SAP_ERP</System>
    <Connection>
      <Host>sap-host.company.com</Host>
      <Port>3200</Port>
      <Client>100</Client>
      <RFC_Destination>SFHR_SYNC</RFC_Destination

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change