Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-13945

ASN import with blank PO# - Cannot insert duplicate key in object 'dbo.tbEntityItemCostAdjust' error

    Details

    • Type: Testing Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Invalid
    • Affects Version/s: CFA 2021R3
    • Fix Version/s: None
    • Component/s: Imports, Ordering
    • Labels:
      None
    • SCRUM Team:
      Brotherhood of Mutants
    • Root cause - Reason:
      Configuration
    • Sprint:
      2021.R4 New Features Sprint 1, 2021.R4 New Features Sprint 2

      Description

      ASN import with blank PO# - Cannot insert duplicate key in object 'dbo.tbEntityItemCostAdjust' error.

      I've noticed that ASN import for Sysco in CFA Staging creates the following error:

        • Error : 3/25/2021 1:16:54 PM : Shipping Confirmation Data Import on 3/25/2021 1:16:52 PM : MMS.Utilities.MxUniqueIndexException: Violation of PRIMARY KEY constraint 'PK_tbEntityItemCostAdjust'. Cannot insert duplicate key in object 'dbo.tbEntityItemCostAdjust'. The duplicate key value is (588, 16, Mar 25 2021 9:16AM).
          The statement has been terminated. ---> System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_tbEntityItemCostAdjust'. Cannot insert duplicate key in object 'dbo.tbEntityItemCostAdjust'. The duplicate key value is (588, 16, Mar 25 2021 9:16AM).
          The statement has been terminated.

      I would like to understand the root cause. ASN import file and the log are attached. Thank you, Stacy

        Attachments

          Activity

            People

            • Assignee:
              stacy.privalova Stacy Privalova
              Reporter:
              stacy.privalova Stacy Privalova
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.