Symptom
In Manage Data, the order of a new field created for an object (example )Legal Entity that is tied to an association is different in View/Read mode and in Edit ( Make Correction ) Mode
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
- SAP SuccessFactors Employee Central - Foundation Objects
Reproducing the Issue
1. Go to Configure Object Definition
2. Select Object ( Ex. Legal Entity )
3. Take Action > Make Correction
4. Add new field (ex: cust_addtestfield)
5. Save
6. Observe that there's a list of Associations
7. Go to Manage Data
8. Search Object ( Ex. Legal Entity )
9. Notice the order of the new field (addtestfield) - View Mode
10. Select Take Action > Make Correction and noticed that the order of the new field (addtestfield), shows in the USA Association Section
11. Search another Legal Entity, that's not on the list of Association from the Configure Object Definition ( Legal Entity) Example : Australia.
When go to Take Action> Make Correction, the new field ( Ex. addtestfield ) is in same order, no change
Cause
The order of the field changes because the countryOfRegistration field control the visibility of the CSF association.
Resolution
This is Expected Behavior.
If the field needs to appear in a more consistent manner, it has to be placed before the countryOfRegistration field via Configuration Object Definitions. This can be done by changing the field orders.
Keywords
Order , new field, created , Generic Object , Legal Entity , Manage Data , change Edit , Make Correction, mode, Configure Object Definition , Association, view , KBA , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , Problem