InsiteConnect for Prophet 21 reference

The salesperson information is important so that we can set the primary sales rep on the customer records.  This allows your customers to know who their sales reps are, and allows your sales reps to view customer data in Optimizely <<product-name>>. It is also required if using the Request for Quote functionality in <<product-name>>.

Deletion Strategy – We will use Ignore and not delete any salesperson records automatically during the refresh.

The payment terms refresh populates the payment methods table in <<product-name>>, which is referenced in history tables and sets the default value in the customer table used in order submission.    Typically, once this is run, customers can update the descriptions in the Admin Console to reflect the values displayed to the end user, such as ‘Terms’.

Deletion Strategy – We will use Ignore and not delete any payment method records automatically during the refresh.

The Product Refresh process retrieves item/product information directly from the Prophet 21 ERP database (inv_mast).

Deletion Strategy – We will set the Deactivate On flag for the item record.

<<product-name>> retrieves Product Cross-Sells via a direct call to the Prophet 21 database. This refresh can be modified or copied to use specific record types or relationships needed for a given implementation.

Deletion Strategy – This refresh uses the Ignore option. Users may create manual entries for different types of relationships that are not managed in Prophet 21.

<<product-name>> retrieves Alternate Units of Measure via a direct call to the Prophet 21 database.  This refresh is done as a separate step in the Product Refresh

Deletion Strategy – <<product-name>> uses the Delete option for this data.

<<product-name>> uses real-time calls to obtain pricing and availability via real-time calls. No refresh of inventory will be used.  See the section on Pricing for the API call mapping.

The customer refresh pulls both Bill-To and Ship-to information into a common customer table.

Deletion Strategy – <<product-name>> retrieves all customer records and physically sets the IsActive flag directly from the data, so the Ignore delete action will be used. <<product-name>> must use Ignore, since the data will be retrieved in two separate sweeps.

Customer-specific product data will be retrieved by <<product-name>> via a direct call to the Prophet 21 database.

Deletion Strategy – <<product-name>> uses the Delete option to physically remove records that are no longer valid. <<product-name>> also uses Delta Datasets.

<<product-name>> retrieves pricing from Prophet 21 via real-time calls, so no refresh is needed.  The API used for this function is GetItemPrice.

Use an API to calculate if the tax calculator is set to Prophet 21 and uses the API GetOrderSummary.

<<product-name>> submits order to Prophet 21 via real-time calls.  The API used for this function is OrderImport.

<<product-name>> calls the payment gateway directly to authorize a user’s credit card.  The authorization information is passed into Prophet 21 via the order submission process using an authorization token returned by the payment gateway.

<<product-name>> uses a standard direct call to an API endpoint to display the A/R aging information on the Invoice History page.  The standard aging buckets must be set up as global options in Settings.  We do not use the labels returned from the API, only the balances themselves.

The API used is GetMyAccountOpenAR.

<<product-name>> retrieves Order history data from Prophet 21 via a direct call to the ERP database. The data is stored within the <<product-name>> database and refreshed on a regular interval, typically once a day.

To limit the number of order records analyzed, the integration process uses a lookback period in the query.  This query is performed against the Prophet 21 order header transaction date AND the order line transaction date.

Orders placed in <<product-name>> are immediately added to the order history tables.  This ensures that a user will immediately see their orders on the Order History pages under My Account. Because Prophet 21’s Order Submit API does not dynamically create the order, we had to create a batch process to find orders that were created from the Web and update them in <<product-name>> prior to running Order History. It is imperative that the Order Assignment job is run first or else the order history records for orders that started on the web will be duplicated in history since the ERP Number is the data we anchor to for creating or updating the information. This job specifically looks back 5 days (defined in the job’s where clause and can be adjusted) to find web-based orders (based on the ‘taker’ field = ‘ESTORE’) and update them in <<product-name>>.

The shipment refresh is dependent on having shipment data in the ERP from which we can obtain tracking information.  This refresh is typically run once per day and also uses a lookback period from which to run the query to limit the number of order records analyzed. This query is used against the order header transaction date only since we do not expect shipment records to change once generated.

Deletion Strategy – Since this is not a full snapshot and this data is highly unlikely to change once processed, the Ignore delete action is used.

Invoice data is retrieved from Prophet 21 via a direct call to ERP database. The data is stored within the <<product-name>> database and refreshed on a regular interval, typically once a day.

To limit the number of records analyzed, the integration process will use a lookback period when constructing the query. This query is used against the invoice date since we do not expect records to change once invoiced.

Refer to the Implementation Notes in Order History Refresh for additional information.

Deletion Strategy –  We will employ the Ignore strategy, as we will only be taking a snapshot and do not expect line information to change once the status of the order is changed to Invoiced.