Epicor Prophet 21 Installation Instructions

Go to Subscriptions Management > Subscriptions and click Search Certified Integration Marketplace and Subscribe.
​

Click the Epicor Prophet 21 Integration title.
​

Click the Subscribe button.

Enter the Name of the subscription and select a Version . It can be set to any relevant and unique subscription name within the company where this subscription is created.

Select Create Default Mappings (recommended). If you don’t want to create default mappings and want to create all mappings from scratch by yourself then uncheck this box.
​

Enter the API URL endpoint for your Epicor Prophet 21 instance:

Enter your Epicor Prophet 21 Username and Password.

Enter the Product Poll Search Days. This defines how far back the system searches for product data during the initial polling run. If left blank, the system defaults to 4 days. For example, entering 100 retrieves product records from the past 100 days, which is useful for capturing missed records during setup or after downtime.

Enter the Product Inventory Search Poll Days. This defines how far back the system searches for inventory data during the initial polling run.

Enter the Time Zone Offset for your location. The value is based on UTC. Use a value such as +6, -4, etc. Common time zone offset values are:

Enter the Company Poll Search Days. This defines how far back the system searches for company data during the initial polling run.

Enter the Transaction Poll Search Days. This defines how far back the system searches for transaction data during the initial polling run.

Enter the Transaction Tracking Poll Search Days. This defines how far back the system searches for shipment data during the initial polling run. If left blank, the system defaults to 4 days. For example, entering 100 retrieves shipment records from the past 100 days, which is useful for capturing missed records during setup or after downtime.

Enter the Customer Poll Search Days. This defines how far back the system searches for customer data during the initial polling run.

Enter the API Throttle Limit. This setting prevents any single integration or user from overwhelming the system with too many requests. It protects system performance by controlling the number of API requests that can run simultaneously, ensuring fair usage.

Enter the API Throttle Seconds. This defines the time window during which the API Throttle Limit is measured. If an integration makes too many requests within this time window, additional requests are rejected until the window resets.

Enter the number of Concurrent Connections. This specifies the maximum number of simultaneous API connections that Dotdigital can process for a user or integration. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.

Enter the number of Concurrent Batch Executions. This specifies the maximum number of simultaneous batch executions that can process for an integration at one time. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.

Click Apply to save the settings.

Initiate a sample data pull. (To iPaaS.com).

Initiate a sample data push. (From iPaaS.com).

Run an end-to-end business process.

Validate key features like field mappings, workflow triggers, and logging.

Review integration logs in iPaaS.com.