InsiteConnect for IFS reference
Describes the InsiteConnect for IFS reference in Optimizely Configured Commerce.
Note
As of January 2023, Optimizely no longer adds new functionality to ERP connectors. Instead, partners can build customized solutions for clients. Optimizely continues to fix ERP connector bugs only if there are no workarounds or extensibility solutions available.
Supporting tables
Salespeople
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 Configured Commerce. It is also required if using the Request for Quote functionality in Configured Commerce.
Deletion Strategy – We will use Ignore and not delete any salesperson records automatically during the refresh.
| Field Mapping: Salesperson Refresh | |||
|---|---|---|---|
| Field Name | ERP Source (contacts) | Destination (Salesperson) | Notes |
| Salesperson Number | Contact_salesrep.salesrep_id | SalespersonNumber | Select only records from contact_salesrep where delete_flag = ‘N’ |
| Name | First_name + ‘ ‘ + last_name | Name |  |
| Email Address | email_address | Â | |
| Title | title | Title | Â |
| Phone number | direct_phone | Phone1 | Â |
| Manager Number | sales_manager_id | SalesManager | If provided, we can track the manager of the sales rep which allows access to the sales rep’s accounts and quotes |
Payment Methods
The payment terms refresh populates the payment methods table in Configured Commerce, 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.
| Field Mapping: Payment Terms Refresh | |||
|---|---|---|---|
| Field Name | ERP Source (sasta) | Destination (PaymentMethod) | Notes |
Company | Cono | N/A | Used for filtering the correct records only. Obtain value from the system setting |
Record Type | Codeiden = ‘T’ |  | Using code ‘T’ to pull in the terms codes from the system admin table |
Terms Code | Codeval | Name | Â |
Description | descrip | Description | Â |
COD/Cash | n/a | IsCreditCard | This terms code requires payment by credit card on the site |
Active Indicator |  | ActivateOn | Not overwritten – set on initial setup to current date |
Product tables
Products
The Product Refresh process retrieves item/product information directly from the P21 ERP database (inv_mast).
Deletion Strategy – We will set the Deactivate On flag for the item record.
| Field Mapping: Product Refresh – Product | |||
|---|---|---|---|
| Field Name | ERP Source (inv_mast) | Destination (Product) | Notes |
ERP Item # | item_id | Name ERPNumber | This is the primary natural key to the table |
Item Title & Item Description | extended_desc | ShortDescription ERPDescription | Short description will not be overwritten – it is expected to be maintained in the application or from a PIM |
URL Segment | item_id | URLSegment | Appending the item number to ensure uniqueness |
Tax Code/Class | item_sales_tax_class | TaxCode1 | Â |
Unit of Measure | base_unit | UnitOfMeasure | This is the stocking unit of measure to properly handle conversions |
Unit Weight | net_weight | ShippingWeight | Â |
UNSPSC | unspsc_code | UNSPSC | Not mapped: Used for punchout and needs to be enabled in the Application Dictionary |
UPC Code | upc_or_ean_id | UPCCode | Not mapped: Used for punchout and needs to be enabled in the Application Dictionary |
Base Unit Price | price1 | BasicListPrice | Â |
Tax Class | item_sales_tax_class | TaxCode1 | Â |
Product Cross-Sell
Configured Commerce retrieves Product Cross-Sells via a direct call to the P21 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 P21.
| Field Mapping: Product Cross-Sells | |||
|---|---|---|---|
| Field Name | ERP Source | Destination (ProductRelatedProduct) | Notes |
| Primary Item | inv_mast.inv_mast_UID | ProductID | This is joined to ony match records of the inv_mast_uid field in inv_sub. |
| Related Item | inv_sub.item_id | RelatedProductID | This is joined to ony match records of the sub_inv_mast_uid field in inv_sub in addition to the above join. |
Product Alternate Unit of Measure
Configured Commerce retrieves Alternate Units of Measure via a direct call to the P21 database. This refresh is done as a separate step in the Product Refresh
Deletion Strategy:Â Configured Commerce uses the Delete option for this data.
| Field Mapping: Product Alternate Unit of Measure | |||
|---|---|---|---|
| Field Name | ERP Source | Destination (ProductUnitOfMeasure) | Notes |
| Product # | inv_mast.item_id | Product.ERPNumber | Lookup to Product |
| Unit of Measure | item_uom.unit_of_measure | UnitOfMeasure | Â |
| Conversion Factor | item_uom.unit_size | QtyPerBaseUnitOfMeasure | Â |
Inventory tables
Configured Commerce 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.
Customer tables
Customer
The customer refresh pulls both Bill-To and Ship-to information into a common customer table.
Deletion Strategy – Configured Commerce retrieves all customer records and physically sets the IsActive flag directly from the data, so the Ignore delete action will be used. Configured Commerce must use Ignore, since the data will be retrieved in two separate sweeps. Delta Dataset option will be disabled.
| Field Mapping: Customer (Bill-To) | |||
|---|---|---|---|
| Field Name | ERP Source (customer) | ISC Destination (Customer) | Notes |
Customer # | customer_id | CustomerNumber ERPNumber | Â |
Ship-To # | Â | CustomerSequence | Static Value = Blank |
Customer Name | customer_name | Company | Â |
Address Line 1-3 | phys_address[1..3] | Address1..3 | Â |
City | phys_city | City | Â |
State | phys_state | StateId | Lookup being used – must exist in <> |
Country | phys_country | CountryId | Must match country abbreviation to be valid, uses lookup |
Postal Code | phys_postal_code | PostalCode | Â |
Customer Type | Â | CustomerType | Optional field |
email_address | Must match proper email format or an error will be generated - default job ignores nulls and "DNE" | ||
Phone 1 | central_phone_number | Phone | Â |
Fax | Â | Fax | Â |
Terms Code | terms_id | TermsCode | Should match a valid payment method;not enforced on refresh |
Tax Code 1 | Â | TaxCode1 | Static Value = Blank; Relying on calls to API to determine the tax amount in cart. |
Tax Code 2 | Â | TaxCode2 | |
Currency Code | currency_id | CurrencyId | Must match a valid currency code |
Outside Sales Rep | salesrep_id | PrimarySalespersonId | Must match a valid sales rep |
Inside Sales Rep |  |  | If desired, can be mapped to Salesperson instead of the outside sales rep. We only support a single, assigned sales rep to the account. |
Credit Limit | credit_limit | CreditLimit | Not enforced as standard feature |
Active | delete_flag | IsActive | Y = 0 All others = 1 |
| Field Mapping: Customer (Ship-To) | |||
|---|---|---|---|
| Field Name | ERP Source (customer) | Destination (Customer) | Notes |
Customer # | customer_id | CustomerNumber ERPNumber | Â |
Ship-To # | Â | CustomerSequence | Â |
Customer Name | customer_name | Company | Â |
Address Line 1-3 | phys_address[1..3] | Address1..3 | Â |
City | phys_city | City | Â |
State | phys_state | StateId | Lookup – must match a valid state for the country supplied |
Country | phys_country | CountryId | Lookup – must match a valid country. |
Postal Code | phys_postal_code | PostalCode | Â |
Customer Type | arsc.custtype | CustomerType | Â |
email_address | Validated against standard email formats and will error if incorrect. | ||
Phone 1 | central_phone_number | Phone | Â |
Fax | Â | Fax | Â |
Tax Code 1 | Â | TaxCode1 | Static Value = Blank; Relying on calls to API to determine the tax amount in cart. |
Tax Code 2 | Â | TaxCode2 | |
Currency Code | currency_id | CurrencyId | Must match valid currency code |
Outside Sales Rep | salesrep_id | PrimarySalespersonId | Must match valid sales rep |
Inside Sales Rep |  | PrimarySalespersonId | If desired, can be mapped to Salesperson instead of the outside sales rep. We only support a single, assigned sales rep to the account. |
Credit Limit | credit_limit | CreditLimit | Typically enforced only at customer level but not a standard function |
Active | delete_flag | IsActive | Y = 0 All others = 1 |
Customer Products
Customer-specific product data will be retrieved by Configured Commerce via a direct call to the P21 database.
Deletion Strategy – Configured Commerce uses the Delete option to physically remove records that are no longer valid. Configured Commerce also uses Delta Datasets.
| Field Mapping: Customer Product | |||
|---|---|---|---|
| Field Name | ERP Source | Destination (CustomerProduct) | Notes |
| ERP Part # | inv_xref.item_id | ProductId | Lookup to Product table |
| Customer # | customer.customer_id | CustomerId | Only pull records WHERE icsec.shipto is blank (bill-to level). Lookup to customer table. |
| Customer Part # | inv_xref.their_item_id | Name | Customer’s product number |
Pricing tables
Pricing API
Configured Commerce retrieves pricing from P21 via real-time calls, so no refresh is needed. The API used for this function is GetItemPrice.
| Field Mapping: Pricing & Availability | ||||
|---|---|---|---|---|
| Field Name | Commerce Table.Field | ERP Web Service Field | Notes | |
| Â | N/A | <B2BSellerVersion> | Defaults to MajorVersion of 5, MinorVersion of 11, BuildNumber of 100. | |
| Customer # | CustomerNumber | Â <CustomerCode> | Â | |
| Â | Â | <StoreName> | Â | |
| Â | Â | <LocationID>Â | Â | |
| Â Â <ListOfItems>Â | This contains some number of line items as children, each in item tags. | |||
| <Item> | Information in this tag is for a single item. | |||
| Product # | Product.ERPNumber | <ItemID> | Â | |
| Â Qty Ordered | "1"Â | <Quantity> | We use this normally to get the default price ofr a quantity of 1. | |
| Unit of Measure |  Product.UnitOfMeasure | <UnitName> |  | |
| </Item> | End of Item | |||
| End of List | |||
Tax (order simulation)
Tax Calculation
| Field Mapping: Order Submit – Header | |||
|---|---|---|---|
| Â | Â | Â <B2BSellerVersion> | Defaults to MajorVersion of 5, MinorVersion of 11, BuildNumber of 100. |
| Â Customer # | CustomerNumber | <CustomerCode> | Â |
| Â | Â | <StoreName>Â | Â |
| Â Web Order # | OrderNumber | <WebReferenceNumber>Â | Â |
| Â | Â | <Anonymous> | Hard-coded to N. |
| Â Customer PO | CustomerPo | Â <PONumber> | Â |
| Â | Â | <NotePadText>Â | Â |
| Â | Â "False" | <UseContractAddress>Â | Hard-coded to False |
| Â | Â | <FreightCode> | Â |
| Â | Â | <ContactID>Â | Â |
| <CustomerShipTo> | Contains ShipToIDs and ShipToAddresses> | ||
| Â Ship-To # | CustomerSequence | <ShipToID> | Â |
| <ShipToAddress> | Contains Below Tags | ||
| Ship-To Name | STCompanyName | <ShipToCompanyName> |  |
| Â Ship-To Address 1 | STAddress1Â | <ShipToAddress1> | Â |
| Ship-To Address 2Â | STAddress2Â | <ShipToAddress2> | Â |
| Ship-to Address 3Â | STAddress3Â | <ShipToAddress3> | Â |
| Ship-to City | STCity | <ShipToCity> |  |
| Ship-to State | STState | <ShipToState> |  |
| Ship-to Postal Code | STPostalCode | <ShipToZip> |  |
| Ship-to Country | STCountry | <ShipToCountry> |  |
| </ShipToAddress> | Â | ||
| Â Ship-To Contact First Name | Â STFirstName | <ShiptoContactFirstName> | Â |
| Ship-To Contact Last Name | STLastName | <ShipToContactLastName> |  |
| Ship-To Phone | STPhone | <ShipToPhone> |  |
| Â Ship-To Email | STEmail | <ShipToEMail> | Â |
| Â Ship Via | Â ShipVia.ERPShipCode | <ShipToCarrierID> | Â |
| </CustomerShipTo> | Â | ||
| <CreditCard> | This entire envelope is only required for credit card orders. | ||
| </CreditCard> | Â | ||
| <ListOfMerchandiseCredits> | Contains Merchandise Credit Lines | ||
| <MerchandiseCredit> | Contains MerchandiseCredit # and Amount | ||
| Â | Â | <MerchandiseCreditNumber> | Â |
| Â | Â | <Amount> | Â |
| </MerchandiseCredit> | Â | ||
| </ListofMerchandiseCredits> | Â | ||
| <ListOfLineItems> | Contains Line Items | ||
| <LineItem> | Contains Individual line item information. | ||
| Â ERP Part # | EPRNumber | <ItemID> | Â |
| Â Quantity Ordered | QtyOrdered | <OrderQuantity> | Â |
| Â Unit of Measure | UnitOfMeasure | <UnitName> | Â |
| Â Unit Sell Price | NetUnitPrice | <UnitPrice> | Â |
| Â Warehouse | Warehouse | <SourceLocation> | Â |
| Â | Â | <NotepadText> | Â |
| </LineItem> | Â | ||
| </ListOfLineItems> | Â | ||
| <ListOfCoupons> | Â | ||
| </ListOfCoupons> | Â |
Order submission
Order Submit API
Configured Commerce submits order to P21 via real-time calls. The API used for this function is OrderImport.
| Field Mapping: Order Submit – Header | |||
|---|---|---|---|
| Â | Â | Â <B2BSellerVersion> | Defaults to MajorVersion of 5, MinorVersion of 11, BuildNumber of 100. |
| Â Customer # | CustomerNumber | <CustomerCode> | Â |
| Â | Â | <StoreName>Â | Â |
| Â Web Order # | OrderNumber | <WebReferenceNumber>Â | Â |
| Â | Â | <Anonymous> | Hard-coded to N. |
| Â Customer PO | CustomerPo | Â <PONumber> | Â |
| Â | Â | <NotePadText>Â | Â |
| Â | Â | <UseContractAddress>Â | Hard-coded to False |
| Â | Â | <FreightCode> | Â |
| Â | Â | <ContactID>Â | Â |
| <CustomerShipTo> | Contains ShipToIDs and ShipToAddresses> | ||
| Â Ship-To # | CustomerSequence | <ShipToID> | Â |
| <ShipToAddress> | Contains Below Tags | ||
| Ship-To Name | STCompanyName | <ShipToCompanyName> |  |
| Â Ship-To Address 1 | STAddress1Â | <ShipToAddress1> | Â |
| Ship-To Address 2Â | STAddress2Â | <ShipToAddress2> | Â |
| Ship-to Address 3Â | STAddress3Â | <ShipToAddress3> | Â |
| Ship-to City | STCity | <ShipToCity> |  |
| Ship-to State | STState | <ShipToState> |  |
| Ship-to Postal Code | STPostalCode | <ShipToZip> |  |
| Ship-to Country | STCountry | <ShipToCountry> |  |
| </ShipToAddress> | Â | ||
| Â Ship-To Contact First Name | Â STFirstName | <ShiptoContactFirstName> | Â |
| Ship-To Contact Last Name | STLastName | <ShipToContactLastName> |  |
| Ship-To Phone | STPhone | <ShipToPhone> |  |
| Â Ship-To Email | STEmail | <ShipToEMail> | Â |
| Â Ship Via | Â ShipVia.ERPShipCode | <ShipToCarrierID> | Â |
| </CustomerShipTo> | Â | ||
| <CreditCard> | This entire envelope is only required for credit card orders. | ||
| </CreditCard> | Â | ||
| <ListOfMerchandiseCredits> | Contains Merchandise Credit Lines | ||
| <MerchandiseCredit> | Contains MerchandiseCredit # and Amount | ||
| Â | Â | <MerchandiseCreditNumber> | Â |
| Â | Â | <Amount> | Â |
| </MerchandiseCredit> | Â | ||
| </ListofMerchandiseCredits> | Â | ||
| <ListOfLineItems> | Contains Line Items | ||
| <LineItem> | Contains Individual line item information. | ||
| Â ERP Part # | EPRNumber | <ItemID> | Â |
| Â Quantity Ordered | QtyOrdered | <OrderQuantity> | Â |
| Â Unit of Measure | UnitOfMeasure | <UnitName> | Â |
| Â Unit Sell Price | NetUnitPrice | <UnitPrice> | Â |
| Â Warehouse | Warehouse | <SourceLocation> | Â |
| Â | Â | <NotepadText> | Â |
| </LineItem> | Â | ||
| </ListOfLineItems> | Â | ||
| <ListOfCoupons> | Â | ||
| </ListOfCoupons> | Â |
Credit card processing
Configured Commerce calls the payment gateway directly to authorize a user’s credit card. The authorization information is passed into P21 via the order submission process using an authorization token returned by the payment gateway.
A/R aging balances (invoices)
A/R Aging Balances API
Configured Commerce 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.
Existing orders
Order History
Configured Commerceretrieves Order history data from P21 via a direct call to the ERP database. The data is stored within the Configured Commerce 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 P21 order header transaction date AND the order line transaction date.
Orders placed through Configured Commerce 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 the P21 connector order submission uses the real-time API, the ERP order # should also be present.
| Field Mapping: Order History - Header | |||
|---|---|---|---|
| Field Name | ERP Table.Field (oe_hdr) | Commerce Table.Field (OrderHistory) | Notes |
ERP Order # | Order_no | ERPOrderNumber | Â |
Order Status | Completed | Status | Value - Description Y - Completed Any other value - Open |
Order Date | order_date | OrderDate | Â |
Customer # | customer_id | CustomerNumber | Â |
Customer PO # | po_no | CustomerPO | Â |
Terms Code | terms | Terms | Â |
Ship Via | carrier_id | ShipCode | Â |
Requested Ship Date | requested_date | RequestedDeliveryDate | Â |
Billing Information: Company/Name | customer_name | BTCompanyName | Â |
Billing Information: Address | phys_address[1..2] | BTAddress1..2 | Â |
Billing Information: City | phys_city | BTCity | Â |
Billing Information: State | phys_state | BTState | Â |
Billing Information : Zip | phys_postal_code | BTPostalCode | Â |
Billing Information Country | phys_country | BTCountry | Â |
Shipping Information: Company/Name | ship2_name | STCompanyName | Â |
Shipping Information: Address | ship2_add[1..2] | STAddress1..2 | Â |
Shipping Information: City | ship2_city | STCity | Â |
Shipping Information: State | ship2_state | STState | Â |
Shipping Information: Postal Code | ship2_zip | STPostalCode | Â |
Shipping Information: Country | ship2_country | STCountry | Â |
Subtotal | oe_line.extended_price | ProductTotal | This is calculated by summing all of the extended_price lines from the oe_line table for this order. |
Sales Tax | oe_line.sales_tax | TaxAmount | This is calculated by summing all of the sales_tax lines from the oe_line table for this order. |
Order Total | Calculated | OrderTotal | SUM(Subtotal + Sales Tax) |
Shipments
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, the integration process will use a lookback period when constructing the query. 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.
| Field Mapping: Order History - Shipment | |||
|---|---|---|---|
| Field Name | ERP Table.Field (oe_pick_ticket) | Commerce Table.Field (Shipment) | Notes |
| ERP Order Number | Oe_hdr.order_no | ERPOrderNumber | Â |
| Shipment # | pick_ticket_no | ShipmentNumber | Â |
| Shipment Date | ship_date | ShipmentDate | Â |
| Field Mapping: Order History – Shipment Packages | |||
|---|---|---|---|
| Field Name | ERP Table.Field (oe_pick_ticket) | Commerce Table.Field (ShipmentPackage) | Notes |
| Shipment # | pick_ticket_no | ShipmentID | Â |
| Ship Via | carrier_id | Carrier | Â |
| Tracking # | tracking_no | TrackingNumber | Â |
| Freight Amount | freight_out | Freight | Â |
| Package # | line_no | PackageNumber | Â |
Invoices
Invoice data is retrieved from P21 via a direct call to ERP database. The data is stored within the Configured Commerce 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.
| Field Mapping: Invoice History - Header | |||
|---|---|---|---|
| Field Name | ERP Table.Field (invoice_hdr) | Commerce Table.Field (InvoiceHistory) | Notes |
Invoice # | invoice_no | InvoiceNumber | Â |
Invoice Date | invoice_date | InvoiceDate | Â |
Invoice Due Date | net_due_date | DueDate | Â |
Invoice Type |  | InvoiceType | Static value = ‘Invoice’ |
Open Invoice Flag | Â pain_in_full_flag | IsOpen | "N" = 1 All other values = 0 |
Customer # | customer_id | CustomerNumber | Â |
Ship-To # | ship_to_id | CustomerSequence | Â |
Customer PO # | po_no | CustomerPO | Â |
Terms | terms_id | Terms | Â |
Ship Code | carrier_name | ShipCode | Â |
Salesperson | salesrep_id | Salesperson | Â |
Subtotal | Calculated | ProductTotal | total_amount - other_charge_amount - tax_amount |
Sales Tax | tax_amount | TaxAmount | Â |
Shipping | other_charge_amount | ShippingAndHandling | Â |
Invoice Total | total_amount | InvoiceTotal | Â |
Current Balance | calculated | CurrentBalance | total_amount - amount_paid |
Billing Information: Company/Name | bill2_name | BTCompanyName | Â |
Billing Information: Address | bill2_address[1..2] | BTAddress1..2 | Â |
Billing Information: City | bill2_city | BTCity | Â |
Billing Information: Country | bill2_country | BTCountry | Â |
Billing Information: State | bill2_state | BTState | Â |
Billing Information: Zip | bill2_postal-code | BTPostalCode | Â |
Ship-To Information: Company/Name | ship2_name | STCompanyName | Â |
Ship-To Information: Address | ship2_address[1..2] | STAddress1..2 | Â |
Ship-To Information: City | ship2_city | STCity | Â |
Ship-To Information: State | ship2_state | STState | Â |
Ship-To Information : Zip | ship2_postal_code | STPostalCode | Â |
Ship-To Information : Country | ship2_country | STCountry | Â |
| Field Mapping: Invoice History - Detail | |||
|---|---|---|---|
| Field Name | ERP Web Service Field (invoice_line) | Commerce Table.Field (InvoiceHistoryLine) | Notes |
| Invoice # | invoice_hdr.invoice_no | InvoiceHistoryId | concatenation of (oeeh.orderno) + "-" + (oeeh.ordersuf,"99") |
| Line Number | line_no | LineNumber | Â |
| Release Number | Â | ReleaseNumber | Static value = 0 |
| Item # | item_id | ProductERPNumber | Â |
| Item Description | item_desc | Description | Â |
| Unit of Measure | unit_of_measure | UnitOfMeasure | Â |
| Qty Invoiced | qty_shipped | QtyInvoiced | Â |
| Unit Price | unit_price | UnitPrice | Â |
| Extended Price | extended_price | LineTotal | Â |
Updated over 1 year ago