Setting up Third-Party HCM to PSA Integration

Create a dedicated API user in PSA. Assign one of the following permission sets to them, depending on whether you want to create resources as contact or person account records:

• PSA Resource API - Contact
• PSA Resource API - Person Account

You must also assign the ERP Core - Read Only permission set to the API user.

Refer to the Salesforce Help for best practice information on creating API users.

Set up your third-party HCM application as a connected app to be able to authenticate and send data to PSA.

See the Salesforce Help for more information about connected apps.

Decide what information you want to send from your third-party HCM application to PSA and configure your application to send data via the API. In addition to the standard keys, several custom keys are available to enable you to customize the type of resource information you send.

See "PSA REST API Developer Reference" on FinancialForce Community for more information.

The Feature Console simplifies the setup tasks for some FinancialForce features.

To configure PSA to receive information from your third-party HCM application, follow the PSA Resource API feature steps on the Feature Console tab.

For more information about using the Feature Console, see Feature Console.

The PSA Resource API feature uses many components that may be used by other ERP integrations. If you want to disable this feature after it has been enabled, complete the following steps:

• Manually disable the related subscriptions on the ERP Setup page
• Use the Feature Console to mark the feature as disabled

If required, you can use ERP features to add data transformation tables (DTTs). DTTs enable you to convert data received from your third-party HCM app by storing defined source and target values.

By default, PSA provides data transformation tables to enable you to:

• Map common employment status values
• Ensure all records created via the API use the Resource record type on the Contact object

Example

The following table displays some examples of how you can use DTTs to convert one or more source keys and values to target fields and values that match the structure and terminology in your PSA org.

Key	Source Value 1	Additional Key	Source Value 2	Target Field	Target Value
Division	Consulting	Location	California	Group	California Consultants
Division	Consulting	Location	New York	Group	New York Consultants
Location	California	-	-	Region	CA
Cost Center	US Field Operations	Department	Consulting	Practice	Consultant

See "Data Transformation Tables" and "Creating a Data Transformation Table" in the ERP Help for more information.

If required, you can use ERP features to customize the default field mappings to suit your organization’s requirements.

You may want to:

• Create mappings for custom keys
• Create mappings for keys that relate to organizational structure to support the region, practice, and group structure in your organization

See "Adding Mappings to Subscriptions" in the ERP Help for more information.

If required, you can use ERP features to add static information to all records created via the PSA Resource API. For example, you might want all API resource records to include a common account name or description, or create all records as a specific record type.

See Creating a Static Mapping for the PSA Resource API for more information.

Consider the following to ensure you do not create duplicate or invalid records in PSA.

If you are a new PSA customer, ensure that you create resources in PSA before adding their manager details. To do this, exclude the ReportsTo key from your API messages. When you have created the resources in PSA, you can include the ReportsTo key in your API messages to update their manager details.

If you are an existing PSA customer, ensure that all resources you intend to update via the API contain an API resource correlation ID. The ID on the resource record must match the resource's unique ID in your third-party HCM application.