SAP Knowledge Base Article - Public

2173590 - Blank Page When importing Succession Data Model


Getting a Blank page when importing succession data model


Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental


Employee Central - Data Models


System performs a back end validation whenever you try to import succession DataM odel.

Validation will be on the configuration between Country Specific succession DM and succession DM

System will throw a blank screen as shown above if the validation is broken


  • Unsupported Feature enabled:
    Please make sure the following setting is disabled (unchecked):
          Provisioning -> Company Settings -> Enable OpenText Integration
    In case it is enabled, please uncheck that checkbox, save and try the import again.

  • Configuration Mismatch between Succession Data Model and Country Specific Succession Data Model:
    1.Import a blank Country Specific succession DM first. Do not forget to take back up of existing CSF DM

       What is a blank CSF DM?
       A country specific xml without any data in between following tags. Please find the attached blank Country specific DM for your reference

       SAMPLE of blank CS-SDM:
       <?xml version="1.0" encoding="UTF-8"?>
       <!DOCTYPE country-specific-fields PUBLIC 
       "-//SuccessFactors, Inc.//DTD Country Specific Field Configuration//EN"

    2.Upload your new Succession Data Model. It will be successful

    3.Now try uploading the original Country Specific DM. The system will now throw the exact error.

       Error Examples

       A. Section mismatch between SDM and CSF DM:

          Sections which is not configured in “succession DM “should not be added in “Country Specific succession DM”
          Let us say we have following sections in succession DM
          - positionInfoList
          - orgFieldsList
          - jobFieldsList

          Below section is configured in CSF DM
          - eeoFieldsList

          This is a mismatch as per the above concept as eeoFieldsList is not added in succession DM

       B.Visibility and required status mismatch for same fields under same section
          “Custom-string1” configured in succession DM and CSF succession DM under “job info “section

          In succession DM
          <hris-field max-length="128" id="custom-string1" visibility="both" required="false" pii="false" allow-import="false" showTrailingZeros="false">

          In CSF succession DM
          <hris-field max-length="128" id="custom-string1" visibility="none" required="false" pii="false" allow-import="false" showTrailingZeros="false">
          Here visibility is “both” in succession and “none” in CSF succession, an example for visibility mismatch

    4.Correct it and upload the CSF



Blank Screen, Succession Data Model, Provisioning, blank, empty, screen, import, data model, XML, Enable OpenText Integration , KBA , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , LOD-SF-EC-PRV , Provisioning Changes , Problem


SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM suite all versions