Narvar Integration

Purpose: You can use the integration with Narvar in order to have Narvar generate shipment confirmation and delivery update emails to customers.

In this topic:

Narvar Process Overview

Purpose: When the Use Narvar Integration (M57) system control value is selected, Order Administration sends an order request message to Narvar when the shipment is processed by the BILL_ASYNC job. This message includes information about:

  • The sold-to customer and the shipping address.
  • Each item on the order, including items that have not yet been fully shipped or that were shipped previously.
  • The shipment(s) made, including the ship via and tracking number.
  • The warehouse that shipped the item(s).

For more information: See the Narvar Order Request Message in the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1) for details.

Messages from Narvar to the customer generated when? Narvar generates notification to the customer using the information provided in the order request message based on updates from the carrier; for example, the customer might receive an email indicating that the package is on its way, or has been delivered.

Other email generation settings do not apply: When Narvar integration is in use:

You need to use your account with Narvar to complete configuration, as well as completing the Narvar Integration Setup within Order Administration.

Other email notifications: Only shipment confirmation emails are generated through the Narvar integration. Other email notifications, including return confirmations, follow the standard processes described in the Outbound Email API.

For more information, see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Things to note:

  • Items included in the Narvar order message:
    • Items that are on the order but still open (that is, not yet shipped, sold out, or canceled), are included in the message with a fulfillment_status of NOT_SHIPPED.

    • Items that have been sold out are included with a fulfillment_status of CANCELED.

    • Items that have been canceled are included with a fulfillment_status of CANCELED, regardless of whether the cancel reason used was flagged to reduce demand.

    • Physical stored value cards: If Use Streamlined Stored Value Card Billing (I23) is selected, then the Narvar order message is generated when you use Working with Physical Stored Value Card Assignment (WPSA); however, no carrier, carrier service, or tracking number is included in the message. However, if Use Streamlined Stored Value Card Billing (I23) is not selected and you confirm physical stored value cards as you do other shipments, then the carrier, carrier service, and tracking information is included.

  • Items not included:
    • Main set items.

    • Non-inventory items, including virtual stored value cards.

    • Items added with a negative quantity to process a return.

    • Membership items.

    • Subscription items.

    • Express-billed items.

If the only items on the order fall into one of these categories, then no order message is sent to Narvar.

Drop ship items: When you confirm a drop ship purchase order, either within Order Administration or through integration with Order Orchestration, then order shipment detail records are not created, and as a result, the carrier, ship method, carrier service, and tracking number are not passed; however, order shipment detail records are created when you confirm a drop ship pick slip.

  • If Email notification not selected: The order type must have Email notification selected for the customer to receive the email notification; otherwise, message is generated to the Narvar Non-Deliverable Email Address for Shipment Confirmations (M59). However, in this case, the order transaction history message still indicates Order sent to Narvar.
  • Order Orchestration integration:
    • Eligible to be sent to Narvar: The following types of orders are eligible to be sent to Narvar:

      • Brokered backorders that originated in Order Administration, submitted to Order Orchestration as a brokered backorder and fulfilled by a location in another system; also, if the order is assigned back to Order Administration as a fulfilling order, the fulfilling order is sent to Narvar.

      • Delivery orders that originated in another system and were assigned to Order Administration for fulfillment (that is, not fulfilling orders).

      • Retail pickup orders that are not fulfilling orders: Retail pickup orders that are not fulfilling orders for orders originating in Order Administration. These are orders that originated in another system, and that Order Orchestration sent to Order Administration for fulfillment.

      • Ship for pickup orders that originated in Order Administration; also, if the order is assigned back to Order Administration as a fulfilling order, the fulfilling order is sent to Narvar.

    • Not eligible to be sent to Narvar: Store pickup orders are not sent to Narvar.

The generation of order request messages to Narvar is not affected by the setting of the Consolidated Invoice (B49) system control value.

Important:

In Order Management System 21.0 or higher, or Order Administration, you cannot select the Consolidated Invoice system control value if it is not already selected. If the system control value is currently selected (set to Y) and you deselect it (change it to N or blank), you cannot then change it back to selected. The option to consolidate invoices will be removed at a later date.

Email repository: Order request messages are not tracked in the Email Repository.

Narvar Integration Setup

The setup in Order Administration related to the Narvar integration is described below.

Contact Narvar for information on creating and configuring an account.

Other Setup

Ship via configuration: Complete the following fields to configure mapping a ship via name and service type for Narvar:

The list of valid names and service codes are provided by Narvar.

You must complete the Narvar Carrier Name in order for the tracking number links to work correctly at the Display Package Information Screen, in Streamlined Order Inquiry (DORI), and at the Order Summary page in Contact Center.

Web service authentication: Use the Work with Outbound Web Service Authentication Screen to review or work with web service authentication with Narvar.

Note:

Narvar currently supports only Basic authentication.

Order type setting: The order type’s the Email notification flag must be selected for the order request to Narvar to be generated. Also, the Shipment Confirmation must be selected at the Order Type Email Selection Screen for the order type, or the Narvar Non-Deliverable Email Address for Shipment Confirmations (M59) is included rather than the customer’s actual email address.

Narvar Troubleshooting

Trouble with tracking number links:

Valid tracking number required: If there is no tracking number sent to Narvar, or the tracking number is invalid, then the customer will not receive shipment update notifications from Narvar.

Note:

No order shipment detail records are created, and as a result, the carrier, ship method, carrier service, and tracking number are not passed if:
  • You bill by batch.
  • You do not enter a tracking number,
  • You use the Working with Physical Stored Value Card Assignment (WPSA) option for a physical stored value card.
  • You confirm a drop ship purchase order, either within Order Administration or through integration with Order Orchestration; however, order shipment detail records are created when you confirm a drop ship pick slip.

Note:

The tracking number specified for a shipment must be unique. Do not attempt to send the same tracking number for multiple shipments on the order.

Tracking number URL: The tracking number URL is stored in the ORDER_SHIPMENT_DETAILS table, composed of the Narvar Track URL Prefix (M60) and the tracking number identified at shipment.

The tracking number consists of https://BASE.URL.com/CARRIER?tracking_numbers=1234&order_number=001-12345-001, where:

  • https://BASE.URL.com/ is the Narvar Track URL Prefix (M60).
  • CARRIER is the Narvar carrier name specified for the ship via.
  • 1234 is the tracking number.
  • 001 is the company number.
  • 12345 is the order number.
  • 001 is the ship-to number.

Required for tracking: The Narvar Track URL Prefix (M60) is required for a valid tracking number link to be enabled in emails or on screens. If you are using the Narvar integration and submit an order request to Narvar while the tracking URL prefix is not defined, the Narvar.log file contains errors such as:

Shipment tracking is disable for company 123

Unable to construct shipment tracking URL for order 456

Where 123 is the company number and 456 is the order number.

Error displayed: Also, if the tracking URL is not defined, when you click on the tracking number link at the screens mentioned above, an error window indicates: Tracking information not available. Check Narvar Order Error Export screen for failures.

However, a Narvar Order Error Export record is not created because the tracking number link could not be created correctly if there are no other issues with the order request to Narvar.

Working with Narvar Errors: Use the Narvar Order Export Errors page in Modern View to review and work with the errors listed below. The NOEE menu option controls authority to this page.

These errors are stored in the INT_NARVAR_EXPORT_ERROR table.

Country codes: Narvar supports a two-position country code; however, the order request message does not fail if a three-position country code is passed.

Extra message? An extra order request message might be sent to Narvar if, for example, the order has shipped, and then an additional express-billed item is added. The express-billed item is not included in the order request message, so the additional message is identical to the previous message and does not affect updates generated by Narvar.

Narvar Error Summary

Issue Narvar.log Entry Order Transaction History Message Response Type Error at Narvar Order Export Errors Page

Narvar Outbound Service URL (M58) is blank

Shipment Tracking URL or credentials cannot be found

Failure sending order to Narvar

0

oms.app.exception

Application Failure

The order message is not generated because the Narvar Non-Deliverable Email Address for Shipment Confirmations (M59) is blank, and the order is not eligible to have the email actually sent to the customer (see that system control value for more information)

Missing Narvar Non-Deliverable Email Address

Failure sending order to Narvar

0

oms.app.exception

Application Failure: Missing Narvar Non-Deliverable Email Address

The user ID and password specified for Narvar Service are not valid. See Work with Outbound Web Service Authentication Screen for more information.

Bad Credentials, Please provide valid acck and auth token.

Failure sending order to Narvar

401

unauthorized.action

Bad Credentials, Please provide valid acck and auth token.

Narvar Outbound Service URL (M58) is invalid

Shipment tracking order response code 405 and message {"status":"ERROR","messages":[{"level":"ERROR","code":"method.not_allowed","message":"Request method POST not supported"}]}

Failure sending order to Narvar

405

method.not.allowed

Request method POST not supported

The shipment date specified was not formatted correctly.

message.invalid. order.shipments. date

Invalid ship date. Please enter UTC format ’yyyy-MM-dd’T’HH:mm"SSS.zzz’ for ship date

Failure sending order to Narvar

422

message.invalid.order. shipments.date

Invalid ship date. Please enter UTC format ’yyyy-MM-dd’T’HH:mm"SSS.zzz’ for ship date

Configuration issues: Check your Narvar Integration Setup if you see the following error codes:

  • 400: BAD REQUEST
  • 403: FORBIDDEN
  • 404: NOT FOUND

Other errors: Contact your Oracle representative or Narvar for information on the following error codes:

  • 304: NOT MODIFIED
  • 409: ITEM ALREADY EXISTS
  • 500: INTERNAL SERVER ERROR
  • 502: INTERNAL SERVER ERROR
  • 503: SERVICE UNAVAILABLE or INTERNAL ERROR