We are in the process of updating the partitioned user information missing in our child site and are looking for the list of users who are not updated.  Although we understand when a user does not appear under Other User Info they are missing an active, linked partition, Manage > Core Administration > User Manager > Other User Info has limitation of 2000 user list.  How can administrators determine which users are missing partitioned users in the child site?

Administrators can determine which users are missing partitioned users by reviewing and comparing data exports.

1. Core Administration > Site Manager > Data Import/Export
2. Export both the Export Enterprise Users and the Export User Data (Consolidated File) task files
3. Compare the users listed in the SharedUserExport.csv (Enterprise User file) to those in the UserConsolidatedExport.csv (User Data file)
• The SharedUserExport.csv includes all users
• The UserConsolidatedExport includes users with active partitioned users
4. Users present in the SharedUserExport.csv yet not in the UserconsolidatedExport.csv are users who either do not have a partitioned user assigned or their partitioned user was deactivated at the time of the export task.  Users present in the SharedUserExport.csv yet not in the UserconsolidatedExport.csv will not appear under Other User Info until the partition is linked and active.

The following are the steps to resolve missing/deactivated partitioned users:

1. Core Administration > Site Manager > Data Import/Export
2. Search Import Users or Import User Data (Consolidated File)
3. Click Import
   • Import Users: User.csv and the PCardMap.csv
   • Import User Data (Consolidated File): UserConsolidated.csv
4. Select import operation Update Only (to reactivate) or Create(to create) as needed
5. Click Run

Once the task completes, the Partitioned User will be created/active. 

In an FPC configuration, only the Enterprise User (Shared User) gets replicated from parent realm to child realm.  The Partitioned User (Import Users User.csv) should be loaded directly in child realm.  Since accounting details are maintained in partitioned user object, if the User.csv file is loaded in parent realm the data will not be replicated to child realm. Source

Also in regards to FPC configurations if importing the UserConsolidated.csv, keep in mind of the ImportCtrl field; How the ImportCtrl column works?  

See the Common data import and administration guide for SAP Ariba Procurement solutions guide for more information on importing and maintaining user data.

Core Procurement > Core Administration > Core Administration User Management