Importing from HCM to ClientSpace

Process Overview

  • The HCMUser API is used by Azure Web services to login to HCM and retrieve the change events. This also creates Queue records. The initial and ongoing imports then use these Queue records to retrieve the HCM data using the HCMAPI config.
  • Note: Failure to log in terminates the process and a log entry is generated.
  • A list of HCM subscriptions is retrieved from HCM. The subscriptions establish the type of information that must be monitored for change events in the ongoing import. For more details, also see HCM Import Subscription Processing .

  • If running initial imports, the HCM Import Initial Sync scheduled process brings over Company data and then brings over Department, Division, Employee, Employment, Job, and Location data to ClientSpace if Active import maps exist for these categories.

  • Thereafter, the HCM Import Ongoing scheduled process evaluates HCM events (Company and Employee changes) that may affect previously imported Client and Employee data. The ongoing scheduled process also monitors for changes and locates events that trigger the creation of new Clients and Employees in ClientSpace. Active import maps must also exist for the ongoing import maps. All active ongoing import map configurations are processed each time the scheduled process executes.

    • The HCM Import Ongoing scheduled process imports ongoing data for clients only when a matching Client Number exists in ClientSpace.

    • ClientSpace ignores inactive Client Master records.

  • Applicable HCM events are converted into Import Queue records.

  • HCM data is extracted from the Import Queue records and loaded into ClientSpace through scheduled processes.

Note:  During an Import, if an exception occurs during the dataform save, the system logs an appropriate exception in both the Import logs and the exception log.

Related Topics: