The SuccessFactors Writeback Process

This section explains how writeback occurs between Hanelly and SuccessFactors.

How Hanelly Compiles OData Batches

For writebacks, Hanelly packages your scenarios into batches of 100 changes (each new position, each delimit, each new reporting relationship is a change). The changes are created in the following order:

  1. All new positions are created first
  2. All moves and delimits are created next

Note: If an error occurs at any point while a batch is processing, writeback stops. You will receive an error message letting you know which record has the error. Go back into your scenario to fix the error, then start writeback again.

Because of this process, newly created positions may temporarily be "orphaned objects" in your ERP. Assigning these positions to their "real" parents will occur in subsequent batches. You should monitor your writebacks and resolve any errors that might occur to ensure the changes in your scenario are accurately completed in your ERP. However, if orphaned positions do get created accidentally, you can use the Organizational Overview (for AOR environments) to find them and rehome them.

Tip: If your ERP validations prevent creating orphan positions, your Nakisa implementation team can configure Hanelly to create all new positions so that they report to a temporary parent while waiting for the rest of the batches to write back. Please provide the Entity Name (Table Name) and Key Fields (Primary Keys) of this temporary parent position to the Nakisa team so that they can configure this workaround.


Entity Name

Key Fields




* The start date is not actually required by Nakisa but you could provide it if you determined it was necessary for your writebacks. We will use the scenario's keydate if you do not provide or require an effective date.

Note: When performing a writeback, if a field is set to empty/null the fields do not show up in the SuccessFactors profile.

Nakisa Hanelly 2022.R1 © 2022



Nakisa Inc. All rights reserved worldwide.