HCM Import Subscription Processing

When the HCM Import API runs, HCM subscriptions are processed:

  • The subscription list in HCM is compared to the active subscription records in ClientSpace (System Admin >Administrative Data> HCM Subscription).

  • In ClientSpace, each active subscription record represents a schema. A schema defines the data being imported: Client, Employee, Location, Division, Department and Job.

    Note: Subscriptions establish the type of information that must be monitored for change events for the ongoing import.

  • For each active ClientSpace HCM subscription record, we look for a match in the HCM subscription list. To support this comparison, we created an HCM Schema lookup group and lookup values (System Admin >Lookups) that allows us to match an HCM code to a Code/Decode value pairing in ClientSpace. The code and decode values in the HCM Schema lookup group are as follows:

    Code

    Decode

    0

    Client

    1

    Employee

    4

    Location

    5

    Division

    6

    Department

    7

    Job

  • Each subscription record in ClientSpace is evaluated as follows:

    • On the ClientSpace HCM Subscription record for a schema, the ClientSpace Subscription ID is compared to the HCM Subscription list for a match.

    • If ClientSpace Subscription ID is empty, we subscribe to HCM for that schema, retrieve a Subscription ID (GUID) from HCM and update the ClientSpace Subscription record with the ClientSpace Subscription ID. We also update the Process Date and Process Time fields with the current date and time.

    • If the ClientSpace Subscription ID is NOT empty, and a match is found to HCM subscription list, no updates are made. This is a good subscription.

    • If the ClientSpace Subscription ID is NOT empty, and no match is found to HCM subscription list, we subscribe to HCM for that schema, retrieve a Subscription ID (GUID) from HCM and overwrite the bad ClientSpace Subscription ID on the ClientSpace Subscription record with a good ClientSpace Subscription ID. We also update the Process Date and Process Time fields with the current date and time.

  • We repeat the evaluation step outline above until all ClientSpace subscription records are processed.

  • Finally, when all of the ClientSpace records have been processed, we unsubscribe from the records in HCM where a match could not be found.

Related Topics: