1. Administering Pricing
  2. Troubleshoot Importing Price Lists

Troubleshoot Importing Price Lists

Click the job for the scheduled process that you run when you use the Price List Import Template, open the attachments in the details section, then examine the log files.

Log File

Description

Txt files created for the Import Price List Header job, the Access Set, or the Import Price List Items job.

Describes the error.

Log files created for the Import a Price List job or the Import Price List job.

Describes the status of the child jobs.

Tips for Using Scheduled Processes

  • Make sure the status of the Load Interface file for the scheduled process is Succeeded and isn't in a Warning or Error state.

  • Make sure you correctly set the parameters when you run the Import Price List scheduled process.

  • Examine the server logs. If the scheduled process doesn't create the txt file for the job, then a problem might exist with the database or some unknown exception might have happened. Examine the server logs for the job that doesn't create a txt file.

  • Examine the interface tables. See the section later in this topic.

  • If you have to run more than one batch, then run them sequentially, one after the other. Don't run them at the same time. This will help to improve performance.
  • Run your scheduled processes during nonpeak hours. For example, if you typically don't do many business transactions between midnight and 8AM, then schedule them to run at 2AM.

Other Tips you Can Try

  • Make sure you include only price lists in PriceListsImportBatchTemplate.xlsm and only discount lists in DiscountListImportTemplate.xlsm.
  • Don't include discount lists PriceListsImportBatchTemplate.xlsm.
  • Don't include price lists in DiscountListImportTemplate.xlsm.
  • Keep your template files up to date. Oracle periodically modifies the templates. Download the latest file with each update.
  • Make sure you set up your pricing parameters, including the Default Price Periodicity UOM Class parameter. Pricing uses these parameters during your import to validate your import data. For details, see Manage Pricing Parameters.
  • Make sure you set up your administrators. For details, see Set Up Roles and Privileges for Pricing Administrators
  • Make sure the source Id is unique and meaningful. For example, make sure the SOURCE_PRICE_LIST_ID attribute for the Price List Item is unique in the context of the price list. This helps the import process know how to handle the attribute. For example, if an identifier attribute isn't part of an entity, such as a price list header, and if the identifier isn't unique, then the import can't create a relationship between it and the entity.
  • You can't use a computer that runs on the Macintosh operating system with file-based data import. You must use a computer that runs on the Windows operating system.
  • Make sure the value that you enter for the Batch Name is meaningful. For example, don't use a number. Instead, enter text that describes what you are uploading, such as Import Discount Lists from Vision Operations.

Dates

Make sure you use the correct format for each data type in your import payload. For example, you must use the yyyy/mm/dd hh:mm:ss format for most date attributes. The descriptions in the FBDI spreadsheet tells you the format you must use.

If you use the Date data type or the Timestamp data type in the Domain attribute of a pricing matrix's condition column, then you must represent that date as a string in the FBDI spreadsheet. Use this format in the spreadsheet:

'yyyy-mm-dd hh:mm:ss

where

  • The first character is an apostrophe. The apostrophe instructs FBDI to store the value as a string and prevents FBDI from using Excel's standard date format.
  • Include a dash between year and month, and between month and day.

For example:

'2024-05-24 18:45:00

Examine the Interface Tables

  1. Get administrative access so you can query the Oracle database.

  2. Query the interface tables, then examine the status.

    Status

    Description

    NEW

    Not processed.

    ERROR

    Processed but includes a data error.

    VALIDATED

    Processed but not imported because one or more children contain an error.

    IMPORTED

    Successfully imported.

    For details, see the Interface Tables That the Price List Import Template Uses section in this topic.

  3. Examine the IMPORT_STATUS_CODE column of the QP_PRICE_LISTS_INT table. This column describes the overall status of the price list.

    Status

    Description

    COMPLETED

    The scheduled process imported the price list and each child entity.

    PARTIAL

    The scheduled process imported only part of the price list.

Here's the hierarchy that Pricing uses. Use the status of each item in this hierarchy to help isolate where the error happens.

Price List Header 
  Item
    Component Item
      Charge
    Charge
      Tier
        Tier Header
          Tier Line
      Matrix
        Matrix Dimension
          Matrix Rules

For example, Item is a child of Price List Header, Component Item is a child of Item, and Charge is a child of Component Item.

Pricing processes each child entity only if the parent is valid. If the parent.

  • Doesn't fail validation. If a child errors, then the status of the parent is VALIDATED and the child status is ERROR, VALIDATED, or NEW.

  • Fails validation. The parent status is ERROR and the status for each child is NEW.

For example, if a charge error happens, then the hierarchy will contain these values.

Price List Header, IMPORTED
  Item, VALIDATED
    Component item
      Charge
    Charge
      Tier, NEW
        Tier Header
          Tier Line
      Matrix, NEW 
        Matrix Dimension
          Matrix Rules

For another example, if a tier header error happens, then the hierarchy will contain these values.

Price List Header, IMPORTED 
  Item, VALIDATED
    Component item
      Charge
    Charge, VALIDATED
      Tier
        Tier Header
          Tier Line, NEW
      Matrix, VALIDATED
        Matrix Dimension
          Matrix Rules

Related Topics