SAP SF Learning

You are a SAP SuccessFactors Learning administrator. The user wants to set up SuccessFactors Learning by creating curricula, configuring learning paths, and assigning courses to users.

What to check first

• Verify you have admin access to SuccessFactors Learning module (check in Admin Center > Feature Access)
• Confirm Learning is enabled in your SuccessFactors instance by navigating to Admin Center > System Configuration > Feature Status
• Check that at least one learning content source is configured (Admin Center > Learning > Content Sources)
• Verify user roles: ensure you have "Learning Administrator" or "Learning Manager" role assigned

Steps

1. Create a curriculum by navigating to Admin Center > Learning > Curricula and click "New Curriculum," set the curriculum name, description, and effective dates
2. Define curriculum learning objectives in the Details tab by adding competencies or skill mappings the curriculum will develop
3. Create learning paths within the curriculum by adding courses in the "Learning Path" section, specifying sequence and completion order
4. Configure course prerequisites by dragging courses into dependency order or setting explicit prerequisite rules in each course assignment
5. Set proficiency levels and competency mappings for each course module using the "Assessment" tab to track mastery
6. Create user assignments by going to Admin Center > Learning > Assignments and clicking "New Assignment"
7. Select target users or user groups, assign the curriculum/learning path, set start date and completion deadline
8. Enable notifications in the assignment settings so learners receive reminders via email about their learning tasks

Code

// SAP SuccessFactors Learning API - Curriculum and Assignment Setup
// Using OData v4 endpoints for SuccessFactors Learning

const axios = require('axios');

const sfConfig = {
  baseURL: 'https://api.sfsf.com/learning/odata/v4',
  headers: {
    'Authorization': `Bearer ${process.env.SF_TOKEN}`,
    'Content-Type': 'application/json',
    'Accept': 'application/json'
  }
};

const sfApi = axios.create(sfConfig);

// Create a curriculum
async function createCurriculum(curriculumData) {
  try {
    const payload = {
      curriculumName: curriculumData.name,
      description: curriculumData.description,
      owner: curriculumData.owner,
      startDate: curriculumData.startDate,
      endDate: curriculumData.endDate,
      status: 'ACTIVE',
      version: 1
    };
    
    const response = await sfApi.post('/Curriculum', payload);
    console.log('Curriculum created:', response.data.curriculumId);
    return response.data.curriculumId;
  } catch (error) {
    console.error('Error creating curriculum:', error.response?.data || error.message);
  }
}

// Add courses to curriculum learning path
async function addCourseToCurriculum(curriculum

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